Issue: Transparency (e.g. NAS visibility of) CUI

["Nelson, David" <dnelson@enterasys.com>]

Oh, yeah... the template.  Sorry.  :-(

Description of issue: The transparency (e.g. NAS visibility) of CUI
Submitter name: Dave Nelson
Submitter email address: dnelson@enterasys.com
Date first submitted: December 21, 1004
Reference: (general CUI thread on the lsit)
Document: draft-ietf-radext-chargeable-user-id-00.txt
Comment type: T
Priority: S
Section: 2.1
Rationale/Explanation of issue:

Since CUI is intended for utilization at the NAS and at intermediate
Proxies in a way that is not possible using the Class attribute, what is
the utility of the opaque data format of CUI?  I understand that
opaqueness can be rendered transparent with the bilateral sharing of
proprietary information, pursuant to a business contract.  However, that
exception notwithstanding, if the intent of CUI is visibility and
utility to the NAS and to the Proxies, I suggest that the opaque data
format be removed from the draft, in the interest of global,
multi-vendor interoperability.

Requested change:

In Section 2.1, delete the following text:

    " 04 - Opaque string
         Opaque string is a value that is assigned to the user by the
         home network in an unspecified format, where the home network
         asserts that this value represents a particular user. "

and modify the following text, from:

     " 05 - reserved "
to:

     " 04-FF - reserved "


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