mailto:a...@yumaworks.com>>
Date: Wednesday, 3 April 2024 at 19:07
To: Joe Clarke (jclarke) mailto:jcla...@cisco.com>>
Cc: Jason Sterne (Nokia)
mailto:40nokia@dmarc.ietf.org>>,
netmod@ietf.org<mailto:netmod@ietf.org>
mailto:netmod@ietf.org>>
Subject: Re: [netmod
rimental RFC.
Regards,
> Rob
>
Andy
>
>
>
> *From: *netmod on behalf of Andy Bierman <
> a...@yumaworks.com>
> *Date: *Wednesday, 3 April 2024 at 19:07
> *To: *Joe Clarke (jclarke)
> *Cc: *Jason Sterne (Nokia) ,
> netmod@ietf.org
> *Subject: *Re: [netmo
ine a file naming scheme for
YANG 2.0
since it does not exist and will probably never exist.
> Regards,
> Rob
>
Andy
>
>
>
>
> *From: *netmod on behalf of Andy Bierman <
> a...@yumaworks.com>
> *Date: *Wednesday, 3 April 2024 at 19:07
> *To: *Joe Clarke (j
: Jason Sterne (Nokia) ,
netmod@ietf.org
Subject: Re: [netmod] YANG Versioning: filename recommendations for YANG Semver
Hi,
On Wed, Apr 3, 2024 at 10:34 AM Joe Clarke (jclarke)
mailto:jcla...@cisco.com>> wrote:
From: Andy Bierman mailto:a...@yumaworks.com>>
Date: Tuesday, April 2
Hi,
On Wed, Apr 3, 2024 at 10:34 AM Joe Clarke (jclarke)
wrote:
>
>
>
>
> *From: *Andy Bierman
> *Date: *Tuesday, April 2, 2024 at 17:40
> *To: *Joe Clarke (jclarke)
> *Cc: *Jason Sterne (Nokia) ,
> netmod@ietf.org
> *Subject: *Re: [netmod] YANG Versioning
> This can never happen since the '#' char is not allowed in a YANG module name.
> YANG 1.1 tools look for MODNAME[@DATE].EXT.
> If the YANG module name is not in this format the tool will not find the
> module.
https://datatracker.ietf.org/doc/html/rfc7950#section-5.2 says:
The name of
From: Andy Bierman
Date: Tuesday, April 2, 2024 at 17:40
To: Joe Clarke (jclarke)
Cc: Jason Sterne (Nokia) ,
netmod@ietf.org
Subject: Re: [netmod] YANG Versioning: filename recommendations for YANG Semver
On Tue, Apr 2, 2024 at 2:11 PM Joe Clarke (jclarke)
mailto:jcla...@cisco.com>>
On Tue, Apr 2, 2024 at 2:11 PM Joe Clarke (jclarke)
wrote:
> Thanks, Andy. See inline below.
>
>
>
> I do not agree with these recommendations to change the file names of YANG
> modules.
>
> The OFFICIAL YANG version is RFC 7950 - YANG 1.1.
>
> Any module using YANG version 1.1 needs to follow t
Thanks, Andy. See inline below.
I do not agree with these recommendations to change the file names of YANG
modules.
The OFFICIAL YANG version is RFC 7950 - YANG 1.1.
Any module using YANG version 1.1 needs to follow the rules in RFC 7950.
Additional file naming that can be ignored by YANG 1.1 to
Hi,
I do not agree with these recommendations to change the file names of YANG
modules.
The OFFICIAL YANG version is RFC 7950 - YANG 1.1.
Any module using YANG version 1.1 needs to follow the rules in RFC 7950.
Additional file naming that can be ignored by YANG 1.1 tools is OK.
I do not understan
Hello NETMOD WG,
At IETF 119, during the YANG Versioning discussions, there was a suggestion to
raise the filename issue again as one last issue to resolve before going to
last call.
Version 10 of Module Versioning had the following content that was subsequently
removed in version 11:
https://
11 matches
Mail list logo
