RE: REMINDER: RADEXT WG Last Call on "Crypto-Agility Requirements for RADIUS"

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

Joseph Salowey writes...

> [Joe] Yes, this would be possible, I think it would involve 
> defining the behavior in this type of error condition and the
> associated signaling.  It wouldn't necessarily be too hard, but
> it would be additional messaging.

That's all I'm really looking for here.  Some assurance that existing RADIUS
mechanisms could be used, albeit in a sub-optimal fashion, to address the
requirement for cipher-suite "negotiation".  Said in other words, we are
creating no requirement to introduce capability negotiation into RADIUS in
order to complete the crypto-agility work.



--
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/>