idnits 2.17.1 draft-yeh-radext-ext-traffic-statistics-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 == Line 439 has weird spacing: '... uest ept ...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 15, 2012) is 4204 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) == Outdated reference: A later version (-13) exists of draft-ietf-radext-radius-extensions-06 ** Downref: Normative reference to an Informational RFC: RFC 2866 ** Downref: Normative reference to an Informational RFC: RFC 2869 ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) -- No information found for draft-hu-v6ops-radius-issues-ipv6-00 - is the name correct? == Outdated reference: A later version (-16) exists of draft-ietf-radext-ipv6-access-11 -- No information found for draft-maglione-radext-ipv6-acct-extensions-01 - is the name correct? -- No information found for draft-yeh-radext-dual-stack-access-02 - is the name correct? Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Radext Working Group L. Yeh 3 Internet-Draft Huawei Technologies 4 Intended status: Standards Track M. Boucadair 5 Expires: April 18, 2013 France Telecom 6 October 15, 2012 8 RADIUS Accounting Extensions for Traffic Statistics 9 draft-yeh-radext-ext-traffic-statistics-04 11 Abstract 13 This document specifies the RADIUS extensions of attributes for the 14 traffic statistics with different type, which can be used to support 15 the differentiated accounting policies and traffic recording on the 16 AAA server. 18 Status of this Memo 20 This Internet-Draft is submitted in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF). Note that other groups may also distribute 25 working documents as Internet-Drafts. The list of current Internet- 26 Drafts is at http://datatracker.ietf.org/drafts/current/. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 This Internet-Draft will expire on April 18, 2013. 35 Copyright Notice 37 Copyright (c) 2012 IETF Trust and the persons identified as the 38 document authors. All rights reserved. 40 This document is subject to BCP 78 and the IETF Trust's Legal 41 Provisions Relating to IETF Documents 42 (http://trustee.ietf.org/license-info) in effect on the date of 43 publication of this document. Please review these documents 44 carefully, as they describe your rights and restrictions with respect 45 to this document. Code Components extracted from this document must 46 include Simplified BSD License text as described in Section 4.e of 47 the Trust Legal Provisions and are provided without warranty as 48 described in the Simplified BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. Terminology and Conventions . . . . . . . . . . . . . . . . . 4 54 3. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 4 55 4. Acct-Traffic-Statistics attribute . . . . . . . . . . . . . . 4 56 4.1. Container attribute of Acct-Traffic-Statistics . . . . . . 5 57 4.2. Contained attribute of Acct-Traffic-Statistics . . . . . . 6 58 4.2.1. Acct-Traffic-Statistics.Stack-Type . . . . . . . . . . 6 59 4.2.2. Acct-Traffic-Statistics.Input-Octets . . . . . . . . . 7 60 4.2.3. Acct-Traffic-Statistics.Output-Octets . . . . . . . . 7 61 4.2.4. Acct-Traffic-Statistics.Input-Packets . . . . . . . . 8 62 4.2.5. Acct-Traffic-Statistics.Output-Packets . . . . . . . . 9 63 4.2.6. Acct-Traffic-Statistics.DSCP-Type . . . . . . . . . . 10 64 5. Table of Attribute . . . . . . . . . . . . . . . . . . . . . . 10 65 6. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11 66 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 67 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 68 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 69 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 70 10.1. Normative References . . . . . . . . . . . . . . . . . . . 12 71 10.2. Informative References . . . . . . . . . . . . . . . . . . 12 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 74 1. Introduction 76 RADIUS has been widely used as the centralized authentication, 77 authorization and subscriber management method for the service 78 provision in Broadband access network. [RFC3162], [RFC4818] and 79 [I-D.ietf-radext-ipv6-access] have specified some attributes to 80 support the service provision for IPv6 access. In the meantime, 81 RADIUS is also a protocol for carrying accounting information between 82 a Network Access Server (NAS) and a shared accounting server. In the 83 scenarios of dual-stack or any other IPv6 migration technologies, 84 there is a demand to report the separated IPv4 & IPv6 traffic 85 statistics for the differential accounting and traffic recording. 87 [BBF TR-187], whose purpose is to describe the network architecture 88 and elements requirements in the PPPoE scenario to support IPv6-only 89 or dual-stack for Internet access service, has explicitly expressed 90 in its Section 9.4, that the BNG must be able to support separate 91 queues, input and output counters for IPv4 or IPv6 traffic. Note 92 that BNG of BBF is a kind of broadband NAS of IETF. Meanwhile [BBF 93 TR-187] suggested to use the RADIUS attributes (eg. Acct-Input- 94 Octets (42), Acct-Output-Octets (43), Acct-Input-Packets (47), Acct- 95 Output-Packets (48)) for the combination of IPv6 and IPv4 traffic. 96 That means the new RADIUS attributes for reporting the separated IPv4 97 or IPv6 traffic statistics are required to be defined. 99 [I-D.hu-v6ops-radius-issues-ipv6-00] presented the same issue on 100 'protocol specific accounting' for the dual-stack traffic statistics, 101 but it also limits to the PPP case. 102 [I-D.maglione-radext-ipv6-acct-extensions-01] and 103 [I-D.yeh-radext-dual-stack-access-02] tried to defined a batch of 104 attributes on the traffic statistics respectively for the IPv6-only 105 access and dual-stack access in the traditional type space with the 106 flat mode , while [I-D.winter-radext-fancyaccounting] indicated that 107 the accounting attributes of Input-Octets, Output-Octets, Input- 108 Packets and Output-Packets can be grouped in the new basic data type 109 of TLV-nesting defined in Section 2.3 of 110 [I-D.ietf-radext-radius-extensions] for the extended type space. 111 According to [RFC6158] and Section 6.3 of 112 [I-D.ietf-radext-radius-extensions], Nesting-TLV is the only 113 recommendation for the new attribute design which intends to employ 114 multiple fields in the complex data type now. Based on the judge of 115 the quickly-exhausted traditional type space, the Radext Working 116 Group tends to adopt the new data type of nesting-TLV defined for the 117 extended type space to report the traffic statistics for the 118 accounting extension. 120 This document specifies new attributes of the traffic statistics with 121 different types for the extension of RADIUS accounting to support the 122 differentiated accounting policies and traffic recording on the AAA 123 server. The reporting traffic types include the combination of stack 124 types and the optional DSCP types. 126 Note: This document tries to narrow the scope of the solution space 127 just to meet the requirements explicitly expressed by the industry 128 without defining new RADIUS messages or introducing a new namespace 129 for the additional interoperability. 131 2. Terminology and Conventions 133 Definitions for terms and acronyms not specifically defined in this 134 document are defined in [RFC2865], [RFC2866], [RFC2869], [RFC3575], 135 [RFC6158], and [I-D.ietf-radext-radius-extensions]. 137 The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, 138 SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, when they appear in this 139 document, are to be interpreted as described in BCP 14, [RFC2119]. 141 3. Deployment Scenarios 143 Figure 1 shows the typical use case of the traffic statistics 144 reporting for the dual-stack users. 146 +----------+ +----------+ +----------+ 147 | Host / | PPPoE | | RADIUS | AAA | 148 | Customer | ------------ | NAS | ------------ | Server | 149 | Router | IPoE | | Accounting | | 150 +----------+ +----------+ +----------+ 151 Dual-Stack Separated queues and counter 152 for IPv4 and IPv6 traffic 154 Figure 1: Traffic Statistics of Dual-Stack Users for RADIUS 155 Accounting 157 Note that traffic statistics reporting is also needed in the IPv6 158 transition cases, such as DS-Lite, 6rd or MAP, where AFTR (Address 159 Family Transition Router) or BR (Border Router) may act as the 160 broadband NAS. 162 4. Acct-Traffic-Statistics attribute 164 Acct-traffic-statistics attribute is designed according to the 165 guidelines described in [RFC6158] and Section 6 of 166 [I-D.ietf-radext-radius-extensions]. It adopts the data structure of 167 the TLV nesting, has 1 container attribute, Acct-Traffic-Statistics, 168 and 6 contained sub-attributes, Stack-Type, Input-Octets, Output- 169 Octets, Input-Packets, Output-Packets, DSCP-Type (Differentiated 170 Services CodePoint), and possible support the extensible types of 171 traffic statistics in the future. The sub-attribute of Stack-Type 172 MUST be included, one or more sub-attribute of Input-Octets, Output- 173 Octets, Input-Packets or Output-Packets sub-attributes MUST be 174 included and sub-attribute of DSCP-Type MAY be included in the 175 container attribute, Acct-Traffic-Statistics. Because each of the 176 sub-attributes has its own type code, the appearance of the contained 177 sub-attributes is not necessary in a fixed order. 179 4.1. Container attribute of Acct-Traffic-Statistics 181 Description 183 The container attribute of Acct-Traffic-Statistics, which includes 184 sub-attributes of Stack-Type, or DSCP-Type, and Input-Octets, 185 Output-Octets, Input-Packets or Output-Packets, reports how many 186 octets or packets of the specified traffic type, from the user or 187 sent to the user, from the starting of the associated service 188 provided. The sub-attributes of Stack-Type or DSCP-Type indicates 189 the specified traffic type. One or more Acct-traffic-statistics 190 attribute can be presented in Accounting-Request(4) message while 191 the Acct-Status-Type(40) is set to Interim-Update or Stop. 193 The format of Acct-Traffic-Statistics attribute format is shown as 194 below. The fields are transmitted from left to right. 196 0 1 2 3 197 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 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | Type | Length | Extended-Type | Value | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | Value (cont.)... 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 Type 206 241, which indicates the extended type space. 208 Length 210 The length of the whole attribute in octet. 212 Extended-Type 213 TBA for Acct-Traffic-Statistics (See Section 8) 215 Value 217 The Value of the container attribute are the sub-attributes 218 defined in Section 4.2 in TLV nesting mode. At least the sub- 219 attribute of Stack-Type, and one of Input-Octets, Output-Octets, 220 Input-Packets or Output-Packets sub-attributes MUST be included. 222 4.2. Contained attribute of Acct-Traffic-Statistics 224 4.2.1. Acct-Traffic-Statistics.Stack-Type 226 Description 228 Acct-Traffic-Statistics.Stack-Type sub-attribute indicates the 229 type of the separated and combined traffic for IPv4 and IPv6. 231 The format of Acct-Traffic-Statistics.Stack-Type sub-attribute is 232 shown as below. The fields are transmitted from left to right. 234 0 1 2 3 235 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 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Type | Length | Value | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | Value (cont.) | 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 Type 244 TBA.1 for Acct-Traffic-Statistics.Stack-Type (See Section 8) 246 Length 248 6 250 Value 252 Enumerated Data Type in 4-Octet unsigned integer defined in 253 [RFC6158]. The beginning 3 Octets are reserved for future use, 254 and are set to 0x00 now. The decimal value of the last octet is 255 defined as follows: 257 0 Combined traffic of IPv4 and IPv6 258 1 IPv4-only traffic 260 2 IPv6-only traffic 262 4.2.2. Acct-Traffic-Statistics.Input-Octets 264 Description 266 Acct-Traffic-Statistics.Input-Octets sub-attribute indicates how 267 many octets in IP layer received from the user (or subscriber 268 device) from the starting of the service authorized. 270 The format of Acct-Traffic-Statistics.Input-Octets sub-attribute 271 is shown as below. The fields are transmitted from left to right. 273 0 1 2 3 274 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 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 | Type | Length | Value | 277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 | Value (cont.) | 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | Value (cont.) | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 Type 285 TBA.2 for Acct-Traffic-Statistics.Input-Octets (See Section 8) 287 Length 289 10 291 Value 293 Integer64 data type in 8-Octet unsigned integer defined in 294 [I-D.ietf-radext-radius-extensions]. 296 4.2.3. Acct-Traffic-Statistics.Output-Octets 298 Description 300 Acct-Traffic-Statistics.Output-Octets sub-attribute indicates how 301 many octets in IP layer forwarded to the user (or subscriber 302 device) from the starting of the service authorized. 304 The format of Acct-Traffic-Statistics.Output-Octets sub-attribute 305 is shown as below. The fields are transmitted from left to right. 307 0 1 2 3 308 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 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | Type | Length | Value | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | Value (cont.) | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | Value (cont.) | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 Type 319 TBA.3 for Acct-Traffic-Statistics.Output-Octets (See Section 8) 321 Length 323 10 325 Value 327 Integer64 data type in 8-Octet unsigned integer defined in 328 [I-D.ietf-radext-radius-extensions]. 330 4.2.4. Acct-Traffic-Statistics.Input-Packets 332 Description 334 Acct-Traffic-Statistics.Input-Packets sub-attribute indicates how 335 many packets in IP layer received from the user (or subscriber 336 device) from the starting of the service authorized. 338 The format of Acct-Traffic-Statistics.Input-Packets sub-attribute 339 is shown as below. The fields are transmitted from left to right. 341 0 1 2 3 342 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 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 | Type | Length | Value | 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | Value (cont.) | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | Value (cont.) | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 Type 353 TBA.4 for Acct-Traffic-Statistics.Input-Packets (See Section 8) 355 Length 357 10 359 Value 361 Integer64 data type in 8-Octet unsigned integer defined in 362 [I-D.ietf-radext-radius-extensions]. 364 4.2.5. Acct-Traffic-Statistics.Output-Packets 366 Description 368 Acct-Traffic-Statistics.Input-Packets sub-attribute indicates how 369 many packets in IP layer forwarded to the user (or subscriber 370 device) from the starting of the service authorized. 372 The format of Acct-Traffic-Statistics.Output-Packets sub-attribute 373 is shown as below. The fields are transmitted from left to right. 375 0 1 2 3 376 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 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | Type | Length | Value | 379 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 380 | Value (cont.) | 381 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 382 | Value (cont.) | 383 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 385 Type 387 TBA.5 for Acct-Traffic-Statistics.Output-Packets (See Section 8) 389 Length 391 10 393 Value 395 Integer64 data type in 8-Octet unsigned integer defined in 396 [I-D.ietf-radext-radius-extensions]. 398 4.2.6. Acct-Traffic-Statistics.DSCP-Type 400 Description 402 Acct-Traffic-Statistics.DSCP-Type sub-attribute indicates the DSCP 403 type of the separated or combined IPv4 and IPv6 traffic. 405 The format of Acct-Traffic-Statistics.DSCP-Type sub-attribute is 406 shown as below. The fields are transmitted from left to right. 408 0 1 2 3 409 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 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 | Type | Length | Value | 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 | Value (cont.) | 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 416 Type 418 TBA.6 for Acct-Traffic-Statistics.DSCP-Type (See Section 8) 420 Length 422 6 424 Value 426 Enumerated Data Type in 4-Octet unsigned integer defined in 427 [RFC6158]. The beginning 3 Octets are reserved for future use, 428 and are set to 0x00 now. The first 2 bits of the last octet are 429 reserved for future use, and are set to 00 now. The last 6 bits 430 of the last octet is used to contain the DSCP value as per 431 [RFC2474]. 433 5. Table of Attribute 435 The following table provides a guide to which attributes may be found 436 in which kinds of packets, and in what quantity. 438 Req- Acc- Rej- Chall Accounting # Attribute 439 uest ept ect -enge Request 440 0 0 0 0 0+ TBA Acct-Traffic-Statistics 442 The meaning of the above table entries is as follows: 444 0 This attribute MUST NOT be present. 445 0+ Zero or more instances of this attribute MAY be present. 446 0-1 Zero or one instance of this attribute MAY be present. 447 1 Exactly one instance of this attribute MUST be present. 448 1+ One or more of these attributes MUST be present. 450 6. Diameter Considerations 452 Given that the Attributes defined in this document are allocated from 453 the RADIUS extended type space (see Section 8), no special handling 454 is required by Diameter entities. 456 7. Security Considerations 458 Security issues related RADIUS are described in Section 8 of 459 [RFC2865] and Section 5 of [RFC3162]. 461 8. IANA Considerations 463 The authors of this document request to assign new Radius type codes 464 for Acct-Traffic-Statistics and its following sub-attributes. 466 Acct-Traffic-Statistics.Stack-Type 467 Acct-Traffic-Statistics.Input-Octets 468 Acct-Traffic-Statistics.Output-Octets 469 Acct-Traffic-Statistics.Input-Packets 470 Acct-Traffic-Statistics.Output-Packets 471 Acct-Traffic-Statistics.DSCP-Type 473 These type codes should be allocated from the RADIUS extended type 474 space based on Section 10 of [I-D.ietf-radext-radius-extensions] and 475 "IETF Review" policy [RFC5226]. 477 9. Acknowledgements 479 Thanks to Roberta Maglione, Jie Hu for their efforts in the history 480 to bring this problem to IETF, to Stefan Winter, Alan DeKok, Peter 481 Deacon for their valuable comments in the mailing list of Radext. 483 10. References 484 10.1. Normative References 486 [I-D.ietf-radext-radius-extensions] 487 DeKok, A. and A. Lior, "Remote Authentication Dial In User 488 Service (RADIUS) Protocol Extensions", 489 draft-ietf-radext-radius-extensions-06 (work in progress), 490 June 2012. 492 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 493 Requirement Levels", BCP 14, RFC 2119, March 1997. 495 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 496 "Definition of the Differentiated Services Field (DS 497 Field) in the IPv4 and IPv6 Headers", RFC 2474, 498 December 1998. 500 [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, 501 "Remote Authentication Dial In User Service (RADIUS)", 502 RFC 2865, June 2000. 504 [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, June 2000. 506 [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS 507 Extensions", RFC 2869, June 2000. 509 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", 510 RFC 3162, August 2001. 512 [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote 513 Authentication Dial In User Service)", RFC 3575, 514 July 2003. 516 [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix 517 Attribute", RFC 4818, April 2007. 519 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 520 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 521 May 2008. 523 [RFC6158] DeKok, A. and G. Weber, "RADIUS Design Guidelines", 524 BCP 158, RFC 6158, March 2011. 526 10.2. Informative References 528 [BBF TR-187] 529 Broadband Forum, "IPv6 for PPP Broadband Access, Issue 1", 530 May 2010. 532 [I-D.hu-v6ops-radius-issues-ipv6-00] 533 Hu, J., Yan, L., Wang, Q., and J. Qin, "RADIUS issues in 534 IPv6 deployments", February 2011. 536 [I-D.ietf-radext-ipv6-access] 537 Dec, W., Sarikaya, B., Zorn, G., Miles, D., and B. 538 Lourdelet, "RADIUS attributes for IPv6 Access Networks", 539 draft-ietf-radext-ipv6-access-11 (work in progress), 540 August 2012. 542 [I-D.maglione-radext-ipv6-acct-extensions-01] 543 Maglione, R., Krishnan, S., Kavanagh, A., Varga, B., and 544 J. Kaippallimalil, "RADIUS Accounting Extensions for 545 IPv6", January 2011. 547 [I-D.winter-radext-fancyaccounting] 548 Winter, S., "RADIUS Accounting for traffic classes", 549 draft-winter-radext-fancyaccounting-02 (work in progress), 550 July 2012. 552 [I-D.yeh-radext-dual-stack-access-02] 553 Yeh, L. and T. Tsou, "RADIUS Attributes for Dual Stack 554 Access", March 2011. 556 Authors' Addresses 558 Leaf Y. Yeh 559 Huawei Technologies 560 Shenzhen 561 P. R. China 563 Email: leaf.y.yeh@huawei.com 565 Mohamed Boucadair 566 France Telecom 567 Rennes, 568 France 570 Email: mohamed.boucadair@orange.com