RE: Comments to "RADIUS Attributes Extension "

["David Mariblanca (ML/EEM)" <david.mariblanca@ericsson.com>]

Thanks for the quick reply, Farid.
I see the NAS may need to associate the user with some identity. But (using your example) how does a NAS know who is 3456@anyisp.com ? 3456@anyisp.com means nothing.
Or is it the case that the NAS will use 3456@anyisp.com for example to report accounting information to other network element, where the mapping 3456@anyisp.com<->"real identity" exists ?

David.

-----Original Message-----
From: Adrangi, Farid [mailto:farid.adrangi@intel.com]
Sent: lunes, 14 de junio de 2004 23:54
To: David Mariblanca (ML/EEM); radiusext@ops.ietf.org
Subject: RE: Comments to "RADIUS Attributes Extension "


Hello David,
Thanks for your comments.  Please see my responses inline.
BR,
Farid


> -----Original Message-----
> From: David Mariblanca (ML/EEM) 
> [mailto:david.mariblanca@ericsson.com] 
> Sent: Monday, June 14, 2004 7:41 AM
> To: 'radiusext@ops.ietf.org'; Adrangi, Farid
> Subject: Comments to "RADIUS Attributes Extension "
> 
> 
> 
> Hi Farid and all,
> small comments to this paper
> 
> - Diameter should be considered (comment already given as I can see).
> 
Yes.  We should.
> - In User Alias Identity attribute, I don't see why a home 
> network operator may wish to use this it, if it is hiding the 
> user identity in other payload of the message. I mean, it the 
> home network is hiding the user identity it's because it 
> wants some kind of privacy for the user identity. So if this 
> attribute is used, such privacy would be broken. Even more, 
> if the Alias used is some identity with an standardized 
> format like E.164 or the IMSI.
> 

That is not the problem.  The problem is that the NAS needs to associate
the user with some identity when the user authenticates to the access
network using an anonymous id.  So, the home network needs to convey
some form of identity to the NAS for that user's session -- it does not
have to be the user's real identity.  For example, it could be
3456@anyisp.com.  Please let me know if this did not answer questions.

> - Also, this attribute seems at the beginning to be for all 
> purposes but later on its description is very focused on 
> charging functions.

We chose a generic name that can used for other purposes.  We can use
specific name like billable identity or chargeable user identity.
> 
> Regards,
> David.
> 
> 
> 
> 
> 

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