[Netconf] configuration models status and timeline

[Juergen Schoenwaelder <[e-mail]>]

Kent,

I liked your presentation since it was trying to close issues. I went
through the recording and here is my short summary of where we are:

1. trust anchors / keystore -> option #1 (resolved)

2. local-or-keystore keys -> keep + feature statement (resolved)

3. move groupings to crypt-types -> ? (unresolved)

4. move algorithm identities -> ? (discussion with security people)

5. periodic connections -> periodic feature (resolved)

6. tcp keepalives -> ? (protocol layer keep alives with a feature?)

So the sticky ones are #4 and #6.

- Concerning #4, will you manage to talk to the security people this
  week and can we expect a proposal soon after?

- Concerning #6, I am not really sure what protocol layer keep alives
  are (the client sending an "empty" rpc? - this would not need any
  server configuration just a definition how empty rpcs are handled;
  we would needs something similar than for RESTCONF). If this takes
  time to work out, perhaps another option is to remove keep alives
  from the models and to keep them on the TODO list for a future
  extension?

So given this, what is your (realistic) estimation when we can have
drafts that have all issues resolved and that go to WG last call?

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
Fax:   [phone]         <https://www.jacobs-university.de/>