YANG Versioning Weekly Call Minutes - 2021-01-26
New order of topics for Interim, and rough time allocated:
Intros (chair, Jason): 10 minutes
T2) IANA considerations: how are final RFC revision labels assigned ?
https://github.com/netmod-wg/yang-ver-dt/issues/59
- Rob
- 10 minutes
T3) YANG file naming when revision labels are being used (symbolic links?
@<revision-label>) ?
- Reshad
- 20 minutes
T1) Definition/meaning of BC vs NBC for config false nodes
https://github.com/netmod-wg/yang-ver-dt/issues/15
- Balazs
- 35 minutes
T4) SemVer: gaps in history, removing revision statements
https://github.com/netmod-wg/yang-ver-dt/issues/61
- Joe
- 15 minutes
We discussed Github issue #12 about BC vs NBC for changing extension statements
https://github.com/netmod-wg/yang-ver-dt/issues/12
- decided to shelve this for now and bring it to the larger WG
We discussed topic T3:
- what chars should be allowed in filenames? in revision-labels ?
- allow unicode? Probably not.
- Be restrictive with a small allowed-list ? a-zA-Z0-9_-.,+
- Comma is sometimes used in version strings (precedence), also used sometimes
as a decimal separator. Concern about CSV.
e.g. -> 1.6.0,1 (indicates this is greater than 2.0.0)
- What about ';' (shell metachar in unix). Probably avoid this one.
- Be less restrictive and have a deny-list ? 0x00-0x1F 0x7F " * / : < > ? \ |,
#, @
- Use the same rules as YANG module name?
We discussed topic T4:
- only match on labels in the history contained in the 1 file? vs parsing
multiple files to build the complete lineage ?
- warning about removing history (especially if the entry had an NBC tag)
Rgds,
Jason
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
