[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 RFC 4679

Network Working Group                                       V. Mammoliti
Internet-Draft                                                   G. Zorn
Expires: August 26, 2006                                   Cisco Systems
                                                               P. Arberg
                                                  Redback Networks, Inc.
                                                             R. Rennison
                                                             ECI Telecom
                                                       February 22, 2006


              DSL Forum Vendor-Specific RADIUS Attributes
                 draft-mammoliti-radius-dsl-vsa-01.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   applicable patent or other IPR claims of which he or she is aware
   have been or will be disclosed, and any of which he or she becomes
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on August 26, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   This document describes the set of Remote Authentication Dial in User
   Service Vendor-Specific Attributes (RADIUS VSAs) defined by the DSL
   Forum.




Mammoliti, et al.        Expires August 26, 2006                [Page 1]


Internet-Draft                DSL Forum VSA                February 2006


   These attributes are designed to transport Digital Subscriber Line
   (DSL) information which is not supported by the standard RADIUS
   attribute set.  It is expected that this document will be updated if
   and when the DSL Forum defines additional vendor-specific attribute,
   since its primary purpose is to provide a reference for DSL equipment
   vendors wishing to interoperate with other vendors' products.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.   Terminology  . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1  Requirements Language  . . . . . . . . . . . . . . . . . .   3
     2.2  Technical Terms and Acronyms . . . . . . . . . . . . . . .   3
   3.   Attributes . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1  DSL Forum RADIUS VSA Definition  . . . . . . . . . . . . .   4
     3.2  DSL Forum Vendor Specific Sub-attribute Encoding . . . . .   5
     3.3  Sub-attribute Definitions  . . . . . . . . . . . . . . . .   6
       3.3.1  Agent-Circuit-Id . . . . . . . . . . . . . . . . . . .   6
       3.3.2  Agent-Remote-Id  . . . . . . . . . . . . . . . . . . .   7
       3.3.3  Actual-Data-Rate-Upstream  . . . . . . . . . . . . . .   8
       3.3.4  Actual-Data-Rate-Downstream  . . . . . . . . . . . . .   9
       3.3.5  Minimum-Data-Rate-Upstream . . . . . . . . . . . . . .   9
       3.3.6  Minimum-Data-Rate-Downstream . . . . . . . . . . . . .  10
       3.3.7  Attainable-Data-Rate-Upstream  . . . . . . . . . . . .  11
       3.3.8  Attainable-Data-Rate-Downstream  . . . . . . . . . . .  11
       3.3.9  Maximum-Data-Rate-Upstream . . . . . . . . . . . . . .  12
       3.3.10   Maximum-Data-Rate-Downstream . . . . . . . . . . . .  13
       3.3.11   Minimum-Data-Rate-Upstream-Low-Power . . . . . . . .  14
       3.3.12   Minimum-Data-Rate-Downstream-Low-Power . . . . . . .  14
       3.3.13   Maximum-Interleaving-Delay-Upstream  . . . . . . . .  15
       3.3.14   Actual-Interleaving-Delay-Upstream . . . . . . . . .  16
       3.3.15   Maximum-Interleaving-Delay-Downstream  . . . . . . .  17
       3.3.16   Actual-Interleaving-Delay-Downstream . . . . . . . .  17
       3.3.17   Access-Loop-Encapsulation  . . . . . . . . . . . . .  18
       3.3.18   IWF-Session  . . . . . . . . . . . . . . . . . . . .  19
   4.   Table of Attributes  . . . . . . . . . . . . . . . . . . . .  20
   5.   IANA Considerations  . . . . . . . . . . . . . . . . . . . .  21
   6.   Security Considerations  . . . . . . . . . . . . . . . . . .  21
   7.   References . . . . . . . . . . . . . . . . . . . . . . . . .  21
     7.1  Normative References . . . . . . . . . . . . . . . . . . .  21
     7.2  Informative References . . . . . . . . . . . . . . . . . .  21
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  22
        Intellectual Property and Copyright Statements . . . . . . .  24








Mammoliti, et al.        Expires August 26, 2006                [Page 2]


Internet-Draft                DSL Forum VSA                February 2006


1.  Introduction

   The DSL Forum has created additional RADIUS [RFC2865] [RFC2866]
   vendor-specific attributes to carry DSL line identification and
   characterization information.  This information is forwarded from the
   Access Node/DSLAM to the BRAS via Vendor-Specific PPPoE Tags
   [RFC2516], and DHCP Relay Options [RFC3046] and Vendor-Specific
   Information Suboptions [RFC4243].  This document describes the
   subscriber line identification and characterization information and
   its mapping to RADIUS VSAs by the BRAS.

   The information acquired may be used to provide authentication and
   accounting functionality.  It may also be collected and be used for
   management and troubleshooting purposes.

   Discussion of this draft may be directed to the authors.

2.  Terminology

   The following sections define the usage and meaning of certain
   specialized terms in the contest of this document.

2.1  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.2  Technical Terms and Acronyms

   Access Node/DSLAM
      The Access Node/DSLAM is a DSL signal terminator that contains a
      minimum of one Ethernet interface that serves as its northbound
      interface into which it aggregates traffic from several ATM-based
      (subscriber ports) or Ethernet-based southbound interfaces.

   BNG
      Broadband Network Gateway.  A BNG is an IP edge router where
      bandwidth and QoS policies are applied; the functions performed by
      a BRAS are a superset of those performed by a BNG.

   BRAS
      Broadband Remote Access Server.  A BRAS is a BNG and is the
      aggregation point for the subscriber traffic.  It provides
      aggregation capabilities (e.g.  IP, PPP, Ethernet) between the
      access network and the core network.  Beyond its aggregation
      function, the BRAS is also an injection point for policy
      management and IP QoS in the access network.



Mammoliti, et al.        Expires August 26, 2006                [Page 3]


Internet-Draft                DSL Forum VSA                February 2006


   DSL
      Digital Subscriber Line.  DSL is a technology that allows digital
      data transmission over wires in the local telephone network.

   DSLAM
      Digital Subscriber Line Access Multiplexer.  DSLAM is a device
      that terminates DSL subscriber lines.  The data is aggregated and
      forwarded to ATM- or Ethernet-based aggregation networks.

   IWF
      Interworking Function.  The set of functions required for
      interconnecting two networks of different technologies (e.g., ATM
      and Ethernet.  IWF is utilized to enable the carriage of PPPoA
      traffic over PPPoE.


3.  Attributes

   The following subsections describe the Attributes defined by this
   document.  These Attributes MAY be transmitted in one or more RADIUS
   Attributes of type Vendor-Specific [RFC2865].  More than one
   attribute MAY be transmitted in a single Vendor-Specific Attribute;
   if this is done, the attributes SHOULD be packed as a sequence of
   Vendor-Type/Vendor-Length/Value triples following the initial Type,
   Length and Vendor-ID fields.

3.1  DSL Forum RADIUS VSA Definition

   Description

      This Attribute functions as a "container", encapsulating one or
      more vendor-specific sub-attributes; the encoding follows the
      recomendations in [RFC2865].

   A summary of the generic DSL Forum VSA format is shown below.  The
   fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |  Length       |           Vendor-Id
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            Vendor-Id (cont)       |       Sub-Attribute(s)...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+







Mammoliti, et al.        Expires August 26, 2006                [Page 4]


Internet-Draft                DSL Forum VSA                February 2006


   Type

      26 for Vendor-Specific

   Length

      This field MUST be set equal to the sum of the Vendor-Length
      fields of the sub-attributes contained in the Vendor-Specific
      Attribute, plus six (Type + Length + Vendor-Id).

   Vendor-Id

      This field MUST be set to decimal 3561, the enterprise number
      assigned to the ADSL Forum [IANA].

   Sub-Attributes

      This field MUST contain one or more DSL Forum Vendor-Specific sub-
      attributes, as specified below.


3.2  DSL Forum Vendor Specific Sub-attribute Encoding

   A summary of the sub-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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | Vendor-Type | Vendor-Length |  Value...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      The Vendor-Type field is one octet in length and contains the sub-
      attribute type, as assigned by the DSL forum.

   Vendor-Length

      The Vendor-Length field is one octet, and indicates the length of
      the entire sub-attribute, including the Vendor-Type, Vendor-Length
      and Value fields.

   Value

      The Value field is zero or more octets and contains information
      specific to the sub-attribute.  The format and length of the Value
      field is determined by the Vendor-Type and Vendor-Length fields.



Mammoliti, et al.        Expires August 26, 2006                [Page 5]


Internet-Draft                DSL Forum VSA                February 2006


      The format of the value field is one of 2 data types, string or
      integer [RFC2865].


3.3  Sub-attribute Definitions

   The following sub-sections define the DSL Forum vendor-specific sub-
   attributes.

3.3.1  Agent-Circuit-Id

   Description

      This Attribute contains information describing the subscriber
      agent circuit ID corresponding to the logical access loop port of
      the Access Node/DSLAM from which a subscriber's requests are
      initiated.  It MAY be present in both Access-Request and
      Accounting-Request packets.

   A summary of the Agent-Circuit-Id Attribute format is shown below.
   The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |           String...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      1 for Agent-Circuit-Id

   Vendor-Length

      <= 65

   String

      The String field contains information about the Access-Node to
      which the subscriber is attached, along with an identifier for the
      subscriber's DSL port on that Access-Node.

      The exact syntax of the string is implementation dependant;
      however, a typical practice is to subdivide it into two or more
      space-separated components, one to identify the Access-Node and
      another the subscriber line on that node, with perhaps an
      indication of whether that line is Ethernet or ATM.  Example
      formats for this string are shown below.



Mammoliti, et al.        Expires August 26, 2006                [Page 6]


Internet-Draft                DSL Forum VSA                February 2006


      "Access-Node-Identifier atm slot/port:vpi.vci""
         (when ATM/DSL is used)

      "Access-Node-Identifier eth slot/port[:vlan-id]"
         (when Ethernet/DSL is used)

      An example showing the slot and port field encoding is given
      below:

      "[Relay-identifier] atm 3/0:100.33"
         (slot = 3, port = 0, vpi = 100, vci = 33)

      The Access-Node-Identifier is a unique ASCII string which does not
      include 'space' characters.  The syntax of the slot and port
      fields reflects typical practices currently in place.  The slot
      identifier does not exceed 6 characters in length and the port
      identifier does not exceed 3 characters in length using a '/' as a
      delimiter.

      The exact manner in which slots are identified is Access Node/
      DSLAM implementation dependent.  The vpi, vci and vlan-id fields
      (when applicable) are related to a given access loop
      (U-interface).


3.3.2  Agent-Remote-Id

   Description

      The Agent-Remote-ID Attribute contains an operator-specific,
      configured string which uniquely identifies the subscriber on the
      associated access loop of the Access Node/DSLAM.

      This Attribute  MAY be included in both Access-Request and
      Accounting-Request packets.

   A summary of the Agent-Remote-Id Attribute format is shown below.
   The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |           String...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+







Mammoliti, et al.        Expires August 26, 2006                [Page 7]


Internet-Draft                DSL Forum VSA                February 2006


   Vendor-Type

      2 for Agent-Remote-Id

   Vendor-Length

      <= 65

   String

      This value of this field is entirely open to the service
      provider's discretion.  For example, it MAY contain a subscriber
      billing ID or telephone number.


3.3.3  Actual-Data-Rate-Upstream

   Description

      This Attribute contains the actual upstream train rate of a
      subscriber's synchronized DSL link .  It MAY be included in both
      Access-Request and Accounting-Request packets.

   A summary of the Actual-Data-Rate-Upstream Attribute format is shown
   below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      129 (0x81) for Actual-Data-Rate-Upstream

   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's actual data rate upstream of a synchronized DSL link.
      The rate is coded in bits per second.




Mammoliti, et al.        Expires August 26, 2006                [Page 8]


Internet-Draft                DSL Forum VSA                February 2006


3.3.4  Actual-Data-Rate-Downstream

   Description

      This Attribute contains the actual downstream train rate of a
      subscriber's synchronized DSL link .  It MAY be included in both
      Access-Request and Accounting-Request packets.

   A summary of the Actual-Data-Rate-Downstream Attribute format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      130 (0x82) for Actual-Data-Rate-Downstream

   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's actual data rate downstream of a synchronized DSL
      link.  The rate is coded in bits per second.


3.3.5  Minimum-Data-Rate-Upstream

   Description

      This Attribute contains the subscriber's operator-configured
      minimum upstream data rate.  It MAY be included in Accounting-
      Request packets.

   A summary of the Minimum-Data-Rate-Upstream Attribute format is shown
   below.  The fields are transmitted from left to right.







Mammoliti, et al.        Expires August 26, 2006                [Page 9]


Internet-Draft                DSL Forum VSA                February 2006


    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      131 (0x83) for Minimum-Data-Rate-Upstream

   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's minimum upstream data rate (as configured by the
      operator).  The rate is coded in bits per second.


3.3.6  Minimum-Data-Rate-Downstream

   Description

      This Attribute contains the subscriber's operator-configured
      minimum downstream data rate.  It MAY be included in Accounting-
      Request packets.

   A summary of the Minimum-Data-Rate-Downstream Attribute format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      132 (0x84) for Minimum-Data-Rate-Downstream






Mammoliti, et al.        Expires August 26, 2006               [Page 10]


Internet-Draft                DSL Forum VSA                February 2006


   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's minimum downstream data rate (as configured by the
      operator).  The rate is coded in bits per second.


3.3.7  Attainable-Data-Rate-Upstream

   Description

      This Attribute contains the subscriber's attainable upstream data
      rate.  It MAY be included in Accounting-Request packets.

   A summary of the Attainable-Data-Rate-Upstream Attribute format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      133 (0x85) for Attainable-Data-Rate-Upstream

   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's actual DSL attainable upstream data rate.  The rate
      is coded in bits per second.


3.3.8  Attainable-Data-Rate-Downstream






Mammoliti, et al.        Expires August 26, 2006               [Page 11]


Internet-Draft                DSL Forum VSA                February 2006


   Description

      This Attribute contains the subscriber's attainable downstream
      data rate.  It MAY be included in Accounting-Request packets.

   A summary of the Attainable-Data-Rate-Downstream Attribute format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      134 (0x86) for Attainable-Data-Rate-Downstream

   Vendor-Length

      6

   Value

      This field contains a 4 byte unsigned integer, indicating the
      subscriber's actual DSL attainable downstream data rate.  The rate
      is coded in bits per second.


3.3.9  Maximum-Data-Rate-Upstream

   Description

      This Attribute contains the subscriber's maximum upstream data
      rate, as configured by the operator.  It MAY be included in
      Accounting-Request packets.

   A summary of the Maximum-Data-Rate-Upstream Attribute format is shown
   below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |



Mammoliti, et al.        Expires August 26, 2006               [Page 12]


Internet-Draft                DSL Forum VSA                February 2006


   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      135 (0x87) for Maximum-Data-Rate-Upstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value of the subscriber's DSL maximum upstream data rate.  The
      rate is coded in bits per second.


3.3.10  Maximum-Data-Rate-Downstream

   Description

      This Attribute contains the subscriber's maximum downstream data
      rate, as configured by the operator.  It MAY be included in
      Accounting-Request packets.

   A summary of the Maximum-Data-Rate-Downstream Attribute format is
   shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      136 (0x88) for Maximum-Data-Rate-Downstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value of the subscriber's DSL maximum downstream data rate.  The



Mammoliti, et al.        Expires August 26, 2006               [Page 13]


Internet-Draft                DSL Forum VSA                February 2006


      rate is coded in bits per second.


3.3.11  Minimum-Data-Rate-Upstream-Low-Power

   Description

      This Attribute contains the subscriber's minimum upstream data
      rate in low power state, as configured by the operator.  It MAY be
      included in Accounting-Request packets.

   A summary of the Minimum-Data-Rate-Upstream-Low-Power Attribute
   format is shown below.  The fields are transmitted from left to
   right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      137 (0x89) for Minimum-Data-Rate-Upstream-Low-Power

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value of the subscriber's DSL minimum upstream data rate when in
      low power state (L1/L2).  The rate is coded in bits per second.


3.3.12  Minimum-Data-Rate-Downstream-Low-Power

   Description

      This Attribute contains the subscriber's minimum downstream data
      rate in low power state, as configured by the operator.  It MAY be
      included in Accounting-Request packets.

   A summary of the Minimum-Data-Rate-Downstream-Low-Power Attribute
   format is shown below.  The fields are transmitted from left to



Mammoliti, et al.        Expires August 26, 2006               [Page 14]


Internet-Draft                DSL Forum VSA                February 2006


   right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      138 (0x8A) for Minimum-Data-Rate-Downstream-Low-Power

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value of the subscriber's DSL minimum downstream data rate.  The
      rate is coded in bits per second.


3.3.13  Maximum-Interleaving-Delay-Upstream

   Description

      This Attribute contains the subscriber's maximum one-way upstream
      interleaving delay, as configured by the operator.  It MAY be
      included in Accounting-Request packets.

   A summary of the Maximum-Interleaving-Delay-Upstream Attribute format
   is shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+








Mammoliti, et al.        Expires August 26, 2006               [Page 15]


Internet-Draft                DSL Forum VSA                February 2006


   Vendor-Type

      139 (0x8B) for Maximum-Interleaving-Delay-Upstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value in milliseconds of the subscriber's DSL maximum one-way
      upstream interleaving delay.


3.3.14  Actual-Interleaving-Delay-Upstream

   Description

      This Attribute contains the subscriber's actual one-way upstream
      interleaving delay.  It MAY be included in Accounting-Request
      packets.

   A summary of the Actual-Interleaving-Delay-Upstream Attribute format
   is shown below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      140 (0x8C) for Actual-Interleaving-Delay-Upstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value in milliseconds of the subscriber's DSL actual upstream
      interleaving delay.




Mammoliti, et al.        Expires August 26, 2006               [Page 16]


Internet-Draft                DSL Forum VSA                February 2006


3.3.15  Maximum-Interleaving-Delay-Downstream

   Description

      This Attribute contains the subscriber's maximum one-way
      downstream interleaving delay, as configured by the operator.  It
      MAY be included in Accounting-Request packets.

   A summary of the Maximum-Interleaving-Delay-Downstream Attribute
   format is shown below.  The fields are transmitted from left to
   right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      141 (0x8D) for Maximum-Interleaving-Delay-Downstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value in milliseconds of the subscriber's DSL maximum one-way
      downstream interleaving delay.


3.3.16  Actual-Interleaving-Delay-Downstream

   Description

      This Attribute contains the subscriber's actual one-way downstream
      interleaving delay.  It MAY be included in Accounting-Request
      packets.

   A summary of the Actual-Interleaving-Delay-Downstream Attribute
   format is shown below.  The fields are transmitted from left to
   right.





Mammoliti, et al.        Expires August 26, 2006               [Page 17]


Internet-Draft                DSL Forum VSA                February 2006


    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |            Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              Value (cont'd.)      |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      142 (0x8E) for Actual-Interleaving-Delay-Downstream

   Vendor-Length

      6

   Value

      This field is a 4 byte unsigned integer, indicating the numeric
      value in milliseconds of the subscriber's DSL actual downstream
      interleaving delay.


3.3.17  Access-Loop-Encapsulation

   Description

      This Attribute describes the encapsulation(s) used by the
      subscriber on the DSL access loop.  It MAY be present in both
      Access-Request and Accounting-Request packets.

   A summary of the Access-Loop-Encapsulation Attribute format is shown
   below.  The fields are transmitted from left to right.

    0                   1                   2                   3
    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
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |                    Value
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    Value (cont'd) |
   +-+-+-+-+-+-+-+-+

   Vendor-Type

      144 (0x90) for Access-Loop-Encapsulation






Mammoliti, et al.        Expires August 26, 2006               [Page 18]


Internet-Draft                DSL Forum VSA                February 2006


   Vendor-Length

      5

   Value

      This field is a string 3 bytes in length, logically divided into
      three 1 byte sub-fields as shown in the following diagram:

       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 2 3
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   Data Link   |    Encaps 1   |    Encaps 2   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Valid values for the sub-fields are as follows:

      Data Link

         0x01   ATM AAL5
         0x02   Ethernet

      Encaps 1

         0x00   NA - Not Available
         0x01   Untagged Ethernet
         0x02   Single-Tagged Ethernet

      Encaps 2

         0x00   NA - Not Available
         0x01   PPPoA LLC
         0x02   PPPoA Null
         0x03   IPoA LLC
         0x04   IPoA Null
         0x05   Ethernet over AAL5 LLC with FCS
         0x06   Ethernet over AAL5 LLC without FCS
         0x07   Ethernet over AAL5 Null with FCS
         0x08   Ethernet over AAL5 Null without FCS


3.3.18  IWF-Session

   Description

      The presence of this Attribute indicates that the IWF has been
      performed with respect to the subscriber's session; note that no
      data field is necessary.  It MAY be included in both Access-



Mammoliti, et al.        Expires August 26, 2006               [Page 19]


Internet-Draft                DSL Forum VSA                February 2006


      Request and Accounting-Request packets.

   A summary of the IWF-Session Attribute format is shown below.  The
   fields are transmitted from left to right.

    0                   1
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  Vendor-Type  | Vendor-Length |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor-Type

      254 (0xFE) for IWF-Session

   Vendor-Length

      2


4.  Table of Attributes

   The following table provides a guide to which attributes may be found
   in which kinds of packets, and in what quantity; note that since none
   of the DSL Forum VSAs may be present in the Access-Accept, Access-
   Reject or Access-Challenge packets, those columns have been omitted
   from the table.

   Request       Acct-Request  #  Attribute
   0-1       0-1           1 Agent-Circuit-ID
   0-1       0-1           2 Agent-Remote-ID
   0-1       0-1         129 Actual-Data-Rate-Upstream
   0-1       0-1         130 Actual-Data-Rate-Downstream
   0         0-1         131 Minimum-Data-Rate-Upstream
   0         0-1         132 Minimum-Data-Rate-Downstream
   0         0-1         133 Attainable-Data-Rate-Upstream
   0         0-1         134 Attainable-Data-Rate-Downstream
   0         0-1         135 Maximum-Data-Rate-Upstream
   0         0-1         136 Maximum-Data-Rate-Downstream
   0         0-1         137 Minimum-Data-Rate-Upstream-Low-Power
   0         0-1         138 Minimum-Data-Rate-Downstream-Low-Power
   0         0-1         139 Maximum-Interleaving-Delay-Upstream
   0         0-1         140 Actual-Interleaving-Delay-Upstream
   0         0-1         141 Maximum-Interleaving-Delay-Downstream
   0         0-1         142 Actual-Interleaving-Delay-Downstream
   0-1       0-1         144 Access-Loop-Encapsulation
   0-1       0-1         254 IWF-Session




Mammoliti, et al.        Expires August 26, 2006               [Page 20]


Internet-Draft                DSL Forum VSA                February 2006


   The following table defines the meaning of the above table entries.

   0      This Attribute MUST NOT be present in packet.

   0-1    Zero or one instances of this Attribute MAY be present in
          packet.


5.  IANA Considerations

   No IANA action is required.

6.  Security Considerations

   The Attributes described in this document neither increase or
   decrease the security of the RADIUS protocol.  For discussions of
   various RADIUS vulnerabilities, see [RFC2607], [RFC3579], [RFC3162]
   and [RFC3580].

7.  References

7.1  Normative References

   [RFC2865]  Rigney, C., Willens, S., Rubens, A., and W. Simpson,
              "Remote Authentication Dial In User Service (RADIUS)",
              RFC 2865, June 2000.

   [RFC2866]  Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.

7.2  Informative References

   [IANA]     Internet Assigned Numbers Authority, "PRIVATE ENTERPRISE
              NUMBERS", January 2006,
              <http://www.iana.org/assignments/enterprise-numbers>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2516]  Mamakos, L., Lidl, K., Evarts, J., Carrel, D., Simone, D.,
              and R. Wheeler, "A Method for Transmitting PPP Over
              Ethernet (PPPoE)", RFC 2516, February 1999.

   [RFC2607]  Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
              Implementation in Roaming", RFC 2607, June 1999.

   [RFC3046]  Patrick, M., "DHCP Relay Agent Information Option",
              RFC 3046, January 2001.




Mammoliti, et al.        Expires August 26, 2006               [Page 21]


Internet-Draft                DSL Forum VSA                February 2006


   [RFC3162]  Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
              RFC 3162, August 2001.

   [RFC3579]  Aboba, B. and P. Calhoun, "RADIUS (Remote Authentication
              Dial In User Service) Support For Extensible
              Authentication Protocol (EAP)", RFC 3579, September 2003.

   [RFC3580]  Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
              "IEEE 802.1X Remote Authentication Dial In User Service
              (RADIUS) Usage Guidelines", RFC 3580, September 2003.

   [RFC4243]  Stapp, M., Johnson, R., and T. Palaniappan, "Vendor-
              Specific Information Suboption for the Dynamic Host
              Configuration Protocol (DHCP) Relay Agent Option",
              RFC 4243, December 2005.


Authors' Addresses

   Vince Mammoliti
   Cisco Systems
   181 Bay Street, Suite 3400
   Toronto, ON  M5J 2T3
   Canada

   Email: vince@cisco.com


   Glen Zorn
   Cisco Systems
   2901 Third Avenue, Suite 600
   SEA1/5/
   Seattle, WA  98121
   USA

   Phone: +1 (425) 344 8113
   Email: gwz@cisco.com


   Peter Arberg
   Redback Networks, Inc.
   300 Holger Way
   San Jose, CA  95134
   USA

   Email: parberg@redback.com





Mammoliti, et al.        Expires August 26, 2006               [Page 22]


Internet-Draft                DSL Forum VSA                February 2006


   Robert Rennison
   ECI Telecom
   Omega Corporate Center
   1300 Omega Drive
   Pittsburgh, PA  15205
   USA

   Email: robert.rennison@ecitele.com











































Mammoliti, et al.        Expires August 26, 2006               [Page 23]


Internet-Draft                DSL Forum VSA                February 2006


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Mammoliti, et al.        Expires August 26, 2006               [Page 24]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/