Ira,
Lovely, so they continue down the road of breaking URI validation based on STD 66...
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...
I guess I need to re-subscribe to the 6man list so I can provide feedback... :/
> On Mar 20, 2022, at 4:02 PM, ISTO-PWG Internet Printing Protocol workgroup discussion forum via ipp <ipp at pwg.org> wrote:
>> FYI - potential new breakage in IPv6 literals in URIs - probably impacts printers.
>> ---------- Forwarded message ---------
> From: Brian E Carpenter <brian.e.carpenter at gmail.com>
> Date: Sun, Mar 20, 2022 at 3:36 PM
> Subject: [dispatch] Fwd: I-D Action: draft-ietf-6man-rfc6874bis-00.txt
> To: <dispatch at ietf.org>
>>> FYI, 6MAN has now adopted this draft. There's also a simplification of the
> security considerations, following a perceptive comment by Ted Hardie.
>> As a reminder, we are not asking for action by DISPATCH, but of course
> we'd welcome feedback.
>> Regards
> Brian Carpenter
>>> -------- Forwarded Message --------
> Subject: I-D Action: draft-ietf-6man-rfc6874bis-00.txt
> Date: Sun, 20 Mar 2022 04:17:34 -0700
> From: internet-drafts at ietf.org> Reply-To: internet-drafts at ietf.org, ipv6 at ietf.org> To: i-d-announce at ietf.org> CC: ipv6 at ietf.org>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance WG of the IETF.
>> Title : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
> Authors : Brian Carpenter
> Stuart Cheshire
> Robert M. Hinden
> Filename : draft-ietf-6man-rfc6874bis-00.txt
> Pages : 11
> Date : 2022-03-19
>> 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-ietf-6man-rfc6874bis/>> There is also an HTML version available at:
>https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html>>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>> _______________________________________________
> I-D-Announce mailing list
>I-D-Announce at ietf.org>https://www.ietf.org/mailman/listinfo/i-d-announce> Internet-Draft directories: http://www.ietf.org/shadow.html> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt>> _______________________________________________
> dispatch mailing list
>dispatch at ietf.org>https://www.ietf.org/mailman/listinfo/dispatch> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
________________________
Michael Sweet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.pwg.org/pipermail/ipp/attachments/20220320/899012a3/attachment.sig>