[q] CUI-04: NAS controlled?

[Greg Weber <gdweber@cisco.com>]

From draft-ietf-radext-chargeable-user-id-04.txt Section 2.1:

   If a home RADIUS server that supports the CUI attribute receives an
   Access-Request packet containing a CUI (set to nul or otherwise), it
   MUST include the CUI attribute in the Access-Accept packet.
   Otherwise, if the Access-Request packet does not contain a CUI, the
   home RADIUS server MUST NOT include the CUI attribute in the
   Access-Accept packet.

Looking at the last sentence, that seems to mean that the server
cannot ever send CUI unless the NAS hints that it's desired.
Is that the intent?  As you point out in the draft, the NAS can
ignore CUI if it doesn't understand it.  It may be desirable to
not have the NAS send CUI in every request- even if the NAS 
understands how to handle CUI.  This seems to be an unnecessary
restriction on the server.

Comments?

Greg


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