Hi Alexey, See below.
On 5/3/17, 11:51 AM, "rtgwg on behalf of Alexey Melnikov" <rtgwg-boun...@ietf.org on behalf of aamelni...@fastmail.fm> wrote: >Alexey Melnikov has entered the following ballot position for >draft-ietf-rtgwg-yang-key-chain-24: No Objection > >When responding, please keep the subject line intact and reply to all >email addresses included in the To and CC lines. (Feel free to cut this >introductory paragraph, however.) > > >Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html >for more information about IESG DISCUSS and COMMENT positions. > > >The document, along with other ballot positions, can be found here: >https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-key-chain/ > > > >---------------------------------------------------------------------- >COMMENT: >---------------------------------------------------------------------- > >Thank you for addressing my DISCUSS. > >Maybe it is just me, but it would have helped to say that "key string in >ASCII" is a passphrase. I was not sure whether "key string" was a term >used in Routing and/or YANG circles. The best place to clarify this is in >Section 2 (Problem Statement) Typically, authentication keys using for applications such as routing protocols have been configured in ASCII or hexadecimal and still referred to as keys. For example, refer to RFC 7474. I believe the term “passphrase” would be wrong as this seems to imply something like an SSH paraphrase. Thanks, Acee > > >_______________________________________________ >rtgwg mailing list >rtgwg@ietf.org >https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ rtgwg mailing list rtgwg@ietf.org https://www.ietf.org/mailman/listinfo/rtgwg
