Re: [netconf] Genart last call review of draft-ietf-netconf-ssh-client-server-37

[Kent Watsen <[e-mail]>]

Hi Elwyn,

A quick follow-up on one item:


>> s1.4: The jargon <operational> should be replaced by 'operational state
>> datastore' with a reference to Section 5.3 of RFC 8342.
> 
> “Jargon" is a bit overstated.   It is a formal term in the YANG ecosphere.
> It’s just a terminology-import away from being proper.  Far from jargon...
> 
> That said, I can’t fault your proposed text, as it seems easier to do than
> importing a term, and plausibly more proper.
> 
> Even still, I’m beginning to question the need for that section at all.  See
> https://mailarchive.ietf.org/arch/msg/netmod/pL5Mb3S1e9UEqzepPtNGwMUBQ1o/

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