Re: [Netconf] Draft Charter Proposal for NETCONF WG

[Kent Watsen <[e-mail]>]

>>Maybe one of the authors of the RTGWG key-chain draft to try
>> to express how the two modules differ,
>
> Is this a trick question? 

No, it was to see if you could articulate it better than I have
been able to date.


> As the author of ietf-keystore, I'd fully expect that you 
> know the difference.

I do.


>>and why they shouldn't be merged into one draft.
>
> They should't be merged since they serve entirely different 
> purposes and will be implemented and deployed by different 
> sets of network devices. 

Fundamentally, they both are talking about storing keys that
can be referenced.  I could easily make a case for why the
keystore module should include passwords, including policies
around expiration and rollovers, somewhat like RFC7210, which
the key-chain module emulates.  Yes, we're coming at this from
very different angles, but at the end of the day, they're more
alike than not.

FWIW, I'm not actually proposing we merge our drafts/modules,
I'm just using this as a thought exercise for others.

Not that it matters, but I disagree that these modules will 
be implemented by different sets of devices.  As I expect any
router implementing the key-chain module (to configure keys to
protect routing protocols) would also implement the keystore
module (to configure the keys/certificates used to protect e.g.
the SSH/TLS connections over which the key-chain module is 
configured).


> Furthermore, the key-chain draft is more mature and referenced
> by 6-10 other IETF YANG models.

Funny, maybe we should compare dependency graphs using Benoit's 
tool?   But let's wait until Monday since but the Syslog and 
PCE-PCEP drafts should post updates then that import the keystore
module  ;)


Thanks,
Kent