Re: Issue with Guidelines document

["Greg Weber" <gdweber@gmail.com>]

On Sun, Dec 14, 2008 at 12:53 PM, Alan DeKok <aland@deployingradius.com> wrote:
> Bernard Aboba wrote:
>> In this particular case, while RFC 2866 indicates that there are no
>> required attributes in an Accounting-Response, it doesn't prohibit
>> them.
>
>  Hmm...
>
> 5.13.  Table of Attributes
>
>   The following table provides a guide to which attributes may be found
>   in Accounting-Request packets.  No attributes should be found in
>   Accounting-Response packets except Proxy-State and possibly Vendor-
>   Specific.
>
>  That seems pretty clear.  Nothing but Proxy-State && VSA's.
>
>>  So is the issue the inclusion of attributes, or is it the use
>> of those attributes?
>
>  I would like to know what it *means* to have VSA's in an
> Accounting-Response.  What does the NAS do with them?  Log them?  Ignore
> them?  Change it's behavior?

This can be used to communicate server load or pending planned downtime
information back to the NAS which then can be used in server selection
algorithms.  I believe there's a commercial server in the PacketCable space
doing this (for voice gateway RADIUS clients).  Also have heard some
discussion about a server being able to dynamically adjust the interim
accounting
record interval by setting a VSA in the accounting response (mimicking a
Diameter feature), but I'm not sure if that's implemented by any servers.

But it sounds like you're talking about static attribute values below.
Anyway, I don't think we should try to prohibit VSAs in accounting responses.

Greg

>
>  I'm seeing people who insist that they have to put attributes in an
> Accounting-Response.  Sometimes they claim their NAS requires it.  But I
> can't get an explanation as to *why*.
>
>  Alan DeKok.
>
> --
> 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/>