RE: NAI decoration: User Identity issues

[Bernard Aboba <aboba@internaut.com>]

> The details of what is placed in the User-Alias will be worked out between
> the operators when they negotiate their roaming agreements.

If this were the case then the Class attribute would suffice.  To
distinguish itself from Class, the local operator MUST be sure that a
billable identity is contained within the attribute.  If it "could be
anything" then this assurance does not exist (as it does not exist for
Class).  Introducing multiple attribute also clouds the picture. How does
the operator know which one (if any) of the operators contains a billable
identity?

And if intermediaries decorate this attribute then you have
re-introduced all the problems that already existed with User-Name.


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