> Anyhow, cynicism aside, there is a list of eight IANA-maintained modules to
> use as exemplars.
>
> Tom Petch
And five more IANA-maintained modules to-be with
"draft-ietf-netconf-ssh-client-server" and
"draft-ietf-netconf-ssh-client-server".
K.
___
From: netmod on behalf of Juergen Schoenwaelder
Sent: 28 June 2021 19:20
On Mon, Jun 28, 2021 at 12:39:38PM -0400, Michael Richardson wrote:
>
> Juergen Schoenwaelder wrote:
> >> Juergen Schoenwaelder wrote:
> > You revise RFC 8366 and do the following:
>
> > - You define an IANA
On Mon, Jun 28, 2021 at 12:39:38PM -0400, Michael Richardson wrote:
>
> Juergen Schoenwaelder wrote:
> >> Juergen Schoenwaelder wrote:
> >> > Note that there is also a middle ground, namely an enumeration type
> >> > factored out into an IANA maintained module that is process wise
>
Juergen Schoenwaelder wrote:
>> Juergen Schoenwaelder wrote:
>> > Note that there is also a middle ground, namely an enumeration type
>> > factored out into an IANA maintained module that is process wise easier
>> > to extend - should extensions be needed more regularly.
>>
On Mon, Jun 28, 2021 at 12:04:46PM -0400, Michael Richardson wrote:
>
> Juergen Schoenwaelder wrote:
> > Note that there is also a middle ground, namely an enumeration type
> > factored out into an IANA maintained module that is process wise easier
> > to extend - should extensions be
Juergen Schoenwaelder wrote:
> Note that there is also a middle ground, namely an enumeration type
> factored out into an IANA maintained module that is process wise easier
> to extend - should extensions be needed more regularly.
That would suit me. How do we do that?
--
Michael Ri
On Mon, Jun 28, 2021 at 11:54:04AM +, tom petch wrote:
[...]
> As you say, this is never going to be an Erratum.
Yep.
> A leaf of type empty is encoded as, well, empty.
>
> as per RFC 7950.
>
> When this concept was first mentioned, my sense was that while it was
> technically possible,
From: netmod on behalf of Toerless Eckert
Sent: 25 June 2021 23:48
I was first asking about the encoding ;-)
Would be good to understand if this "empty" encoding would result in a
- same of different degree of "backward compatibility" as an extended enum
- same or different size of ascii and
Toerless Eckert wrote:
> Lets hear from yang doctors or yang friends. Right now i bet that if
> the only change for yang vouchers is this enum, then its probably
> easiest to do b), e.g.: make AE be a formal update. I think c) is
> appropriate if we have a larger critical mass of
I was first asking about the encoding ;-)
Would be good to understand if this "empty" encoding would result in a
- same of different degree of "backward compatibility" as an extended enum
- same or different size of ascii and binary encoding ?
I am also not quite clear what difference it really
Toerless Eckert wrote:
tte> https://trac.ietf.org/trac/netmod/wiki/YANG_FAQ#when-use-empty
tte> Is this the solution we are looking for ?
here it the relevant text:
} The second situation is when you want to define an extensible enumeration,
} as an alternative to the type "enumeration
11 matches
Mail list logo
