RE: [Issue 297] Review of Identity Selection -12

Bernard Aboba <aboba@internaut.com> Wed, 27 April 2005 14:41 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Wed, 27 Apr 2005 14:41:54 +0000
Date: Wed, 27 Apr 2005 07:41:37 -0700
From: Bernard Aboba <aboba@internaut.com>
To: Pasi.Eronen@nokia.com
cc: farid.adrangi@intel.com, radiusext@ops.ietf.org
Subject: RE: [Issue 297] Review of Identity Selection -12
Message-ID: <Pine.LNX.4.56.0504270732490.5270@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"

> Since draft-adrangi-eap-network-discovery-12 does not even have
> a reference to RFC 2607, I don't think any "Updates" header
> is needed...

RFC 2607 specifies RADIUS proxy behavior in roaming.  This document
specifies the behavior of RADIUS proxies that handle EAP messages.

Moreoever, the document implicitly assumes a model by which requests
are routed (source routing).

These additions affect the behavior of RADIUS proxies. Between this
document and RFC 2486bis,  many proxies will need to be modified.

I'm suggesting that we explicitly acknowledge the changes by including an
Updates: header.

Another alternative would be to remove the material relating to proxy
behavior, and put it in a separate document within RADEXT WG.  That
document could expand on the required changes in more depth (such as the
expected handling of source routed NAIs).



--
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: [Issue 297] Review of Identity Selection -12 Bernard Aboba