Re: [AAA-WG]: AW: Comments to draft-sterman-aaa-sip-03 and draft-ietf-aaa-sip-a pp-03

Jari Arkko <jari.arkko@piuha.net> Mon, 09 August 2004 13:46 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Mon, 09 Aug 2004 13:47:16 +0000
Message-ID: <41178038.9010909@piuha.net>
Date: Mon, 09 Aug 2004 16:46:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
Reply-To: jari.arkko@piuha.net
Organization: None
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
MIME-Version: 1.0
To: Bernard Aboba <aboba@internaut.com>
Cc: "Beck01, Wolfgang" <BeckW@t-systems.com>, radiusext@ops.ietf.org, Miguel Garcia <Miguel.An.Garcia@nokia.com>
Subject: Re: [AAA-WG]: AW: Comments to draft-sterman-aaa-sip-03 and draft-ietf-aaa-sip-a pp-03
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit

Wolfgang Beck wrote:

> After converting the draft to flat attributes, I tried to save attribute
> space. It is a scarce resource in RADIUS.

Bernard Aboba wrote:

> Also, saving attribute space is not a design goal of this document.
> Diameter compatibility *is* a design goal.

In general, I'd rather have a larger number of attributes
in a draft than cause problems for translation. Of course
we can build special cases for attributes, but I'd rather
have NASREQ-style completely automatic mapping (attribute =>
AVP from RADIUS space) or at least simple table driven
mapping (attribute => AVP from Diameter space with same
type).

Note: if RADIUS attribute space really runs out, we can
create more, through an IETF "vendor" attribute, for
instance.

--Jari

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

Re: [AAA-WG]: AW: Comments to draft-sterman-aaa-s… Jari Arkko
Re: [AAA-WG]: AW: Comments to draft-sterman-aaa-s… Bernard Aboba