[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RADIUS Calling-Station-Id for WiMAX
- To: "'Avi Lior'" <avi@bridgewatersystems.com>, "'Glen Zorn'" <glenzorn@comcast.net>, "'Ray Bell'" <ray@grid-net.com>, "'Matt Holdrege'" <Matt.Holdrege@strixsystems.com>, "'Bernard Aboba'" <bernard_aboba@hotmail.com>, "'Congdon, Paul T \(ProCurve\)'" <paul.congdon@hp.com>, "'Mike Bean'" <bean@alcatel-lucent.com>, <radiusext@ops.ietf.org>, "'Dan Romascanu'" <dromasca@avaya.com>
- Subject: RE: RADIUS Calling-Station-Id for WiMAX
- From: "David B. Nelson" <d.b.nelson@comcast.net>
- Date: Wed, 10 Sep 2008 15:24:58 -0400
- In-reply-to: <8A8CFE8F89C38B41A749C19328C76D6308A47A7662@exchange02.bridgewatersys.com>
- References: <A0941C2137BCA349AA3D32CDA3AEBCA11868B8@tuna.grid-net.com> <000601c9136c$a48adf10$eda09d30$@net> <8A8CFE8F89C38B41A749C19328C76D6308A47A7662@exchange02.bridgewatersys.com>
Avi Lior writes...
> It seems to me that a binary representation would be a more
> appropriate treatment for this value.
Perhaps, but RFC 3580 followed many years of tradition in choosing the
dashed-ASCII representation.
> So it is best to leave the presentation to a presentation layer
> and not the RADIUS layer.
Well, no. The syntax and semantics of RADIUS attribute are a matter of the
RADIUS protocol. There is no presentation layer, and contrary to commonly
held belief, RADIUS is not simply a transport protocol. :-)
> It isn't busted.
Not within the "walled garden" of WiMAX. On a global interoperability
scale, I claim that it is broken.
> And changing it now will break backwards compatibility.
Yes. The question is whether to "cowboy up" and fix it now.
--
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/>