[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipng
Subject:    Re: I-D Action: draft-carpenter-6man-rfc6874bis-03.txt
From:       Brian Carpenter <brian.e.carpenter () gmail ! com>
Date:       2022-02-09 9:21:45
Message-ID: CANMZLAZinunaxMBr8RJYyoYLjK1j37dhS1h2Rthw9n-Gr9A2-g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi Ted,

That makes sense. Maybe we should wait a few days for reactions from 6man.

Regards,
    Brian Carpenter
    (via tiny screen & keyboard)

On Wed, 9 Feb 2022, 21:19 Ted Hardie, <ted.ietf@gmail.com> wrote:

> Hi Brian,
>
> Given the substantive change and the additional update to the IRI syntax,
> may I suggest you bring the updated draft to DISPATCH, so that the folks
> more on the URI side of the house are aware of the changes?  There also
> might be a dispatch action to carry additional discussion to one of the
> more ART-centric groups.
>
> regards,
>
> Ted Hardie
>
> On Tue, Feb 8, 2022 at 8:30 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>> Hi,
>>
>> The authors of this draft did, as previously mentioned, open discussion
>> with various people in the browser community, but we did not find much
>> enthusiasm for implementation. Until there is a great increase in demand
>> for link-locals to be supported by browsers, the necessary work seems
>> unlikely to be done.
>>
>> However, we believe that this demand will eventually arise and therefore
>> it's important that the relevant URI syntax is well-defined. Therefore,
>> we've updated the draft. Apart from editorial improvements, there is a
>> significant change in this version. Following the discussions a few months
>> ago, and after I spent some time looking into the URI parsers in wget and
>> Firefox (and a brief look at curl), we propose to drop the "%25" encoding
>> of "%". The ABNF in this version, originally suggested by Andrew Cady,
>> reflects that proposal. There is extra explanation in the text.
>>
>> The other signficant change is that, as Martin Dürst pointed out, we
>> also
>> need to formally update the IRI syntax. That was an omission in RFC6874.
>>
>> It may be time to consider WG adoption of this draft.
>>
>> Regards
>>      Brian & co-authors
>>
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-carpenter-6man-rfc6874bis-03.txt
>> Date: Tue, 08 Feb 2022 12:06:42 -0800
>> From: internet-drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>          Title           : Representing IPv6 Zone Identifiers in Address
>> Literals and Uniform Resource Identifiers
>>          Authors         : Brian Carpenter
>>                            Stuart Cheshire
>>                            Robert M. Hinden
>>         Filename        : draft-carpenter-6man-rfc6874bis-03.txt
>>         Pages           : 11
>>         Date            : 2022-02-08
>>
>> Abstract:
>>     This document describes how the zone identifier of an IPv6 scoped
>>     address, defined as <zone_id> in the IPv6 Scoped Address Architecture
>>     (RFC 4007), can be represented in a literal IPv6 address and in a
>>     Uniform Resource Identifier that includes such a literal address.  It
>>     updates the URI Generic Syntax and Internationalized Resource
>>     Identifier specifications (RFC 3986, RFC 3987) accordingly, and
>>     obsoletes RFC 6874.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-carpenter-6man-rfc6874bis/
>>
>> There is also an HTML version available at:
>> https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-03.html
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-carpenter-6man-rfc6874bis-03
>>
>>
>> Internet-Drafts are also available by rsync at rsync.ietf.org:
>> :internet-drafts
>>
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft
>> <https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>
>> directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>

[Attachment #5 (text/html)]

<div dir="auto">Hi Ted,<div dir="auto"><br></div><div dir="auto">That makes sense. \
Maybe we should wait a few days for reactions from 6man.<br><br><div \
data-smartmail="gmail_signature" dir="auto">Regards,<br>       Brian Carpenter<br>    \
(via tiny screen &amp; keyboard)</div></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Wed, 9 Feb 2022, 21:19 Ted Hardie, &lt;<a \
href="mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
class="gmail_default" style="font-size:large">Hi Brian,</div><div \
class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" \
style="font-size:large">Given the substantive change and the additional update to the \
IRI syntax, may I suggest you bring the updated draft to DISPATCH, so that the folks \
more on the URI side of the house are aware of the changes?   There also might be a \
dispatch action to carry additional discussion to one of the more ART-centric \
groups.</div><div class="gmail_default" style="font-size:large"><br></div><div \
class="gmail_default" style="font-size:large">regards,</div><div \
class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" \
style="font-size:large">Ted Hardie<br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Tue, Feb 8, 2022 at 8:30 PM Brian E Carpenter &lt;<a \
href="mailto:brian.e.carpenter@gmail.com" target="_blank" \
rel="noreferrer">brian.e.carpenter@gmail.com</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
The authors of this draft did, as previously mentioned, open discussion<br>
with various people in the browser community, but we did not find much<br>
enthusiasm for implementation. Until there is a great increase in demand<br>
for link-locals to be supported by browsers, the necessary work seems<br>
unlikely to be done.<br>
<br>
However, we believe that this demand will eventually arise and therefore<br>
it&#39;s important that the relevant URI syntax is well-defined. Therefore,<br>
we&#39;ve updated the draft. Apart from editorial improvements, there is a<br>
significant change in this version. Following the discussions a few months<br>
ago, and after I spent some time looking into the URI parsers in wget and<br>
Firefox (and a brief look at curl), we propose to drop the &quot;%25&quot; \
encoding<br> of &quot;%&quot;. The ABNF in this version, originally suggested by \
Andrew Cady,<br> reflects that proposal. There is extra explanation in the text.<br>
<br>
The other signficant change is that, as Martin Dürst pointed out, we <br>
also<br>
need to formally update the IRI syntax. That was an omission in RFC6874.<br>
<br>
It may be time to consider WG adoption of this draft.<br>
<br>
Regards<br>
        Brian &amp; co-authors<br>
<br>
<br>
-------- Forwarded Message --------<br>
Subject: I-D Action: draft-carpenter-6man-rfc6874bis-03.txt<br>
Date: Tue, 08 Feb 2022 12:06:42 -0800<br>
From: <a href="mailto:internet-drafts@ietf.org" target="_blank" \
                rel="noreferrer">internet-drafts@ietf.org</a><br>
Reply-To: <a href="mailto:internet-drafts@ietf.org" target="_blank" \
                rel="noreferrer">internet-drafts@ietf.org</a><br>
To: <a href="mailto:i-d-announce@ietf.org" target="_blank" \
rel="noreferrer">i-d-announce@ietf.org</a><br> <br>
<br>
A New Internet-Draft is available from the on-line Internet-Drafts directories.<br>
<br>
<br>
              Title                 : Representing IPv6 Zone Identifiers in Address \
Literals and Uniform Resource Identifiers<br>  Authors              : Brian \
Carpenter<br>  Stuart Cheshire<br>
                                         Robert M. Hinden<br>
            Filename            : draft-carpenter-6man-rfc6874bis-03.txt<br>
            Pages                 : 11<br>
            Date                  : 2022-02-08<br>
<br>
Abstract:<br>
      This document describes how the zone identifier of an IPv6 scoped<br>
      address, defined as &lt;zone_id&gt; in the IPv6 Scoped Address Architecture<br>
      (RFC 4007), can be represented in a literal IPv6 address and in a<br>
      Uniform Resource Identifier that includes such a literal address.   It<br>
      updates the URI Generic Syntax and Internationalized Resource<br>
      Identifier specifications (RFC 3986, RFC 3987) accordingly, and<br>
      obsoletes RFC 6874.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href="https://datatracker.ietf.org/doc/draft-carpenter-6man-rfc6874bis/" \
rel="noreferrer noreferrer" \
target="_blank">https://datatracker.ietf.org/doc/draft-carpenter-6man-rfc6874bis/</a><br>
 <br>
There is also an HTML version available at:<br>
<a href="https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-03.html" \
rel="noreferrer noreferrer" \
target="_blank">https://www.ietf.org/archive/id/draft-carpenter-6man-rfc6874bis-03.html</a><br>
 <br>
A diff from the previous version is available at:<br>
<a href="https://www.ietf.org/rfcdiff?url2=draft-carpenter-6man-rfc6874bis-03" \
rel="noreferrer noreferrer" \
target="_blank">https://www.ietf.org/rfcdiff?url2=draft-carpenter-6man-rfc6874bis-03</a><br>
 <br>
<br>
Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts<br>
<br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href="mailto:I-D-Announce@ietf.org" target="_blank" \
rel="noreferrer">I-D-Announce@ietf.org</a><br> <a \
href="https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft" \
rel="noreferrer noreferrer" \
target="_blank">https://www.ietf.org/mailman/listinfo/i-d-announce<br> \
Internet-Draft</a> directories: <a href="http://www.ietf.org/shadow.html" \
rel="noreferrer noreferrer" target="_blank">http://www.ietf.org/shadow.html</a><br> \
or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel="noreferrer noreferrer" \
target="_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br> <br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href="mailto:ipv6@ietf.org" target="_blank" rel="noreferrer">ipv6@ietf.org</a><br>
Administrative Requests: <a href="https://www.ietf.org/mailman/listinfo/ipv6" \
rel="noreferrer noreferrer" \
                target="_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</blockquote></div>
</blockquote></div>



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic