idnits 2.17.1 draft-ietf-radext-ipv6-access-14.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 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 (January 03, 2013) is 4103 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 (~~), 2 warnings (==), 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: July 07, 2013 Huawei USA 6 G. Zorn 7 Network Zen 8 D. Miles 9 Google 10 B. Lourdelet 11 Juniper Networks 12 January 03, 2013 14 RADIUS attributes for IPv6 Access Networks 15 draft-ietf-radext-ipv6-access-14 17 Abstract 19 This document specifies additional IPv6 RADIUS attributes useful in 20 residential broadband network deployments. The attributes, which are 21 used for authorization and accounting, enable assignment of a host 22 IPv6 address and IPv6 DNS server address via DHCPv6; assignment of an 23 IPv6 route announced via router advertisement; assignment of a named 24 IPv6 delegated prefix pool; and assignment of a named IPv6 pool for 25 host DHCPv6 addressing. 27 Requirements Language 29 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 30 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 31 document are to be interpreted as described in RFC 2119 [RFC2119]. 33 Status of This Memo 35 This Internet-Draft is submitted in full conformance with the 36 provisions of BCP 78 and BCP 79. 38 Internet-Drafts are working documents of the Internet Engineering 39 Task Force (IETF). Note that other groups may also distribute 40 working documents as Internet-Drafts. The list of current Internet- 41 Drafts is at http://datatracker.ietf.org/drafts/current/. 43 Internet-Drafts are draft documents valid for a maximum of six months 44 and may be updated, replaced, or obsoleted by other documents at any 45 time. It is inappropriate to use Internet-Drafts as reference 46 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on July 07, 2013. 50 Copyright Notice 51 Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . 9 81 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 82 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 83 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 84 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 85 8.1. Normative References . . . . . . . . . . . . . . . . . . . 10 86 8.2. Informative References . . . . . . . . . . . . . . . . . . 10 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 utilize an IP address 138 configuration protocol (e.g. a DHCPv6 server) to handle address 139 assignment to RGs/hosts. The RADIUS server authenticates each RG/ 140 host and returns to the attributes used for authorization and 141 accounting. These attributes can include a host's IPv6 address, a 142 DNS server address and a set of IPv6 routes to be advertised via 143 DHCPv6 or ICMPv6. The name of a prefix pool to be used for DHCPv6 144 Prefix Delegation, or the name of an address pool to be used for 145 DHCPv6 address assignment can also be attributes provided to the NAS 146 by the RADIUS AAA server. 148 The following sub-sections discuss how these attributes are used in 149 more detail. 151 2.1. IPv6 Address Assignment 153 DHCPv6 [RFC3315] provides a mechanism to assign one or more non- 154 temporary IPv6 addresses to hosts. To provide a DHCPv6 server 155 residing on a NAS with one or more IPv6 addresses to be assigned, 156 this document specifies the Framed-IPv6-Address Attribute. 158 While [RFC3162] permits an IPv6 address to be specified via the 159 combination of the Framed-Interface-Id and Framed-IPv6-Prefix 160 attributes, this separation is more natural for use with PPP's IPv6 161 Control Protocol than it is for use with DHCPv6, and the use of a 162 single IPv6 address attribute makes for easier processing of 163 accounting records. 165 Since DHCPv6 can be deployed on the same network as ICMPv6 stateless 166 (SLAAC) [RFC4862], it is possible that the NAS will require both 167 stateful and stateless configuration information. Therefore it is 168 possible for the Framed-IPv6-Address, Framed-IPv6-Prefix and Framed- 169 Interface-Id attributes [RFC3162] to be included within the same 170 packet. To avoid ambiguity, the Framed-IPv6-Address attribute is 171 only used for authorization and accounting of DHCPv6-assigned 172 addresses and the Framed-IPv6-Prefix and Framed-Interface-Id 173 attributes are used for authorization and accounting of addresses 174 assigned via SLAAC. 176 2.2. DNS Servers 178 DHCPv6 provides an option for configuring a host with the IPv6 179 address of a DNS server. The IPv6 address of a DNS server can also 180 be conveyed to the host using ICMPv6 with Router Advertisements, via 181 the [RFC6106] option. To provide the NAS with the IPv6 address of a 182 DNS server, this document specifies the DNS-Server-IPv6-Address 183 Attribute. 185 2.3. IPv6 Route Information 187 An IPv6 Route Information option, defined in [RFC4191] is intended to 188 be used to inform a host connected to the NAS that a specific route 189 is reachable via any given NAS. 191 This document specifies the RADIUS attribute that allows the AAA 192 server 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 (DHCPv6-PD) [RFC3633] involves a delegating 212 router 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 delegating router. 220 Since DHCPv6 Prefix Delegation can be used with SLAAC on the same 221 network, it is possible for the Delegated-IPv6-Prefix-Pool and 222 Framed-IPv6-Pool attributes to be included within the same packet. 223 To avoid ambiguity in this scenario, use of the Delegated-IPv6 224 -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 non- 232 temporary IPv6 addresses to hosts. Section 3.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) | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 278 Type 280 TBA1 for Framed-IPv6-Address 282 Length 284 18 286 Address 288 The IPv6 address field contains a 128-bit IPv6 address. 290 3.2. DNS-Server-IPv6-Address 292 The DNS-Server-IPv6-Address attribute contains the IPv6 address of a 293 DNS server. This attribute MAY be included multiple times in Access- 294 Accept packets, when the intention is for a NAS to announce more than 295 one DNS server addresses to a RG/host. The same order of the 296 attributes is expected to be followed in the announcements to the 297 client. The attribute MAY be used in an Access-Request packet as a 298 hint by the NAS to the server regarding the DNS IPv6 address, but the 299 Radius server is not required to honor the hint. 301 The content of this attribute can be inserted in a DHCPv6 option as 302 specified in [RFC3646]. 304 A summary of the DNS-Server-IPv6-Address attribute format is given 305 below. The format of the address is as per [RFC3162]. 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 | Address 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 Address (cont) 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 Address (cont) 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 Address (cont) 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 Address (cont) | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 Type 323 TBA2 for DNS-Server-IPv6-Address 325 Length 327 18 329 Address 331 The 128-bit IPv6 address of a DNS server. 333 3.3. Route-IPv6-Information 335 This attribute specifies a prefix (and corresponding route) for the 336 user on the NAS, which is to be announced using the Route Information 337 Option defined in "Default Router Preferences and More Specific 338 Routes" [RFC4191] Section 2.3. It is used in the Access-Accept 339 packet and can appear multiple times. It MAY be used in an Access- 340 Request packet as a hint by the NAS to the server, but the server is 341 not required to honor the hint. The Route-IPv6-Information attribute 342 format is depicted below. The format of the prefix is as per 343 [RFC3162]. 345 0 1 2 3 346 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 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | Type | Length | Reserved | Prefix-Length | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 350 | | 351 . Prefix (variable) . 352 . . 353 | | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 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 381 a 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 397 TBA4 for Delegated-IPv6-Prefix-Pool 399 Length 401 Length in bytes. At least 3. 403 String 405 The string field contains the name of an assigned IPv6 prefix 406 pool configured on the NAS. The field is not NULL (hexadecimal 407 00) terminated. 409 3.5. Stateful-IPv6-Address-Pool 411 This attribute contains the name of an assigned pool that SHOULD be 412 used to select an IPv6 address for the user on the NAS. If a NAS 413 does not support address pools, the NAS MUST ignore this attribute. 414 A summary of the Stateful-IPv6-Address-Pool attribute format is shown 415 below. It MAY be used in an Access-Request packet as a hint by the 416 NAS to the server regarding the pool, but the server is not required 417 to honor the hint. 419 0 1 2 420 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 421 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 422 | Type | Length | String... 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 Type 427 TBA5 for Stateful-IPv6-Address-Pool 429 Length 431 Length in bytes. At least 3. 433 String 435 The string field contains the name of an assigned IPv6 436 stateful address pool configured on the NAS. The field is not 437 NULL (hexadecimal 00) terminated. 439 3.6. Table of attributes 441 The following table provides a guide to which attributes may be found 442 in which kinds of packets, and in what quantity. The optional 443 inclusion of the options in Access Request messages is intended to 444 allow for a network access server (NAS) to provide the RADIUS server 445 with a hint of the attributes in advance of user authentication, 446 which may be useful in cases where a user re-connects or has a static 447 address. The server is under no obligation to honor such hints. 449 Request Accept Reject Challenge Accounting # Attribute 450 Request 451 0+ 0+ 0 0 0+ TBA1 Framed-IPv6-Address 452 0+ 0+ 0 0 0+ TBA2 DNS-Server-IPv6-Address 453 0+ 0+ 0 0 0+ TBA3 Route-IPv6-Information 454 0+ 0+ 0 0 0+ TBA4 Delegated-IPv6-Prefix-Pool 455 0+ 0+ 0 0 0+ TBA5 Stateful-IPv6-Address-Pool 457 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 specifies additional IPv6 RADIUS attributes useful in 465 residential broadband network deployments. In such networks, the 466 RADIUS protocol may run either over IPv4 or over IPv6 and known 467 security vulnerabilities of the RADIUS protocol apply to the 468 attributes defined in this document. Since IPsec is natively defined 469 for IPv6, it is expected that running RADIUS implementations 470 supporting IPv6 may want to run over IPsec. Where RADIUS is run over 471 IPsec and where certificates are used for authentication, it may be 472 desirable to avoid management of RADIUS shared secrets, so as to 473 leverage the improved scalability of public key infrastructure. 475 6. IANA Considerations 477 This document requires the assignment of five new RADIUS attribute 478 types in the "Radius Types" registry (currently located at http:// 479 www.iana.org/assignments/radius-types for the following attributes: 481 o Framed-IPv6-Address 483 o DNS-Server-IPv6-Address 485 o Route-IPv6-Information 487 o Delegated-IPv6-Prefix-Pool 489 o Stateful-IPv6-Address-Pool 491 7. Acknowledgements 493 The authors would like to thank Bernard Aboba, Benoit Claise, Peter 494 Deacon, Alan DeKok, Alfred Hines, Jouni Korhonen, Roberta Maglione, 495 Leaf Yeh, and Mark Smith for their help and comments in reviewing 496 this document. 498 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., 514 and M. Carney, "Dynamic Host Configuration Protocol for 515 IPv6 (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, 532 "IPv6 Router Advertisement Options for DNS Configuration", 533 RFC 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 545 Behcet Sarikaya 546 Huawei USA 547 1700 Alma Dr. Suite 500 548 Plano, TX 549 US 551 Phone: +1 972-509-5599 552 Email: sarikaya@ieee.org 554 Glen Zorn 555 Network Zen 556 1310 East Thomas Street 557 Seattle, WA 558 US 560 Email: gwz@net-zen.net 561 David Miles 562 Google 564 Email: david.miles@google.com 566 Benoit Lourdelet 567 Juniper Networks 568 France 570 Email: blourdel@juniper.net