view Side-By-Side changes

   INTERNET DRAFT                 P. Congdon, C. Black, Hewlett Packard 
   Category: Informational                 A. Lior, Bridgewater Systems              
   Expires: Aug Dec 2004                             F. Bari, AT&T Wireless               
                                                            Feb 8,               
                                                          July 16, 2004 
                                                      
                      Access 
                                                      
                          Network Bandwidth Capability  
                draft-adrangi-radius-bandwidth-capability-00.txt Parameters  
                draft-adrangi-radius-bandwidth-capability-01.txt 
                                            
    
   Status of this Memo 
    
        This document is an Internet-Draft and is in full conformance 
        with all provisions of Section 10 of RFC2026. 
         
        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. 
         
         
   Abstract 
 
      This  document  describes  network  bandwidth  profile  parameters  and  a 
      protocol framework within which the parameters can be exchanged 
      between that enables an Access Network (AN) and a Home Service Network (HSN) 
      in order AAA server to determine specify the average minimum and maximum bandwidth 
      for both ingress and egress traffic 
      parameters that should be allocated by the AN access network for the 
      duration of an authorized client user session. 
       
    
     












     
   Adrangi, et al.          Expires April 13, Dec 16, 2004             [Page 1] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
   Table of Contents 
    
   1. Introduction....................................................2 
   1.2 Requirements language..........................................3 
   1.3 Terminology....................................................3 
   2. Overview........................................................3 
   2.1 Bandwidth Parameters...........................................3 
   2.1.1 Ingress Minimum Bandwidth....................................3 Bandwidth for ingress and egress.....................3 
   2.1.2 Ingress Maximum Bandwidth....................................4 
   2.1.3 Egress Minimum Bandwidth.....................................4 
   2.1.4 Egress Maximum Bandwidth.....................................4 Bandwidth for ingress and egress.....................3 
   2.2 Protocol.......................................................4 Protocol.......................................................3 
   2.2.1 Static Bandwidth Allocation..................................5 
   2.2.2 Dynamic Bandwidth Allocation.................................7 Allocation.................................6 
   2.2.2.1 Push Method................................................7 Method................................................6 
   2.2.2.2 Pull Method................................................8 
   2.3 Diameter RADIUS Interoperability...............................9 
   3. Operations.....................................................10 
   4. Attribute Format/Syntax........................................10 
   5. Format/Syntax.........................................9 
   4. Table of Attribute(s).........................................12 
   6. Attribute Usage Examples.......................................12 
   7. Attribute(s)..........................................11 
   5. IANA Considerations............................................13 
   8. Considerations............................................12 
   6. Security Considerations........................................13 
   9. Considerations........................................12 
   7. Acknowledgements...............................................13 
   10. References....................................................13 
   8. References.....................................................13 
   AuthorsÆ Addresses................................................14 Addresses................................................13 
 
 
    
   1. Introduction  
     
     The bandwidth that a user is authorized within an Access Network 
     (AN) access network  
     can be a result of the AN bandwidth access network capabilities based on its 
     architecture and access technology, and the type of user 
     subscription to the home network (e.g., gold, silver, bronze user 
     types).   
      
     This document describes a simple protocol framework that enables 
     an Access Network (AN) access network to advertise its network bandwidth capabilities 
     that it can allocate for a given AN client connection 
     to the clientÆs Home Service Network (HSN). connection.  And, it also 
     enables the HSN home network to indicate its selection of the desired network bandwidth 
     capabilities for the client user connection to within the AN. access network.   
 
     User bandwidth can be determined during initial authentication 
     authorization of the session.  It is also desirable to change the 
     bandwidth for the mid-session.  For example, the user may want to purchase 
     additional bandwidth to download a large file.  This document 
     enables operators to dynamically modify the bandwidth allocation 
     for a session. 
      
     This document defines new AAA attributes that can optionally be 
     used for the following; 
      
       . Conveying bandwidth parameters to the home network that an 
          access network can allocate for a given user session 


  
   Adrangi, et al.          Expires Aug Dec 30, 2004             [Page 2] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
     This document defines a new AAA attribute used for exchanging 
     network 
                                   
               
 
       . Conveying the desired bandwidth parameters between the AN and the HSN, to 
     determine from the average minimum and maximum bandwidth for both 
     ingress and egress traffic home 
          network that an AN should allocate be allocated by the access network for 
          the duration of an authorized client the user session.  This attribute is   
      
     These attributes are also used for reporting the allocated 
     bandwidth in accounting records.  The attribute is attributes are described for 
     RADIUS [1]. [1], but works as is also in Diameter [RFC 3588], and 
     through the translation rules defined in [Diameter NASREQ]. 
 
   1.2 Requirements language 
 
      In this document, several words are used to signify the 
      requirements of the specification.  These words are often 
      capitalized.  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]. 
    
   1.3 Terminology 
 
      Access Network (AN) 
          The network that provides wired or wireless connectivity 
          to 
    
 
   2. Overview  
    
     This section describes the Internet for clients (or stations) present in bandwidth parameters and the 
          local access area. This MAY protocol 
     by which these parameters can be in exchanged between a separate security NAS and 
          routing domain with respect the 
     AAA server to help the Home Service Network or a 
          Mediating Network. 
       
      Home Service Network (HSN) 
          The access network providing the service and therefore maintaining 
          the direct relationship to its users and subscribers. All AAA   
          functions are ultimately performed by the HSN. 
 
      RADIUS server 
         ôThis is a server which provides for 
         authentication/authorization via the protocol described in 
         [1], and for accounting as described in [6].ö  It is deployed 
         in the PWLAN AN, MN, and HSN. 
 
   2. Overview  
    
     This section describes determine the bandwidth 
     parameters and that should be allocated for the protocol userÆs connection by which these parameters are exchanged between an AN and a HSN. 
     the access.    
 
   2.1 Bandwidth Parameters 
    
      Bandwidth Profile parameters describe the average consists of four parameters: minimum 
      bandwidth, and maximum 
      data rates (for bandwidth specified both for ingress and egress traffic) for a client 
      connection within an AN.  There are four bandwidth parameters, 
      which are described in the 
      egress.  The following subsections. subsections describe these parameters.  
       
 
   2.1.1 Ingress Minimum Bandwidth 
 
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 3]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 
                                   
               
 
        The for ingress minimum bandwidth parameter and egress 
 
        It indicates the average minimum ingress peak ingress/egress data rate that an AN will try to provide to an the 
        authorized user. user should get within the access network.  This 
        value is a target, rather than a guarantee.   
    
   2.1.2 Ingress Maximum Bandwidth 
    
        The ingress maximum bandwidth parameter indicates the average 
        maximum for ingress data rate that an AN can allow to an authorized 
        user.   
    
   2.1.3 Egress Minimum Bandwidth 
    
        The minimum egress bandwidth parameter indicates the average 
        minimum egress data rate that an AN will try to provide to an 
        authorized user.  
        
   2.1.4 Egress Maximum Bandwidth 
    
        The maximum and egress bandwidth parameter 
         
        It indicates the average maximum ingress/egress data rate that 
        an AN access network can allow to an authorized user.   
 
    
   2.2 Protocol 
    
      Two protocols are described.  One protocol is used to allocate 
      bandwidth when a service is initiated (referred to as Static 
      Bandwidth Allocation); the other protocol describes how to change 
  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 3] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
      bandwidth attribute dynamically that is, mid session (referred mid-session (also 
      referred to as Dynamic Bandwidth Allocation). 
       
      Both protocols exchange bandwidth parameters using the various 
      RADIUS 
      AAA messages, and they are comprised of three phases:  bandwidth 
      Advertisement, Selection, and Confirmation. 
       
      Bandwidth Advertisement: 
 
         MAY be sent in Access-Request packet in RADIUS, and  the AAR 
         and DER commands in Diameter [Diameter NASREQ, Diameter EAP], 
         from the AN NAS to the HSN 
         and conveys home AAA server. The attributes convey 
         possible/available bandwidth parameters that can be allocated 
         for an the AN access network client connection to the HSN AAA server by 
         the 
         AN.  Advertisements are optional. NAS. 
       
      Bandwidth Selection:  
 
         MAY be sent in Access-Accept packet and Change of 
         Authorization (COA) messages. messages in RADIUS. MAY also be sent in 
         RAR command in Diameter [4]. Selection conveys the desired 
         bandwidth parameters for the AN Client an access network client connection 
         to the AN NAS by the HSN. home AAA server. 
    
      Bandwidth Confirmation:   
 
         If Bandwidth Selection is received and enforced, It the 
         attributes MUST be sent in Accounting-Request packets. packets in 
         RADIUS and in ACR command in Diameter. Confirmation indicates 
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 4]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 
         that the desired bandwidth parameters specified by a HSN home 
         network are being enforced by the AN. access network. 
    
    
      The Bandwidth Attribute (BA), Attributes, defined in section 3, is are used to carry 
      the Bandwidth Advertisement, Selection, Confirmation in various 
      RADIUS packets. packets and Diameter commands. 
    
      An Advertisement, Selection, Confirmation is said to be valid if 
      it contains the four aforementioned bandwidth parameters and parameters.  For a 
      valid Advertisement, Selection or Confirmation, the minimum 
      bandwidth rate values for ingress and egress traffic MUST be 
      equal or less than their corresponding maximum bandwidth rate 
      values. 
 
      If a Selection is sent in response to an Advertisement, for the 
      Selection to be considered valid, then the bandwidth parameters in the 
      Selection MUST NOT exceed the corresponding bandwidth parameters 
      in the Advertisement.  A bandwidth rate value of zero in 
      Selection should be interpreted as a ödonÆt careö value.   
 


  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 4] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
      The following subsections describe static and dynamic bandwidth 
      allocation. 
    
   2.2.1 Static Bandwidth Allocation 
 
        Static bandwidth allocation is preformed performed during the initial 
        session authentication / authorization. 
         
        The following diagram shows the protocol interaction between 
        the AN NAS and the HSN home RADIUS server for determining network 
        bandwidth rates that an AN access network needs to allocate for an AN a 
        client connection. 
 
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
       
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 5]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 
                                   
               
 
      AN connection within the access network. 
 
       
        Client      AN Device + AAA client       HSN + AAA Server              NAS                  home RADIUS server      
                                     
          |                  |                              | 
          |                  |                              | 
          | Authentication   |                              | 
          | Phase Begin      |                              | 
          |----------------->|        Access-Request        | 
          |                  |            +                 | 
          |                  |    BA for Advertisement      | 
          |                  |----------------------------->| 
          |                  |                              | 
          |<<More Authentication/Authorization Exchanges>>  | 
          |                  |                              | 
          |                  |                              | 
          |                  |<-----------------------------| 
          |                  |        Access-Accept         | 
          | Authentication   |            +                 | 
          |    Accept        |      BA for Selection        | 
          |<-----------------|                              | 
          |                  |                              | 
          |                  |                              | 
          |                  |       Accounting Request     | 
          |                  |             +                | 
          |                  |     BA for Confirmation      | 
          |                  |----------------------------->| 
          |                  |                              | 
                                        
    
    
        The AN NAS MAY send an Advertisement in an Access-Request message.  
        If the HSN home RADIUS server receives an invalid Advertisement, 
        then the HSN RADIUS server MUST silently discard the Access-Request. Access-
        Request. 
 
        A HSN home RADIUS server MAY send the Selection after receiving a 
        valid Advertisement.  It MAY also send the Selection in the 
        absence of an Advertisement, based on local policies such as 
  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 5] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
        the AN clientÆs subscription profile.  When the AN NAS receives an 
        invalid Selection, it MUST treat the Access-Accept message as 
        an Access Reject. 
         
        If the AN NAS receives a valid Selection in response to an Access-
        Request that did not contain an Advertisement, then the AN NAS MAY 
        honor the Selection. 
         
        If the AN NAS receives a valid Selection in response to an Access-
        Request that contained a valid Advertisement, then the AN NAS MUST 
        honor the Selection. 
         
 
        In the absence of a Selection after sending a valid 
        Advertisement, in accordance with local policy, the AN access 
        network MAY 

  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 6]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 enforce its default bandwidth rate values or it MAY 
        use ôbest öbest effortö bandwidth for that client connection.  
         
   2.2.2 Dynamic Bandwidth Allocation 
 
        Dynamic bandwidth allocation uses the Change of Authorization 
        (COA) RADIUS message as defined in [3], and the Diameter RAR 
        message as defined in [3]. [4]. These messages are referred to as 
        the re-authorization messages in this specification. 
    
        In accordance with [3] there are two methods for dynamically 
        changing authorization attributes of a session.  These two 
        methods are described in this section. 
 
        At anytime during the session the HSN home AAA server may send the AN 
        NAS a COA re-authorization message containing session 
        identification attributes (see [3] for the possible options).  
        The COA re-authorization message may include authorization 
        attributes in which case it is pushing "pushing" the BAs bandwidth 
        attributes to the AN; or NAS. Or, it may instruct the AN NAS to generate 
        an Authorize-Only authorize-only AAA exchange to "pull" the bandwidth 
        attributes. In RADIUS this exchange is an Access-Request (Access-Request with 
        Service-Type set to 
        ôAuthorize-Onlyö) in which case "Authorize-Only". In Diameter it is instructing the AN to 
        pull AAR 
        command with the BAs. Auth-Request-Type AVP set to AUTHORIZE_ONLY. 
         
        In either push "push" or pull "pull" method, upon successful acceptance 
        of the new bandwidth parameters for the session.  The AN session, the NAS MUST 
        generate an Accouting-Stop record that contains the old 
        bandwidth attributes followed by an Accounting-Start message 
        that contains the new bandwidth attributes. 
         
        In order to allow for downstream correlation of the accounting 
        records, an AN NAS that supports dynamic bandwidth allocation MUST 
        include Acct-Multi-Session-Id when writing accounting records.  
 
   2.2.2.1 Push Method 
  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 6] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
    
          In the Push Method, to effect a dynamic bandwidth change the 
          HSN 
          home RADIUS server sends a COA re-authorization message and 
          includes a valid Selection.  The 
          AN RADIUS server MAY also 
          include other attributes in the COA re-authorization message. 
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 7]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 
                                   
               
 
             AN                                            HSN 
             | 
    
    
    
             NAS                                     Home RADIUS Server               
              |                                              | 
              |                                              |  COA 
              |re-authorization + BAs for Selection          | 
              |<---------------------------------------------| 
              |                                              | 
              |                                              | 
              |  COA  re-authorization ACK                        | 
              |--------------------------------------------->| 
              |                                              | 
              |                                              | 
              | Accounting-Stop + old BAs for Confirmation   | 
              |--------------------------------------------->| 
              |                                              | 
              | Accounting-Start + new bandwidth             | 
              |--------------------------------------------->| 
              |                                              | 
              |                                              | 
    
 
          Upon the successful reception of the COA re-authorization message 
          (see [3] for details) by the AN, NAS, if the COA re-authorization 
          message contains an invalid Selection, the AN NAS MUST respond 
          with a COA re-authorization NAK with Error Cause (101) set to ôInvalid 
          öInvalid Requestö (404). 
           
          If the AN NAS is able to offer the requested bandwidth to the 
          specified session, the AN NAS MUST reply with a COA-ACK re-authorization 
          ACK and it MUST generate an Accounting-Stop record containing 
          the old bandwidth attributes followed by an Accounting-Start 
          record containing the new bandwidth attributes.  If the AN NAS 
          can not comply with the request for new bandwidth it MUST 
          reply with 
          a COA-NAK re-authorization NAK with Error Cause (101) set to ô"Resources 
          "Resources Unavailable"(506). 
    
   2.2.2.2 Pull Method 
    
          Alternatively, 
           
          If the NAS receives a re-authorization message that does not 
          include Bandwidth attributes then the NAS must not alter the 
          bandwidth already allocated to the session. 
    
    
    
    
    
  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 7] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
   2.2.2.2 Pull Method 
    
          Alternatively, in the pull method, to effect a dynamic 
          bandwidth change, as per [3], the HSN home network sends a COA re-
          authorization message to instruct the AN to generate an 
          Authorize-Only request (Access-Request with Service-Type set 
          to Authorize-Only). 
 
 
 
 
 
 
 
 
 
 
 
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 8]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 
                                   
               
 
            AN                                             HSN 
 
 
    NAS                                             Home RADIUS server 
        |                                                      | 
        |  COA re-authorization + Service-Type ôAuthorize = öAuthorize Onlyö   | 
             |<----------------------------------------------| 
             | 
        |<-----------------------------------------------------| 
        |                                                      |  COA 
        |re-authorization NAK + Service-Type ôAuthorize Onlyö      | = öAuthorize Onlyö| 
        |          + Error-Cause  "Request Initiated"          | 
             |---------------------------------------------->| 
        |----------------------------------------------------->| 
        |                                                      | 
        | Access-Request + Service-Type ôAuthorize Onlyö| öAuthorize Onlyö       | 
        |                + BAs for Advertisement               | 
             |---------------------------------------------->| 
        |----------------------------------------------------->| 
        |                                                      | 
        | Access-Accept + BAs for Selection                    | 
             |<----------------------------------------------| 
        |<-----------------------------------------------------| 
        |                                                      | 
        | Accounting-Stop + old BAs for Confirmation           | 
             |---------------------------------------------->| 
        |----------------------------------------------------->| 
        |                                                      | 
        | Accounting-Start + new BAs for Confirmation          | 
             |---------------------------------------------->| 
        |----------------------------------------------------->| 
        |                                                      | 
        |                                                      | 
                                      
    
          As with the static bandwidth allocation (described earlier), 
          the AN MAY Advertise the currently available bandwidth in the 
          Authorize-Only message. 
    
          Upon receiving the Authorize-Only message from the AN, the 
          HSN 
          RADIUS server MUST respond with either an Access-Accept 
          message or an Access-Reject message. 
           
          When responding with an Access-Accept message, the HSN RADIUS 
          server MAY include the BAs for Selection.  If the Authorize-Only Authorize-
          Only message included an Advertisement, the bandwidth 
          parameters in Selection MUST be within the bounds of 
          bandwidth parameters in the Advertisement received in the 
          Authorize-Only message. 
           
          Upon sending an Authorize-Only message, the AN will receive 
          an Access-Accept message or an Access-Reject message. 
 



  
   Adrangi, et al.          Expires Dec 30, 2004             [Page 8] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
          Upon receiving an Access-Reject in response to the Authorize-
          Only, the AN will terminate the session and send an 
          Accounting-Stop record. 
           
          Upon receiving an Access-Accept in response to an Authorize-
          Only request that does not contain bandwidth Selection, the 
          AN 
          access network MUST resume utilizing the existing allocate its default bandwidth parameters, rate 
          values, and it then the NAS MUST NOT generate an Accounting Stop message. 
           
  
   Adrangi, et al.          Expires Aug 30, 2004             [Page 9]
    
Internet Draft   Access Network Bandwidth Capability  8 Feb 2004 Accouting-Stop 
          record that contains the old bandwidth attributes followed by 
          an Accounting-Start message that contains the new bandwidth 
          attributes.   
 
          Upon receiving an Access-Accept packet that contains an 
          invalid Bandwidth Selection, the AN MUST treat the response 
          as an Access-Reject and immediately terminate the session. 
           
          Upon receiving an Access-Accept message in response to an 
          Authorize-Only message that contained the Bandwidth 
          Advertisement, then providing the bandwidth selections are 
          within the bounds of the Advertisement, then AN MUST honor 
          the requested bandwidth and generate an Accounting-Stop 
          message that contains the old bandwidth attributes followed 
          by an Account-Start message that contains the new bandwidth 
          attributes.  If the bandwidth Selection were outside the 
          bounds of the Advertisement, then the AN MUST treat the 
          Access-Accept as an Access-Reject and immediately terminate 
          the session. 
           
          Upon receiving an Access-Accept message that contains a valid 
          Selection in response to an Authorize-Only that did not 
          contain the Advertisement, the AN MAY honor the Selection or 
          it MAY continue to honor the previously agreed to bandwidth.  
          In the former case, the AN must generate an Accounting Stop 
          message containing the old bandwidth attributes followed by 
          an Accounting-Start message containing the current bandwidth 
          attributes.  
    
 
   3. Operations  
    
     Operation  is  identical  to  that  defined  in  
           
   2.3 Diameter RADIUS  AAA 
     specifications  [1][2] Interoperability 
 
      In deployments where both RADIUS clients talking with Diameter 
      Servers or Diameter Client talking with RADIUS server then a 
      translation agent will be deployed and  Dynamic  Authorization  Extensions operate in accordance to 
     Remote Authentication Dial In User Service (RADIUS)[3]. 
    
   4. 
      the NASREQ specification. 
 
   3. Attribute Format/Syntax 
    
     This section describes format and syntax for the attribute attributes that 
     carries AN 
     carry the network bandwidth rate parameters. The attribute is attributes are used 
     for bandwidth rate parameters Advertisement, Selection, and 
     Confirmation. 
      
     The attribute MAY be present in Access-Request, Access-Accept, 
     Accounting-Request. 
      
  
   Adrangi, et al.          Expires Aug Dec 30, 2004             [Page 10] 9] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
    
     A summary of the AN Bandwidth Parameter Attribute Attributes is shown below. 
    
    
    
       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     |     Params     Value                     | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |             Value             | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    
         
        Type  
         
            TBD Network Bandwidth Capability  
         
         
        Length 
         
           8 
 
        Params 
         
           It indicates what the value signifies.  The values defined 
           in the document are: 
            
           1 û - Ingress Average Minimum Bandwidth Rate for Ingress Traffic 
         
         
        Length 
         
           6  
    
        Value 
            
        An integer value representing the ingress average minimum 
        bandwidth rate in 
           bits bytes per second second. 
 
         
       0 1 2 û Average Minimum Bandwidth Rate for Ingress Traffic in 
           Kilo bits per second 3 û Average Minimum Bandwidth Rate for Ingress Traffic in 
           Giga bits per second 4 û Average Maximum Bandwidth Rate for Ingress Traffic in 
           bits per second 5 û Average Maximum Bandwidth Rate for Ingress Traffic in 
           Kilo bits per second 6 û Average Maximum Bandwidth Rate for Ingress Traffic in 
           Giga bits per second 7 û Average Minimum Bandwidth Rate for Egress Traffic in 
           bits per second 8 û Average Minimum Bandwidth Rate for Egress Traffic in 
           Kilo bits per second 9 û Average Minimum Bandwidth Rate for Egress Traffic in 
           Giga bits per second 
           10 û Average Maximum Bandwidth Rate for Egress Traffic in 
           bits per second 
           11 û Average Maximum Bandwidth Rate for Egress Traffic in 
           Kilo bits per second 
           12 û 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |     Type      |    Length     |     Value                     | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |             Value             | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    
         
        Type  
         
            TBD - Ingress Average Maximum Bandwidth Rate for Egress Traffic  
         
         
        Length 
         
           6 
         
    
        Value 
            
        An  integer  value  representing  the  egress  average  minimum 
        bandwidth rate in 
           Giga bits bytes per second 
         
  
   Adrangi, et al.          Expires Aug Dec 30, 2004            [Page 11] 10] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
         
         
        Value 
            
           An integer value interpreted based the value of Param. 
    
   5.  Table of Attribute(s) 
 
     The following table provides a guide to which attribute(s) may be 
     found in which kinds of packets, and in what quantity.   
    
    
     Request Accept Reject Challenge Accounting  #  Attribute 
                                      Request 
       0-4      0-4      0      0         0-4   TBD  Network Bandwidth  
                                                     Capability  
    
    
    
   For Change-of-Authorization Messages 
    
      Request   ACK      NAK   #   Attribute 
    
       0-4      0-4      0    TBD   Network Bandwidth Capability 
    
    
   6. Attribute Usage Examples 
    
     This section provides an example on how Bandwidth attribute can be 
     used to indicate the four bandwidth rate parameters, in 
     Advertisement, Selection, and Confirmation. 
      
     Ingress Minimum Bandwidth Rate for 28 Kilo bits per second 
                                   
               
 
         
         
       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 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |     TBD     Type      |    7    Length     |  2     Value                     | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |                         28             Value             | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    
   Ingress Maximum 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    
         
        Type  
         
            TBD Egress Average Minimum Bandwidth Rate for 28 Kilo bits 
         
         
        Length 
         
           6 
         
    
        Value 
            
        An integer value representing the ingress average maximum 
        bandwidth rate in bytes per second 
    
    
       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 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |     TBD     Type      |    7    Length     |  5     Value                     | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |                         28             Value             | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
    
         
        Type  
         
            TBD Egress Minimum Average Maximum Bandwidth Rate for 28 Kilo bits 
         
         
        Length 
         
           6 
    
        Value 
            
        An  integer  value  representing  the  egress  average  maximum 
        bandwidth Rate in bytes per second 
    
    
    
   4. Table of Attribute(s) 
  
   Adrangi, et al.          Expires Aug Dec 30, 2004            [Page 12] 11] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
 
     The following table provides a guide to which attribute(s) may be 
     found in which kinds of packets, and in what quantity.   
    
    
   Request Accept Reject Challenge Accounting  #  Attribute 
                                   Request 
   0-1      0-1   0      0         0-1        TBD Ingress Minimum Band.  
                                                      
   0-1      0-1   0      0         0-1        TBD Ingress Maximum Band.  
                                                      
   0-1      0-1   0      0         0-1        TBD Egress Minimum Band.  
    
   0-1      0-1   0      0         0-1        TBD Egress Minimum Band.  
    
    
   For Change-of-Authorization Messages 
    
      Request  ACK    NAK      #   Attribute 
    
       0-1      0 1 2 3 4 5 6 7 8 9      0 1 2 3 4 5 6 7 8 9      TBD      Ingress Minimum Bandwidth 
       0-1      0 1 2 3 4 5 6 7 8 9      0 1 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |      TBD       |    7          |  8                            | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |                         28                                    | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
 
   Egress      Ingress Maximum Bandwidth Rate for 28 Kilo bits per second 
       0-1      0 1 2 3 4 5 6 7 8 9      0 1 2 3 4 5 6 7 8 9      TBD      Egress Minimum Bandwidth 
       0-1      0 1 2 3 4 5 6 7 8 9      0 1 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |      TBD       |    7          |  11                           | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
      |                         28                                    | 
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
 
    
    
   7.      Egress Maximum Bandwidth 
                                    
                                   
    
   Note 1 : if the Change-of-Authorization message contains any 
   bandwidth attributes then all the bandwidth attributes received for 
   this session are overwritten.  If the Change-of-Authorization 
   message does not contain any bandwidth attributes then, the 
   previously received bandwidth attributes remain in effect. 
    
   Note 2: if one of the attribute is included in a qualified RADIUS 
   packet, then all the three attributes MUST be included. 
    
   5. IANA Considerations 
    
     This document requires the assignment of  three four new RADIUS attribute 
     numbers for the following attribute(s): 
      
           AN-Bandwidth-Rate-Paramters 
      
        1) Ingress Average Minimum Bandwidth Rate 
        2) Ingress Average Maximum Bandwidth Rate 
        3) Egress Average Minimum Bandwidth Rate 
        4) Egress Average Maximum Bandwidth Rate 
            
     Please See section 3 for the registered list of numbers. 
    
    
   8. 
      
 
   6. Security Considerations 
    
  
   Adrangi, et al.          Expires Dec 30, 2004            [Page 12] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
     The attributes in this document have no additional security 
     considerations beyond those already identified in [?]. 
      
    
   9. [1]. 
      
    
   7. Acknowledgements 
      
     The authors would specially like to thank Jari Arkko (of Ericsson) 
     for his through review of the draft, providing feedback/comments 
     and proposing text. 
      
     The authors would like to thank Bernard Aboba (of Microsoft), 
     Parviz Yegani (of Cisco), Stefan De_cnodder (of alcatel) for their 
     feedback and guidance. 
    
   10. 
    
   8. References 
 
     [1] Rigney, C., Rubens, A., Simpson, W. and S. Willens, "Remote  
         Authentication Dial In User Server (RADIUS)", RFC 2865, June 
         2000.  
                        
     [2] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000.  
                        
     [3] Chiba, M., Dommety, G., Eklud, M., Mitton, D., Aboba, B.,  
         ôDynamic  
         öDynamic Authorization Extensions to Remote Authentication 
         Dial In User Service (RADIUS)ö, RFC 3576, July 2003. 
    
     [4] Calhoun, et al., ö Diameter Base Protocolö, RFC 3588, 
         September 2003. 
    
    
   AuthorsÆ Addresses 
 
      Farid Adrangi 
      Intel Corporation 
      2111 N.E. 25th Avenue 
      Hillsboro  OR 
      USA 
 
      Chuck Black  
      ProCurve Networking Business  
      Hewlett-Packard Company  
      8000 Foothills Blvd  
      Roseville, CA 95747  
        
      Phone:  +1 916 785 9713  
      Fax:    +1 916 785 1199  
      Email:  chuck.black@hp.com 
 
 
      Paul Congdon  
      ProCurve Networking Business  
  
   Adrangi, et al.          Expires Aug Dec 30, 2004            [Page 13] 
    
Internet Draft   Access   Network Bandwidth Capability  8 Feb Parameters  July 16 2004 
                                   
               
 
    
   AuthorsÆ Addresses 
 
   Farid Adrangi, Intel Corporatation        farid.adrangi@intel.com 
   Chuck Black, Hewlett Packard Company      chuck.black@hp.com 
   Paul Congdon, Hewlett Packard 
                                   
               
 
      Hewlett-Packard Company  
      8000 Foothills Blvd - MS 5662  
      Roseville, CA 95747  
        
      Phone:  +1 916 785 5753  
      Fax:    +1 916 785 8478  
      Email:  paul.congdon@hp.com 
    
      Avi Lior 
      Bridgewater Systems Corporation 
      303 Terry Fox Drive 
      Suite 100 
      Ottawa, Ontario  K2K 3J1 
      Canada 
 
      Farooq Bari, Bari 
      AT&T Wireless 
      7277 164th Avenue N.E. 
      Redmond  WA 
      USA 
    
      Phone: +1 425-580-5526 
      EMail: farooq.bari@attws.com             
   Avi Lior, Bridgwater Systems Corporation  avi@bridgewatersystems.com 
       
    
    
    
   Full Copyright Statement 
    
        Copyright  (C)  The  Internet  Society  (2002).    All  Rights 
        Reserved. 
         
        This  document  and  translations  of  it  may  be  copied  and 
        furnished to others, and derivative works that comment on or 
        otherwise explain it or assist in its implementation may be 
        prepared, copied, published and distributed, in whole or in 
        part, without restriction of any kind, provided that the above 
        copyright notice and this paragraph are included on all such 
        copies and derivative works.  However, this document itself may 
        not be modified in any way, such as by removing the copyright 
        notice or references to the Internet Society or other Internet 
        organizations, except as needed for the purpose of developing 
        Internet standards in which case the procedures for copyrights 
        defined in the Internet Standards process must be followed, or 
        as required to translate it into languages other than English. 
         
        The limited permissions granted above are perpetual and will 
        not be revoked by the Internet Society or its successors or 
        assigns. 
         


  
   Adrangi, et al.          Expires Dec 30, 2004            [Page 14] 
    
Internet Draft   Network Bandwidth Parameters  July 16 2004 
                                   
               
 
        This document and the information contained herein is provided 
        on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 
        ENGINEERING TASK FORCE DISCLAIMS 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.                             
                 
         
   Acknowledgement 
         
        Funding for the RFC Editor function is currently provided by 
        the Internet Society. 
         
         





































  
   Adrangi, et al.          Expires Aug Dec 30, 2004            [Page 14] 15] 
----