[Last-Call] Re: Last Call: <draft-ietf-6man-zone-ui-05.txt> (Entering IPv6 Zone Identifiers in User Interfaces) to Proposed Standard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Dec 30, 2024 at 10:07:59AM -0800, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document: - 'Entering IPv6 Zone Identifiers in User
> Interfaces'
>   <draft-ietf-6man-zone-ui-05.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@xxxxxxxx mailing lists by 2025-01-13. Exceptionally, comments may
> be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>

Section 3 says:

   The zone identifiers that can be used are limited by the
   host operating system, since [RFC4007] only specifies that they are
   coded in ASCII, without specifying a maximum length.

Section	6 says:

   RFC 4007 does not specify the character set allowed in a zone
   identifier.

So either RFC 4007 says the zone identifier is ASCII or it does not.
My reading of RFC 4007 is that it is silent about the character set,
but perhaps I missed the spot where it says otherwise.

/js

-- 
Jürgen Schönwälder              Constructor University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany

-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux