[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: RADIUS Calling-Station-Id for WiMAX
- To: "'Avi Lior'" <firstname.lastname@example.org>, "'David B. Nelson'" <email@example.com>, "'Glen Zorn'" <firstname.lastname@example.org>, "'Ray Bell'" <email@example.com>, "'Matt Holdrege'" <Matt.Holdrege@strixsystems.com>, "'Bernard Aboba'" <firstname.lastname@example.org>, "'Congdon, Paul T \(ProCurve\)'" <email@example.com>, "'Mike Bean'" <firstname.lastname@example.org>, <email@example.com>, "'Dan Romascanu'" <firstname.lastname@example.org>
- Subject: RE: RADIUS Calling-Station-Id for WiMAX
- From: "David B. Nelson" <email@example.com>
- Date: Thu, 11 Sep 2008 13:44:21 -0400
- In-reply-to: <8A8CFE8F89C38B41A749C19328C76D6308A47A76AC@exchange02.bridgewatersys.com>
- Organization: Elbrys Networks, Inc.
- References: <A0941C2137BCA349AA3D32CDA3AEBCA11868B8@tuna.grid-net.com> <000601c9136c$a48adf10$eda09d30$@net> <8A8CFE8F89C38B41A749C19328C76D6308A47A7662@exchange02.bridgewatersys.com> <685F3FC2BA114A07BBED15A9766D544E@NEWTON603> <8A8CFE8F89C38B41A749C19328C76D6308A47A76AC@exchange02.bridgewatersys.com>
> Exactly so why are we worried about how the attribute is formatted.
> Specifically for humans. The dash-notation or colon-notation is used by
> humans or text based protocols. If RADIUS wanted to stay out of the
> presentation layer business it should have kept the MAC codification as it
> appears over the wire at the NAS. Conversion to other formats should be
> done as late as possible.
Uhhh... I think you're missing a key point here. There is no presentation
layer -- the "presentation" is hard-coded into the attribute definitions.
If the attribute content is intended only for human consumption, as are most
RADIUS Accounting attributes, then it truly doesn't matter. OTOH, if the
RADIUS server is going to make some access control policy decision, or in
general customize the session to be delivered, based on the content of an
attribute, then that attribute had better have a standardized format, if we
are to have any expectation of multi-vendor, global interoperability.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.