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

Re: Object identifier and type spaces in a rationalized RADIUS data model

To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Object identifier and type spaces in a rationalized RADIUS data model
From: Bernard Aboba <aboba@internaut.com>
Date: Wed, 9 Jun 2004 08:18:48 -0700 (PDT)
Cc: john.loughney@nokia.com, radiusext@ops.ietf.org
In-reply-to: <40C6E4EF.9050704@piuha.net>
References: <DADF50F5EC506B41A0F375ABEB3206360143C00F@esebe023.ntc.nokia.com> <40C6E4EF.9050704@piuha.net>

> > Quick question - have you looked at the backwards compatibility-ness
> > of this proposal?  If new implementations support it its important
> > that they don't break older implementations.

One way to handle this is for a NAS supporting the new attributes to send
an attribute in the new format indicating support for the new format. The
RADIUS server would then be able to send those attributes -- but if it
didn't receive the "compatibility" attribute it would be advised not to
send them.

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

References:
- RE: Object identifier and type spaces in a rationalized RADIUS data model
  - From: <john.loughney@nokia.com>
- Re: Object identifier and type spaces in a rationalized RADIUS data model
  - From: Jari Arkko <jari.arkko@piuha.net>

Prev by Date: Re: Object identifier and type spaces in a rationalized RADIUS data model
Next by Date: RE: Rationalizing the RADIUS data model
Previous by thread: Re: Object identifier and type spaces in a rationalized RADIUS data model
Next by thread: RE: Object identifier and type spaces in a rationalized RADIUS data model
Index(es):
- Date
- Thread