One document matched: draft-winter-radext-fancyaccounting-00.xml

<?xml version = '1.0'?>
<?rfc rfcedstyle='yes'?>
<?rfc rfcprocack='yes'?>
<?rfc toc='yes'?>
<?rfc symrefs='yes'?>
<!DOCTYPE rfc SYSTEM "../xml2rfc-1.35pre1/rfc2629.dtd" [

      <!ENTITY rfc2866     PUBLIC '' '../rfc-bib/reference.RFC.2866.xml'>
      <!ENTITY rfc2119     PUBLIC '' '../rfc-bib/reference.RFC.2119.xml'>

    ]>
<rfc ipr='trust200902' docName='draft-winter-radext-fancyaccounting-00' category='std'>
  <front>
    <title abbrev="RADIUS Fancy Accounting" >RADIUS Accounting for traffic classes</title>
    <author fullname="Stefan Winter" initials="S." surname="Winter" >
	<organization abbrev="RESTENA" >Fondation RESTENA</organization>
	<address>
		<postal>
			<street>6, rue Richard Coudenhove-Kalergi</street>
			<city>Luxembourg</city>
			<code>1359</code>
			<country>LUXEMBOURG</country>
		</postal>
		<phone>+352 424409 1</phone>
		<facsimile>+352 422473</facsimile>
		<email>stefan.winter@restena.lu</email>
		<uri>http://www.restena.lu.</uri>
	</address>
    </author>
    <date day="31" month="March" year="2011" />
    <area>Operations and Management Area</area>
    <workgroup>RADIUS Extensions Working Group</workgroup>
    <keyword>RADIUS</keyword>
    <keyword>AAA</keyword>
    <keyword>Accounting</keyword>
    <abstract>
	    <t>This document specifies new attributes for RADIUS Accounting to enable NAS reporting of subsets of the total traffic in a user session.</t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction" anchor="intro">
<t>RADIUS Accounting <xref target="RFC2866" /> defines counters for octets and packets, both in the incoming and outgoing direction.  Usage of these counters enables an operator create volume-based billing models and to execute proper capacity planning on its infrastructure.</t>
<t> The Accounting model is based on the assumption that all traffic in a user session is treated equally; i.e. that there are no differences in the billing model of one class of traffic over another.</t>
<t> Actual deployments suggest that this assumption is no longer valid. In particular, different traffic classes are defined with DSCP; and billing the use of these traffic classes separately is an understandable request.</t>
<t> Plus, the introduction of dual-stack operation on links creates an understandable interest of getting separate statistics about the amount of IPv4 vs. IPv6 usage on a link; be it for billing or statistical reasons.</t>  
<t>This document defines Accounting attributes that supplement (but not replace) the accounting counters in RFC2866. It utilizes the new "extended attributes" in RADIUS to group accounting reports about traffic classes together.</t>

	<section title="Requirements Language" anchor="reqlang">
		<t>In this document, several words are used to signify the
requirements of the specification.  The key words "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
<xref target="RFC2119" /></t>
	</section>
    </section>
    <section title="Definitions" anchor="def">
	<section title="Unsigned 64-Bit Integer datatype" anchor="bit64">
	<t>RADIUS Accounting in RFC2866 uses two distinct attributes, Acct-(Input Output)-Octets and Acct-(Input Output) Gigawords, to transport 64 bit counter values. The reasons for defining a 64 Bit value across two attributes are historic. This specification defines a new datatype, "Unsigned 64 Bit Integer" to convey 64 bit counter values natively.</t>
        <t>Type: UINT64 - Length: 8 octets - Value: 64 bit unsigned integer, most significant byte first</t>
	</section>
	<section title="Acct-Traffic-Class attribute">
	<t>The attribute Acct-Traffic-Group is a container for a group of sub-attributes which specify the class of traffic that is being reported about, and the amount of traffic in a user session that falls into this class.</t>
	<t>Attribute: 245.1 Acct-Traffic-Class - Type: TLV - Length: >3 octets</t>
	<t>There can be multiple instances of this grouped attribute in a Accounting-Interim-Update or a Accounting-Stop packet. The attribute MUST NOT be present in an Accounting-Start packet.</t>
	<t> It is not required that the sum of all traffic in all instances is the total sum of octets and packets in the user's session. I.e.  the traffic classes used in the Accounting packet do not need to partition the total traffic in non-overlapping segments.</t>
	<t>The total number of octets and packets in a user session continues to be sent in the RFC2866 attributes.</t>
		<section title="Acct-Traffic-Class-Id attribute">
			<t>The attribute Acct-Traffic-Class-Id, sub-attribute in the group Acct-Traffic-Class, defines the class of traffic for which the other attributes in the instance of Acct-Traffic-Class count octets and packets.</t> 
			<t> Every group instance MUST contain exactly one of Acct-Traffic-Class-Id or Acct-Traffic-Class-Name (see below). I.e. if Acct-Traffic-Class-Id is present in the Acct-Traffic-Class instance, then the attribute Acct-Traffic-Class-Name MUST NOT be present.</t>
			<t> Attribute: 245.1.1 Acct-Traffic-Class-Id - Type: Enum - Values:
				<list style="numbers">
				  <t>IPv4</t>
				  <t>IPv6</t>
				  <t>DSCP 0</t>
				  <t>DSCP 1</t>
				  <t>...</t>
				</list>
			</t>
			<t>Allocations of new values for this attribute are subject to expert review.</t>
		</section>
		<section title="Acct-Traffic-Class-Name attribute">
			<t> The attribute Acct-Traffic-Class-Name, sub-attribute in the group Acct-Traffic-Class, defines the class of traffic for which the other attributes in the instance of Acct-Traffic-Class count octets and packets.</t>
			<t> Every group instance MUST contain exactly one of Acct-Traffic-Class-Id (see above) or Acct-Traffic-Class-Name. I.e. if Acct-Traffic-Class-Name is present in the Acct-Traffic-Class instance, then the attribute Acct-Traffic-Class-Id MUST NOT be present.</t>
			<t> Attribute: 245.1.2 Acct-Traffic-Class-Name - Type: STRING - Value: 1-250 octets</t>
		</section>
		<section title="Acct-Traffic-Class-Input-Octets attribute">
			<t> The attribute Acct-Traffic-Class-Input-Octets, sub-attribute in the group Acct-Traffic-Class, carries the number of octets that belong to the class of traffic indicated by Acct-Traffic-Class-Id or Acct-Traffic-Class-Name and have been sent to the entity for which the accounting packet was generated.</t>
			<t> Attribute: 245.1.3 Acct-Traffic-Class-Input-Octets - Type: UINT64 - Value: number of octets sent to entity, matching the class of traffic</t>
		</section>
                <section title="Acct-Traffic-Class-Output-Octets attribute">
                        <t> The attribute Acct-Traffic-Class-Output-Octets, sub-attribute in the group Acct-Traffic-Class, carries the number of octets that belong to the class of traffic indicated by Acct-Traffic-Class-Id or Acct-Traffic-Class-Name and have been sent from the entity for which the accounting packet was generated.</t>
                        <t> Attribute: 245.1.4 Acct-Traffic-Class-Output-Octets - Type: UINT64 - Value: number of octets sent from entity, matching the class of traffic</t>
                </section>
                <section title="Acct-Traffic-Class-Input-Packets attribute">
                        <t> The attribute Acct-Traffic-Class-Input-Packets, sub-attribute in the group Acct-Traffic-Class, carries the number of packets that belong to the class of traffic indicated by Acct-Traffic-Class-Id or Acct-Traffic-Class-Name and have been sent to the entity for which the accounting packet was generated.</t>
                        <t> Attribute: 245.1.5 Acct-Traffic-Class-Input-Packets - Type: UINT64 - Value: number of packets sent to entity, matching the class of traffic</t>
                </section>
                <section title="Acct-Traffic-Class-Output-Packets attribute">
                        <t> The attribute Acct-Traffic-Class-Output-Packets, sub-attribute in the group Acct-Traffic-Class, carries the number of packets that belong to the class of traffic indicated by Acct-Traffic-Class-Id or Acct-Traffic-Class-Name and have been sent from the entity for which the accounting packet was generated.</t>
 			<t> Attribute: 245.1.6 Acct-Traffic-Class-Output-Packets - Type: UINT64 - Value: number of packets sent from entity, matching the class of traffic</t>
                </section>
	</section>
	</section>
	<section title="Example">
		<t>A NAS is configured to create statistics regarding IPv6 usage of CPE for statistical reasons, and of the amount of HTTP traffic sent to the example.com web site for billing reasons.</t> 
		<t> User john@example.com starts a user session, transfers 1200 Bytes in 10 packets via IPv6 to the internet, and receives 4500 Bytes in 30 packets over IPv6 from the internet.</t>
		<t>  In the same session, The user visits the IPv4-only example.com web site by sending 6000 bytes in 4 packets to the web site, and receiving 450000 Bytes in 35 packets from the web site.</t>
		<t> Then, the user terminates the session and an Accounting-Stop packet is generated.</t>
		<t> The NAS sends the recorded octet and packet values to his RADIUS Accounting server.  Since there is no ENUM value for "Traffic on TCP/80 to example.com, all IP versions" in Acct-Traffic-Group-Id, the NAS indicates this class of traffic in a corresponding string. The relevant attributes in the Account-Stop packet are:</t>
<t>Accounting-Traffic-Group
<list>
<t>    Accounting-Group-Id = IPv6</t>
<t>    Acct-Input-Octets = 4500</t>
<t>    Acct-Output-Octets = 1200</t>
<t>    Acct-Input-Packets = 30</t>
<t>    Acct-Output-Octets = 10</t>
</list>
</t>
<t>Accounting-Traffic-Group
<list>
<t>    Accounting-Group-Name = "Traffic on TCP/80 to example.com, all IP versions"</t>
<t>    Acct-Input-Octets = 450000</t>
<t>    Acct-Output-Octets = 6000</t>
<t>    Acct-Input-Packets = 35</t>
<t>    Acct-Output-Octets = 4</t>
</list>
</t>
	</section>
    <section title="Privacy Considerations" anchor="privacy">
	    <t> Reveals user's traffic usage patterns. Shouldn't be sent unencrpyptedly.</t>
    </section>
    <section title="IANA Considerations" anchor="iana">
	    <t>This document has actions for IANA. TBD later.</t>
    </section>
  </middle>
  <back>
	  <references title="Normative References">
		  &rfc2866;
                  &rfc2119;

          </references>	
  </back>
</rfc>