[netconf] updates to client/server drafts

[Kent Watsen <[e-mail]>]

The updates can be broadly described as thus:

1) in crypto-types, replaced the 'action' statements with 'crypt-hash' like equivalents.  If folks don't like the "verbs", then we can simply remove them, having no solution for asking the device to generate a key or install a hidden key.

2) in trust-anchors, renamed "trust-anchors" to "truststore"

3) in both truststore and keystore, moved everything under a 'grouping' statement which is then used by a 'container'.  This is almost an editorial update.

4) in tcp-client-server, added support for external NAT (we can remove is preferred)

5) in restconf-client-server, added an 'http-listen' (not https-listen) choice, to support case when server is behind a TLS-terminator.  This draft isn't adopted yet, but this is driven by my needing to support this use case in a project I'm working on.  (ps: yes, I'm implementing the entire ietf-restconf-server model).

6) also in restconf-client-server, refactored the server module to be more like other 'server' models.  If folks like it, I will also apply the same also to the client model, as well as to both the netconf client/server models.  Now the 'restconf-server-grouping' is just the RC-specific bits (i.e., the "demux" container minus the container), 'restconf-server-[listen|callhome]-stack-grouping' is the protocol stack for a single connection, and 'restconf-server-app-grouping' is effectively what was before (both listen+callhome for many inbound/outbound endpoints).

There are other smaller changes, please see the change logs and diffs for details.


PS: the chairs are hoping to enter crypto-types, truststore, and keystore in Last Call in a couple weeks.   There may be another update to crypto-types draft before then pending on my Huawei co-authors.   The remainder of the drafts need more work before ready for Last Call.

Thanks,
Kent // contributor