Re: -01 version of Chargeable User Identity

[Greg Weber <gdweber@cisco.com>]

Hi Farid,
A question on how -01 attempts to resolve a particular
part of issue #14.

  From -00:
                       The NAS or the access network AAA server MUST 
      include  this  attribute  in  the  Accounting  Requests  (Start, 
      Interim, and Stop) messages if it was included in the Access 
      Accept message. 
  
  From #14:
      [BA] I don't understand how backward compatibility is achieved. 
      How is a RADIUS server to know whether the NAS supports the CUI 
      attribute?

  -01 adds:
      In cases where the home RADIUS server cannot determine the NAS 
      support for CUI attribute, it MUST send both the UserName (1) 
      attribute and CUI attribute, with the understanding that if the 
      NAS supports the CUI attribute the CUI attribute will override 
      the identity portion the UserName (1) attribute.  That is, the 
      UserName(1) attribute will be used for routing and the CUI 
      attribute will be used for identity purposes. 

But the additional text does not obviate the still existing
excerpt from the -00 draft.  -01 still says that the NAS
MUST send the new attribute if it is received and that is 
a compatibility problem.

Greg

> 
> Hi all,
> The version -01 should appear on ID repository soon.  In the mean time,
> you can access the draft here :
> http://mng.ctgisp.com/IETF/RADIUSEXT/draft-adrangi-radius-chargeable-use
> r-id-01.txt.
> 
> The -01 update addresses the two issues (issue 13 and 14) submitted
> against the draft by David and Bernard respectively - please see
> http://www.drizzle.com/~aboba/RADEXT/#Issue%2014 for the detailed
> descriptions of the issues.
> 
> 
> Bernard,
> 
> Regarding two of your comments,
> 
> - Made a clarification on encoded format for CUI string.  But, we
> weren't sure if you were also questioning the proposed
> XX:YYYYYYYYYY format rather than just NAI or other encoding supported by
> Username.   
> 
> - Diameter translation /CoA message comment, are you suggesting to
> prohibit the user of the attribute in COA/Disconnect message?  Please
> note that the CUI is for identifying the user session than username.  
> 
> BR,
> Farid
> 
> --
> 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/>