Re: Comments on "RADIUS Design Guidelines" document

[Alan DeKok <aland@deployingradius.com>]

Bernard Aboba wrote:
>> > Since [EXTEN] defines extensions to the standard RADIUS attribute
>> > space and this section is talking about VSAs, the reference is a bit
>> > confusing. Is the intent to suggest that VSAs other than type 0
>> > can also use the [EXTEN] format?
>>
>> Yes.
> 
> You might say, "with a different vendor-type" to make that clear.

  OK.  I'll add some text to that effect.

>> RFC 2869, Section 5.19 (Table of Attributes) indicates that
>> Connect-Info is permitted in Access-Request packets. Admins would like
>> to use this information to perform policy checks.
> 
> OK.  The question still remains, though.  If an attribute is only used in
> Accounting-Request packets, does the argument against complex
> attributes still apply? 

  My preference would be to say yes, especially where the contents of
that attribute are interpreted by *later* policies on the server.

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