idnits 2.17.1 draft-ietf-radext-ipv6-access-11.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 -- The document date (August 1, 2012) is 4287 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: 0 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W. Dec, Ed. 3 Internet-Draft Cisco Systems, Inc. 4 Intended status: Standards Track B. Sarikaya 5 Expires: February 2, 2013 Huawei USA 6 G. Zorn 7 Network Zen 8 D. Miles 9 Google 10 B. Lourdelet 11 August 1, 2012 13 RADIUS attributes for IPv6 Access Networks 14 draft-ietf-radext-ipv6-access-11.txt 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 February 2, 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 3 68 2.1. IPv6 Address Assignment . . . . . . . . . . . . . . . . . 4 69 2.2. Recursive DNS Servers . . . . . . . . . . . . . . . . . . 4 70 2.3. IPv6 Route Information . . . . . . . . . . . . . . . . . . 5 71 2.4. Delegated IPv6 Prefix Pool . . . . . . . . . . . . . . . . 5 72 2.5. Stateful IPv6 address pool . . . . . . . . . . . . . . . . 6 73 3. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 6 74 3.1. Framed-IPv6-Address . . . . . . . . . . . . . . . . . . . 6 75 3.2. DNS-Server-IPv6-Address . . . . . . . . . . . . . . . . . 7 76 3.3. Route-IPv6-Information . . . . . . . . . . . . . . . . . . 8 77 3.4. Delegated-IPv6-Prefix-Pool . . . . . . . . . . . . . . . . 9 78 3.5. Stateful-IPv6-Address-Pool . . . . . . . . . . . . . . . . 10 79 3.6. Table of attributes . . . . . . . . . . . . . . . . . . . 10 80 4. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11 81 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 82 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 83 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 84 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 85 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 86 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12 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, one or more IP Network Access Servers (NASes), and an 118 Authentication 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 the host's IPv6 address to be configured via DHCPv6 as 142 well as the IPv6 address of a DNS server to be advertised to the 143 client. The name of a prefix pool to be used for DHCPv6 Prefix 144 Delegation, or the set of IPv6 routes to be announced to the host can 145 also be attributes provided to the NAS from 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 or 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 IPv6CP than 160 it is for use with DHCPv6, and the use of a single IPv6 address 161 attribute makes for easier processing of accounting records. 163 Since DHCPv6 can be deployed on the same network as ICMPv6 stateless 164 (SLAAC) [RFC4862], it is possible that the NAS will require both 165 stateful and stateless configuration information. Therefore it is 166 possible for the Framed-IPv6-Address, Framed-IPv6-Prefix and Framed- 167 Interface-Id attributes [RFC3162] to be included within the same 168 packet. To avoid ambiguity, the Framed-IPv6-Address attribute is 169 only used for authorization and accounting of DHCPv6-assigned 170 addresses and the Framed-IPv6-Prefix and Framed-Interface-Id 171 attributes are used for authorization and accounting of addresses 172 assigned via SLAAC. 174 2.2. Recursive DNS Servers 176 DHCPv6 provides an option for configuring a host with the IPv6 177 address of a DNS server. The IPv6 address of a DNS server can also 178 be conveyed to the host using ICMPv6 with Router Advertisements, via 179 the experimental [RFC6106] option. To provide the NAS with the IPv6 180 address of a DNS server, this document specifies the DNS-Server-IPv6- 181 Address Attribute. 183 2.3. IPv6 Route Information 185 An IPv6 Route Information option, defined in [RFC4191] is intended to 186 be used to inform a host connected to the NAS that a specific route 187 is reachable via the NAS. This is particularly desirable in cases 188 where the RG or host are multi-homed to different NASes as shown in 189 Figure 1. 191 This document specifies the RADIUS attribute that allows the AAA 192 system to provision the announcement by the NAS of a specific Route 193 Information Option to an accessing host. The NAS may advertise this 194 route using the method defined in [RFC4191], or using other 195 equivalent methods. Any other information, such as preference or 196 life-time values, that is to be present in the actual announcement 197 using a given method is assumed to be determined by the NAS using 198 means not scoped by this document (e.g. local configuration on the 199 NAS). 201 While the Framed-IPv6-Prefix Attribute defined in [RFC3162] Section 202 2.3 causes the route to be advertised in an RA, it cannot be used to 203 configure more specific routes. While the Framed-IPv6-Route 204 Attribute defined in [RFC3162] Section 2.5 causes the route to be 205 configured on the NAS, and potentially announced via an IP routing 206 protocol, depending on the value of Framed-Routing, it does not 207 result in the route being announced in an RA. 209 2.4. Delegated IPv6 Prefix Pool 211 DHCPv6 Prefix Delegation [RFC3633] involves a delegating router 212 selecting a prefix and delegating it on a temporary basis to a 213 requesting router. The delegating router may implement a number of 214 strategies as to how it chooses what prefix is to be delegated to a 215 requesting router, one of them being the use of a local named prefix 216 pool. The Delegated-IPv6-Prefix-Pool Attribute allows the RADIUS 217 server to convey a prefix pool name to a NAS hosting a DHCPv6-PD 218 server and acting as a delegated router. 220 Since DHCPv6 Prefix Delegation can conceivably be used on the same 221 network as SLAAC, it is possible for the Delegated-IPv6-Prefix-Pool 222 and Framed-IPv6-Pool attributes to be included within the same 223 packet. To avoid ambiguity in this scenario, use of the Delegated- 224 IPv6-Prefix-Pool attribute should be restricted to authorization and 225 accounting of prefix pools used in DHCPv6 Prefix Delegation and the 226 Framed-IPv6-Pool attribute should be used for authorization and 227 accounting of prefix pools used in SLAAC. 229 2.5. Stateful IPv6 address pool 231 DHCPv6 [RFC3315] provides a mechanism to assign one or more or non- 232 temporary IPv6 addresses to hosts. Section 2.1 introduces the 233 Framed-IPv6-Address Attribute to be used for providing a DHCPv6 234 server residing on a NAS with one or more IPv6 addresses to be 235 assigned to the clients. An alternative way to achieve a similar 236 result is for the NAS to select the IPv6 address to be assigned from 237 an address pool configured for this purpose on the NAS. This 238 document specifies the Stateful-IPv6-Address-Pool attribute to allow 239 the RADIUS server to convey a pool name to be used for such stateful 240 DHCPv6 based addressing, and any subsequent accounting. 242 3. Attributes 244 The fields shown in the diagrams below are transmitted from left to 245 right. 247 3.1. Framed-IPv6-Address 249 This Attribute indicates an IPv6 Address that is assigned to the NAS- 250 facing interface of the RG/host. It MAY be used in Access-Accept 251 packets, and MAY appear multiple times. It MAY be used in an Access- 252 Request packet as a hint by the NAS to the server that it would 253 prefer these IPv6 address(es), but the server is not required to 254 honor the hint. Since it is assumed that the NAS will add a route 255 corresponding to the address, it is not necessary for the server to 256 also send a host Framed-IPv6-Route attribute for the same address. 258 This Attribute can be used by a DHCPv6 process on the NAS to assign a 259 unique IPv6 address to the RG/host. 261 A summary of the Framed-IPv6-Address Attribute format is shown below. 262 The format of the address is as per [RFC3162]. 264 0 1 2 3 265 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 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Type | Length | Address 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 Address (cont) 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 Address (cont) 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 Address (cont) 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 Address (cont.) | 277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 Type 281 TBA1 for Framed-IPv6-Address 283 Length 285 18 287 Address 289 The IPv6 address field contains a 128-bit IPv6 address. 291 3.2. DNS-Server-IPv6-Address 293 The DNS-Server-IPv6-Address Attribute contains the IPv6 address of a 294 recursive DNS server. This attribute MAY be included multiple times 295 in Access-Accept packets, when the intention is for a NAS to announce 296 more than one recursive DNS address to an RG/host. The same order of 297 the attributes is expected to be followed in the announcements to the 298 client. The attribute MAY be used in an Access-Request packet as a 299 hint by the NAS to the server regarding the DNS IPv6 Address, but the 300 Radius server is not required to honor the hint. 302 The content of this attribute can be inserted in a DHCPv6 option as 303 specified in [RFC3646]. 305 A summary of the DNS-Server-IPv6-Address Attribute format is given 306 below. The format of the address is as per [RFC3162]. 308 0 1 2 3 309 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 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 311 | Type | Length | Address 312 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 313 Address (cont) 314 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 Address (cont) 316 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 317 Address (cont) 318 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 319 Address (cont.) | 320 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 Type 324 TBA2 for DNS-Server-IPv6-Address 326 Length 328 18 330 Address 332 The 128-bit IPv6 address of a DNS server. 334 3.3. Route-IPv6-Information 336 This Attribute specifies a prefix (and corresponding route) for the 337 user on the NAS, which is to be announced using the Route Information 338 Option defined in "Default Router Preferences and More Specific 339 Routes" [RFC4191] Section 2.3. It is used in the Access-Accept 340 packet and can appear multiple times. It MAY be used in an Access- 341 Request packet as a hint by the NAS to the server, but the server is 342 not required to honor the hint. The Route-IPv6-Information attribute 343 format is depicted below. The format of the prefix is as per 344 [RFC3162]. 346 0 1 2 3 347 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 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | Type | Length | Reserved | Prefix-Length | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | | 352 . Prefix (variable) . 353 . . 354 | | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 Type 359 TBA3 for Route-IPv6-Information 361 Length 363 Length in bytes. At least 4 and no larger than 20; typically 12 364 or less. 366 Prefix Length 368 8-bit unsigned integer. The number of leading bits in the Prefix 369 that are valid. The value ranges from 0 to 128. The prefix field 370 is 0, 8 or 16 octets depending on Length. 372 Prefix 374 Variable-length field containing an IP prefix. The Prefix Length 375 field contains the number of valid leading bits in the prefix. 376 The bits in the prefix after the prefix length (if any) are 377 reserved and MUST be initialized to zero. 379 3.4. Delegated-IPv6-Prefix-Pool 381 This Attribute contains the name of an assigned pool that SHOULD be 382 used to select an IPv6 delegated prefix for the user. If a NAS does 383 not support multiple prefix pools, the NAS MUST ignore this 384 Attribute. It MAY be used in an Access-Request packet as a hint by 385 the NAS to the server regarding the pool, but the server is not 386 required to honor the hint. 388 A summary of the Delegated-IPv6-Prefix-Pool Attribute format is shown 389 below. 390 0 1 2 391 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 | Type | Length | String... 394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 396 Type 398 TBA4 for Delegated-IPv6-Prefix-Pool 400 Length 402 Length in bytes. At least 3. 404 String 406 The string field contains the name of an assigned IPv6 prefix pool 407 configured on the NAS. The field is not NULL (hexadecimal 00) 408 terminated. 410 3.5. Stateful-IPv6-Address-Pool 412 This Attribute contains the name of an assigned pool that SHOULD be 413 used to select an IPv6 address for the user. If a NAS does not 414 support address pools, the NAS MUST ignore this Attribute. A summary 415 of the Stateful-IPv6-Address-Pool Attribute format is shown below. 416 It MAY be used in an Access-Request packet as a hint by the NAS to 417 the server regarding the pool, but the server is not required to 418 honor the hint. 420 0 1 2 421 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Type | Length | String... 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 Type 428 TBA5 for Stateful-IPv6-Address-Pool 430 Length 432 Length in bytes. At least 3. 434 String 436 The string field contains the name of an assigned IPv6 stateful 437 address pool configured on the NAS. The field is not NULL 438 (hexadecimal 00) terminated. 440 3.6. Table of attributes 442 The following table provides a guide to which attributes may be found 443 in which kinds of packets, and in what quantity. The optional 444 inclusion of the options in Access Request messages is intended to 445 allow for a network access server (NAS) to provide the RADIUS server 446 with a hint of the attributes in advance of user authentication, 447 which may be useful in cases where a user re-connects or has a static 448 address. The server is under no obligation to honor such hints. 450 Request Accept Reject Challenge Accounting # Attribute 451 Request 452 0+ 0+ 0 0 0+ TBA1 Framed-IPv6-Address 453 0+ 0+ 0 0 0+ TBA2 DNS-Server-IPv6-Address 454 0+ 0+ 0 0 0+ TBA3 Route-IPv6-Information 455 0+ 0+ 0 0 0+ TBA4 Delegated-IPv6-Prefix-Pool 456 0+ 0+ 0 0 0+ TBA5 Stateful-IPv6-Address-Pool 458 4. Diameter Considerations 460 Given that the Attributes defined in this document are allocated from 461 the standard RADIUS type space (see Section 6), no special handling 462 is required by Diameter entities. 464 5. Security Considerations 466 This document describes the use of RADIUS for the purposes of 467 authentication, authorization and accounting in IPv6-enabled 468 networks. In such networks, the RADIUS protocol may run either over 469 IPv4 or over IPv6. Known security vulnerabilities of the RADIUS 470 protocol apply to the attributes defined in this document. Since 471 IPsec is natively defined for IPv6, it is expected that running 472 RADIUS implementations supporting IPv6 may want to run over IPsec. 473 Where RADIUS is run over IPsec and where certificates are used for 474 authentication, it may be desirable to avoid management of RADIUS 475 shared secrets, so as to leverage the improved scalability of public 476 key infrastructure. 478 6. IANA Considerations 480 This document requires the assignment of five new RADIUS Attribute 481 Types in the "Radius Types" registry (currently located at 482 http://www.iana.org/assignments/radius-types for the following 483 attributes: 485 o Framed-IPv6-Address 487 o DNS-Server-IPv6-Address 489 o Route-IPv6-Information 491 o Delegated-IPv6-Prefix-Pool 493 o Stateful-IPv6-Address-Pool 495 7. Acknowledgements 497 The authors would like to thank Bernard Aboba, Peter Deacon, Alan 498 DeKok, Alfred Hines, Jouni Korhonen, Roberta Maglione, Leaf Yeh, and 499 Mark Smith for their help and comments in reviewing this document. 501 8. References 503 8.1. Normative References 505 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 506 Requirement Levels", BCP 14, RFC 2119, March 1997. 508 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 509 Address Autoconfiguration", RFC 4862, September 2007. 511 8.2. Informative References 513 [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", 514 RFC 3162, August 2001. 516 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 517 and M. Carney, "Dynamic Host Configuration Protocol for 518 IPv6 (DHCPv6)", RFC 3315, July 2003. 520 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 521 Host Configuration Protocol (DHCP) version 6", RFC 3633, 522 December 2003. 524 [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host 525 Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, 526 December 2003. 528 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 529 More-Specific Routes", RFC 4191, November 2005. 531 [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix 532 Attribute", RFC 4818, April 2007. 534 [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, 535 "IPv6 Router Advertisement Options for DNS Configuration", 536 RFC 6106, November 2010. 538 Authors' Addresses 540 Wojciech Dec (editor) 541 Cisco Systems, Inc. 542 Haarlerbergweg 13-19 543 Amsterdam , NOORD-HOLLAND 1101 CH 544 Netherlands 546 Email: wdec@cisco.com 547 Behcet Sarikaya 548 Huawei USA 549 1700 Alma Dr. Suite 500 550 Plano, TX 551 US 553 Phone: +1 972-509-5599 554 Email: sarikaya@ieee.org 556 Glen Zorn 557 Network Zen 558 1310 East Thomas Street 559 Seattle, WA 560 US 562 Email: gwz@net-zen.net 564 David Miles 565 Google 567 Phone: 568 Fax: 569 Email: David.Miles@google.com 570 URI: 572 Benoit Lourdelet 573 France 575 Email: blourdelet@aim.com