RE: [AAA-WG]: Support for Geopriv RADIUS attributes in Diameter

[<john.loughney@nokia.com>]

Hi Jari,

> I'd prefer the NASREQ approach.

I think that would be reasonable.  Do you think that this should be written-up 
anywhere?  Should I try to supply some text for the geopriv draft?

John

> john.loughney@nokia.com wrote:
> 
> >Hi all,
> >
> >I've gotten some queries, off-list, about how 3GPP should 
> handle the location 
> >AVPs that are defined in:
> >
> >http://www.ietf.org/internet-drafts/draft-ietf-geopriv-radius
> -lo-02.txt
> >
> >3GPP has defined the Wa interface, which is based on 
> Diameter, that will
> >interwork with RADIUS and will carry the RADIUS AVPs.  Would standard
> >NASREQ rules apply here (Diameter would just re-use the 
> RADIUS codes), or
> >should these AVPs also be defined in a seperate Diameter draft?
> >
> >The draft above is quite weak on how these attributes should 
> be handled
> >in Diameter, so I wanted to see what both the AAA WG and RADEXT WG 
> >thought.
> >
> >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/>