Class attribute, RFC Specified usage of ...
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 client MUST NOT interpret the attribute locally. A summary of the Class Attribute format is shown below. The fields are transmitted from left to right. 0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- | Type | Length | String ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Type 25 for Class. Length >= 3 String The String field is one or more octets. The actual format of the information is site or application specific, and a robust implementation SHOULD support the field as undistinguished octets. The codification of the range of allowed usage of this field is outside the scope of this specification. Was there an RFC that went on to define the proper usage of the Class attribute, or is it's usage still ambiguous ? I know some people use it to link accounting data to an authentication attempt.... Thanks, Arran -- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk) Authentication, Authorisation and Accounting Officer Infrastructure Services | ENG1 E1-1-08 University Of Sussex, Brighton EXT:01273 873900 | INT: 3900
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 local to the radius server, do what you like with it".
I know some people use it to link accounting data to an authentication attempt....
That's one (common) use. There are others e.g. I've used it to signal to the accounting server the type of NAS so that the exact method for kicking a session is known purely from the SQL accounting info.
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-Request - i.e. "it's local to the radius server, do what you like with it".
Yes the RFC describes how parties should process the attribute, but it doesn't explicitly define an intended use.
I know some people use it to link accounting data to an authentication attempt....
That's one (common) use. There are others e.g. I've used it to signal to the accounting server the type of NAS so that the exact method for kicking a session is known purely from the SQL accounting info.
Heh, thats a neat idea :) Thanks, Arran
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
Arran Cudbard-Bell -
Phil Mayers