Re: [netmod] 6991bis: address-with-prefix-length

Yes, correct, my misremembering (I'm working also with JSONSchema which doesn't have that).

> -----Original Message-----
> From: Martin Bjorklund [mailto:mbj@tail-f.com]
> Sent: Monday, April 1, 2019 2:04 PM
> To: Michael Rehder <Michael.Rehder@Amdocs.com>
> Cc: netmod@ietf.org
> Subject: Re: [netmod] 6991bis: address-with-prefix-length
> 
> Hi,
> 
> Michael Rehder <Michael.Rehder@Amdocs.com> wrote:
> 
> [...]
> 
> > Note also that the ietf pattern regexp are not anchored so "
> > junk192.168.1.1"
> > and
> > "    192.168.1.1   "
> > Are accepted.
> 
> No, this is not correct.  YANG uses the XSD "dialect" of regular expressions.  In
> this dialect, all patterns are implicitly anchored.
> 
> 
> /martin
> 
> > I don't know why they are unanchored. This makes them unusable in my
> > view.
> >
> > As a result I've written my own regxp and a somewhat elaborate MUST
> > clause for canonical format check but a specific type would be better.
> > Another perspective is to ensure there is some way to avoid using MUST
> > to simply constrain type.
> > Has that ever been discussed?
> >
> > Thanks
> > Mike
> >
> > > -----Original Message-----
> > > --------------------------------------------------------------------
> > > --
> > >
> > > Message: 1
> > > Date: Mon, 1 Apr 2019 16:38:34 +0200
> > > From: Kristian Larsson <kristian@spritelink.net>
> > > To: netmod@ietf.org
> > > Subject: [netmod] 6991bis: address-with-prefix-length
> > > Message-ID: <10d3413c-df96-6e7d-df82-5542bb02348d@spritelink.net>
> > > Content-Type: text/plain; charset=utf-8; format=flowed
> > >
> > > Hello,
> > >
> > > seeing that 6991 is up for a refresh I wonder if this would be the
> > > time to suggest the addition of a type for
> > > address-and-prefix-length, for example like 192.0.2.1/24?
> > >
> > > I find that it's the most natural way express the address and
> > > prefix-length to configure on an interface or for some other use. We
> > > currently have an ip-prefix type which allows CIDR style prefixes
> > > but since all bits to the right of the mask is to be 0 it is only
> > > possible to use for describing the IP prefix / network address
> > > itself - not the address of a host in that network.
> > >
> > > I actually wish the interface-ip modules would have used a combined
> > > leaf for these settings rather than the dual-leaf approach it
> > > currently has, but I suppose that ship has sailed :/
> > >
> > > Regardless, can we add such a type? Is this the document and time to
> > > do it? :)
> > >
> > > Kind regard,
> > >     Kristian.
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 2
> > > Date: Mon, 1 Apr 2019 18:13:21 +0200
> > > From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
> > > To: Kristian Larsson <kristian@spritelink.net>
> > > Cc: <netmod@ietf.org>
> > > Subject: Re: [netmod] 6991bis: address-with-prefix-length
> > > Message-ID:
> > > 	<20190401161321.seiodlfsmjjvjcp5@anna.jacobs.jacobs-university.de>
> > > Content-Type: text/plain; charset="us-ascii"
> > >
> > > This is the right time for this and I would call these
> > > ip-address-prefix, ipv4- address-prefix and ipv6-address prefix.
> > >
> > > /js
> > >
> > > On Mon, Apr 01, 2019 at 04:38:34PM +0200, Kristian Larsson wrote:
> > > > Hello,
> > > >
> > > > seeing that 6991 is up for a refresh I wonder if this would be the
> > > > time to suggest the addition of a type for
> > > > address-and-prefix-length, for example like 192.0.2.1/24?
> > > >
> > > > I find that it's the most natural way express the address and
> > > > prefix-length to configure on an interface or for some other use.
> > > > We currently have an ip-prefix type which allows CIDR style
> > > > prefixes but since all bits to the right of the mask is to be 0 it
> > > > is only possible to use for describing the IP prefix / network
> > > > address itself - not the address of a host in that network.
> > > >
> > > > I actually wish the interface-ip modules would have used a
> > > > combined leaf for these settings rather than the dual-leaf
> > > > approach it currently has, but I suppose that ship has sailed :/
> > > >
> > > > Regardless, can we add such a type? Is this the document and time
> > > > to do it?
> > > > :)
> > > >
> > > > Kind regard,
> > > >    Kristian.
> > > >
> > > > _______________________________________________
> > > > netmod mailing list
> > > > netmod@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/netmod
> > >
> > > --
> > > Juergen Schoenwaelder           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/>
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 3
> > > Date: Mon, 1 Apr 2019 16:31:12 +0000
> > > From: "Acee Lindem (acee)" <acee@cisco.com>
> > > To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>,
> > > 	"Kristian Larsson" <kristian@spritelink.net>
> > > Cc: "netmod@ietf.org" <netmod@ietf.org>
> > > Subject: Re: [netmod] 6991bis: address-with-prefix-length
> > > Message-ID: <F1537180-6BF3-40C7-BCFA-3AAE0290AE9D@cisco.com>
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > I believe the "address-" could be omitted from the type identifiers.
> > > At least within the routing area, "ipv4-prefix" is unambiguous.
> > > Thanks,
> > > Acee
> > >
> > > ?On 4/1/19, 12:14 PM, "netmod on behalf of Juergen Schoenwaelder"
> > > <netmod-bounces@ietf.org on behalf of j.schoenwaelder@jacobs-
> > > university.de> wrote:
> > >
> > >     This is the right time for this and I would call these
> > >     ip-address-prefix, ipv4-address-prefix and ipv6-address
> > >     prefix.
> > >
> > >     /js
> > >
> > >     On Mon, Apr 01, 2019 at 04:38:34PM +0200, Kristian Larsson wrote:
> > >     > Hello,
> > >     >
> > >     > seeing that 6991 is up for a refresh I wonder if this would be the
> > >     > time to
> > >     > suggest the addition of a type for address-and-prefix-length, for
> > >     > example
> > >     > like 192.0.2.1/24?
> > >     >
> > >     > I find that it's the most natural way express the address and
> > >     > prefix-length
> > >     > to configure on an interface or for some other use. We currently have
> > >     > an
> > >     > ip-prefix type which allows CIDR style prefixes but since all bits to
> > >     > the
> > >     > right of the mask is to be 0 it is only possible to use for describing
> > >     > the
> > >     > IP prefix / network address itself - not the address of a host in that
> > >     > network.
> > >     >
> > >     > I actually wish the interface-ip modules would have used a combined
> > >     > leaf
> > > for
> > >     > these settings rather than the dual-leaf approach it currently has,
> > >     > but I
> > >     > suppose that ship has sailed :/
> > >     >
> > >     > Regardless, can we add such a type? Is this the document and time to
> > >     > do it?
> > >     > :)
> > >     >
> > >     > Kind regard,
> > >     >    Kristian.
> > >     >
> > >     > _______________________________________________
> > >     > netmod mailing list
> > >     > netmod@ietf.org
> > >     > https://www.ietf.org/mailman/listinfo/netmod
> > >
> > >     --
> > >     Juergen Schoenwaelder           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
> > >     netmod@ietf.org
> > >     https://www.ietf.org/mailman/listinfo/netmod
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Message: 4
> > > Date: Mon, 1 Apr 2019 17:23:37 +0000
> > > From: "Acee Lindem (acee)" <acee@cisco.com>
> > > To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>,
> > > 	"Kristian Larsson" <kristian@spritelink.net>
> > > Cc: "netmod@ietf.org" <netmod@ietf.org>
> > > Subject: Re: [netmod] 6991bis: address-with-prefix-length
> > > Message-ID: <A0F7987F-AA67-4A63-8FEE-3B74B5B47CF1@cisco.com>
> > > Content-Type: text/plain; charset="utf-8"
> > >
> > > Ok, now I'm confused. I see that the ietf-inet-type model already
> > > has the types ipv4-prefix and ipv6-prefix. How are these any
> > > different???
> > > Thanks,
> > > Acee
> > >
> > > ?On 4/1/19, 12:31 PM, "Acee Lindem (acee)" <acee@cisco.com> wrote:
> > >
> > >     I believe the "address-" could be omitted from the type
> > >     identifiers. At least
> > > within the routing area, "ipv4-prefix" is unambiguous.
> > >     Thanks,
> > >     Acee
> > >
> > >     On 4/1/19, 12:14 PM, "netmod on behalf of Juergen Schoenwaelder"
> > > <netmod-bounces@ietf.org on behalf of j.schoenwaelder@jacobs-
> > > university.de> wrote:
> > >
> > >         This is the right time for this and I would call these
> > >         ip-address-prefix, ipv4-address-prefix and ipv6-address
> > >         prefix.
> > >
> > >         /js
> > >
> > >         On Mon, Apr 01, 2019 at 04:38:34PM +0200, Kristian Larsson wrote:
> > >         > Hello,
> > >         >
> > >         > seeing that 6991 is up for a refresh I wonder if this would be the
> > >         > time to
> > >         > suggest the addition of a type for address-and-prefix-length, for
> > >         > example
> > >         > like 192.0.2.1/24?
> > >         >
> > >         > I find that it's the most natural way express the address and
> > >         > prefix-
> > > length
> > >         > to configure on an interface or for some other use. We currently
> > >         > have an
> > >         > ip-prefix type which allows CIDR style prefixes but since all bits
> > >         > to the
> > >         > right of the mask is to be 0 it is only possible to use for
> > >         > describing the
> > >         > IP prefix / network address itself - not the address of a host in
> > >         > that
> > >         > network.
> > >         >
> > >         > I actually wish the interface-ip modules would have used a
> > > combined leaf for
> > >         > these settings rather than the dual-leaf approach it currently has,
> > >         > but I
> > >         > suppose that ship has sailed :/
> > >         >
> > >         > Regardless, can we add such a type? Is this the document and time
> > >         > to do
> > > it?
> > >         > :)
> > >         >
> > >         > Kind regard,
> > >         >    Kristian.
> > >         >
> > >         > _______________________________________________
> > >         > netmod mailing list
> > >         > netmod@ietf.org
> > >         > https://www.ietf.org/mailman/listinfo/netmod
> > >
> > >         --
> > >         Juergen Schoenwaelder           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
> > >         netmod@ietf.org
> > >         https://www.ietf.org/mailman/listinfo/netmod
> > >
> > >
> > >
> > >
> > >
> > > ------------------------------
> > >
> > > Subject: Digest Footer
> > >
> > > _______________________________________________
> > > netmod mailing list
> > > netmod@ietf.org
> > > https://www.ietf.org/mailman/listinfo/netmod
> > >
> > >
> > > ------------------------------
> > >
> > > End of netmod Digest, Vol 133, Issue 2
> > > **************************************
> > This email and the information contained herein is proprietary and
> > confidential and subject to the Amdocs Email Terms of Service, which
> > you may review at https://www.amdocs.com/about/email-terms-of-service
> > <https://www.amdocs.com/about/email-terms-of-service>
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> >
This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>