idnits 2.17.1 draft-maglione-radext-ipv6-acct-extensions-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 8, 2010) is 5162 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Downref: Normative reference to an Informational RFC: RFC 2866 Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 RADEXT R. Maglione 3 Internet-Draft Telecom Italia 4 Intended status: Standards Track S. Krishnan 5 Expires: September 9, 2010 A. Kavanagh 6 Ericsson 7 B. Varga 8 Magyar Telekom 9 J. Kaippallimalil 10 Huawei USA 11 March 8, 2010 13 RADIUS Accounting Extensions for IPv6 14 draft-maglione-radext-ipv6-acct-extensions-01 16 Abstract 18 This document describes additional RADIUS attributes to be used for 19 collecting IPv6 statistics in RADIUS Accounting messages. 21 Status of this Memo 23 This Internet-Draft is submitted to IETF in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF), its areas, and its working groups. Note that 28 other groups may also distribute working documents as Internet- 29 Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 The list of current Internet-Drafts can be accessed at 37 http://www.ietf.org/ietf/1id-abstracts.txt. 39 The list of Internet-Draft Shadow Directories can be accessed at 40 http://www.ietf.org/shadow.html. 42 This Internet-Draft will expire on September 9, 2010. 44 Copyright Notice 46 Copyright (c) 2010 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the BSD License. 59 This document may contain material from IETF Documents or IETF 60 Contributions published or made publicly available before November 61 10, 2008. The person(s) controlling the copyright in some of this 62 material may not have granted the IETF Trust the right to allow 63 modifications of such material outside the IETF Standards Process. 64 Without obtaining an adequate license from the person(s) controlling 65 the copyright in such materials, this document may not be modified 66 outside the IETF Standards Process, and derivative works of it may 67 not be created outside the IETF Standards Process, except to format 68 it for publication as an RFC or to translate it into languages other 69 than English. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 74 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 75 3. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 3 76 4. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 77 4.1. Sending Accounting-Request packets . . . . . . . . . . . . 3 78 5. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 4 79 5.1. IPv6-Acct-Input-Octets . . . . . . . . . . . . . . . . . . 4 80 5.2. IPv6-Acct-Output-Octets . . . . . . . . . . . . . . . . . . 4 81 5.3. IPv6-Acct-Input-Packets . . . . . . . . . . . . . . . . . . 5 82 5.4. IPv6-Acct-Output-Packets . . . . . . . . . . . . . . . . . 6 83 5.5. IPv6-Acct-Input-Gigawords . . . . . . . . . . . . . . . . . 6 84 5.6. IPv6-Acct-Output-Gigawords . . . . . . . . . . . . . . . . 7 85 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 86 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 87 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 88 8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 89 8.2. Informative References . . . . . . . . . . . . . . . . . . 8 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 92 1. Introduction 94 [RFC2866]and [RFC2869] specify RADIUS attributes to be used for 95 carrying statistics regarding how many packets/octets/Gigawords have 96 been sent/received over a port while delivering the service. 98 With the introduction of the IPv6 in broadband environment there is a 99 need to be able to collect IPv6 specific statistics, thus new RADIUS 100 attribute have to be defined. This document describes additional 101 RADIUS attributes for collecting IPv6 specific statistics in RADIUS 102 Accounting messages. 104 2. Terminology 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in [RFC2119]. 110 3. Deployment Scenarios 112 There are deployment scenarios, like for example dual-stack 113 environments, where the Service Provider may need to collect separate 114 statistics for IPv6 traffic. This may be used in order to 115 differentiate among multiple service offers or to monitor the growth 116 of IPv6 traffic in the network, compared to IPv4. 118 Existing RADIUS attributes like Acct-Input-Octets, Acct-Output- 119 Octets, Acct-Input-Packets, Acct-Output-Packets, Acct-Input-Gigawords 120 and Acct-Output-Gigawords, could be used to collect statistics for 121 all traffic(including IPv4, IPv6 and other protocols), while the 122 availability of IPv6 specific RADIUS attributes would allow the 123 collection of IPv6 statistics. 125 4. Operation 127 4.1. Sending Accounting-Request packets 129 Accounting-Request packets are sent from a client (typically a 130 Network Access Server or its proxy) to a RADIUS accounting server, 131 and convey information used to provide accounting for a service 132 provided to a user. The client transmits a RADIUS packet with the 133 Code field set to 4 (Accounting-Request). 135 If the Accounting-Request packet includes a Framed-IPv6-Prefix, that 136 attribute MUST contain the IPv6 prefix allocated to the user. In 137 deployment scenarios where DHCPv6 prefix delegation is used, the 138 Accounting-Request packet will contain a Delegated-IPv6-Prefix 139 attribute that contains the IPv6 prefix delegated to the user. 141 5. Attributes 143 This section defines six new RADIUS attributes for IPv6 statistics. 144 These attributes correspond to the generic protocol-independent 145 attributes Acct-Input-Octets, Acct-Output-Octets,Acct-Input-Packets, 146 Acct-Output-Packets, Acct-Input-Gigawords and Acct-Output-Gigawords 147 as defined in [RFC2866][RFC2869]. 149 5.1. IPv6-Acct-Input-Octets 151 Description 153 This attribute indicates how many IPv6 octets have been received from 154 the port over the course of this service being provided, and can only 155 be present in Accounting-Request records where the Acct-Status-Type 156 is set to Stop or Interim-Update. 158 A summary of the IPv6-Acct-Input-Octets attribute format is shown 159 below. The fields are transmitted from left to right. 161 0 1 2 3 162 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 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | Type | Length | Value | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 | Value (cont) | 167 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 169 Type 171 TBA1 for IPv6-Acct-Input-Octets. 172 Length 173 6 175 Value 176 The Value field is four octets. 178 5.2. IPv6-Acct-Output-Octets 180 Description 182 This attribute indicates how many IPv6 octets have been sent to the 183 port in the course of delivering this service, and can only be 184 present in Accounting-Request records where the Acct-Status-Type is 185 set to Stop or Interim-Update. 187 A summary of the IPv6-Acct-Output-Octets attribute format is shown 188 below. The fields are transmitted from left to right. 190 0 1 2 3 191 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 192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 | Type | Length | Value | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Value (cont) | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 Type 200 TBA2 for IPv6-Acct-Output-Octets. 201 Length 202 6 204 Value 205 The Value field is four octets. 207 5.3. IPv6-Acct-Input-Packets 209 Description 211 This attribute indicates how many IPv6 packets have been received 212 from the port over the course of this service being provided to a 213 Framed User, and can only be present in Accounting-Request records 214 where the Acct-Status-Type is set to Stop or Interim-Update. 216 A summary of the IPv6-Acct-Input-Packets attribute format is shown 217 below. The fields are transmitted from left to right. 219 0 1 2 3 220 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 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | Type | Length | Value | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | Value (cont) | 225 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 Type 229 TBA3 for IPv6-Acct-Input-Packets. 230 Length 231 6 233 Value 234 The Value field is four octets. 236 5.4. IPv6-Acct-Output-Packets 238 Description 240 This attribute indicates how many IPv6 packets have been sent to the 241 port in the course of delivering this service to a Framed User, and 242 can only be present in Accounting-Request records where the Acct- 243 Status-Type is set to Stop or Interim-Update. 245 A summary of the IPv6-Acct-Output-Packets attribute format is shown 246 below. The fields are transmitted from left to right. 248 0 1 2 3 249 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 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Type | Length | Value | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | Value (cont) | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 256 Type 258 TBA4 for IPv6-Acct-Output-Packets. 259 Length 260 6 262 Value 263 The Value field is four octets. 265 5.5. IPv6-Acct-Input-Gigawords 267 Description 269 This attribute indicates how many times the IPv6-Acct-Input-Octets 270 counter has wrapped around 2^32 over the course of this service being 271 provided, and can only be present in Accounting-Request records where 272 the Acct-Status-Type is set to Stop or Interim-Update. 274 A summary of the IPv6-Acct-Input-Gigawords attribute format is shown 275 below. The fields are transmitted from left to right. 277 0 1 2 3 278 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 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | Type | Length | Value | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | Value (cont) | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 Type 287 TBA5 for IPv6-Acct-Input-Gigawords. 288 Length 289 6 291 Value 292 The Value field is four octets. 294 5.6. IPv6-Acct-Output-Gigawords 296 Description 298 This attribute indicates how many times the IPv6-Acct-Output-Octets 299 counter has wrapped around 2^32 in the course of delivering this 300 service, and can only be present in Accounting-Request records where 301 the Acct-Status-Type is set to Stop or Interim-Update. 303 A summary of the IPv6-Acct-Output-Gigawords attribute format is shown 304 below. The fields are transmitted from left to right. 306 0 1 2 3 307 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 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 | Type | Length | Value | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | Value (cont) | 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 Type 316 TBA6 for IPv6-Acct-Output-Gigawords. 317 Length 318 6 320 Value 321 The Value field is four octets. 323 6. Security Considerations 325 This document has no additional security considerations beyond those 326 already identified in [RFC2865] 328 7. IANA Considerations 330 This document requests the allocation of six new Radius attribute 331 types from the IANA registry "Radius Attribute Types" located at 332 http://www.iana.org/assignments/radius-types 334 IPv6-Acct-Input-Octets - TBA1 335 IPv6-Acct-Output-Octets - TBA2 336 IPv6-Acct-Input-Packets - TBA3 337 IPv6-Acct-Output-Packets - TBA4 338 IPv6-Acct-Input-Gigawords - TBA5 339 IPv6-Acct-Output-Gigawords - TBA6 341 8. References 343 8.1. Normative References 345 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 346 Requirement Levels", BCP 14, RFC 2119, March 1997. 348 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 349 "Remote Authentication Dial In User Service (RADIUS)", 350 RFC 2865, June 2000. 352 [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 354 8.2. Informative References 356 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 357 Extensions", RFC 2869, June 2000. 359 Authors' Addresses 361 Roberta Maglione 362 Telecom Italia 363 Via Reiss Romoli 274 364 Torino 10148 365 Italy 367 Phone: 368 Email: roberta.maglione@telecomitalia.it 370 Suresh Krishnan 371 Ericsson 372 8400 Blvd Decarie 373 Town of Mount Royal, Quebec 374 Canada 376 Email: suresh.krishnan@ericsson.com 378 Alan Kavanagh 379 Ericsson 380 8400 Blvd Decarie 381 Town of Mount Royal, Quebec 382 Canada 384 Email: alan.kavanagh@ericsson.com 386 Balazs Varga 387 Magyar Telekom 389 Email: varga.balazs@telekom.hu 391 John Kaippallimalil 392 Huawei USA 393 1700 Alma Dr. Suite 500 394 Plano, TX 75075 396 Phone: +1 214-606-2005 397 Fax: 398 Email: jkaippal@huawei.com 399 URI: