RE: Response to Issue 46

["Adrangi, Farid" <farid.adrangi@intel.com>]

You have a point, David.  We can add something like this to the draft:

"
The CUI represents an chargeable identity as defined by the business
relationship. Typically the CUI represents the identity of the actual
user
but it may also indicate other chargeable identities such as a group of
users.
"

Would that address your concern?

BR,
Farid

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Nelson, David
> Sent: Monday, January 17, 2005 10:24 AM
> To: radiusext@ops.ietf.org
> Subject: RE: Response to Issue 46 
> 
> 
> Farid Adrangi writes...
> 
> > Isn't the draft say that the CUI is an alias to user's real 
> identity?
> > Doesn't that mean that there needs to be a unique mapping 
> between CUI
> > and the actual user?
> 
> Not necessisarily.  The username dnelson@enterasys.com might 
> be aliased
> as engineering@enterasys.com, if the policy at Enterasys were to lump
> all employees with engineering job codes into a single class for alias
> identification purposes.  I don't see any text that would 
> preclude this
> kind of approach.
> 
> 
> 
> --
> 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/>
> 

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