| Hi Elwyn, A quick follow-up on one item:
Whilst the linked email thread has resulted in changing the guidance some, I reviewed more carefully how this section was being used in all nine drafts, and found that it was containing some useful information that would be missed if the section were removed. I also found that the “jargon” syntax is pretty prevalent, not only throughout these nine drafts, but in other published drafts as well…and swapping out the usage everywhere would a huge effort. That said, I agree that adequate references were missing, and so I updated The section (all nine drafts) to reference the documents defining the syntax. For instance, see the last sentence below, from in the ssh-client-server draft: 1.4. Adherence to the NMDA This document is compliant with the Network Management Datastore Architecture (NMDA) [RFC8342]. For instance, as described in [I-D.ietf-netconf-trust-anchors] and [I-D.ietf-netconf-keystore], trust anchors and keys installed during manufacturing are expected to appear in <operational> (Section 5.3 of [RFC8342]), and <system> [I-D.ietf-netmod-system-config], if implemented. This this okay? Kent |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
