On Mon, Nov 07, 2022 at 03:24:39PM +0000, Reshad Rahman wrote:
> Hi,
> Looking at the regex patterns for ipv6-address, specifically [\p{N}\p{L}], it
> allows only letters and numerical characters. So e.g '-' and '/' etc are not
> allowed even though they are commonly used in interface names. Is this an
> oversight?
The definition surely is not desirable, whether it is an oversight or
a bug is hard to tell.
The root of the problem is that there is no clear definition what
makes a valid zone name. Its a somewhat complicated story, not only
affecting management interfaces but also user facing URIs. I wrote my
understanding of the situation up as a blog post:
<https://www.beadg.de/js/post/interface-zone-names/>
Assuming that draft-ietf-6man-rfc6874bis-05 will get approved by the
IESG, one could move to unreserved ASCII characters (RFC 3986) plus
the forward slash for the zone name.
/js
--
Jürgen Schönwälder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
