IETF Logo Mail Archive

Re: questions on draft-mariblanca-aaa-eap-lla-00.txt

Bernard Aboba <aboba@internaut.com> Sat, 17 July 2004 14:37 UTC

Envelope-to: radiusext-data@psg.com
Delivery-date: Sat, 17 Jul 2004 14:40:40 +0000
Date: Sat, 17 Jul 2004 07:37:58 -0700
From: Bernard Aboba <aboba@internaut.com>
To: Jari Arkko <jari.arkko@piuha.net>
cc: radiusext@ops.ietf.org, "David Mariblanca (EE/EEM)" <david.mariblanca@ericsson.com>
Subject: Re: questions on draft-mariblanca-aaa-eap-lla-00.txt
Message-ID: <Pine.LNX.4.56.0407170735410.27904@internaut.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"

> But since they do exist, we are not going to do extensions that
> break backwards compatibility without a very good reason. This
> I believe is independent of any potential attempts to extend
> the data model: data model extensions, if any, would only apply
> to new attributes.

Right.  There is a proposal on the table to provide a well-defined data
model (including sub-attribute support) within an extended attribute
space, whose use will be explicitly negotiated between the RADIUS client
and server.  However, the charter explicitly forbids any non-backward
compatible changes within the standard RADIUS attribute space.

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

v2.23.0 | Report a Bug | By Email