1-7No. Attribute No. Attribute42 Acct-Input-Octets 89 (unassigned)43 Acct-Output-Octets 90 Tunnel-Client-Auth-id44 Acct-Session-Id 91 Tunnel-Server-Auth-idThe attribute types listed in Table 1-2 are defined by RFC 2865, RFC 2866, RFC 2867, and RFC 2868.Extended RADIUS AttributesThe RADIUS protocol features excellent extensibility. Attribute 26 (Vender-Specific) defined by RFC2865 allows a vender to define extended attributes to implement functions that the standard RADIUSprotocol does not provide.A vendor can encapsulate multiple type-length-value (TLV) sub-attributes in RADIUS packets forextension in applications. As shown in Figure 1-5, a sub-attribute that can be encapsulated in Attribute26 consists of the following four parts:z Vendor-ID (four bytes): Indicates the ID of the vendor. Its most significant byte is 0 and the otherthree bytes contain a code complying with RFC 1700. The vendor ID of H3C is 2011.z Vendor-Type: Indicates the type of the sub-attribute.z Vendor-Length: Indicates the length of the sub-attribute.z Vendor-Data: Indicates the contents of the sub-attribute.Figure 1-5 Segment of a RADIUS packet containing an extended attributeProtocols and StandardsThe protocols and standards related to AAA and RADIUS include:z RFC 2865: Remote Authentication Dial In User Service (RADIUS)z RFC 2866: RADIUS Accountingz RFC 2867: RADIUS Accounting Modifications for Tunnel Protocol Supportz RFC 2868: RADIUS Attributes for Tunnel Protocol Supportz RFC 2869: RADIUS Extensions
