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

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



Hi John, Lionel & Jari,

I would assume that the concerns are because in 3GPP we do also
have the Diameter-Diameter case without any translation. The text
below and the draft does not address that case.

Cheers,
       Jouni


-----Original Message-----
From:	owner-radiusext@ops.ietf.org on behalf of john.loughney@nokia.com
Sent:	Mon 4/18/2005 1:42 PM
To:	lionel.morand@francetelecom.com; jari.arkko@kolumbus.fi
Cc:	aaa-wg@merit.edu; radiusext@ops.ietf.org
Subject:	RE: RE : [AAA-WG]: Support for Geopriv RADIUS attributes in Diameter
Hi Lionel,

> The following statement is not enough?
> 
> 8.  Diameter RADIUS Interoperability
> 
>    In deployments where RADIUS clients talk with DIAMETER servers or
>    DIAMETER clients talk with RADIUS servers then a translation agent
>    will be deployed and operate in accordance to the NASREQ
>    specification [14].

That was what I was wondering.  Some of the people who queried me about this
thought it wasn't enough; that's why I am checking with the rest of the
WG.

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