RE: Questions on modified Extended Attribute format?

["Matt Holdrege" <Matt.Holdrege@strixsystems.com>]

While I completely understand the disappointment with the IETF RADIUS
development process I don't think that it is a good idea to give up on
alignment. Alignment is a VERY serious issue given that mixed 802.11 and
802.16 networks will be the norm for many, many years to come. 

And although there are a few WiMax implementations out now, 802.16e in a
real sense still hasn't started yet so I don't see any serious problem
with making changes. 

-Matt


-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of Avi Lior
Sent: Wednesday, January 09, 2008 4:17 AM
To: David B. Nelson; radiusext@ops.ietf.org
Subject: RE: Questions on modified Extended Attribute format?

WiMAX did try to align at one time.  But things have changed.

And to get WiMAX to align again with the IETF would be hard now.  We
would need a good reason to change given that we have implementation.
But not impossible since lots of things are changing.

But to be 100 clear, the WiMAX encoding is WiMAX's encoding and not
IETF.  While compatiblity is desirable it is not required at this stage.

It would have been nice if the IETF addressed the issues -- much --
earlier.  

Note in WiMAX we use the M bit but dont use the tag part. 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of David B. Nelson
> Sent: Wednesday, December 26, 2007 9:59 PM
> To: radiusext@ops.ietf.org
> Subject: RE: Questions on modified Extended Attribute format?
> 
> Bernard Aboba writes...
>  
> > >  WiMAX uses the same attribute format as proposed here.  Changes 
> > > that are incompatible with WiMAX should be discouraged.
> > 
> > I would agree.   If the extensions remain compatible with WiMAX then
> > the amount of code duplication will be minimized.
> 
> I'm not so sure that I agree.  We should do what's right for 
> the RADIUS community.  If that happens to be compatible with 
> WiMAX, then great.
> 
> 
> 
> --
> 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/>
> 

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

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