[Netconf] update to client/server drafts

[Kent Watsen <[e-mail]>]

All drafts updated! It looks like a big change, but almost all of it
goes to:

 1) the introduction of the new crypto-types and trust-anchors modules

 2) the resurrection of the keystore module, along with groupings 
    enabling keys to be locally-defined of a reference to a key in
    the keystore module

 3) reformatting all YANG modules to not exceed 69 chars/line.




To recap, the relationship between these drafts is:

                     crypto-types
                       ^      ^
                      /        \
                     /          \
           trust-anchors      keystore
              ^      ^------+    ^   ^
              |              \   |   |
              |      +-----------+   |
              |     /          \     |
       ssh-client-server      tls-client-server
        ^                      ^           ^
        |                      |           |
        |            +---------+           |
        |           /                      |
 netconf-client-server          restconf-client-server





I have some questions for the WG:

 1) no regrets about trust-anchors being separate from keystore,
    right?

 2) are we happy with keystore's "local-or-keystore" groupings
    (not too complicated?) and, if yes, should we have a similar
    ability for trust-anchors (e.g., a "local-or-trust-anchor"
    grouping like in the keystore module)?

 3) should some of keystore's groupings be moved to crypto-types?
    e.g., asymmetric-key-grouping isn't a keystore-specific
    concept.

 4) should trust-anchors include SSH host keys at all?  Maybe this
    draft should define two modules (x509-trust-anchors and
    ssh-trust-anchors)?

 5) should algorithm identities be moved from ssh/tls-client/server
    to crypto-types?

 6) should we add a "periodic" feature to the netconf/restconf
    client/server drafts, enablings the initiating peer to
    optionally support periodic connections? 

I'll start a thread for each later, my only goal for mentioning
them here is to get people thinking about such things when looking
at these drafts. 




Next steps:

My current plan is to update the zerotouch draft next, to make use
of the new trust-anchor and keystore drafts, in the example device
configuration module in the Appendix.

Once the zerotouch draft is submitted for publication, I'll swing
back around to these drafts, hopefully updating them one more time
before Montreal.

In the meanwhile, it would be awesome if you all could take a good
look at these.  You really only need to look at the YANG modules
themselves, but I still recommend looking at the drafts, which
contain tree diagrams and examples that makes everything easier
to understand.



Thanks,
Kent // contributor