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

RE: Review of draft-ietf-geopriv-radius-lo-04.txt



> And blindly requesting for location information (as you propose) I run
> the risk of having a rejection by getting to a NAS that does not support
> Challenge in the first place. 

The only reason a RADIUS server will need to send an Access-Challenge is 
if it *requires* location and it is not present.  In that case, the RADIUS 
server cannot allow access if location isn't provided.  

If the RADIUS server doesn't require location, then it can just request 
location in the Access-Accept.  If it gets it, great.  If not, it is 
willing to live with out it. 

In either case (mandatory or optional), capability advertisement by the 
NAS is irrelevant. 


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