# DSL Forum VSAs in AAA Access and Accounting Messages

JunosE Software supports the inclusion of a set of DSL Forum vendor-specific attributes (VSAs) in the following AAA access and accounting messages:

- Access-Request
- Acct-Start
- Acct-Stop
- Interim-Acct (if Acct-Stop messages are specified)
- CoA-Request

The DSL Forum VSAs convey information about the subscriber associated with the digital subscriber line (DSL) and the data rate of the DSL. When you use radius include dsl-forum-attributes to enable inclusion of the DSL Forum VSAs in these AAA messages, the router includes all of the attributes listed in Table 44 in the specified message, provided that the VSA is available in the information that the router receives from the digital subscriber line access multiplexer (DSLAM).

| Note: JunosE Software also supports several Juniper Networks VSAs that you can use to include DSL-related information. See Juniper Networks VSAs .

Table 44 lists the DSL Forum VSAs supported by JunosE Software in Access-Request, Acct-Start, Acct-Stop, (if Acct-Stop is specified) Interim-Acct, and CoA-Request messages. JunosE Software uses the vendor ID assigned to the DSL Forum (3561, or DE9 in hexadecimal format) by the Internet Assigned Numbers Authority (IANA).

For information about configuring inclusion of the DSL Forum VSAs, see DSL Forum Vendor-Specific Attributes. For a detailed description of the DSL Forum VSAs supported by JunosE Software, see DSL Forum VSAs .

Table 44: DSL Forum (Vendor ID 3561) VSAs Supported in AAA Access and Accounting Messages

Attribute Number | Attribute Name | Access-Request | Acct-Start | Acct-Stop | Interim-Acct | CoA-Request
--- | --- | --- | --- | --- | --- | ---
[26-1] | Agent-Circuit-Id | ✓ | ✓ | ✓ | ✓ | ✓
[26-2] | Agent-Remote-Id | ✓ | ✓ | ✓ | ✓ | ✓
[26-129] | Actual-Data-Rate-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-130] | Actual-Data-Rate-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-131] | Minimum-Data-Rate-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-132] | Minimum-Data-Rate-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-133] | Attainable-Data-Rate-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-134] | Attainable-Data-Rate-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-135] | Maximum-Data-Rate-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-136] | Maximum-Data-Rate-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-137] | Minimum-Data-Rate-Upstream-Low-Power | ✓ | ✓ | ✓ | ✓ | –
[26-138] | Minimum-Data-Rate-Downstream-Low-Power | ✓ | ✓ | ✓ | ✓ | –
[26-139] | Maximum-Interleaving-Delay-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-140] | Actual-Interleaving-Delay-Upstream | ✓ | ✓ | ✓ | ✓ | –
[26-141] | Maximum-Interleaving-Delay-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-142] | Actual-Interleaving-Delay-Downstream | ✓ | ✓ | ✓ | ✓ | –
[26-144] | Access-Loop-Encapsulation | ✓ | ✓ | ✓ | ✓ | –
[26-254] | IWF-Session | ✓ | ✓ | ✓ | ✓ | –