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

["Avi Lior" <avi@bridgewatersystems.com>]

Hi David,

You could call it hints...

BTW this is already in the capability draft...and there it is stronger
then just hints.  Because if the NAS says I support X and the Server
says I want X then the NAS MUST provide X.

When we say hint it means to me that its up to the NAS to determine
whether it delivers X. 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Nelson, David
> Sent: Thursday, September 08, 2005 2:19 PM
> To: radiusext@ops.ietf.org
> Subject: RE: Capabilities (was Re: AW: Review of 
> draft-ietf-geopriv-radius-lo-04.txt )
> 
> Alan DeKok Writes...
> 
> >   For RADIUS conversations that don't use Access-Challenge, the 
> > solution is to extend them to use Access-Challenge.  This is 
> > "fail-safe" under the current design, in that existing 
> implementations 
> > will treat unsupported Access-Challenge as reject.  The 
> method above 
> > for capability exchange can then be used to enforce capability 
> > requirements.
> 
> 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.
> 
> 
> --
> 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/>
> 

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