Re: [netmod] NULL value for uint16

Hi Mahesh, management interface usually do not change protocol semantics (for the simple reason that protocol engines do not necessarily know which management interfaces control them and their peers). Does the Babel RFC reserve the special sequence number 0? If not, does this document formally up

Re: [netmod] NULL value for uint16

[Bringing in babel WG, instead of maintaining two threads] Hi Juergen, > On Sep 10, 2021, at 1:09 PM, Jürgen Schönwälder > wrote: > > On Fri, Sep 10, 2021 at 01:40:03PM -0400, Lou Berger wrote: > >> and it references an RFC that says: >> >> This is a 16-bit unsigned integer; >> i

Re: [netmod] NULL value for uint16

From: Jürgen Schönwälder Sent: 10 September 2021 21:09 On Fri, Sep 10, 2021 at 01:40:03PM -0400, Lou Berger wrote: > and it references an RFC that says: > > This is a 16-bit unsigned integer; > if the data model uses zero (0) to represent NULL values for > unsigned integers, th

Re: [netmod] NULL value for uint16

> On 2021-09-10, at 22:09, Jürgen Schönwälder > wrote: > > We are talking about RFC 9046? Well… SECDIR Last Call Review (of -11): Has Issues RTGDIR Last Call Review (of -11): Ready GENART Last Call Review (of -11): Ready RTGDIR Early Review (of -03): Has Issues OPSDIR Last Call Review -

Re: [netmod] NULL value for uint16

Andy Bierman writes: > On Fri, Sep 10, 2021 at 9:47 AM Randy Presuhn < > randy_pres...@alumni.stanford.edu> wrote: > >> Hi - >> >> On 2021-09-10 9:42 AM, Andy Bierman wrote: >> > Hi, >> > >> > Maybe the use of [null] in RFC 7951 is confusing people >> > https://datatracker.ietf.org/doc/html/rfc79

Re: [netmod] NULL value for uint16

On Fri, Sep 10, 2021 at 01:40:03PM -0400, Lou Berger wrote: > and it references an RFC that says: > > This is a 16-bit unsigned integer; > if the data model uses zero (0) to represent NULL values for > unsigned integers, the data model MAY use a different data type > that

Re: [netmod] NULL value for uint16

Tom, okay, you made me look... The full text is leaf received-metric {    type uint16;    description "The metric with which this route was advertised by the   neighbor, or maximum value (infinity) to indicate the   route was recentl

Re: [netmod] NULL value for uint16

Hi - On 2021-09-10 9:57 AM, Andy Bierman wrote: On Fri, Sep 10, 2021 at 9:47 AM Randy Presuhn > wrote: Hi - On 2021-09-10 9:42 AM, Andy Bierman wrote: > Hi, > > Maybe the use of [null] in RFC 7951 is confusing people > h

Re: [netmod] NULL value for uint16

On Fri, Sep 10, 2021 at 9:47 AM Randy Presuhn < randy_pres...@alumni.stanford.edu> wrote: > Hi - > > On 2021-09-10 9:42 AM, Andy Bierman wrote: > > Hi, > > > > Maybe the use of [null] in RFC 7951 is confusing people > > https://datatracker.ietf.org/doc/html/rfc7951#section-6.9 > >

Re: [netmod] NULL value for uint16

Hi - On 2021-09-10 9:42 AM, Andy Bierman wrote: Hi, Maybe the use of [null] in RFC 7951 is confusing people https://datatracker.ietf.org/doc/html/rfc7951#section-6.9 Are you suggesting that the type of this leaf should be a choice o

Re: [netmod] NULL value for uint16

gt; Subject: Re: [netmod] NULL value for uint16 > > The RFC editor is not going to fix this, for them it is beyond > editorial. For me it makes sense to report this, let alone to spread > the word that there is no NULL in YANG land. Sure, things like this > should be catched earlier but thi

Re: [netmod] NULL value for uint16

From: Jürgen Schönwälder Sent: 10 September 2021 17:18 To: tom petch Cc: netmod@ietf.org Subject: Re: [netmod] NULL value for uint16 The RFC editor is not going to fix this, for them it is beyond editorial. For me it makes sense to report this, let alone to spread the word that there is no NULL

Re: [netmod] NULL value for uint16

The RFC editor is not going to fix this, for them it is beyond editorial. For me it makes sense to report this, let alone to spread the word that there is no NULL in YANG land. Sure, things like this should be catched earlier but things are as they are and a late fix is still better than publishing

Re: [netmod] NULL value for uint16

From: Jürgen Schönwälder Sent: 10 September 2021 13:14 I guess the description should be worded as "This leaf does not exist if ..." instead of talking about NULL, a concept that does not exist in the YANG language and the protocols. One subtle point with the "does not exist" approach is tha

Re: [netmod] NULL value for uint16

On 10. 09. 21 13:56, tom petch wrote: > Does NULL have any meaning for a leaf of type uint16? > > Looking at a leaf of type uint16 the description says that > 'This metric will be NULL (no value) ..' Without the context, I'd guess it means that the value isn't set and has no default. As you wrot

Re: [netmod] NULL value for uint16

I guess the description should be worded as "This leaf does not exist if ..." instead of talking about NULL, a concept that does not exist in the YANG language and the protocols. One subtle point with the "does not exist" approach is that a client cannot reliably distinguish between 'a leaf do

[netmod] NULL value for uint16

Does NULL have any meaning for a leaf of type uint16? Looking at a leaf of type uint16 the description says that 'This metric will be NULL (no value) ..' Some languages differentiate a 'never been set' state from e.g set to zero or some other value but for me, YANG does not have that concept.