On Tue, Jun 18, 2024 at 1:53 AM Jürgen Schönwälder
wrote:
> The YANG naming scheme is (module, path). The XML namespaces are an
> XML serialization artifact.
>
> By promising backwards compatibility, the (module, path) naming scheme
> was sufficient (non-backwards compatible changes require to
Thanks a lot Med. I have submitted a new version to incorporate your fixes. You
might want to review it at
https://author-tools.ietf.org/iddiff?url2=draft-ietf-netmod-system-config-08.
Best Regards,
Qiufang
-Original Message-
From: mohamed.boucad...@orange.com
Internet-Draft draft-ietf-netmod-system-config-08.txt is now available. It is
a work item of the Network Modeling (NETMOD) WG of the IETF.
Title: System-defined Configuration
Authors: Qiufang Ma
Qin Wu
Chong Feng
Name:draft-ietf-netmod-system-config-08.txt
The YANG naming scheme is (module, path). The XML namespaces are an
XML serialization artifact.
By promising backwards compatibility, the (module, path) naming scheme
was sufficient (non-backwards compatible changes require to change either
the module, the path, or both).
The versioning effort
Hi Qiufang,
Thanks for taking care of this.
I submitted right now a PR with some minor fixes (e.g., align with 8407bis
reco): https://github.com/netmod-wg/system-config/pull/38
Other than that, this looks good to me.
Cheers,
Med
> -Message d'origine-
> De : maqiufang (A)
> Envoyé
Hi Xufeng,
Thank you for the review.
Please see inline.
Cheers,
Med
> -Message d'origine-
> De : Xufeng Liu via Datatracker
> Envoyé : mardi 18 juin 2024 05:33
> À : yang-doct...@ietf.org
> Cc : draft-ietf-netmod-rfc8407bis@ietf.org; last-
> c...@ietf.org; netmod@ietf.org
>
Kent,
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.”
In the
