Arran Cudbard-Bell wrote:
> Yes the RFC describes how parties should process the attribute, but it
> doesn't explicitly define an intended use.
Yup. "Stuff happens with Class. Cool stuff! Honest!"
Welcome to the RADIUS RFC's. Hence RFC 5080, and others.
Alan DeKok.
-
List info/subscrib
Phil Mayers wrote:
Was there an RFC that went on to define the proper usage of the Class
attribute, or is it's usage still ambiguous ?
Ambiguous how? The RFC seems pretty specific to me; the field is NOT to
be interpreted by the NAS, is generated in the Access-Accept and sent in
Accounting-Re
Was there an RFC that went on to define the proper usage of the Class
attribute, or is it's usage still ambiguous ?
Ambiguous how? The RFC seems pretty specific to me; the field is NOT to
be interpreted by the NAS, is generated in the Access-Accept and sent in
Accounting-Request - i.e. "it's l
Hi,
RFC 2865:
5.25. Class
Description
This Attribute is available to be sent by the server to the client
in an Access-Accept and SHOULD be sent unmodified by the client to
the accounting server as part of the Accounting-Request packet if
accounting is supported. The cli
4 matches
Mail list logo
