Kent Watsen <[email protected]> writes: > NETMOD WG, > > I was recently asked why YANG module namespaces aren’t versioned. For > example, the “1.0” at the end of this URI > "urn:ietf:params:xml:ns:yang:ietf-crypto-types:1.0”. The stated concern was > "because without this, then management of backward compatibility becomes a > nightmare.” > > This convention was established prior to my becoming active in the IETF, but > my guess is that the reason is because the YANG-module update rules in RFC > 7950 Section 11 ensure backwards compatibility, and hence the versioning the > namespace would have no value. That said, the YANG Versioning effort > introduces the possibility of NBC changes, which makes me wonder if this is > something that should be discussed.
I believe this was a deliberate decision. The info about module versions is available elsewhere (in the module proper and/or in YANG library data), so I don't see any necessity of having it in the namespace. Can you (or somebody) provide details why "backward compatibility becomes a nightmare"? Speaking practically, the namespace identifier in JSON representation is just the module name, so adding versions to namespaces would cause troubles. Lada > > Thoughts? > > Kent > > > > _______________________________________________ > netmod mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Ladislav Lhotka <[email protected]> PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
