RE: Chargeable-User-Identity

["Glen Zorn" <glenzorn@comcast.net>]

> Pasi Eronen writes...
> 
> > Many of the other attributes in RFC 5580 indeed have
> > complex encodings, but using Operator-Name doesn't
> > necessarily require anything new from the RADIUS server...
> > The "Namespace ID" values are intentionally printable ASCII
> > digits, so you could treat the whole attribute as one string,
> > and put something like 'if Operator-Name == "1example.com"
> > then...' in your RADIUS configuration.
> 
> Yeah.
> 
> At the risk of appearing to beat a very dead horse, I'll observe that
> the
> notion of RADIUS attribute re-use, outside the original area of
> application,
> is yet another reason to use simple attributes that comply with the
> RADIUS
> Design Guidelines.

OK, I'll bite: why?  Either the server & client support the attributes in
question or not, regardless of whether they follow those guidelines.  

> 
> Sigh.

Indeed.



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