| TOC |
|
This document describes additional RADIUS attributes to be used for collecting IPv6 statistics in RADIUS Accounting messages.
This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and 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 27, 2010.
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the BSD License.
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
1.
Introduction
2.
Terminology
3.
Deployment Scenarios
4.
Operation
4.1.
Sending Accounting-Request packets
5.
Attributes
5.1.
IPv6-Acct-Input-Octets
5.2.
IPv6-Acct-Output-Octets
5.3.
IPv6-Acct-Input-Packets
5.4.
IPv6-Acct-Output-Packets
5.5.
IPv6-Acct-Input-Gigawords
5.6.
IPv6-Acct-Output-Gigawords
6.
Security Considerations
7.
IANA Considerations
8.
References
8.1.
Normative References
8.2.
Informative References
§
Authors' Addresses
| TOC |
[RFC2866] (Rigney, C., “RADIUS Accounting,” June 2000.)and [RFC2869] (Rigney, C., Willats, W., and P. Calhoun, “RADIUS Extensions,” June 2000.) specify RADIUS attributes to be used for carrying statistics regarding how many packets/octets/Gigawords have been sent/received over a port while delivering the service. These attributes are IPv4 specific. With the introduction of the IPv6 in broadband environment there is a need to be able to collect IPv4 and IPv6 statistics separately, thus new RADIUS attribute have to be defined.
This document describes additional RADIUS attributes for collecting IPv6 specific statistics in RADIUS Accounting messages.
| TOC |
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] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).
| TOC |
There are deployment scenarios, like for example dual-stack environments, where the Service Provider may need to collect separate statistics for IPv4 and IPv6 traffic. This may be used in order to differentiate among multiple service offers or to monitor the growth of IPv6 traffic in the network, compared to IPv4.
The availability of different RADIUS attributes for IPv4 and IPv6 traffic would allow the collection of separate statistics for IPv4 and IPv6 traffic.
| TOC |
| TOC |
Accounting-Request packets are sent from a client (typically a Network Access Server or its proxy) to a RADIUS accounting server, and convey information used to provide accounting for a service provided to a user. The client transmits a RADIUS packet with the Code field set to 4 (Accounting-Request).
If the Accounting-Request packet includes a Framed-IPv6-Prefix, that attribute MUST contain the IPv6 prefix allocated to the user. In deployment scenarios where DHCPv6 prefix delegation is used, the Accounting-Request packet will contain a Delegated-IPv6-Prefix attribute that contains the IPv6 prefix delegated to the user.
| TOC |
This section defines six new RADIUS attributes for IPv6 statistics. These attributes correspond to the attributes Acct-Input-Octets, Acct-Output-Octets,Acct-Input-Packets, Acct-Output-Packets, Acct-Input-Gigawords and Acct-Output-Gigawords as defined in [RFC2866][RFC2869] that are defined for collecting combined statistics for IPv4 and IPv6 traffic. Since service providers may like to collect statistics for IPv6 traffic separately from IPv4 traffic, separate counters for IPv6 traffic are needed.
| TOC |
Description
This attribute indicates how many IPv6 octets have been received from the port over the course of this service being provided, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Input-Octets 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA1 for IPv6-Acct-Input-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
Description
This attribute indicates how many IPv6 octets have been sent to the port in the course of delivering this service, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Output-Octets 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA2 for IPv6-Acct-Input-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
Description
This attribute indicates how many IPv6 packets have been received from the port over the course of this service being provided to a Framed User, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Input-Packets 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA3 for IPv6-Acct-Input-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
Description
This attribute indicates how many IPv6 packets have been sent to the port in the course of delivering this service to a Framed User, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Output-Packets 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA4 for IPv6-Acct-Output-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
Description
This attribute indicates how many times the IPv6-Acct-Input-Octets counter has wrapped around 2^32 over the course of this service being provided, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Input-Gigawords 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA5 for IPv6-Acct-Input-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
Description
This attribute indicates how many times the IPv6-Acct-Output-Octets counter has wrapped around 2^32 in the course of delivering this service, and can only be present in Accounting-Request records where the Acct-Status-Type is set to Stop or Interim-Update.
A summary of the IPv6-Acct-Output-Gigawords 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Value |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type
TBA6 for IPv6-Acct-Input-Octets.
Length
6
Value
The Value field is four octets.
| TOC |
This document has no additional security considerations beyond those already identified in [RFC2865] (Rigney, C., Willens, S., Rubens, A., and W. Simpson, “Remote Authentication Dial In User Service (RADIUS),” June 2000.)
| TOC |
This document requests the allocation of six new Radius attribute types from the IANA registry "Radius Attribute Types" located at http://www.iana.org/assignments/radius-types
IPv6-Acct-Input-Octets - TBA1
IPv6-Acct-Output-Octets - TBA2
IPv6-Acct-Input-Packets - TBA3
IPv6-Acct-Output-Packets - TBA4
IPv6-Acct-Input-Gigawords - TBA5
IPv6-Acct-Output-Gigawords - TBA6
| TOC |
| TOC |
| [RFC2119] | Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). |
| [RFC2865] | Rigney, C., Willens, S., Rubens, A., and W. Simpson, “Remote Authentication Dial In User Service (RADIUS),” RFC 2865, June 2000 (TXT). |
| TOC |
| [RFC2866] | Rigney, C., “RADIUS Accounting,” RFC 2866, June 2000 (TXT). |
| [RFC2869] | Rigney, C., Willats, W., and P. Calhoun, “RADIUS Extensions,” RFC 2869, June 2000 (TXT). |
| TOC |
| Roberta Maglione | |
| Telecom Italia | |
| Via Reiss Romoli 274 | |
| Torino 10148 | |
| Italy | |
| Phone: | |
| Email: | roberta.maglione@telecomitalia.it |
| Suresh Krishnan | |
| Ericsson | |
| 8400 Blvd Decarie | |
| Town of Mount Royal, Quebec | |
| Canada | |
| Email: | suresh.krishnan@ericsson.com |
| Alan Kavanagh | |
| Ericsson | |
| 8400 Blvd Decarie | |
| Town of Mount Royal, Quebec | |
| Canada | |
| Email: | alan.kavanagh@ericsson.com |
| Balazs Varga | |
| Magyar Telekom | |
| Email: | varga.balazs@telekom.hu |