Single RADIUS Class attribute supported by HP's Comware - Bug or Enhancement?

[Arran Cudbard-Bell]

On 30 May 2014, at 06:02, Nick Lowe <nick.lowe at gmail.com> wrote:

> Thanks!
> 
> They do return a single Class attribute so they are already
> impementing that SHOULD aspect of the RFC, just not properly as
> multiples must be supported if this feature is implemented.
> 
> "5.44.  Table of Attributes
> 
>   The following table provides a guide to which attributes may be found
>   in which kinds of packets, and in what quantity.
> 
>   Request   Accept   Reject   Challenge   #    Attribute
>   0         0+       0        0           25   Class"

I'd say HP are doing a pretty good job of being RFC compliant by only 
returning a single value. It's what the vast majority of vendors do.

Why do you need more than 253 bytes of class string anyway?

Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team

FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 881 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20140530/3a3925e3/attachment.pgp>