RE: Crypto-agility requirement and draft-zorn-radius-encattr/draft-zorn-radius-keywrap

["David B. Nelson" <dnelson@elbrysnetworks.com>]

Dan Harkins writes...

> If you're submitting a draft that only does AES Key wrap with no
> capability to substitute anything else then you can mandate other
> attributes that may be necessary. This isn't crypto-agile though.

That's a good point.  True crypto-agility is about modularly interchangeable
cipher suites, not simply replacing a fixed, but compromised, cipher suite
with another fixed, but currently robust, cipher suite.



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>