From: Mahesh Jethanandani <[email protected]<mailto:[email protected]>> Date: Monday, April 18, 2016 at 4:43 PM To: Acee Lindem <[email protected]<mailto:[email protected]>> Cc: Kent Watsen <[email protected]<mailto:[email protected]>>, Tom Petch <[email protected]<mailto:[email protected]>>, Martin Bjorklund <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Routing WG <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Netconf] mbj review of draft-ietf-netconf-restconf-server-model-09
On Apr 18, 2016, at 10:25 AM, Acee Lindem (acee) <[email protected]<mailto:[email protected]>> wrote: I did get some negative feedback with respect to adding “routing-“ to the model name since key chains are used for other non-routing applications as well. One of those non-routing protocols is BFD. I am fine if the model is called protocol-key-chain, but I wonder what happens the next entity needing key-chain is not a protocol. The bigger question in my mind is, are these really different types of key-chains models, or are we talking about one key-chain model? The rtgwg key chain model is the one we all know and love associated with the graceful rollover of configurable keys. The netconf model is list of certificates for a public key. Please look at the information content of the two models. I hope I don’t have to answer this question again ;^) Acee Mahesh Jethanandani [email protected]<mailto:[email protected]>
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
