Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15

2023-03-24 Thread Carsten Bormann
On 24. Mar 2023, at 22:29, Jürgen Schönwälder wrote: > > using '"(%.+)"' in the IP address types may be the most liberal answer Pedantically speaking, no. /./ does not include all of ASCII, which is not liberal enough if you want to preserve the newlines in your interface names that are

Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15

2023-03-24 Thread Jürgen Schönwälder
On Sat, Mar 25, 2023 at 08:31:28AM +1300, Brian E Carpenter wrote: > On 25-Mar-23 02:29, Jürgen Schönwälder wrote: > > Rob, > > > > using '"(%.+)"' in the IP address types may be the most liberal answer > > and in line with the interface YANG module. Applications using > >

[netmod] NETMOD Agenda Updated

2023-03-24 Thread Kent Watsen
The NETMOD agenda has been updated: https://datatracker.ietf.org/meeting/116/session/netmod And produced in full below for convenience. Kent (and Jason for putting it together!) # Agenda/Materials for the NETMOD 116 WG Session

Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15

2023-03-24 Thread Brian E Carpenter
On 25-Mar-23 02:29, Jürgen Schönwälder wrote: Rob, using '"(%.+)"' in the IP address types may be the most liberal answer and in line with the interface YANG module. Applications using draft-ietf-6man-rfc6874bis will have to resort to %-encodings to deal with forward slashes and the like, which

Re: [netmod] Changes to IPv6 zone definition in draft-ietf-netmod-rfc6991-bis-15

2023-03-24 Thread Jürgen Schönwälder
Rob, using '"(%.+)"' in the IP address types may be the most liberal answer and in line with the interface YANG module. Applications using draft-ietf-6man-rfc6874bis will have to resort to %-encodings to deal with forward slashes and the like, which likely is OK in the web context. I do not