7 Network Working Group V. Mammoliti
8 Request for Comments: 4679 G. Zorn
9 Category: Informational Cisco Systems
11 Redback Networks, Inc.
17 DSL Forum Vendor-Specific RADIUS Attributes
21 This memo provides information for the Internet community. It does
22 not specify an Internet standard of any kind. Distribution of this
27 Copyright (C) The Internet Society (2006).
31 This RFC is not a candidate for any level of Internet Standard. The
32 IETF disclaims any knowledge of the fitness of this RFC for any
33 purpose and in particular notes that the decision to publish is not
34 based on IETF review for such things as security, congestion control,
35 or inappropriate interaction with deployed protocols. The RFC Editor
36 has chosen to publish this document at its discretion. Readers of
37 this document should exercise caution in evaluating its value for
38 implementation and deployment. See RFC 3932 for more information.
42 This document describes the set of Remote Authentication Dial-In User
43 Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL
46 These attributes are designed to transport Digital Subscriber Line
47 (DSL) information that is not supported by the standard RADIUS
48 attribute set. It is expected that this document will be updated if
49 and when the DSL Forum defines additional vendor-specific attributes,
50 since its primary purpose is to provide a reference for DSL equipment
51 vendors wishing to interoperate with other vendors' products.
58 Mammoliti, et al. Informational [Page 1]
60 RFC 4679 DSL Forum RADIUS VSA September 2006
65 1. Introduction ....................................................3
66 2. Terminology .....................................................3
67 2.1. Requirements Language ......................................3
68 2.2. Technical Terms and Acronyms ...............................3
69 3. Attributes ......................................................5
70 3.1. DSL Forum RADIUS VSA Definition ............................5
71 3.2. DSL Forum Vendor Specific Sub-Attribute Encoding ...........6
72 3.3. Sub-attribute Definitions ..................................6
73 3.3.1. Agent-Circuit-Id ....................................6
74 3.3.2. Agent-Remote-Id .....................................8
75 3.3.3. Actual-Data-Rate-Upstream ...........................9
76 3.3.4. Actual-Data-Rate-Downstream .........................9
77 3.3.5. Minimum-Data-Rate-Upstream .........................10
78 3.3.6. Minimum-Data-Rate-Downstream .......................11
79 3.3.7. Attainable-Data-Rate-Upstream ......................11
80 3.3.8. Attainable-Data-Rate-Downstream ....................12
81 3.3.9. Maximum-Data-Rate-Upstream .........................13
82 3.3.10. Maximum-Data-Rate-Downstream ......................13
83 3.3.11. Minimum-Data-Rate-Upstream-Low-Power ..............14
84 3.3.12. Minimum-Data-Rate-Downstream-Low-Power ............15
85 3.3.13. Maximum-Interleaving-Delay-Upstream ...............16
86 3.3.14. Actual-Interleaving-Delay-Upstream ................16
87 3.3.15. Maximum-Interleaving-Delay-Downstream .............17
88 3.3.16. Actual-Interleaving-Delay-Downstream ..............18
89 3.3.17. Access-Loop-Encapsulation .........................19
90 3.3.18. IWF-Session .......................................20
91 4. Table of Attributes ............................................21
92 5. Security Considerations ........................................21
93 6. References .....................................................22
94 6.1. Normative References ......................................22
95 6.2. Informative References ....................................22
114 Mammoliti, et al. Informational [Page 2]
116 RFC 4679 DSL Forum RADIUS VSA September 2006
121 The DSL Forum has created additional RADIUS [RFC2865] [RFC2866]
122 vendor-specific attributes to carry DSL line identification and
123 characterization information. This information is forwarded from the
124 Access Node/DSLAM to the BRAS via Vendor-Specific PPPoE Tags
125 [RFC2516], DHCP Relay Options [RFC3046], and Vendor-Specific
126 Information Suboptions [RFC4243]. This document describes the
127 subscriber line identification and characterization information and
128 its mapping to RADIUS VSAs by the BRAS.
130 The information acquired may be used to provide authentication and
131 accounting functionality. It may also be collected and used for
132 management and troubleshooting purposes.
136 The following sections define the usage and meaning of certain
137 specialized terms in the context of this document.
139 2.1. Requirements Language
141 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
142 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
143 document are to be interpreted as described in [RFC2119].
145 2.2. Technical Terms and Acronyms
148 ATM Adaption Layer 5 [ITU.I363-5.1996]
151 The Access Node/DSLAM is a DSL signal terminator that contains a
152 minimum of one Ethernet interface that serves as its northbound
153 interface into which it aggregates traffic from several
154 Asynchronous Transfer Mode (ATM)-based (subscriber ports) or
155 Ethernet-based southbound interfaces.
158 Broadband Network Gateway. A BNG is an IP edge router where
159 bandwidth and QoS policies are applied; the functions performed by
160 a BRAS are a superset of those performed by a BNG.
170 Mammoliti, et al. Informational [Page 3]
172 RFC 4679 DSL Forum RADIUS VSA September 2006
176 Broadband Remote Access Server. A BRAS is a BNG and is the
177 aggregation point for the subscriber traffic. It provides
178 aggregation capabilities (e.g., IP, PPP, Ethernet) between the
179 access network and the core network. Beyond its aggregation
180 function, the BRAS is also an injection point for policy
181 management and IP QoS in the access network.
184 Digital Subscriber Line. DSL is a technology that allows digital
185 data transmission over wires in the local telephone network.
188 Digital Subscriber Line Access Multiplexer. DSLAM is a device
189 that terminates DSL subscriber lines. The data is aggregated and
190 forwarded to ATM- or Ethernet-based aggregation networks.
193 Frame Check Sequence. The FCS is a checksum added to an Ethernet
194 frame for error detection/correction purposes.
200 Interworking Function. The set of functions required for
201 interconnecting two networks of different technologies (e.g., ATM
202 and Ethernet). IWF is utilized to enable the carriage of PPP over
203 ATM (PPPoA) traffic over PPPoE.
226 Mammoliti, et al. Informational [Page 4]
228 RFC 4679 DSL Forum RADIUS VSA September 2006
233 The following subsections describe the Attributes defined by this
234 document. These Attributes MAY be transmitted in one or more RADIUS
235 Attributes of type Vendor-Specific [RFC2865]. More than one
236 attribute MAY be transmitted in a single Vendor-Specific Attribute;
237 if this is done, the attributes SHOULD be packed as a sequence of
238 Vendor-Type/Vendor-Length/Value triples following the initial Type,
239 Length, and Vendor-Id fields.
241 3.1. DSL Forum RADIUS VSA Definition
245 This Attribute functions as a "container", encapsulating one or
246 more vendor-specific sub-attributes; the encoding follows the
247 recommendations in [RFC2865].
249 A summary of the generic DSL Forum VSA format is shown below. The
250 fields are transmitted from left to right.
253 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
255 | Type | Length | Vendor-Id
256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
257 Vendor-Id (cont) | Sub-Attribute(s)...
258 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
262 26 for Vendor-Specific
266 This field MUST be set equal to the sum of the Vendor-Length
267 fields of the sub-attributes contained in the Vendor-Specific
268 Attribute, plus six (Type + Length + Vendor-Id).
272 This field MUST be set to decimal 3561, the enterprise number
273 assigned to the ADSL Forum [IANA].
277 This field MUST contain one or more DSL Forum Vendor-Specific
278 sub-attributes, as specified below.
282 Mammoliti, et al. Informational [Page 5]
284 RFC 4679 DSL Forum RADIUS VSA September 2006
287 3.2. DSL Forum Vendor Specific Sub-Attribute Encoding
289 A summary of the sub-attribute format is shown below. The fields are
290 transmitted from left to right.
293 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
295 | Vendor-Type | Vendor-Length | Value...
296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
300 The Vendor-Type field is one octet in length and contains the
301 sub-attribute type, as assigned by the DSL Forum.
305 The Vendor-Length field is one octet and indicates the length of
306 the entire sub-attribute, including the Vendor-Type,
307 Vendor-Length, and Value fields.
311 The Value field is zero or more octets and contains information
312 specific to the sub-attribute. The format and length of the Value
313 field is determined by the Vendor-Type and Vendor-Length fields.
314 The format of the value field is one of 2 data types, string or
317 3.3. Sub-attribute Definitions
319 The following sub-sections define the DSL Forum vendor-specific sub-
322 3.3.1. Agent-Circuit-Id
326 This Attribute contains information describing the subscriber
327 agent circuit identifier corresponding to the logical access loop
328 port of the Access Node/DSLAM from which a subscriber's requests
329 are initiated. It MAY be present in both Access-Request and
330 Accounting-Request packets.
332 A summary of the Agent-Circuit-Id Attribute format is shown below.
333 The fields are transmitted from left to right.
338 Mammoliti, et al. Informational [Page 6]
340 RFC 4679 DSL Forum RADIUS VSA September 2006
344 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
346 | Vendor-Type | Vendor-Length | String...
347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
351 1 for Agent-Circuit-Id
359 The String field contains information about the Access-Node to
360 which the subscriber is attached, along with an identifier for the
361 subscriber's DSL port on that Access-Node.
363 The exact syntax of the string is implementation dependent;
364 however, a typical practice is to subdivide it into two or more
365 space-separated components, one to identify the Access-Node and
366 another the subscriber line on that node, with perhaps an
367 indication of whether that line is Ethernet or ATM. Example
368 formats for this string are shown below.
370 "Access-Node-Identifier atm slot/port:vpi.vci"
371 (when ATM/DSL is used)
373 "Access-Node-Identifier eth slot/port[:vlan-id]"
374 (when Ethernet/DSL is used)
376 An example showing the slot and port field encoding is given
379 "[Relay-identifier] atm 3/0:100.33"
380 (slot = 3, port = 0, vpi = 100, vci = 33)
382 The Access-Node-Identifier is a unique ASCII string that does not
383 include 'space' characters. The syntax of the slot and port
384 fields reflects typical practices currently in place. The slot
385 identifier does not exceed 6 characters in length, and the port
386 identifier does not exceed 3 characters in length using a '\' as a
394 Mammoliti, et al. Informational [Page 7]
396 RFC 4679 DSL Forum RADIUS VSA September 2006
399 The exact manner in which slots are identified is Access
400 Node/DSLAM implementation dependent. The vpi, vci, and vlan-id
401 fields (when applicable) are related to a given access loop
404 3.3.2. Agent-Remote-Id
408 The Agent-Remote-Id Attribute contains an operator-specific,
409 statically configured string that uniquely identifies the
410 subscriber on the associated access loop of the Access Node/DSLAM.
412 In a typical subscriber environment, multiple attributes can be
413 used to identify the user, among others: Username (for example, as
414 defined on a PPP client); Agent-Circuit-Id (a static, pre-defined
415 string sent from the Access Node/DSLAM); Agent-Remote-Id (an
416 operator-defined string configured on and sent by the Access
419 This Attribute MAY be included in both Access-Request and
420 Accounting-Request packets.
422 A summary of the Agent-Remote-Id Attribute format is shown below.
423 The fields are transmitted from left to right.
426 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
428 | Vendor-Type | Vendor-Length | String...
429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
433 2 for Agent-Remote-Id
441 This value of this field is entirely open to the service
442 provider's discretion. For example, it MAY contain a subscriber
443 billing identifier or telephone number.
450 Mammoliti, et al. Informational [Page 8]
452 RFC 4679 DSL Forum RADIUS VSA September 2006
455 3.3.3. Actual-Data-Rate-Upstream
459 This Attribute contains the actual upstream train rate of a
460 subscriber's synchronized DSL link. It MAY be included in both
461 Access-Request and Accounting-Request packets.
463 A summary of the Actual-Data-Rate-Upstream Attribute format is shown
464 below. The fields are transmitted from left to right.
467 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
468 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
469 | Vendor-Type | Vendor-Length | Value
470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
476 129 (0x81) for Actual-Data-Rate-Upstream
484 This field contains a 4-byte unsigned integer, indicating the
485 subscriber's actual data rate upstream of a synchronized DSL link.
486 The rate is coded in bits per second.
488 3.3.4. Actual-Data-Rate-Downstream
492 This Attribute contains the actual downstream train rate of a
493 subscriber's synchronized DSL link. It MAY be included in both
494 Access-Request and Accounting-Request packets.
496 A summary of the Actual-Data-Rate-Downstream Attribute format is
497 shown below. The fields are transmitted from left to right.
506 Mammoliti, et al. Informational [Page 9]
508 RFC 4679 DSL Forum RADIUS VSA September 2006
512 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
514 | Vendor-Type | Vendor-Length | Value
515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
521 130 (0x82) for Actual-Data-Rate-Downstream
529 This field contains a 4-byte unsigned integer, indicating the
530 subscriber's actual data rate downstream of a synchronized DSL
531 link. The rate is coded in bits per second.
533 3.3.5. Minimum-Data-Rate-Upstream
537 This Attribute contains the subscriber's operator-configured
538 minimum upstream data rate. It MAY be included in Accounting-
541 A summary of the Minimum-Data-Rate-Upstream Attribute format is shown
542 below. The fields are transmitted from left to right.
545 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
546 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
547 | Vendor-Type | Vendor-Length | Value
548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
554 131 (0x83) for Minimum-Data-Rate-Upstream
562 Mammoliti, et al. Informational [Page 10]
564 RFC 4679 DSL Forum RADIUS VSA September 2006
569 This field contains a 4-byte unsigned integer, indicating the
570 subscriber's minimum upstream data rate (as configured by the
571 operator). The rate is coded in bits per second.
573 3.3.6. Minimum-Data-Rate-Downstream
577 This Attribute contains the subscriber's operator-configured
578 minimum downstream data rate. It MAY be included in Accounting-
581 A summary of the Minimum-Data-Rate-Downstream Attribute format is
582 shown below. The fields are transmitted from left to right.
585 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
586 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
587 | Vendor-Type | Vendor-Length | Value
588 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
590 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
594 132 (0x84) for Minimum-Data-Rate-Downstream
602 This field contains a 4-byte unsigned integer, indicating the
603 subscriber's minimum downstream data rate (as configured by the
604 operator). The rate is coded in bits per second.
606 3.3.7. Attainable-Data-Rate-Upstream
610 This Attribute contains the subscriber's attainable upstream data
611 rate. It MAY be included in Accounting-Request packets.
613 A summary of the Attainable-Data-Rate-Upstream Attribute format is
614 shown below. The fields are transmitted from left to right.
618 Mammoliti, et al. Informational [Page 11]
620 RFC 4679 DSL Forum RADIUS VSA September 2006
624 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
625 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
626 | Vendor-Type | Vendor-Length | Value
627 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
629 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
633 133 (0x85) for Attainable-Data-Rate-Upstream
641 This field contains a 4-byte unsigned integer, indicating the
642 subscriber's actual DSL attainable upstream data rate. The rate
643 is coded in bits per second.
645 3.3.8. Attainable-Data-Rate-Downstream
649 This Attribute contains the subscriber's attainable downstream
650 data rate. It MAY be included in Accounting-Request packets.
652 A summary of the Attainable-Data-Rate-Downstream Attribute format is
653 shown below. The fields are transmitted from left to right.
656 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
658 | Vendor-Type | Vendor-Length | Value
659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
665 134 (0x86) for Attainable-Data-Rate-Downstream
674 Mammoliti, et al. Informational [Page 12]
676 RFC 4679 DSL Forum RADIUS VSA September 2006
681 This field contains a 4-byte unsigned integer, indicating the
682 subscriber's actual DSL attainable downstream data rate. The rate
683 is coded in bits per second.
685 3.3.9. Maximum-Data-Rate-Upstream
689 This Attribute contains the subscriber's maximum upstream data
690 rate, as configured by the operator. It MAY be included in
691 Accounting-Request packets.
693 A summary of the Maximum-Data-Rate-Upstream Attribute format is shown
694 below. The fields are transmitted from left to right.
697 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
698 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
699 | Vendor-Type | Vendor-Length | Value
700 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
702 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
706 135 (0x87) for Maximum-Data-Rate-Upstream
714 This field is a 4-byte unsigned integer, indicating the numeric
715 value of the subscriber's DSL maximum upstream data rate. The
716 rate is coded in bits per second.
718 3.3.10. Maximum-Data-Rate-Downstream
722 This Attribute contains the subscriber's maximum downstream data
723 rate, as configured by the operator. It MAY be included in
724 Accounting-Request packets.
730 Mammoliti, et al. Informational [Page 13]
732 RFC 4679 DSL Forum RADIUS VSA September 2006
735 A summary of the Maximum-Data-Rate-Downstream Attribute format is
736 shown below. The fields are transmitted from left to right.
739 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
740 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
741 | Vendor-Type | Vendor-Length | Value
742 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
744 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
748 136 (0x88) for Maximum-Data-Rate-Downstream
756 This field is a 4-byte unsigned integer, indicating the numeric
757 value of the subscriber's DSL maximum downstream data rate. The
758 rate is coded in bits per second.
760 3.3.11. Minimum-Data-Rate-Upstream-Low-Power
764 This Attribute contains the subscriber's minimum upstream data
765 rate in low power state, as configured by the operator. It MAY be
766 included in Accounting-Request packets.
768 A summary of the Minimum-Data-Rate-Upstream-Low-Power Attribute
769 format is shown below. The fields are transmitted from left to
773 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
775 | Vendor-Type | Vendor-Length | Value
776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
782 137 (0x89) for Minimum-Data-Rate-Upstream-Low-Power
786 Mammoliti, et al. Informational [Page 14]
788 RFC 4679 DSL Forum RADIUS VSA September 2006
797 This field is a 4-byte unsigned integer, indicating the numeric
798 value of the subscriber's DSL minimum upstream data rate when in
799 low power state (L1/L2). The rate is coded in bits per second.
801 3.3.12. Minimum-Data-Rate-Downstream-Low-Power
805 This Attribute contains the subscriber's minimum downstream data
806 rate in low power state, as configured by the operator. It MAY be
807 included in Accounting-Request packets.
809 A summary of the Minimum-Data-Rate-Downstream-Low-Power Attribute
810 format is shown below. The fields are transmitted from left to
814 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
815 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
816 | Vendor-Type | Vendor-Length | Value
817 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
819 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
823 138 (0x8A) for Minimum-Data-Rate-Downstream-Low-Power
831 This field is a 4-byte unsigned integer, indicating the numeric
832 value of the subscriber's DSL minimum downstream data rate. The
833 rate is coded in bits per second.
842 Mammoliti, et al. Informational [Page 15]
844 RFC 4679 DSL Forum RADIUS VSA September 2006
847 3.3.13. Maximum-Interleaving-Delay-Upstream
851 This Attribute contains the subscriber's maximum one-way upstream
852 interleaving delay, as configured by the operator. It MAY be
853 included in Accounting-Request packets.
855 A summary of the Maximum-Interleaving-Delay-Upstream Attribute format
856 is shown below. The fields are transmitted from left to right.
859 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
860 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
861 | Vendor-Type | Vendor-Length | Value
862 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
864 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
868 139 (0x8B) for Maximum-Interleaving-Delay-Upstream
876 This field is a 4-byte unsigned integer, indicating the numeric
877 value in milliseconds of the subscriber's DSL maximum one-way
878 upstream interleaving delay.
880 3.3.14. Actual-Interleaving-Delay-Upstream
884 This Attribute contains the subscriber's actual one-way upstream
885 interleaving delay. It MAY be included in Accounting-Request
888 A summary of the Actual-Interleaving-Delay-Upstream Attribute format
889 is shown below. The fields are transmitted from left to right.
898 Mammoliti, et al. Informational [Page 16]
900 RFC 4679 DSL Forum RADIUS VSA September 2006
904 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
905 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
906 | Vendor-Type | Vendor-Length | Value
907 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
909 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
913 140 (0x8C) for Actual-Interleaving-Delay-Upstream
921 This field is a 4-byte unsigned integer, indicating the numeric
922 value in milliseconds of the subscriber's DSL actual upstream
925 3.3.15. Maximum-Interleaving-Delay-Downstream
929 This Attribute contains the subscriber's maximum one-way
930 downstream interleaving delay, as configured by the operator. It
931 MAY be included in Accounting-Request packets.
933 A summary of the Maximum-Interleaving-Delay-Downstream Attribute
934 format is shown below. The fields are transmitted from left to
938 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
939 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
940 | Vendor-Type | Vendor-Length | Value
941 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
943 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
947 141 (0x8D) for Maximum-Interleaving-Delay-Downstream
954 Mammoliti, et al. Informational [Page 17]
956 RFC 4679 DSL Forum RADIUS VSA September 2006
965 This field is a 4-byte unsigned integer, indicating the numeric
966 value in milliseconds of the subscriber's DSL maximum one-way
967 downstream interleaving delay.
969 3.3.16. Actual-Interleaving-Delay-Downstream
973 This Attribute contains the subscriber's actual one-way downstream
974 interleaving delay. It MAY be included in Accounting-Request
977 A summary of the Actual-Interleaving-Delay-Downstream Attribute
978 format is shown below. The fields are transmitted from left to
982 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
984 | Vendor-Type | Vendor-Length | Value
985 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
987 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
991 142 (0x8E) for Actual-Interleaving-Delay-Downstream
999 This field is a 4-byte unsigned integer, indicating the numeric
1000 value in milliseconds of the subscriber's DSL actual downstream
1010 Mammoliti, et al. Informational [Page 18]
1012 RFC 4679 DSL Forum RADIUS VSA September 2006
1015 3.3.17. Access-Loop-Encapsulation
1019 This Attribute describes the encapsulation(s) used by the
1020 subscriber on the DSL access loop. It MAY be present in both
1021 Access-Request and Accounting-Request packets.
1023 A summary of the Access-Loop-Encapsulation Attribute format is shown
1024 below. The fields are transmitted from left to right.
1027 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
1028 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1029 | Vendor-Type | Vendor-Length | Value
1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1036 144 (0x90) for Access-Loop-Encapsulation
1044 This field is a string 3 bytes in length, logically divided into
1045 three 1-byte sub-fields as shown in the following diagram:
1048 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
1049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1050 | Data Link | Encaps 1 | Encaps 2 |
1051 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1053 Valid values for the sub-fields are as follows:
1066 Mammoliti, et al. Informational [Page 19]
1068 RFC 4679 DSL Forum RADIUS VSA September 2006
1073 0x00 NA - Not Available
1074 0x01 Untagged Ethernet
1075 0x02 Single-Tagged Ethernet
1079 0x00 NA - Not Available
1084 0x05 Ethernet over AAL5 LLC with FCS
1085 0x06 Ethernet over AAL5 LLC without FCS
1086 0x07 Ethernet over AAL5 Null with FCS
1087 0x08 Ethernet over AAL5 Null without FCS
1093 The presence of this Attribute indicates that the IWF has been
1094 performed with respect to the subscriber's session; note that no
1095 data field is necessary. It MAY be included in both Access-
1096 Request and Accounting-Request packets.
1098 A summary of the IWF-Session Attribute format is shown below. The
1099 fields are transmitted from left to right.
1102 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
1103 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1104 | Vendor-Type | Vendor-Length |
1105 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
1109 254 (0xFE) for IWF-Session
1122 Mammoliti, et al. Informational [Page 20]
1124 RFC 4679 DSL Forum RADIUS VSA September 2006
1127 4. Table of Attributes
1129 The following table provides a guide to which attributes may be found
1130 in which kinds of packets, and in what quantity; note that since none
1131 of the DSL Forum VSAs may be present in the Access-Accept, Access-
1132 Reject or Access-Challenge packets, those columns have been omitted
1135 Request Acct-Request # Attribute
1136 0-1 0-1 1 Agent-Circuit-Id
1137 0-1 0-1 2 Agent-Remote-Id
1138 0-1 0-1 129 Actual-Data-Rate-Upstream
1139 0-1 0-1 130 Actual-Data-Rate-Downstream
1140 0 0-1 131 Minimum-Data-Rate-Upstream
1141 0 0-1 132 Minimum-Data-Rate-Downstream
1142 0 0-1 133 Attainable-Data-Rate-Upstream
1143 0 0-1 134 Attainable-Data-Rate-Downstream
1144 0 0-1 135 Maximum-Data-Rate-Upstream
1145 0 0-1 136 Maximum-Data-Rate-Downstream
1146 0 0-1 137 Minimum-Data-Rate-Upstream-Low-Power
1147 0 0-1 138 Minimum-Data-Rate-Downstream-Low-Power
1148 0 0-1 139 Maximum-Interleaving-Delay-Upstream
1149 0 0-1 140 Actual-Interleaving-Delay-Upstream
1150 0 0-1 141 Maximum-Interleaving-Delay-Downstream
1151 0 0-1 142 Actual-Interleaving-Delay-Downstream
1152 0-1 0-1 144 Access-Loop-Encapsulation
1153 0-1 0-1 254 IWF-Session
1155 The following table defines the meaning of the above table entries.
1157 0 This Attribute MUST NOT be present in packet.
1159 0-1 Zero or one instances of this Attribute MAY be present in
1162 5. Security Considerations
1164 The security of these Attributes relies on an implied trust
1165 relationship between the Access Node/DSLAM and the BRAS. The
1166 identifiers that are inserted by the Access Node/DSLAM are
1167 unconditionally trusted; the BRAS does not perform any validity check
1168 on the information received. These Attributes are intended to be
1169 used in environments in which the network infrastructure (the Access
1170 Node/DSLAM, the BRAS, and the entire network in which those two
1171 devices reside) is trusted and secure.
1178 Mammoliti, et al. Informational [Page 21]
1180 RFC 4679 DSL Forum RADIUS VSA September 2006
1183 As used in this document, the word "trusted" implies that
1184 unauthorized traffic cannot enter the network except through secured
1185 and trusted devices and that all devices internal to the network are
1186 secure and trusted. Careful consideration should be given to the
1187 potential security vulnerabilities that are present in this model
1188 before deploying this option in actual networks.
1190 The Attributes described in this document neither increase nor
1191 decrease the security of the RADIUS protocol. For discussions of
1192 various RADIUS vulnerabilities, see [RFC2607], [RFC3579], [RFC3162],
1197 6.1. Normative References
1199 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1200 Requirement Levels", BCP 14, RFC 2119, March 1997.
1202 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
1203 "Remote Authentication Dial In User Service (RADIUS)",
1204 RFC 2865, June 2000.
1206 [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.
1208 6.2. Informative References
1210 [IANA] Internet Assigned Numbers Authority, "PRIVATE ENTERPRISE
1211 NUMBERS", January 2006,
1212 <http://www.iana.org/assignments/enterprise-numbers>.
1215 International Telecommunications Union, "B-ISDN ATM
1216 Adaptation Layer Specification: Type 5 AAL", ITU-T
1217 Recommendation I.363.5, August 1996.
1219 [RFC2516] Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D.,
1220 and R. Wheeler, "A Method for Transmitting PPP Over
1221 Ethernet (PPPoE)", RFC 2516, February 1999.
1223 [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
1224 Implementation in Roaming", RFC 2607, June 1999.
1226 [RFC3046] Patrick, M., "DHCP Relay Agent Information Option",
1227 RFC 3046, January 2001.
1229 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
1230 RFC 3162, August 2001.
1234 Mammoliti, et al. Informational [Page 22]
1236 RFC 4679 DSL Forum RADIUS VSA September 2006
1239 [RFC3579] Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication
1240 Dial In User Service) Support For Extensible
1241 Authentication Protocol (EAP)", RFC 3579, September 2003.
1243 [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
1244 "IEEE 802.1X Remote Authentication Dial In User Service
1245 (RADIUS) Usage Guidelines", RFC 3580, September 2003.
1247 [RFC4243] Stapp, M., Johnson, R., and T. Palaniappan, "Vendor-
1248 Specific Information Suboption for the Dynamic Host
1249 Configuration Protocol (DHCP) Relay Agent Option",
1250 RFC 4243, December 2005.
1290 Mammoliti, et al. Informational [Page 23]
1292 RFC 4679 DSL Forum RADIUS VSA September 2006
1299 181 Bay Street, Suite 3400
1303 EMail: vince@cisco.com
1308 2901 Third Avenue, Suite 600
1313 Phone: +1 (425) 344 8113
1314 EMail: gwz@cisco.com
1318 Redback Networks, Inc.
1323 EMail: parberg@redback.com
1328 Omega Corporate Center
1330 Pittsburgh, PA 15205
1333 EMail: robert.rennison@ecitele.com
1346 Mammoliti, et al. Informational [Page 24]
1348 RFC 4679 DSL Forum RADIUS VSA September 2006
1351 Full Copyright Statement
1353 Copyright (C) The Internet Society (2006).
1355 This document is subject to the rights, licenses and restrictions
1356 contained in BCP 78 and at www.rfc-editor.org/copyright.html, and
1357 except as set forth therein, the authors retain all their rights.
1359 This document and the information contained herein are provided on an
1360 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
1361 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
1362 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
1363 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
1364 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
1365 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1367 Intellectual Property
1369 The IETF takes no position regarding the validity or scope of any
1370 Intellectual Property Rights or other rights that might be claimed to
1371 pertain to the implementation or use of the technology described in
1372 this document or the extent to which any license under such rights
1373 might or might not be available; nor does it represent that it has
1374 made any independent effort to identify any such rights. Information
1375 on the procedures with respect to rights in RFC documents can be
1376 found in BCP 78 and BCP 79.
1378 Copies of IPR disclosures made to the IETF Secretariat and any
1379 assurances of licenses to be made available, or the result of an
1380 attempt made to obtain a general license or permission for the use of
1381 such proprietary rights by implementers or users of this
1382 specification can be obtained from the IETF on-line IPR repository at
1383 http://www.ietf.org/ipr.
1385 The IETF invites any interested party to bring to its attention any
1386 copyrights, patents or patent applications, or other proprietary
1387 rights that may cover technology that may be required to implement
1388 this standard. Please address the information to the IETF at
1393 Funding for the RFC Editor function is provided by the IETF
1394 Administrative Support Activity (IASA).
1402 Mammoliti, et al. Informational [Page 25]