RE: RE: draft-jones-radius-geopriv

[Avi Lior <avi@bridgewatersystems.com>]

John,
Perhaps I can jump in here. 

One reason for location information is as identified in this draft
http://www.ietf.org/internet-drafts/draft-adrangi-radiusext-location-informa
tion-00.txt

Location information can be used during Authorization to determine whether
the subscriber is allowed access at a given location etc...

Location information is also needed during billing.  For example the tax
rate may be based on the location where the user has accessed the network as
opposed to the location of the home network.

This type of location information needs to be transported to the home
network and must only be used for that intention.

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com] 
> Sent: February 17, 2004 12:40 PM
> To: mark.jones@bridgewatersystems.com; jschnizl@cisco.com
> Cc: radiusext@ops.ietf.org; geopriv@ietf.org
> Subject: RE: RE: draft-jones-radius-geopriv
> 
> 
> Hi Mark,
> 
> > 1) Provide guidelines for RADIUS implementers needing to transport 
> > subscriber location information and remain compliant with 
> the GEOPRIV 
> > privacy and security requirements. We also wanted to examine the 
> > various roaming scenarios and provide recommendations on 
> how location 
> > information should be sent between AAA servers using RADIUS.
> 
> Question on the second part.  What are the use cases for 
> transporting location info?  I've never really considered 
> RADIUS a transport protocol, so this seems like an odd usage 
> of RADIUS.
> 
> thanks,
> John
> 
> --
> 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/>