Re: [q] CUI-04: NAS controlled?

[Barney Wolff <barney@databus.com>]

On Tue, Apr 12, 2005 at 07:30:19PM -0400, Greg Weber wrote:
> 
> >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.

We've been over this.  2865 allows ignoring unknown attributes, but
does not mandate it.  Since CUI is strictly for the benefit of the
sender of the Access-Request, if the NAS or proxy doesn't demand it,
the server has no reason to send it.

-- 
Barney Wolff         http://www.databus.com/bwresume.pdf
I never met a computer I didn't like.

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