One document matched: draft-yeh-radext-ext-traffic-statistics-01.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc, which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2865 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2865.xml">
<!ENTITY RFC2866 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2866.xml">
<!ENTITY RFC2869 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2869.xml">
<!ENTITY RFC3162 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3162.xml">
<!ENTITY RFC4818 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4818.xml">
<!ENTITY RFC5226 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5226.xml">

]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt'?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), please see ttp://xml.resource.org/authoring/README.html. -->
<?rfc strict="yes"?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->

<rfc category="std" docName="draft-yeh-radext-ext-traffic-statistics-01" ipr="trust200902">

<!-- category values: std, bcp, info, exp, and historic ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902, or pre5378Trust200902 you can add the attributes updates="NNNN" and obsoletes="NNNN" they will automatically be output with "(if approved)" -->


<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only necessary if the full title is longer than 39 characters -->

  <title abbrev="RADIUS Accounting Extensions">
  RADIUS Accounting Extensions of Traffic Statistics</title>

    <author fullname="Leaf Y. Yeh" initials="L." role="editor" surname="Yeh">
      <organization>Huawei Technologies</organization>
      <address>
        <postal>
          <street>F4, Huawei Area, Bantian,</street>
          <city>Longgang District</city>
          <region>Shenzhen</region>
          <code>518129</code>
          <country>P.R.China</country>
        </postal>
        <phone>+86-755-28971871</phone>
        <email>leaf.y.yeh@huawei.com</email>
      </address>
    </author>   
             
   <date year="2011" />
    
    <!-- Meta-data Declarations -->
    <area>Ops&Mgmt</area>
    <workgroup>Radext Working Group</workgroup>
    <keyword>RADIUS Attributes</keyword>
    <keyword>Dual Stack</keyword>
    <keyword>User Type</keyword>


<abstract>
<t>This document specifies the RADIUS attributes extensions of IPv4 and IPv6 traffic statistics for the differentiated accounting policies and traffic recording on the AAA server.</t>
</abstract>

</front>

<!-- ***** MIDDLE MATTER ***** -->

<middle>

  	
<section anchor="s1" title="Introduction">

<t>RADIUS has been widely used as the centralized Authentication and Authorization management method for the service provision to the users in Broadband network.   <xref target="RFC3162"/>, <xref target="RFC4818"/> and <xref target="ietf-radext-ipv6-access-05"/> has specified some attributes to support the service provision of IPv6-only and dual-stack. Radius is also a protocol for carrying accounting information between a Network Access Server and a shared accounting server. In the scenarios of dual-stack or any other IPv6 transition use case, such as DS-Lite, 6rd or the potential 4rd, there is a demand to report the separated IPv4 & IPv6 traffic statistics for the differential accounting and traffic recording.</t>

<t><xref target="BBF TR-187"/> (Edited by ALU & Cisco), which dedicates for the network architecture models and elements requirements in the PPPoE scenario to support IPv6-only or dual stack for Internet access service, has expressed this demand in its section 9.4. The explicit texts are as follows:
<list style="empty">
<t>The BNG must also be able to support separate queues for IPv4 and IPv6 traffic, as they may be used to offer IPv4 and IPv6 services with different policies.</t>
<t>Note that BNG of BBF is a kind of NAS of IETF.</t>
<t>R-60 The BNG MUST support forwarding IPv6 and IPv4 traffic in common traffic classes.</t>
<t>R-61 The BNG MUST support forwarding IPv6 and IPv4 traffic in separate traffic classes.</t>
<t>R-64 The BNG MUST support input and output octet counters that are separate for both IPv6 and IPv4 traffic.</t>
<t>R-65 The BNG MUST support input and output packet counters that are separate for both IPv6 and IPv4 traffic.</t>
</list></t>
<t>Per the section 9.4 of BBF TR-187, the NAS is required to support separate queues and counters for IPv4 or IPv6 traffic, and the Radius attributes of Acct-Input-Octets, Acct-Output-Octets, Acct-Input-Packets, Acct-Output-Packets are recommended to use for the combination traffic. That means some new RADIUS attributes is required to report the separated IPv4 or IPv6 traffic statistics.</t>

<t><xref target="draft-maglione-radext-ipv6-acct-extensions-01"/> (Edited by Telecom Italia, Ericsson & Magyar Telekom) tries to define the following attributes:</t>      
<figure><artwork>
   IPv6-Acct-Input-Octets
   IPv6-Acct-Output-Octets
   IPv6-Acct-Input-Packets
   IPv6-Acct-Output-Packets
   IPv6-Acct-Input-Gigawords
   IPv6-Acct-Output-Gigawords
</artwork></figure>
<t>for the collecting of IPv6 traffic statistics in RADIUS accounting messages. <xref target="draft-hu-v6ops-radius-issues-ipv6-00"/> (Edited by China Telecom & ZTE) presents the same issue on the accounting for dual-stack traffic statistics, but it sounds like limit to the PPP case. <xref target="draft-winter-radext-fancyaccounting-00"/> also shows the interest to define a group of attributes to report the statistics for various traffic classes, but tries to use the extended type space. And <xref target="draft-yeh-radext-dual-stack-access-02"/> (Edited Huawei) tries to use the traditional format defined in <xref target="RFC2865"/>, <xref target="RFC2866"/> and <xref target="RFC2869"/> to extend some new attributes:</t>
<figure><artwork>
   Acct-Input-IPv4-Octets
   Acct-Output-IPv4-Octets
   Acct-Input-IPv4-Packets
   Acct-Output-IPv4-Packets
   Acct-Input-IPv4-Gigawords
   Acct-Output-IPv4-Gigawords
   Acct-Input-IPv6-Octets
   Acct-Output-IPv6-Octets
   Acct-Input-IPv6-Packets
   Acct-Output-IPv6-Packets
   Acct-Input-IPv6-Gigawords
   Acct-Output-IPv6-Gigawords
</artwork></figure>
<t>against the dual-stack case for traffic statistics reporting in RADIUS.</t>

<t><xref target="draft-ietf-radext-radius-extensions-02"/>, which is already in the phase of WGLC, has extended the type space of RADIUS attribute and defined the new formats for the extended type attributes with some new data types. That might means the type code in the new extended space will be used to define a new attribute, if it is agreed to move the 'Unassigned' code space (from 144 to 191) to be 'Deprecated'.</t>

<t>This document tries to use both the traditional format defined in <xref target="RFC2865"/> and the new format defined in <xref target="draft-ietf-radext-radius-extensions-02"/> for the extension of IPv4 and IPv6 traffic statistics, and let the WG decides which one is more suitable for the cases mentioned here.</t>

</section>


<section anchor="s2" title="Terminology and Language">

<t>This document describes some new RADIUS attributes and the associated usage on NAS and AAA server. This document should be read in conjunction with the relevant RADIUS specifications, including <xref target="RFC2865"/>, <xref target="RFC2866"/>, <xref target="RFC2869"/>, and <xref target="draft-ietf-radext-radius-extensions-02"/>, for a complete mechanism. Definitions for terms and acronyms not specifically defined in this document are defined in RFC2865, RFC2866, RFC2869, and <xref target="draft-ietf-radext-radius-extensions-02"/>.</t>

<t>The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in BCP 14, <xref target="RFC2119"/>.</t>

</section>


<section anchor="s3" title="Deployment Scenarios">

<t>Figure 1 show the typical use case of the traffic statistics reporting for the dual-stack users.</t>

<figure anchor="f1" title="Traffic Statistics of Dual-Stack Users for RADIUS Accounting">
<artwork>
 +----------+                +----------+                +----------+
 |  Host /  |      PPPoE     |          |     RADIUS     |   AAA    |
 | Customer |  ------------  |   NAS    |  ------------  |  Server  |
 |  Router  |      IPoE      |          |   Accounting   |          |
 +----------+                +----------+                +----------+
  Dual-Stack         Separated queues and counter
                      for IPv4 and IPv6 traffic
</artwork>
</figure>

<t>Note that traffic statistics reporting is also needed in the IPv6 transition cases, such as DS-Lite, 6rd or the potential 4rd.</t>

</section>




<section anchor="s4" title="Traffic Statistics Attributes">

<section anchor="s4.1" title="Define the Attributes in the Traditional Unsigned Type Space">

<t>There are 8 new attributes of the traffic statistics, including:</t> 
<figure><artwork>
   Acct-Input-IPv4-Octets
   Acct-Output-IPv4-Octets
   Acct-Input-IPv4-Packets
   Acct-Output-IPv4-Packets
   Acct-Input-IPv6-Octets
   Acct-Output-IPv6-Octets
   Acct-Input-IPv6-Packets
   Acct-Output-IPv6-Packets
</artwork></figure>
<t>defined in this section per the traditional format defined in <xref target="RFC2865"/>.</t>

<t>Description
<list style="empty">
<t>The traffic statistics attributes, including Acct-Input-IPv4-Octets, Acct-Output-IPv4-Octets, Acct-Input-IPv4-Packets, Acct-Output-IPv4-Packets and Acct-Input-IPv6-Octets, Acct-Output-IPv6-Octets, Acct-Input-IPv6-Packets, Acct-Output-IPv6-Packets, indicate how many octets or packets of IPv4 or IPv6 received from the user or sent to the user from the starting of this service provided, and can be present in Accounting-Request records while the Acct-Status-Type is set to Interim-Update or Stop.</t>

<t>For the attribute of Acct-Input-IPv4-Octets, NAS report how many Octets of IPv4 traffic received from the user from the starting of the service authorized.</t>
<t>For the attribute of Acct-Output-IPv4-Octets, NAS report how many Octets of IPv4 traffic sent to the user from the starting of the service authorized.</t>
<t>For the attribute of Acct-Input-IPv4-Packets, NAS report how many packets of IPv4 traffic received from the user from the starting of the service authorized.</t> 
<t>For the attribute of Acct-Output-IPv4-Packets, NAS report how many packets of IPv4 traffic sent to the user from the starting of the service authorized.</t>

<t>For the attribute of Acct-Input-IPv6-Octets, NAS report how many Octets of IPv6 traffic received from the user from the starting of the service authorized.</t>
<t>For the attribute of Acct-Output-IPv6-Octets, NAS report how many Octets of IPv6 traffic sent to the user from the starting of the service authorized.</t>
<t>For the attribute of Acct-Input-IPv6-Packets, NAS report how many packets of IPv6 traffic received from the user from the starting of the service authorized.</t> 
<t>For the attribute of Acct-Output-IPv6-Packets, NAS report how many packets of IPv6 traffic sent to the user from the starting of the service authorized.</t>
</list></t>

<t>A summary of the Traffic Statistics attributes format is shown as below. The fields are transmitted from left to right.</t>
<figure><artwork>
    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    |              Value            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         Value (cont.)                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Value (cont.)        |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>

<t>Type
<list style="empty">
<t>TBAn (by IANA)</t>
</list></t>

<t>Length
<list style="empty">
<t>=10</t>
</list></t>

<t>Value
<list style="empty">
<t>The Value field is 8 octets and uses Integer64 defined in <xref target="draft-ietf-radext-radius-extensions-02"/>, for its data type.</t>
</list></t>

</section>


<section anchor="s4.2" title="Define the Attributes in the Extended Type Space">

<t>Description
<list style="empty">
<t>The definition and usage of the traffic statistics attributes, including Acct-Input-IPv4-Octets, Acct-Output-IPv4-Octets, Acct-Input-IPv4-Packets, Acct-Output-IPv4-Packets and Acct-Input-IPv6-Octets, Acct-Output-IPv6-Octets, Acct-Input-IPv6-Packets, Acct-Output-IPv6-Packets, are the same as that described in section 4.1</t>
</list></t>

<t>A summary of the Traffic Statistics attributes format is shown as below. The fields are transmitted from left to right.</t>
<figure><artwork>
    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    | Extended-Type |     Value     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                         Value (cont.)                         |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                 Value (cont.)                 |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork></figure>

<t>Type</t>
<figure><artwork>
   Acct-Input-IPv4-Octets     241.TBA1(by IANA) or 241.42(suggested)
   Acct-Output-IPv4-Octets    241.TBA2(by IANA) or 241.43(suggested)
   Acct-Input-IPv4-Packets    241.TBA3(by IANA) or 241.47(suggested)
   Acct-Output-IPv4-Packets   241.TBA4(by IANA) or 241.48(suggested)
   Acct-Input-IPv6-Octets     241.TBA5(by IANA) or 242.42(suggested)
   Acct-Output-IPv6-Octets    241.TBA6(by IANA) or 242.43(suggested)
   Acct-Input-IPv6-Packets    241.TBA7(by IANA) or 242.47(suggested)
   Acct-Output-IPv6-Packets   241.TBA8(by IANA) or 242.48(suggested)
</artwork></figure>

<t>Length
<list style="empty">
<t>=11</t>
</list></t>

<t>Value
<list style="empty">
<t>The Value field is 8 octets and uses Integer64 defined in <xref target="draft-ietf-radext-radius-extensions-02"/>, for its data type.</t>
</list></t>

</section>

</section>




<section anchor="s5" title="Table of Attributes">

<t>The following table provides a guide to which attributes may be found in which kinds of packets, and in what quantity.</t>

<figure><artwork>
Req-  Acc-  Rej-  Chall  Accounting #      Attribute
uest  ept   ect   -enge  Request 
0     0     0     0      0-1        TBA1   Acct-Input-IPv4-Octets
0     0     0     0      0-1        TBA2   Acct-Output-IPv4-Octets
0     0     0     0      0-1        TBA3   Acct-Input-IPv4-Packets
0     0     0     0      0-1        TBA4   Acct-Output-IPv4-Packets
0     0     0     0      0-1        TBA5   Acct-Input-IPv6-Octets
0     0     0     0      0-1        TBA6   Acct-Output-IPv6-Octets
0     0     0     0      0-1        TBA7   Acct-Input-IPv6-Packets
0     0     0     0      0-1        TBA8   Acct-Output-IPv6-Packets
</artwork></figure>

<t>The meaning of the above table entries is as follows:</t>

<figure><artwork>
0    This attribute MUST NOT be present.
0+   Zero or more instances of this attribute MAY be present.
0-1  Zero or one instance of this attribute MAY be present.
1    Exactly one instance of this attribute MUST be present.
1+   One or more of these attributes MUST be present.
</artwork></figure>

</section>


<section anchor="s6" title="Security Considerations">

<t>Security issues related RADIUS are described in section 8 of RFC2865 and section 5 of RFC3162.</t>

</section>


<section anchor="s7" title="IANA Considerations">

<t>IANA is requested to assign 8 new attribute types code in the "Radius Types" registry (http://www.iana.org/assignments/radius-types for the following attributes:</t>

<figure><artwork>
   Acct-Input-IPv4-Octets
   Acct-Output-IPv4-Octets
   Acct-Input-IPv4-Packets
   Acct-Output-IPv4-Packets
   Acct-Input-IPv6-Octets
   Acct-Output-IPv6-Octets
   Acct-Input-IPv6-Packets
   Acct-Output-IPv6-Packets
</artwork></figure>

<t>IANA should allocate these codes from the standardized type space of the RADIUS attributes using the "IETF Review" policy <xref target="RFC5226"/>.</t>

</section>


<section anchor="s8" title="Acknowledgements">

<t>TBD</t>

</section>


</middle>

<!-- ***** BACK MATTER ***** -->

<back>

<references title="Normative References">

  &RFC2119;
  &RFC2865;
  &RFC2866;
  &RFC2869;
  &RFC3162;
  &RFC4818;
  
  <reference anchor='draft-ietf-radext-radius-extensions-02'>
	  <front>
	    <title>Remote Authentication Dial In User Service (RADIUS) Protocol Extensions</title> 
	    <author initials='A.' surname='DeKok' fullname='Alan DeKok' />
	    <author initials='A.' surname='Lior' fullname='Avi Lior' />
	    <date year='2011' month='Oct' />
	  </front>
  </reference>  

</references>

<references title="Informative References">

  &RFC5226;
  
  <reference anchor='BBF TR-187'>
	  <front>
	    <title>IPv6 for PPP Broadband Access, Issue 1</title> 
	    <author initials='' surname='Broadband Forum' fullname='' />
	    <date year='2010' month='May' />
	  </front>
  </reference>
  <reference anchor='ietf-radext-ipv6-access-05'>
	  <front>
	    <title>RADIUS attributes for IPv6 Access Networks</title> 
	    <author initials='B.' surname='Lourdelet' fullname='Benoit Lourdelet' />
	    <author initials='W.' surname='Dec' fullname='Wojciech Dec' />
	    <author initials='B.' surname='Sarikaya' fullname='Behcet Sarikaya' />
	    <author initials='G.' surname='Zorn' fullname='Glen Zorn' />
	    <author initials='D.' surname='Miles' fullname='David Miles' />
	    <date year='2011' month='July' />
	  </front>
  </reference>
  <reference anchor='draft-hu-v6ops-radius-issues-ipv6-00'>
	  <front>
	    <title>RADIUS issues in IPv6 deployments</title> 
   	    <author initials='J.' surname='Hu' fullname='Jie Hu' />
	    <author initials='L.' surname='Yan' fullname='Lu Yan' />
	    <author initials='Q.' surname='Wang' fullname='Qian Wang' />
	    <author initials='J.' surname='Qin' fullname='Jacni Qin' />
	    <date year='2011' month='February' />
	  </front>
  </reference>
  <reference anchor='draft-maglione-radext-ipv6-acct-extensions-01'>
	  <front>
	    <title>RADIUS Accounting Extensions for IPv6</title> 
	    <author initials='R.' surname='Maglione' fullname='Roberta Maglione' />
	    <author initials='S.' surname='Krishnan' fullname='Suresh Krishnan' />
	    <author initials='A.' surname='Kavanagh' fullname='Alan Kavanagh' />
	    <author initials='B.' surname='Varga' fullname='Balazs Varga' />
	    <author initials='J.' surname='Kaippallimalil' fullname='John Kaippallimalil' />
	    <date year='2011' month='January' />
	  </front>
  </reference>
  <reference anchor='draft-winter-radext-fancyaccounting-00'>
	  <front>
	    <title>RADIUS Accounting for traffic classes</title> 
	    <author initials='S.' surname='Winter' fullname='Stefan Winter' />
	    <date year='2011' month='March' />
	  </front>
  </reference> 
  <reference anchor='draft-yeh-radext-dual-stack-access-02'>
	  <front>
	    <title>RADIUS Attributes for Dual Stack Access</title> 
	    <author initials='L.' surname='Yeh' fullname='Leaf Yeh' />
  	    <author initials='T.' surname='Tsou' fullname='Tina Tsou' />
	    <date year='2011' month='March' />
	  </front>
  </reference>
</references>

</back>
</rfc>