RE: Extending RADIUS Attribute Space

[Avi Lior <avi@bridgewatersystems.com>]

See inline.

> -----Original Message-----
> From: Randy Bush [mailto:randy@psg.com] 
> Sent: August 25, 2003 2:31 AM
> To: Avi Lior
> Cc: 'Nelson, David'; 'radiusext@ops.ietf.org'
> Subject: RE: Extending RADIUS Attribute Space
> 
> 
> > My point is this, so far we have a request for addressing 
> an issue for 
> > allowing an attribute to be larger then that which is allowed by 
> > RADIUS. Instead of inventing a specific scheme for that I 
> am proposing 
> > to reuse a solution that already exists that will address 
> that problem 
> > *plus* another one.
> 
> good idea.  you might want to look at the aaa diameter work.  
> let's not reinvent it piece by piece.

I am totally familiar with Diameter. Are you suggesting that if I need
larger attributes I should use Diameter?

If you are then, I will be fine with that.  However, Diameter is only
requested by 3GPP and new features in 3GPP2.  The rest of the world, is
using RADIUS and will continue to use RADIUS for a long time to come.

I thought that this RADIUS EXT group is forming to help address some of the
new needs in RADIUS.  So I am trying to solve these types of problems.  I am
not trying to reinvent Diameter piece by piece.  I don't even see how you
get to that conclusion from my message.

All we wanted to do was:
A) As a minimum, create a mechanism to create more RADIUS attribute types in
a way that is backwards compatible with existing RADIUS.

B) As part of that we could provide a way to increase the message size
(someone asked for that). This again can be done easily by borrowing from
EAP and PEAP; and

C) Optionally address the issue of how to extend a message again using EAP.

If these 3 items are reinventing Diameter then perhaps we shouldn't have
done Diameter.

Avi

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