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

[<john.loughney@nokia.com>]

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

So, a few points:

 

This draft should say that because Diameter Base inherits the RADIUS code space, this is applicable

for Diameter.  Section 4.1 of RFC 3588 says:

   AVP Code
      The AVP Code, combined with the Vendor-Id field, identifies the
      attribute uniquely.  AVP numbers 1 through 255 are reserved for
      backward compatibility with RADIUS, without setting the Vendor-Id
      field.  AVP numbers 256 and above are used for Diameter, which are
      allocated by IANA (see Section 11.1).

Maybe some text should be added so readers know that.  

Some text about using NASREQ for protocol translation could be added, in addition to what is there already.

Additionally, I think that the IANA considerations should also request that IANA update the Diameter registry
with this info as well.

John

 -----Original Message-----
From: ext [mailto:jouni.korhonen@teliasonera.com]
Sent: 18 April, 2005 14:16
To: Loughney John (Nokia-NRC/Helsinki); 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 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/>