RE: The RADIUS attribute space: an assessment

["Avi Lior" <avi@bridgewatersystems.com>]

Some update:

Now that Diameter has been standerdized, 3GPP2 has started to include
Diameter in the Packet Data Network.  RADIUS is still mandatory and now
Vendors are free to deliver products based on Diameter.  Operators will
now have a choice.  Support for NASREQ, Mobile IP, EAP Application and
Credit Control.

WiMAX release 1.0 is based exclusively on RADIUS. However it is
anticipated that Diameter will come in the next release (1.5) I will
certainly try to bring it in.

We all know about the uses of Diameter in 3GPP.

I think that Diameter POs will start to come in the Carrier market.  But
it will take years before Diameter will overtake RADIUS.

When we talk about Diameter vs RADIUS etc we have to consider that there
are different deployement and business drivers to consider.  There is no
right answer except for one:  let the market decide.

I will continue to do work on (extend) RADIUS in the IETF or elsewhere
as long as my customers are willing to pay for that work.

I will also continue to work on Diameter because I belive that customers
will start to want it.

I think that we should extend the RADIUS attribute space in the IETF and
support new features etc...

The work mentioned by Bernard in Mobile IPv4 that requires 31 attributes
is a direct result of the philosophy of some in RADEXT that want flat
attribute space.  If we did the work in MIPv4 using complex attribute
encoding we would probably only need 10 attributes or less.

Therefore I think we should allow more complex attribute encoding. 

I am somewhat puzzled by Glen: on one hand he is yelling "Pull the plug"
on the other hand it seems that he is the RADIUS poster boy judging by
the number of RADIUS drafts he has floating around.

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