idnits 2.17.1 draft-ietf-radext-ipv6-access-13.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 : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 19, 2012) is 4179 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) -- Obsolete informational reference (is this intentional?): RFC 3315 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 3633 (Obsoleted by RFC 8415) -- Obsolete informational reference (is this intentional?): RFC 6106 (Obsoleted by RFC 8106) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W.D. Dec, Ed. 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track B.S. Sarikaya 5 Expires: April 20, 2013 Huawei USA 6 G.Z. Zorn 7 Network Zen 8 D.M. Miles 9 Google 10 B.L. Lourdelet 11 October 19, 2012 13 RADIUS attributes for IPv6 Access Networks 14 draft-ietf-radext-ipv6-access-13 16 Abstract 18 This document specifies additional IPv6 RADIUS attributes useful in 19 residential broadband network deployments. The attributes, which are 20 used for authorization and accounting, enable assignment of a host 21 IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an 22 IPv6 route announced via router advertisement; assignment of a named 23 IPv6 delegated prefix pool; and assignment of a named IPv6 pool for 24 host DHCPv6 addressing. 26 Requirements Language 28 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 29 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 30 document are to be interpreted as described in RFC 2119 [RFC2119]. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at http://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on April 20, 2013. 49 Copyright Notice 51 Copyright (c) 2012 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 67 2. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 3 68 2.1. IPv6 Address Assignment . . . . . . . . . . . . . . . . . 3 69 2.2. DNS Servers . . . . . . . . . . . . . . . . . . . . . . . 4 70 2.3. IPv6 Route Information . . . . . . . . . . . . . . . . . . 4 71 2.4. Delegated IPv6 Prefix Pool . . . . . . . . . . . . . . . . 5 72 2.5. Stateful IPv6 address pool . . . . . . . . . . . . . . . . 5 73 3. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 3.1. Framed-IPv6-Address . . . . . . . . . . . . . . . . . . . 5 75 3.2. DNS-Server-IPv6-Address . . . . . . . . . . . . . . . . . 6 76 3.3. Route-IPv6-Information . . . . . . . . . . . . . . . . . . 7 77 3.4. Delegated-IPv6-Prefix-Pool . . . . . . . . . . . . . . . . 8 78 3.5. Stateful-IPv6-Address-Pool . . . . . . . . . . . . . . . . 9 79 3.6. Table of attributes . . . . . . . . . . . . . . . . . . . 9 80 4. Diameter Considerations . . . . . . . . . . . . . . . . . . . 10 81 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 82 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 83 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 84 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 85 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11 86 8.2. Informative References . . . . . . . . . . . . . . . . . . 11 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 89 1. Introduction 91 This document specifies additional RADIUS attributes used to support 92 configuration of DHCPv6 and/or ICMPv6 Router Advertisement (RA) 93 parameters on a per-user basis. The attributes, which complement 94 those defined in [RFC3162] and [RFC4818], support the following: 96 o Assignment of specific IPv6 addresses to hosts via DHCPv6. 98 o Assignment of an IPv6 DNS server address, via DHCPv6 or Router 99 Advertisement [RFC6106]. 101 o Configuration of more specific routes to be announced to the user 102 via the Route Information Option defined in [RFC4191] Section 2.3. 104 o The assignment of a named delegated prefix pool for use with "IPv6 105 Prefix Options for DHCPv6" [RFC3633]. 107 o The assignment of a named stateful address pool for use with 108 DHCPv6 stateful address assignment [RFC3315]. 110 2. Deployment Scenarios 112 The extensions in this draft are intended to be applicable across a 113 wide variety of network access scenarios where Radius is involved. 114 One such typical network scenario is illustrated in Figure 1. It is 115 composed of a IP Routing Residential Gateway (RG) or host, a Layer 2 116 Access-Node (AN) e.g. a Digital Subscriber Line Access Multiplexer - 117 DSLAM, an IP Network Access Servers (NASes), and an Authentication 118 Authorization & Accounting (AAA) server. 120 +-----+ 121 | AAA | 122 | | 123 +--+--+ 124 ^ 125 . 126 .(Radius) 127 . 128 v 129 +------+ +---+---+ 130 +------+ | AN | | NAS | 131 | RG/ +-------| +-----------+----------+ | 132 | host | | | | | 133 +------+ (DSL) +------+ (Ethernet) +-------+ 135 Figure 1 137 In the depicted scenario the NAS may embed a IP addressing protocols 138 (e.g. a DHCPv6 server) to handle address assignment to RGs/hosts. 139 The RADIUS server authenticates each RG/host and returns to the 140 attributes used for authorization and accounting. These attributes 141 can include a host's IPv6 address, a DNS server address and a set of 142 IPv6 routes to be advertised via DHCPv6 or ICMPv6. The name of a 143 prefix pool to be used for DHCPv6 Prefix Delegation, or the name of 144 an address pool to be used for DHCPv6 address assignment can also be 145 attributes provided to the NAS by the RADIUS AAA server. 147 The following sub-sections discuss how these attributes are used in 148 more detail. 150 2.1. IPv6 Address Assignment 152 DHCPv6 [RFC3315] provides a mechanism to assign one or more non- 153 temporary IPv6 addresses to hosts. To provide a DHCPv6 server 154 residing on a NAS with one or more IPv6 addresses to be assigned, 155 this document specifies the Framed-IPv6-Address Attribute. 157 While [RFC3162] permits an IPv6 address to be specified via the 158 combination of the Framed-Interface-Id and Framed-IPv6-Prefix 159 attributes, this separation is more natural for use with PPP's IPv6 160 Control Protocol than it is for use with DHCPv6, and the use of a 161 single IPv6 address attribute makes for easier processing of 162 accounting records. 164 Since DHCPv6 can be deployed on the same network as ICMPv6 stateless 165 (SLAAC) [RFC4862], it is possible that the NAS will require both 166 stateful and stateless configuration information. Therefore it is 167 possible for the Framed-IPv6-Address, Framed-IPv6-Prefix and Framed- 168 Interface-Id attributes [RFC3162] to be included within the same 169 packet. To avoid ambiguity, the Framed-IPv6-Address attribute is 170 only used for authorization and accounting of DHCPv6-assigned 171 addresses and the Framed-IPv6-Prefix and Framed-Interface-Id 172 attributes are used for authorization and accounting of addresses 173 assigned via SLAAC. 175 2.2. DNS Servers 177 DHCPv6 provides an option for configuring a host with the IPv6 178 address of a DNS server. The IPv6 address of a DNS server can also 179 be conveyed to the host using ICMPv6 with Router Advertisements, via 180 the [RFC6106] option. To provide the NAS with the IPv6 address of a 181 DNS server, this document specifies the DNS-Server-IPv6-Address 182 Attribute. 184 2.3. IPv6 Route Information 186 An IPv6 Route Information option, defined in [RFC4191] is intended to 187 be used to inform a host connected to the NAS that a specific route 188 is reachable via any given NAS. 190 This document specifies the RADIUS attribute that allows the AAA 191 server to provision the announcement by the NAS of a specific Route 192 Information Option to an accessing host. The NAS may advertise this 193 route using the method defined in [RFC4191], or using other 194 equivalent methods. Any other information, such as preference or 195 life-time values, that is to be present in the actual announcement 196 using a given method is assumed to be determined by the NAS using 197 means not scoped by this document (e.g. Local configuration on the 198 NAS). 200 While the Framed-IPv6-Prefix Attribute defined in [RFC3162] Section 201 2.3 causes the route to be advertised in an RA, it cannot be used to 202 configure more specific routes. While the Framed-IPv6-Route 203 Attribute defined in [RFC3162] Section 2.5 causes the route to be 204 configured on the NAS, and potentially announced via an IP routing 205 protocol, depending on the value of Framed-Routing, it does not 206 result in the route being announced in an RA. 208 2.4. Delegated IPv6 Prefix Pool 210 DHCPv6 Prefix Delegation (DHCPv6-PD) [RFC3633] involves a delegating 211 router selecting a prefix and delegating it on a temporary basis to a 212 requesting router. The delegating router may implement a number of 213 strategies as to how it chooses what prefix is to be delegated to a 214 requesting router, one of them being the use of a local named prefix 215 pool. The Delegated-IPv6-Prefix-Pool Attribute allows the RADIUS 216 server to convey a prefix pool name to a NAS hosting a DHCPv6-PD 217 server and acting as a delegating router. 219 Since DHCPv6 Prefix Delegation can be used with SLAAC on the same 220 network, it is possible for the Delegated-IPv6-Prefix-Pool and 221 Framed-IPv6-Pool attributes to be included within the same packet. 222 To avoid ambiguity in this scenario, use of the Delegated-IPv6 223 -Prefix-Pool attribute should be restricted to authorization and 224 accounting of prefix pools used in DHCPv6 Prefix Delegation and the 225 Framed-IPv6-Pool attribute should be used for authorization and 226 accounting of prefix pools used in SLAAC. 228 2.5. Stateful IPv6 address pool 230 DHCPv6 [RFC3315] provides a mechanism to assign one or more non- 231 temporary IPv6 addresses to hosts. Section 3.1 introduces the 232 Framed-IPv6-Address Attribute to be used for providing a DHCPv6 233 server residing on a NAS with one or more IPv6 addresses to be 234 assigned to the clients. An alternative way to achieve a similar 235 result is for the NAS to select the IPv6 address to be assigned from 236 an address pool configured for this purpose on the NAS. This document 237 specifies the Stateful-IPv6-Address-Pool attribute to allow the 238 RADIUS server to convey a pool name to be used for such stateful 239 DHCPv6 based addressing, and any subsequent accounting. 241 3. Attributes 243 The fields shown in the diagrams below are transmitted from left to 244 right. 246 3.1. Framed-IPv6-Address 248 This Attribute indicates an IPv6 Address that is assigned to the NAS- 249 facing interface of the RG/host. It MAY be used in Access-Accept 250 packets, and MAY appear multiple times. It MAY be used in an Access- 251 Request packet as a hint by the NAS to the server that it would 252 prefer these IPv6 address(es), but the server is not required to 253 honor the hint. Since it is assumed that the NAS will add a route 254 corresponding to the address, it is not necessary for the server to 255 also send a host Framed-IPv6-Route attribute for the same address. 257 This Attribute can be used by a DHCPv6 process on the NAS to assign a 258 unique IPv6 address to the RG/host. 260 A summary of the Framed-IPv6-Address Attribute format is shown below. 261 The format of the address is as per [RFC3162]. 263 0 1 2 3 264 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 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Type | Length | Address 267 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 268 Address (cont) 269 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 270 Address (cont) 271 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 272 Address (cont) 273 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 Address (cont.) | 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 Type 279 TBA1 for Framed-IPv6-Address 281 Length 283 18 285 Address 287 The IPv6 address field contains a 128-bit IPv6 address. 289 3.2. DNS-Server-IPv6-Address 291 The DNS-Server-IPv6-Address Attribute contains the IPv6 address of a 292 DNS server. This attribute MAY be included multiple times in Access- 293 Accept packets, when the intention is for a NAS to announce more than 294 one DNS server addresses to a RG/host. The same order of the 295 attributes is expected to be followed in the announcements to the 296 client. The attribute MAY be used in an Access-Request packet as a 297 hint by the NAS to the server regarding the DNS IPv6 Address, but the 298 Radius server is not required to honor the hint. 300 The content of this attribute can be inserted in a DHCPv6 option as 301 specified in [RFC3646]. 303 A summary of the DNS-Server-IPv6-Address Attribute format is given 304 below. The format of the address is as per [RFC3162]. 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 | Address 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 Address (cont) 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 Address (cont) 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 Address (cont) 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 Address (cont.) | 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 Type 322 TBA2 for DNS-Server-IPv6-Address 324 Length 326 18 328 Address 330 The 128-bit IPv6 address of a DNS server. 332 3.3. Route-IPv6-Information 334 This Attribute specifies a prefix (and corresponding route) for the 335 user on the NAS, which is to be announced using the Route Information 336 Option defined in "Default Router Preferences and More Specific 337 Routes" [RFC4191] Section 2.3. It is used in the Access-Accept packet 338 and can appear multiple times. It MAY be used in an Access-Request 339 packet as a hint by the NAS to the server, but the server is not 340 required to honor the hint. The Route-IPv6-Information attribute 341 format is depicted below. The format of the prefix is as per 342 [RFC3162]. 344 0 1 2 3 345 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 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | Type | Length | Reserved | Prefix-Length | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | | 350 . Prefix (variable) . 351 . . 352 | | 353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 Type 357 TBA3 for Route-IPv6-Information 359 Length 361 Length in bytes. At least 4 and no larger than 20; typically 362 12 or less. 364 Prefix Length 366 8-bit unsigned integer. The number of leading bits in 367 the Prefix that are valid. The value ranges from 0 to 128. The 368 prefix field is 0, 8 or 16 octets depending on Length. 370 Prefix 372 Variable-length field containing an IP prefix. The Prefix 373 Length field contains the number of valid leading bits in the 374 prefix. The bits in the prefix after the prefix length (if any) 375 are reserved and MUST be initialized to zero. 377 3.4. Delegated-IPv6-Prefix-Pool 379 This Attribute contains the name of an assigned pool that SHOULD be 380 used to select an IPv6 delegated prefix for the user on the NAS. If a 381 NAS does not support prefix pools, the NAS MUST ignore this 382 Attribute. It MAY be used in an Access-Request packet as a hint by 383 the NAS to the server regarding the pool, but the server is not 384 required to honor the hint. 386 A summary of the Delegated-IPv6-Prefix-Pool Attribute format is shown 387 below. 389 0 1 2 390 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | Type | Length | String... 393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 395 Type 396 TBA4 for Delegated-IPv6-Prefix-Pool 398 Length 400 Length in bytes. At least 3. 402 String 404 The string field contains the name of an assigned IPv6 prefix 405 pool configured on the NAS. The field is not NULL (hexadecimal 00) 406 terminated. 408 3.5. Stateful-IPv6-Address-Pool 410 This Attribute contains the name of an assigned pool that SHOULD be 411 used to select an IPv6 address for the user on the NAS. If a NAS does 412 not support address pools, the NAS MUST ignore this Attribute. A 413 summary of the Stateful-IPv6-Address-Pool Attribute format is shown 414 below. It MAY be used in an Access-Request packet as a hint by the 415 NAS to the server regarding the pool, but the server is not required 416 to honor the hint. 418 0 1 2 419 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Type | Length | String... 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 Type 426 TBA5 for Stateful-IPv6-Address-Pool 428 Length 430 Length in bytes. At least 3. 432 String 434 The string field contains the name of an assigned IPv6 435 stateful address pool configured on the NAS. The field is not NULL 436 (hexadecimal 00) terminated. 438 3.6. Table of attributes 440 The following table provides a guide to which attributes may be found 441 in which kinds of packets, and in what quantity. The optional 442 inclusion of the options in Access Request messages is intended to 443 allow for a network access server (NAS) to provide the RADIUS server 444 with a hint of the attributes in advance of user authentication, 445 which may be useful in cases where a user re-connects or has a static 446 address. The server is under no obligation to honor such hints. 448 Request Accept Reject Challenge Accounting # Attribute 449 Request 450 0+ 0+ 0 0 0+ TBA1 Framed-IPv6-Address 451 0+ 0+ 0 0 0+ TBA2 DNS-Server-IPv6-Address 452 0+ 0+ 0 0 0+ TBA3 Route-IPv6-Information 453 0+ 0+ 0 0 0+ TBA4 Delegated-IPv6-Prefix-Pool 454 0+ 0+ 0 0 0+ TBA5 Stateful-IPv6-Address-Pool 456 4. Diameter Considerations 458 Given that the Attributes defined in this document are allocated from 459 the standard RADIUS type space (see Section 6), no special handling 460 is required by Diameter entities. 462 5. Security Considerations 464 This document describes the use of RADIUS for the purposes of 465 authentication, authorization and accounting in IPv6-enabled 466 networks. In such networks, the RADIUS protocol may run either over 467 IPv4 or over IPv6. Known security vulnerabilities of the RADIUS 468 protocol apply to the attributes defined in this document. Since 469 IPsec is natively defined for IPv6, it is expected that running 470 RADIUS implementations supporting IPv6 may want to run over IPsec. 471 Where RADIUS is run over IPsec and where certificates are used for 472 authentication, it may be desirable to avoid management of RADIUS 473 shared secrets, so as to leverage the improved scalability of public 474 key infrastructure. 476 6. IANA Considerations 478 This document requires the assignment of five new RADIUS Attribute 479 Types in the "Radius Types" registry (currently located at http:// 480 www.iana.org/assignments/radius-types for the following attributes: 482 o Framed-IPv6-Address 484 o DNS-Server-IPv6-Address 486 o Route-IPv6-Information 488 o Delegated-IPv6-Prefix-Pool 490 o Stateful-IPv6-Address-Pool 492 7. Acknowledgements 494 The authors would like to thank Bernard Aboba, Benoit Claise, Peter 495 Deacon, Alan DeKok, Alfred Hines, Jouni Korhonen, Roberta Maglione, 496 Leaf Yeh, and Mark Smith for their help and comments in reviewing 497 this document. 499 8. References 500 8.1. Normative References 502 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 503 Requirement Levels", BCP 14, RFC 2119, March 1997. 505 [RFC4862] Thomson, S., Narten, T. and T. Jinmei, "IPv6 Stateless 506 Address Autoconfiguration", RFC 4862, September 2007. 508 8.2. Informative References 510 [RFC3162] Aboba, B., Zorn, G. and D. Mitton, "RADIUS and IPv6", RFC 511 3162, August 2001. 513 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and 514 M. Carney, "Dynamic Host Configuration Protocol for IPv6 515 (DHCPv6)", RFC 3315, July 2003. 517 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 518 Host Configuration Protocol (DHCP) version 6", RFC 3633, 519 December 2003. 521 [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host 522 Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, 523 December 2003. 525 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 526 More-Specific Routes", RFC 4191, November 2005. 528 [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix 529 Attribute", RFC 4818, April 2007. 531 [RFC6106] Jeong, J., Park, S., Beloeil, L. and S. Madanapalli, "IPv6 532 Router Advertisement Options for DNS Configuration", RFC 533 6106, November 2010. 535 Authors' Addresses 537 Wojciech Dec (editor) 538 Cisco Systems, Inc. 539 Haarlerbergweg 13-19 540 Amsterdam , NOORD-HOLLAND 1101 CH 541 Netherlands 543 Email: wdec@cisco.com 544 Behcet Sarikaya 545 Huawei USA 546 1700 Alma Dr. Suite 500 547 Plano, TX 548 US 550 Phone: +1 972-509-5599 551 Email: sarikaya@ieee.org 553 Glen Zorn 554 Network Zen 555 1310 East Thomas Street 556 Seattle, WA 557 US 559 Email: gwz@net-zen.net 561 David Miles 562 Google 564 Email: David.Miles@google.com 566 Benoit Lourdelet 567 France 569 Email: blourdelet@aim.com