idnits 2.17.1 draft-ietf-radext-ipv6-access-08.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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 27, 2012) is 4314 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) == Missing Reference: 'RFC3162' is mentioned on line 215, but not defined == Missing Reference: 'RFC4818' is mentioned on line 106, but not defined -- 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 (~~), 4 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: December 29, 2012 Huawei USA 6 G. Zorn 7 Network Zen 8 D. Miles 9 Alcatel-Lucent 10 B. Lourdelet 11 June 27, 2012 13 RADIUS attributes for IPv6 Access Networks 14 draft-ietf-radext-ipv6-access-08.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 December 29, 2012. 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 This document may contain material from IETF Documents or IETF 65 Contributions published or made publicly available before November 66 10, 2008. The person(s) controlling the copyright in some of this 67 material may not have granted the IETF Trust the right to allow 68 modifications of such material outside the IETF Standards Process. 69 Without obtaining an adequate license from the person(s) controlling 70 the copyright in such materials, this document may not be modified 71 outside the IETF Standards Process, and derivative works of it may 72 not be created outside the IETF Standards Process, except to format 73 it for publication as an RFC or to translate it into languages other 74 than English. 76 Table of Contents 78 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 79 2. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . . 4 80 2.1. IPv6 Address Assignment . . . . . . . . . . . . . . . . . 5 81 2.2. Recursive DNS Servers . . . . . . . . . . . . . . . . . . 5 82 2.3. IPv6 Route Information . . . . . . . . . . . . . . . . . . 6 83 2.4. Delegated IPv6 Prefix Pool . . . . . . . . . . . . . . . . 6 84 2.5. Stateful IPv6 address pool . . . . . . . . . . . . . . . . 7 85 3. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 7 86 3.1. Framed-IPv6-Address . . . . . . . . . . . . . . . . . . . 7 87 3.2. DNS-Server-IPv6-Address . . . . . . . . . . . . . . . . . 8 88 3.3. Route-IPv6-Information . . . . . . . . . . . . . . . . . . 9 89 3.4. Delegated-IPv6-Prefix-Pool . . . . . . . . . . . . . . . . 10 90 3.5. Stateful-IPv6-Address-Pool . . . . . . . . . . . . . . . . 10 91 3.6. Table of attributes . . . . . . . . . . . . . . . . . . . 11 92 4. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11 93 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 94 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 95 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12 96 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 97 8.1. Normative References . . . . . . . . . . . . . . . . . . . 12 98 8.2. Informative References . . . . . . . . . . . . . . . . . . 12 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13 101 1. Introduction 103 This document specifies additional RADIUS attributes used to support 104 configuration of DHCPv6 and/or ICMPv6 parameters on a per-user basis. 105 The attributes, which complement those defined in [RFC3162] and 106 [RFC4818], support the following: 108 o Assignment of specific IPv6 addresses to hosts via DHCPv6. 110 o Assignment of an IPv6 DNS server address, via DHCPv6 or ICMPv6 111 [RFC6106]. 113 o Configuration of more specific routes to be announced to the user 114 via the Route Information Option defined in [RFC4191] Section 2.3. 116 o The assignment of a named delegated prefix pool for use with "IPv6 117 Prefix Options for DHCPv6" [RFC3633]. 119 o The assignment of a named stateful address pool for use with 120 DHCPv6 stateful address assignment [RFC3315] 122 2. Deployment Scenarios 124 The extensions in this draft are intended to be applicable across a 125 wide variety of network access scenarios where Radius is involved. 126 One such typical network scenario is illustrated in Figure 1. It is 127 composed of a IP Routing Residential Gateway (RG) or host, a Layer 2 128 Access-Node (e.g. a DSLAM), one or more IP Network Access Servers 129 (NASes), and an AAA server. 131 +-----+ 132 | AAA | 133 | | 134 +--+--+ 135 ^ 136 . 137 .(Radius) 138 . 139 v 140 +------+ +---+---+ 141 +------+ | AN | | NAS | 142 | RG/ +-------| +-----------+----------+ | 143 | host | | | | | 144 +------+ (DSL) +------+ (Ethernet) +-------+ 146 Figure 1 148 In the depicted scenario the NAS may embed a IP addressing protocols 149 (eg a DHCPv6 server) to handle address assignment to RGs/hosts. The 150 RADIUS server authenticates each RG/host and returns to the 151 attributes used for authorization and accounting. These attributes 152 can include the host's IPv6 address to be configured via DHCPv6 as 153 well as the IPv6 address of a DNS server to be advertised to the 154 client. The name of a prefix pool to be used for DHCPv6 Prefix 155 Delegation, or the set of IPv6 routes to be announced to the host can 156 also be attributes provided to the NAS from the RADIUS AAA server 158 The following sub-sections discuss how these attributes are used in 159 more detail. 161 2.1. IPv6 Address Assignment 163 DHCPv6 [RFC3315] provides a mechanism to assign one or more or non- 164 temporary IPv6 addresses to hosts. To provide a DHCPv6 server 165 residing on a NAS with one or more IPv6 addresses to be assigned, 166 this document specifies the Framed-IPv6-Address Attribute. 168 While [RFC3162] permits an IPv6 address to be specified via the 169 combination of the Framed-Interface-Id and Framed-IPv6-Prefix 170 attributes, this separation is more natural for use with IPv6CP than 171 it is for use with DHCPv6, and the use of a single IPv6 address 172 attribute makes for easier processing of accounting records. 174 Since DHCPv6 can be deployed on the same network as ICMPv6 stateless 175 (SLAAC) [RFC4862], it is possible that the NAS will require both 176 stateful and stateless configuration information. Therefore it is 177 possible for the Framed-IPv6-Address, Framed-IPv6-Prefix and Framed- 178 Interface-Id attributes [RFC3162] to be included within the same 179 packet. To avoid ambiguity, the Framed-IPv6-Address attribute is 180 only used for authorization and accounting of DHCPv6-assigned 181 addresses and the Framed-IPv6-Prefix and Framed-Interface-Id 182 attributes are used for authorization and accounting of addresses 183 assigned via SLAAC. 185 2.2. Recursive DNS Servers 187 DHCPv6 provides an option for configuring a host with the IPv6 188 address of a DNS server. The IPv6 address of a DNS server can also 189 be conveyed to the host using ICMPv6 with Router Advertisements, via 190 the experimental [RFC6106] option. To provide the NAS with the IPv6 191 address of a DNS server, this document specifies the DNS-Server-IPv6- 192 Address Attribute. 194 2.3. IPv6 Route Information 196 An IPv6 Route Information option, defined in [RFC4191] is intended to 197 be used to inform a host connected to the NAS that a specific route 198 is reachable via the NAS. This is particularly desirable in cases 199 where the RG or host are multi-homed to different NASes as shown in 200 Figure 1. 202 This document specifies the RADIUS attribute that allows the AAA 203 system to provision the announcement by the NAS of a specific Route 204 Information Option to an accessing host. The NAS may advertise this 205 route using the method defined in [RFC4191], or using other 206 equivalent methods. Any other information, such as preference or 207 life-time values, that is to be present in the actual announcement 208 using a given method is assumed to be determined by the NAS using 209 means not scoped by this document (eg local configuration on the 210 NAS). 212 While the Framed-IPv6-Prefix Attribute defined in [RFC3162] Section 213 2.3 causes the route to be advertised in an RA, it cannot be used to 214 configure more specific routes. While the Framed-IPv6-Route 215 Attribute defined in [RFC3162] Section 2.5 causes the route to be 216 configured on the NAS, and potentially announced via an IGP, 217 depending on the value of Framed-Routing, it does not result in the 218 route being announced in an RA. 220 2.4. Delegated IPv6 Prefix Pool 222 DHCPv6 Prefix Delegation [RFC3633] involves a delegating router 223 selecting a prefix and delegating it on a temporary basis to a 224 requesting router. The delegating router may implement a number of 225 strategies as to how it chooses what prefix is to be delegated to a 226 requesting router, one of them being the use of a local named prefix 227 pool. The Delegated-IPv6-Prefix-Pool Attribute allows the RADIUS 228 server to convey a prefix pool name to a NAS hosting a DHCPv6-PD 229 server and acting as a delegated router. 231 Since DHCPv6 Prefix Delegation can conceivably be used on the same 232 network as SLAAC, it is possible for the Delegated-IPv6-Prefix-Pool 233 and Framed-IPv6-Pool attributes to be included within the same 234 packet. To avoid ambiguity in this scenario, use of the Delegated- 235 IPv6-Prefix-Pool attribute should be restricted to authorization and 236 accounting of prefix pools used in DHCPv6 Prefix Delegation and the 237 Framed-IPv6-Pool attribute should be used for authorization and 238 accounting of prefix pools used in SLAAC. 240 2.5. Stateful IPv6 address pool 242 DHCPv6 [RFC3315] provides a mechanism to assign one or more or non- 243 temporary IPv6 addresses to hosts. Section 2.1 introduces the 244 Framed-IPv6-Address Attribute to be used for providing a DHCPv6 245 server residing on a NAS with one or more IPv6 addresses to be 246 assigned to the clients. An alternative way to achieve a similar 247 result is for the NAS to select the IPv6 address to be assigned from 248 an address pool configured for this purpose on the NAS. This 249 document specifies the DHCPv6-IPv6-Address-Pool attribute to allow 250 the RADIUS server to convey a pool name to be used for such stateful 251 DHCPv6 based addressing, and any subsequent accounting. 253 3. Attributes 255 The fields shown in the diagrams below are transmitted from left to 256 right. 258 3.1. Framed-IPv6-Address 260 This Attribute indicates an IPv6 Address that is assigned to the NAS- 261 facing interface of the RG/host. It MAY be used in Access-Accept 262 packets, and MAY appear multiple times. It MAY be used in an Access- 263 Request packet as a hint by the NAS to the server that it would 264 prefer these IPv6 address(es), but the server is not required to 265 honor the hint. Since it is assumed that the NAS will add a route 266 corresponding to the address, it is not necessary for the server to 267 also send a host Framed-IPv6-Route attribute for the same address. 269 This Attribute can be used by a DHCPv6 process on the NAS to assign a 270 unique IPv6 address to the RG/host. 272 A summary of the Framed-IPv6-Address Attribute format is shown below. 274 0 1 2 3 275 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 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | Type | Length | Address 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 Address (cont) 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 Address (cont) 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 Address (cont) 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 Address (cont.) | 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 Type 290 TBA1 for Framed-IPv6-Address 292 Length 294 18 296 Address 298 The IPv6 address field contains a 128-bit IPv6 address. 300 3.2. DNS-Server-IPv6-Address 302 The DNS-Server-IPv6-Address Attribute contains the IPv6 address of a 303 recursive DNS server. This attribute MAY be included multiple times 304 in Access-Accept packets, when the intention is for a NAS to announce 305 more than one recursive DNS address to an RG/host. The same order of 306 the attributes is expected to be followed in the announcements to the 307 client. 309 The content of this attribute can be inserted in a DHCPv6 option as 310 specified in [RFC3646] or mapped option. 312 A summary of the DNS-Server-IPv6-Address Attribute format is given 313 below. 315 0 1 2 3 316 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 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | Type | Length | Address 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 320 Address (cont) 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 Address (cont) 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 324 Address (cont) 325 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 326 Address (cont.) | 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 329 Type 331 TBA2 for DNS-Server-IPv6-Address 333 Length 335 18 337 Address 339 The 128-bit IPv6 address of a DNS server. 341 3.3. Route-IPv6-Information 343 This Attribute specifies a prefix (and corresponding route) for the 344 user on the NAS, which is to be announced using the Route Information 345 Option defined in "Default Router Preferences and More Specific 346 Routes" [RFC4191] Section 2.3. It is used in the Access-Accept 347 packet and can appear multiple times. The Route-IPv6-Information 348 attribute format is depicted below. 350 0 1 2 3 351 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 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | Type | Length | Reserved | Prefix-Length | 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 355 | | 356 . Prefix (variable) . 357 . . 358 | | 359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 Type 363 TBA3 for Route-IPv6-Information 365 Length 367 Length in bytes. At least 4 and no larger than 20; typically 12 368 or less. 370 Prefix Length 372 8-bit unsigned integer. The number of leading bits in the Prefix 373 that are valid. The value ranges from 0 to 1. The prefix field 374 is 0, 8 or 16 octets depending on Length. 376 Prefix 378 Variable-length field containing an IP prefix. The Prefix Length 379 field contains the number of valid leading bits in the prefix. 381 The bits in the prefix after the prefix length (if any) are 382 reserved and MUST be initialized to zero. 384 3.4. Delegated-IPv6-Prefix-Pool 386 This Attribute contains the name of an assigned pool that SHOULD be 387 used to select an IPv6 delegated prefix for the user. If a NAS does 388 not support multiple prefix pools, the NAS MUST ignore this 389 Attribute. 391 A summary of the Delegated-IPv6-Prefix-Pool Attribute format is shown 392 below. The fields are transmitted from left to right. 393 0 1 2 394 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 396 | Type | Length | String... 397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 399 Type 401 TBA4 for Delegated-IPv6-Prefix-Pool 403 Length 405 Length in bytes. At least 3. 407 String 409 The string field contains the name of an assigned IPv6 prefix pool 410 configured on the NAS. The field is not NULL (hex 00) terminated. 412 3.5. Stateful-IPv6-Address-Pool 414 This Attribute contains the name of an assigned pool that SHOULD be 415 used to select an IPv6 address for the user. If a NAS does not 416 support address pools, the NAS MUST ignore this Attribute. A summary 417 of the Stateful-IPv6-Address-Pool Attribute format is shown below. 418 The fields are transmitted from left to right. 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 (hex 438 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. 445 Request Accept Reject Challenge Accounting # Attribute 446 Request 447 0+ 0+ 0 0 0+ TBA1 Framed-IPv6-Address 448 0+ 0+ 0 0 0+ TBA2 DNS-Server-IPv6-Address 449 0+ 0+ 0 0 0+ TBA3 Route-IPv6-Information 450 0+ 0+ 0 0 0 TBA4 Delegated-IPv6-Prefix-Pool 451 0+ 0+ 0 0 0 TBA5 Stateful-IPv6-Address-Pool 453 4. Diameter Considerations 455 Given that the Attributes defined in this document are allocated from 456 the standard RADIUS type space (see Section 6), no special handling 457 is required by Diameter entities. 459 5. Security Considerations 461 This document describes the use of RADIUS for the purposes of 462 authentication, authorization and accounting in IPv6-enabled 463 networks. In such networks, the RADIUS protocol may run either over 464 IPv4 or over IPv6. Known security vulnerabilities of the RADIUS 465 protocol apply to the attributes defined in this document. Since 466 IPSEC is natively defined for IPv6, it is expected that running 467 RADIUS implementations supporting IPv6 may want to run over IPSEC. 468 Where RADIUS is run over IPSEC and where certificates are used for 469 authentication, it may be desirable to avoid management of RADIUS 470 shared secrets, so as to leverage the improved scalability of public 471 key infrastructure. 473 6. IANA Considerations 475 This document requires the assignment of three new RADIUS Attribute 476 Types in the "Radius Types" registry (currently located at 477 http://www.iana.org/assignments/radius-types for the following 478 attributes: 480 o Framed-IPv6-Address 482 o DNS-Server-IPv6-Address 484 o Route-IPv6-Information 486 o Delegated-IPv6-Prefix-Pool 488 o Stateful-IPv6-Address-Pool 490 7. Acknowledgements 492 The authors would like to thank Bernard Aboba, Roberta Maglione, Leaf 493 Yeh, Alfred Hines, Alan DeKok, Peter Deacon, and Mark Smith for their 494 help and comments in reviewing this document. 496 8. References 498 8.1. Normative References 500 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 501 Requirement Levels", BCP 14, RFC 2119, March 1997. 503 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 504 Address Autoconfiguration", RFC 4862, September 2007. 506 8.2. Informative References 508 [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., 509 and M. Carney, "Dynamic Host Configuration Protocol for 510 IPv6 (DHCPv6)", RFC 3315, July 2003. 512 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 513 Host Configuration Protocol (DHCP) version 6", RFC 3633, 514 December 2003. 516 [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host 517 Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, 518 December 2003. 520 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 521 More-Specific Routes", RFC 4191, November 2005. 523 [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, 524 "IPv6 Router Advertisement Options for DNS Configuration", 525 RFC 6106, November 2010. 527 Authors' Addresses 529 Wojciech Dec (editor) 530 Cisco Systems, Inc. 531 Haarlerbergweg 13-19 532 Amsterdam , NOORD-HOLLAND 1101 CH 533 Netherlands 535 Email: wdec@cisco.com 537 Behcet Sarikaya 538 Huawei USA 539 1700 Alma Dr. Suite 500 540 Plano, TX 541 US 543 Phone: +1 972-509-5599 544 Email: sarikaya@ieee.org 546 Glen Zorn 547 Network Zen 548 1310 East Thomas Street 549 Seattle, WA 550 US 552 Email: gwz@net-zen.net 553 David Miles 554 Alcatel-Lucent 555 L3 / 215 Spring St 556 Melbourne, Victoria 3000, 557 Australia 559 Phone: 560 Fax: 561 Email: David.Miles@alcatel-lucent.com 562 URI: 564 Benoit Lourdelet 565 France