IETF Logo Mail Archive

RE: Questions on modified Extended Attribute format?

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 08 January 2008 09:28 UTC

Return-path: <owner-radiusext@ops.ietf.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JCAlU-0006NE-A9 for radext-archive-IeZ9sae2@lists.ietf.org; Tue, 08 Jan 2008 04:28:56 -0500
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JCAlT-0003R9-NG for radext-archive-IeZ9sae2@lists.ietf.org; Tue, 08 Jan 2008 04:28:56 -0500
Received: from majordom by psg.com with local (Exim 4.68 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1JCAhF-000Bwx-0Z for radiusext-data@psg.com; Tue, 08 Jan 2008 09:24:33 +0000
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.3
Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com) by psg.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.68 (FreeBSD)) (envelope-from <dromasca@avaya.com>) id 1JCAhC-000BwP-3H for radiusext@ops.ietf.org; Tue, 08 Jan 2008 09:24:31 +0000
X-IronPort-AV: E=Sophos;i="4.24,257,1196658000"; d="scan'208";a="84710663"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 08 Jan 2008 04:24:23 -0500
X-IronPort-AV: E=Sophos;i="4.24,257,1196658000"; d="scan'208";a="140337442"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 08 Jan 2008 04:23:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Questions on modified Extended Attribute format?
Date: Tue, 08 Jan 2008 10:23:40 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A047BF686@307622ANEX5.global.avaya.com>
In-Reply-To: <003e01c851c1$fad525f0$f07f71d0$@net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Questions on modified Extended Attribute format?
Thread-Index: AchNvxvE95gozpjSQoKAVguApoAI+AAZAbTwAO0zArA=
References: <003401c83a92$db6ed850$924c88f0$@net> <47729084.8060206@nitros9.org> <005d01c847e8$20c81f30$62585d90$@net> <4772A741.40303@nitros9.org> <007e01c847fa$cbae1a00$630a4e00$@net> <47732E9D.4030803@nitros9.org> <00b401c848e0$2f0e9c60$8d2bd520$@net> <4774B67D.7040603@nitros9.org> <005601c8496f$9e430910$dac91b30$@net> <477C60D6.3020008@nitros9.org> <003e01c851c1$fad525f0$f07f71d0$@net>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Glen Zorn <glenzorn@comcast.net>, Alan DeKok <aland@nitros9.org>
Cc: radiusext@ops.ietf.org
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352


 
 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Glen Zorn
> Sent: Tuesday, January 08, 2008 8:45 AM
> To: 'Alan DeKok'
> Cc: radiusext@ops.ietf.org
> Subject: RE: Questions on modified Extended Attribute format?
> 
> Glen Zorn wrote:
> 
> > As I said, put that way or any other way you like, ANY change is 
> > incompatible with existing deployments.  If one were to add a new
> "standard"
> > attribute (in the old format or the proposed VSA-like format or any 
> > other) it would be incompatible with existing deployments.
> 
>   That isn't the point.  Everyone accepts that 
> implementations have to be updated to handle new standards.  
> One of the major efforts in RADIUS has been to maintain 
> backwards compatibility with existing deployments.
> [gwz]
> You keep saying that but I really don't know where you get 
> this funny idea.
> [/gwz]
> 

The current RADEXT charter is quite explicit about the requirements for
backwards compatibility. 

- All RADIUS work MUST be backward compatible with existing RADIUS 
RFCs,
including RFCs 2618-2621, 2865-2869, 3162, 3575, 3576, 3579, and 3580.

Dan

--
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.46.0 | Report a Bug | By Email | System Status