attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I seem to recall that Mike had some views or opinions in this area, that differed from what the RFCs were specifying. Mike, what is your impression of this IETF proposal?<div class=""><br class=""><div class="">
Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Mar 20, 2022, at 4:02 PM, ISTO-PWG Internet Printing Protocol workgroup discussion forum via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div dir="ltr" class=""><font size="2" class="">FYI - potential new breakage in IPv6 literals in URIs - probably impacts printers.</font><br class=""><div class=""><div class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br class="">From: <b class="gmail_sendername" dir="auto">Brian E Carpenter</b> <span dir="auto" class=""><<a href="mailto:brian.e.carpenter@gmail.com" class="">brian.e.carpenter@gmail.com</a>></span><br class="">Date: Sun, Mar 20, 2022 at 3:36 PM<br class="">Subject: [dispatch] Fwd: I-D Action: draft-ietf-6man-rfc6874bis-00.txt<br class="">To: <<a href="mailto:dispatch@ietf.org" class="">dispatch@ietf.org</a>><br class=""></div><br class=""><br class="">FYI, 6MAN has now adopted this draft. There's also a simplification of the<br class="">
security considerations, following a perceptive comment by Ted Hardie.<br class="">
<br class="">
As a reminder, we are not asking for action by DISPATCH, but of course<br class="">
we'd welcome feedback.<br class="">
<br class="">
Regards<br class="">
Brian Carpenter<br class="">
<br class="">
<br class="">
-------- Forwarded Message --------<br class="">
Subject: I-D Action: draft-ietf-6man-rfc6874bis-00.txt<br class="">
Date: Sun, 20 Mar 2022 04:17:34 -0700<br class="">
From: <a href="mailto:internet-drafts@ietf.org" target="_blank" class="">internet-drafts@ietf.org</a><br class="">
Reply-To: <a href="mailto:internet-drafts@ietf.org" target="_blank" class="">internet-drafts@ietf.org</a>, <a href="mailto:ipv6@ietf.org" target="_blank" class="">ipv6@ietf.org</a><br class="">
To: <a href="mailto:i-d-announce@ietf.org" target="_blank" class="">i-d-announce@ietf.org</a><br class="">
CC: <a href="mailto:ipv6@ietf.org" target="_blank" class="">ipv6@ietf.org</a><br class="">
<br class="">
<br class="">
A New Internet-Draft is available from the on-line Internet-Drafts directories.<br class="">
This draft is a work item of the IPv6 Maintenance WG of the IETF.<br class="">
<br class="">
Title : Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers<br class="">
Authors : Brian Carpenter<br class="">
Stuart Cheshire<br class="">
Robert M. Hinden<br class="">
Filename : draft-ietf-6man-rfc6874bis-00.txt<br class="">
Pages : 11<br class="">
Date : 2022-03-19<br class="">
<br class="">
Abstract:<br class="">
This document describes how the zone identifier of an IPv6 scoped<br class="">
address, defined as <zone_id> in the IPv6 Scoped Address Architecture<br class="">
(RFC 4007), can be represented in a literal IPv6 address and in a<br class="">
Uniform Resource Identifier that includes such a literal address. It<br class="">
updates the URI Generic Syntax and Internationalized Resource<br class="">
Identifier specifications (RFC 3986, RFC 3987) accordingly, and<br class="">
obsoletes RFC 6874.<br class="">
<br class="">
<br class="">
The IETF datatracker status page for this draft is:<br class="">
<a href="https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6874bis/" rel="noreferrer" target="_blank" class="">https://datatracker.ietf.org/doc/draft-ietf-6man-rfc6874bis/</a><br class="">
<br class="">
There is also an HTML version available at:<br class="">
<a href="https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html" rel="noreferrer" target="_blank" class="">https://www.ietf.org/archive/id/draft-ietf-6man-rfc6874bis-00.html</a><br class="">
<br class="">
<br class="">
Internet-Drafts are also available by rsync at <a href="http://rsync.ietf.org" class="">rsync.ietf.org</a>::internet-drafts<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
I-D-Announce mailing list<br class="">
<a href="mailto:I-D-Announce@ietf.org" target="_blank" class="">I-D-Announce@ietf.org</a><br class="">
<a href="https://www.ietf.org/mailman/listinfo/i-d-announce" rel="noreferrer" target="_blank" class="">https://www.ietf.org/mailman/listinfo/i-d-announce</a><br class="">
Internet-Draft directories: <a href="http://www.ietf.org/shadow.html" rel="noreferrer" target="_blank" class="">http://www.ietf.org/shadow.html</a><br class="">
or <a href="ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel="noreferrer" target="_blank" class="">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br class="">
<br class="">
_______________________________________________<br class="">
dispatch mailing list<br class="">
<a href="mailto:dispatch@ietf.org" target="_blank" class="">dispatch@ietf.org</a><br class="">
<a href="https://www.ietf.org/mailman/listinfo/dispatch" rel="noreferrer" target="_blank" class="">https://www.ietf.org/mailman/listinfo/dispatch</a><br class="">
</div></div></div></div>
_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class=""><a href="https://www.pwg.org/mailman/listinfo/ipp">https://www.pwg.org/mailman/listinfo/ipp</a><br class=""></div></blockquote></div><br class=""></div></body></html>