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

RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )

To: "Nelson, David" <dnelson@enterasys.com>
Subject: RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
From: Bernard Aboba <aboba@internaut.com>
Date: Thu, 8 Sep 2005 12:17:20 -0700 (PDT)
Cc: radiusext@ops.ietf.org
In-reply-to: <2A5E4540D4D5934D9A1E7E0B0FDB2D690103258E@MAANDMBX2.ets.enterasys.com>
References: <2A5E4540D4D5934D9A1E7E0B0FDB2D690103258E@MAANDMBX2.ets.enterasys.com>

> RADIUS has always embraced the notion of "hints" that the NAS may send
> to the RADIUS Server in an Access-Request.  It seems to me that your
> proposal might be thought of as "hints" that the RADIUS Server may send
> to the NAS in an Access-Challenge.  That does seem quite useful and
> quite elegant.

It is not only useful and elegant, it is also compatible with RFC 2865 - 
the best of all possible worlds. 

--
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:
- RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
  - From: "Nelson, David" <dnelson@enterasys.com>

Prev by Date: RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
Next by Date: RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
Previous by thread: RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
Next by thread: RE: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
Index(es):
- Date
- Thread