[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Re: Reminder: automated key management is often required for new protocols]



Forwarding to the RADEXT list for a non-subscriber.

Sam Hartman wrote:

Hi.

I think that the applicability of RFC 4107 to radius crypto agility
work is kind of complicated.

I guess my main question is who is driving the work, who will use it.

My personal opinion is that updating radius crypto agility without
adding some form of automated key management doesn't have a lot of
value and may not be worth doing.

However if there are users and implementers who see the value in doing
the crypto agility updates, then perhaps it makes sense to do.

So, my question to you is what is driving this work besides a desire
to be good security citizens?


--- Begin Message ---
Hi.

I think that the applicability of RFC 4107 to radius crypto agility
work is kind of complicated.

I guess my main question is who is driving the work, who will use it.

My personal opinion is that updating radius crypto agility without
adding some form of automated key management doesn't have a lot of
value and may not be worth doing.

However if there are users and implementers who see the value in doing
the crypto agility updates, then perhaps it makes sense to do.

So, my question to you is what is driving this work besides a desire
to be good security citizens?


--- End Message ---