Hi Kristian,

Completely agree.  My suggestion for a tuples type is really for YANG Next.  
I'll add it to the tracker so that it can be discussed.

For the immediate problem, I agree with defining a combined type.  Juergen's 
proposal looks good to me.

Thanks,
Rob


> -----Original Message-----
> From: netmod <netmod-boun...@ietf.org> On Behalf Of Kristian Larsson
> Sent: 02 April 2019 13:28
> To: netmod@ietf.org
> Subject: Re: [netmod] 6991bis: address-with-prefix-length
> 
> Hi Rob,
> 
> On 2019-04-02 14:17, Rob Wilton (rwilton) wrote:
> >> -----Original Message-----
> >> From: netmod <netmod-boun...@ietf.org> On Behalf Of Martin
> Bjorklund
> >> Sent: 01 April 2019 18:30
> >> To: Acee Lindem (acee) <a...@cisco.com>
> >> Cc: netmod@ietf.org
> >> Subject: Re: [netmod] 6991bis: address-with-prefix-length
> >>
> >> Hi,
> >>
> >> The request was for a combined type that contains both an ip address
> >> *and* a prefix length in one value.  Hence the name
> >> "ip-address-and-prefix- length" :)
> >>
> >> I know that this type is convenient, esp. if you use it for manual
> >> input, but I wonder if it really is good practice to squeeze two values 
> >> into
> one.
> >
> > Perhaps allowing YANG to support a tuple type would be an elegant
> solution.  I.e. the value exists on a single path, and has to be atomically
> updated, but the value can still be composed from different types.
> 
> I think that would be a great addition to YANG. I've had numerous
> discussions over the awkardness of using a grouping to group multiple leaves
> together when you really want to define some form of compound / tuple
> type.
> 
> However, that is a longer term project and IMHO not something that should
> stop adding a ip-address-and-prefix-length type to 6991bis today :)
> 
> Kind regards,
>     Kristian.
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to