attachment
<div dir="ltr"><div>Hi Mike,</div><div><br></div><div>I've been watching this one for awhile as an independent submission from</div><div>Brian Carpenter et al. But now they've gotten 6man WG adoption, so it</div><div>would be worthwhile pointing out that they're going further in the direction</div><div>of breaking STD66...</div><div><br></div><div>Of course the joint IETF/W3C URI review list should eventually complain,</div><div>but as long as a few browsers have work-around-hacks, they don't seem</div><div>to make much headway at unwise breakage of general URI parsers.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><i><font size="1">Ira McDonald (Musician / Software Architect)</font></i></div><div><i><font size="1">Chair - SAE Trust Anchors and Authentication TF<br></font></i></div><div dir="ltr"><i><font size="1">Co-Chair - TCG Trusted Mobility Solutions WG</font></i></div><div><i><font size="1">Co-Chair - TCG Metadata Access Protocol SG<br></font></i></div><div dir="ltr"><i><font size="1">Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434</font></i></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 20, 2022 at 4:38 PM Michael Sweet <<a href="mailto:msweet@msweet.org">msweet@msweet.org</a>> 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">Ira,<br>
<br>
Lovely, so they continue down the road of breaking URI validation based on STD 66...<br>
<br>
And if the zone identifier is a simple number (Windows) or the first two characters of the interface name are valid hex digits (possible on all Unix's) then you have the issue of ambiguous decoding of the URI as well...<br>
<br>
I guess I need to re-subscribe to the 6man list so I can provide feedback... :/<br>
<br>
<br>
> On Mar 20, 2022, at 4:02 PM, ISTO-PWG Internet Printing Protocol workgroup discussion forum via ipp <<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a>> wrote:<br>
> <br>
> FYI - potential new breakage in IPv6 literals in URIs - probably impacts printers.<br>
> <br>
> ---------- Forwarded message ---------<br>
> From: Brian E Carpenter <<a href="mailto:brian.e.carpenter@gmail.com" target="_blank">brian.e.carpenter@gmail.com</a>><br>
> Date: Sun, Mar 20, 2022 at 3:36 PM<br>
> Subject: [dispatch] Fwd: I-D Action: draft-ietf-6man-rfc6874bis-00.txt<br>
> To: <<a href="mailto:dispatch@ietf.org" target="_blank">dispatch@ietf.org</a>><br>
> <br>
> <br>
> FYI, 6MAN has now adopted this draft. There's also a simplification of the<br>
> security considerations, following a perceptive comment by Ted Hardie.<br>
> <br>
> As a reminder, we are not asking for action by DISPATCH, but of course<br>
> we'd welcome feedback.<br>
> <br>
> Regards<br>
> Brian Carpenter<br>
> <br>
> <br>
> -------- Forwarded Message --------<br>
> Subject: I-D Action: draft-ietf-6man-rfc6874bis-00.txt<br>
> Date: Sun, 20 Mar 2022 04:17:34 -0700<br>
> From: <a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a><br>
> Reply-To: <a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a>, <a href="mailto:ipv6@ietf.org" target="_blank">ipv6@ietf.org</a><br>
> To: <a href="mailto:i-d-announce@ietf.org" target="_blank">i-d-announce@ietf.org</a><br>
> CC: <a href="mailto:ipv6@ietf.org" target="_blank">ipv6@ietf.org</a><br>
> <br>
> <br>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.<br>
> This draft is a work item of the IPv6 Maintenance WG of the IETF.<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-ietf-6man-rfc6874bis-00.txt<br>
> Pages : 11<br>
> Date : 2022-03-19<br>
> <br>
> Abstract:<br>
> This document describes how the zone identifier of an IPv6 scoped<br>
> address, defined as <zone_id> 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-ietf-6man-rfc6874bis/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6874bis/</a><br>
> <br>
> There is also an HTML version available at:<br>
> <a href="https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html" rel="noreferrer" target="_blank">https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html</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">I-D-Announce@ietf.org</a><br>
> <a href="https://www.ietf.org/mailman/listinfo/i-d-announce" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/i-d-announce</a><br>
> Internet-Draft directories: <a href="http://www.ietf.org/shadow.html" rel="noreferrer" target="_blank">http://www.ietf.org/shadow.html</a><br>
> or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel="noreferrer" target="_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
> <br>
> _______________________________________________<br>
> dispatch mailing list<br>
> <a href="mailto:dispatch@ietf.org" target="_blank">dispatch@ietf.org</a><br>
> <a href="https://www.ietf.org/mailman/listinfo/dispatch" rel="noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/dispatch</a><br>
> _______________________________________________<br>
> ipp mailing list<br>
> <a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
> <a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
<br>
________________________<br>
Michael Sweet<br>
<br>
<br>
<br>
</blockquote></div>