RE: FW: DISCUSS: draft-ietf-radext-delegated-prefix

"Bernard Aboba" <bernard_aboba@hotmail.com> Fri, 09 June 2006 22:30 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Fri, 09 Jun 2006 22:30:58 +0000
Message-ID: <BAY106-F147924E4B5D00AE727ED1893880@phx.gbl>
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: dnelson@enterasys.com, radiusext@ops.ietf.org
Bcc:
Subject: RE: FW: DISCUSS: draft-ietf-radext-delegated-prefix
Date: Fri, 09 Jun 2006 15:30:29 -0700
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"

>This IESG DISCUSS comment from Russ applies equally to all RADEXT WG
>documents that provide for Diameter AVPs, whether by the RFC 4005
>Diameter NAS Application method, or by some other explicit means.  We
>need to develop a suitable chunk of template text for the Security
>Considerations section of RADEXT WG documents to address Diameter
>security considerations, as well as RADIUS security considerations.

I don't believe there are any substantial differences in the security 
implications of these attributes in RADIUS vs. Diameter, and I'd suggest 
that the document say this and leave it at that.



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

RE: FW: DISCUSS: draft-ietf-radext-delegated-pref… Glen Zorn (gwz)
RE: FW: DISCUSS: draft-ietf-radext-delegated-pref… Bernard Aboba
FW: DISCUSS: draft-ietf-radext-delegated-prefix Nelson, David