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

Re: Crypto-agility requirements: Backward Compatibility (from Issue 303)

To: Bernard Aboba <bernard_aboba@hotmail.com>
Subject: Re: Crypto-agility requirements: Backward Compatibility (from Issue 303)
From: Alan DeKok <aland@deployingradius.com>
Date: Mon, 29 Jun 2009 12:00:42 +0200
Cc: "radiusext@ops.ietf.org" <radiusext@ops.ietf.org>
In-reply-to: <BLU137-W18D54B55BA177670D6E72093330@phx.gbl>
References: <BLU137-W18D54B55BA177670D6E72093330@phx.gbl>
User-agent: Thunderbird 2.0.0.22 (Macintosh/20090605)

Bernard Aboba wrote:
> The intent of this paragraph is probably right, but currently, it's
> somewhat open to multiple interpretations. Would something like this
> capture the intent?

  That looks good to me.

  Alan DeKok.

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

References:
- Crypto-agility requirements: Backward Compatibility (from Issue 303)
  - From: Bernard Aboba <bernard_aboba@hotmail.com>

Prev by Date: Re: Crypto-agility requirements: Compromise of Legacy Shared Secret (from Issue 303)
Next by Date: Re: REMINDER: Call for review of the "NAI-based Peer Discovery" document for acceptance as a RADEXT WG work item
Previous by thread: RE: Crypto-agility requirements: Backward Compatibility (from Issue 303)
Next by thread: Crypto-agility requirements: Operational Model (from Issue 303)
Index(es):
- Date
- Thread