Dear all,
Some recent news regarding the schema mount.
Sometimes, magic happens when people speak to each others face to face.
It did happen this week and there is a new schema mount plan that should
make everybody a little bit happier.
The second NETMOD session (Wednesday) will exclusively focus on the
schema mount.
Regards, Benoit (OPS AD)
Dear all,
In the last two weeks, I've been multiplying the schema mount discussions.
It's now time to draw the conclusions and to move on.
I'm sad that schema-mount is not NMDA compliant. We approved
RFC6087bis with the NMDA transition guidelines.
I'm sad that progression to IETF-LC has not been completed on the
schema-mount document since the WGLC in November.
As discussed with the document shepherd Joel, there is not a strong
support position for the schema mount document (version 08), but rough
consensus. The interaction with YANG library bis has been noted during
the WGLC. What happened since that WGLC closure on Nov6th is that the
people position became tougher and that multiple possible tracks have
been investigated. I believe we heard the arguments from everybody.
Taking my AD responsibilities, what's next?
1. We have been losing so much time (which I regret) since the WGLC
that publishing 08 now makes sense, solving one aspect of the problem:
the situation where the set of YANG modules is the same in all
datastores. Is this perfect solution? Certainly not.
The LNE and NI documents, in the RFC editor queue, depend on the
version 8 of schema mount.
So let's pursue that publication path.
2. The document 08 should be edited before requesting the publication.
- The draft should be clearly specified that this solution is not
fully NMDA complaint. For example, in the abstract
- The draft should mention an applicability statement, such as the one
the chairs proposed:
This work was produced during the period when NMDA solutions were being
developed in parallel. While the model defined in this document can be
used with both NMDA and non-NMDA supporting implementations, there are
limitations in its NMDA applicability. When used with Yang Library
[RFC7895] only non-NMDA implementations can be supported. When used with
the revised Yang Library defined in [I.D.ietf-netconf-rfc7895bis], NMDA
implementations can be supported with certain limitations. Specifically,
this document requires use of the now deprecated module-list grouping,
and the same schema represented in schema list of ietf-schema-mount MUST
be used in all datastores. Inline type mount points, which don't use the
schema list, don't have this limitation as they can support different
schema in different datastores by instantiating the
[I.D.ietf-netconf-rfc7895bis] version of YANG library under the inline
mount point. A future revision of this work is expected to provide for
full NMDA support.
- Some edits are needed: the nits from the YD review
https://www.ietf.org/mail-archive/web/netmod/current/msg19443.html
Another one, addressing one of Lada's important complaints.
The use of mount points does not impact the nature of the mounted data
or in which datastore information is made available. For example, the
datastore from which YANG Library module information may be obtained is
not impacted by the use of schema mount. This is case for both the top
level YANG Library module and any YANG Library modules included under a
mount point. The Schema Mount module itself MUST be present in the same
datastore as the YANG Library module.
Next, we want to work on a NMDA solution, based on the pre-09 version
... I guess.
This solution will obsolete the current 08 document and reference the
YANG library bis.
Let's dedicate the full second NETMOD session (on Wednesday) to schema
mount and let's use our energy to focus on the best solution.
Regards, Benoit (as OPS AD)
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
