Jürgen,
Thanks for the careful reading. You are correct. I think implementers have
always assumed ASCII, but it isn't stated.
(RFC 6874 specified ASCII.)
Will fix.
Regards
Brian Carpenter
On 05-Jan-25 02:03, Jürgen Schönwälder wrote:
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
--
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx
