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

RE: Open issues on the Crypto-Agility Requirements draft

To: "'Alan DeKok'" <aland@deployingradius.com>, "'Dave Nelson'" <d.b.nelson@comcast.net>
Subject: RE: Open issues on the Crypto-Agility Requirements draft
From: "Glen Zorn" <glenzorn@comcast.net>
Date: Thu, 11 Jun 2009 22:05:23 +0700
Cc: "'radext mailing list'" <radiusext@ops.ietf.org>
In-reply-to: <4A31152F.2020209@deployingradius.com>
References: <50C5A1D479B047E5811E487440A824F0@NEWTON603> <4A30AA2C.4060803@deployingradius.com> <4C47BAE932794C2880E4F016A803AA52@NEWTON603> <4A31152F.2020209@deployingradius.com>

Alan DeKok [mailto://aland@deployingradius.com] writes:

...
 
>   It makes the "wiretap via RADIUS" issue more difficult.  But I've
> never understood we can securely allow third-parties to insert
> arbitrary
> traffic into an AAA exchange, and *without* having one of the parties
> notice that the traffic exists.

It's not; fortunately, that's not necessary.

...


--
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:
- Open issues on the Crypto-Agility Requirements draft
  - From: "Dave Nelson" <d.b.nelson@comcast.net>
- Re: Open issues on the Crypto-Agility Requirements draft
  - From: Alan DeKok <aland@deployingradius.com>
- RE: Open issues on the Crypto-Agility Requirements draft
  - From: "Dave Nelson" <d.b.nelson@comcast.net>
- Re: Open issues on the Crypto-Agility Requirements draft
  - From: Alan DeKok <aland@deployingradius.com>

Prev by Date: Re: Open issues on the Crypto-Agility Requirements draft
Next by Date: RE: Open issues on the Crypto-Agility Requirements draft
Previous by thread: Re: Open issues on the Crypto-Agility Requirements draft
Next by thread: RE: Open issues on the Crypto-Agility Requirements draft
Index(es):
- Date
- Thread