| 1 |
<pre>Internet Engineering Task Force (IETF) H. Singh |
| 2 |
Request for Comments: 6204 W. Beebee |
| 3 |
Category: Informational Cisco Systems, Inc. |
| 4 |
ISSN: 2070-1721 C. Donley |
| 5 |
CableLabs |
| 6 |
B. Stark |
| 7 |
AT&T |
| 8 |
O. Troan, Ed. |
| 9 |
Cisco Systems, Inc. |
| 10 |
April 2011 |
| 11 |
|
| 12 |
|
| 13 |
<span class="h1">Basic Requirements for IPv6 Customer Edge Routers</span> |
| 14 |
|
| 15 |
Abstract |
| 16 |
|
| 17 |
This document specifies requirements for an IPv6 Customer Edge (CE) |
| 18 |
router. Specifically, the current version of this document focuses |
| 19 |
on the basic provisioning of an IPv6 CE router and the provisioning |
| 20 |
of IPv6 hosts attached to it. |
| 21 |
|
| 22 |
Status of This Memo |
| 23 |
|
| 24 |
This document is not an Internet Standards Track specification; it is |
| 25 |
published for informational purposes. |
| 26 |
|
| 27 |
This document is a product of the Internet Engineering Task Force |
| 28 |
(IETF). It represents the consensus of the IETF community. It has |
| 29 |
received public review and has been approved for publication by the |
| 30 |
Internet Engineering Steering Group (IESG). Not all documents |
| 31 |
approved by the IESG are a candidate for any level of Internet |
| 32 |
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 33 |
|
| 34 |
Information about the current status of this document, any errata, |
| 35 |
and how to provide feedback on it may be obtained at |
| 36 |
<a href="http://www.rfc-editor.org/info/rfc6204">http://www.rfc-editor.org/info/rfc6204</a>. |
| 37 |
|
| 38 |
Copyright Notice |
| 39 |
|
| 40 |
Copyright (c) 2011 IETF Trust and the persons identified as the |
| 41 |
document authors. All rights reserved. |
| 42 |
|
| 43 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 44 |
Provisions Relating to IETF Documents |
| 45 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 46 |
publication of this document. Please review these documents |
| 47 |
carefully, as they describe your rights and restrictions with respect |
| 48 |
to this document. Code Components extracted from this document must |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Singh, et al. Informational [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 55 |
|
| 56 |
|
| 57 |
include Simplified BSD License text as described in Section 4.e of |
| 58 |
the Trust Legal Provisions and are provided without warranty as |
| 59 |
described in the Simplified BSD License. |
| 60 |
|
| 61 |
Table of Contents |
| 62 |
|
| 63 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a> |
| 64 |
<a href="#section-1.1">1.1</a>. Requirements Language ......................................<a href="#page-3">3</a> |
| 65 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a> |
| 66 |
<a href="#section-3">3</a>. Architecture ....................................................<a href="#page-4">4</a> |
| 67 |
<a href="#section-3.1">3.1</a>. Current IPv4 End-User Network Architecture .................<a href="#page-4">4</a> |
| 68 |
<a href="#section-3.2">3.2</a>. IPv6 End-User Network Architecture .........................<a href="#page-4">4</a> |
| 69 |
<a href="#section-3.2.1">3.2.1</a>. Local Communication .................................<a href="#page-6">6</a> |
| 70 |
<a href="#section-4">4</a>. Requirements ....................................................<a href="#page-6">6</a> |
| 71 |
<a href="#section-4.1">4.1</a>. General Requirements .......................................<a href="#page-6">6</a> |
| 72 |
<a href="#section-4.2">4.2</a>. WAN-Side Configuration .....................................<a href="#page-7">7</a> |
| 73 |
<a href="#section-4.3">4.3</a>. LAN-Side Configuration ....................................<a href="#page-11">11</a> |
| 74 |
<a href="#section-4.4">4.4</a>. Security Considerations ...................................<a href="#page-13">13</a> |
| 75 |
<a href="#section-5">5</a>. Acknowledgements ...............................................<a href="#page-13">13</a> |
| 76 |
<a href="#section-6">6</a>. Contributors ...................................................<a href="#page-14">14</a> |
| 77 |
<a href="#section-7">7</a>. References .....................................................<a href="#page-14">14</a> |
| 78 |
<a href="#section-7.1">7.1</a>. Normative References ......................................<a href="#page-14">14</a> |
| 79 |
<a href="#section-7.2">7.2</a>. Informative References ....................................<a href="#page-16">16</a> |
| 80 |
|
| 81 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 82 |
|
| 83 |
This document defines basic IPv6 features for a residential or small- |
| 84 |
office router, referred to as an IPv6 CE router. Typically, these |
| 85 |
routers also support IPv4. |
| 86 |
|
| 87 |
Mixed environments of dual-stack hosts and IPv6-only hosts (behind |
| 88 |
the CE router) can be more complex if the IPv6-only devices are using |
| 89 |
a translator to access IPv4 servers [<a href="./rfc6144" title=""Framework for IPv4/IPv6 Translation"">RFC6144</a>]. Support for such |
| 90 |
mixed environments is not in scope of this document. |
| 91 |
|
| 92 |
This document specifies how an IPv6 CE router automatically |
| 93 |
provisions its WAN interface, acquires address space for provisioning |
| 94 |
of its LAN interfaces, and fetches other configuration information |
| 95 |
from the service provider network. Automatic provisioning of more |
| 96 |
complex topology than a single router with multiple LAN interfaces is |
| 97 |
out of scope for this document. |
| 98 |
|
| 99 |
See [<a href="./rfc4779" title=""ISP IPv6 Deployment Scenarios in Broadband Access Networks"">RFC4779</a>] for a discussion of options available for deploying |
| 100 |
IPv6 in service provider access networks. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Singh, et al. Informational [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Language</span> |
| 114 |
|
| 115 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 116 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 117 |
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 118 |
|
| 119 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 120 |
|
| 121 |
End-User Network one or more links attached to the IPv6 CE |
| 122 |
router that connect IPv6 hosts. |
| 123 |
|
| 124 |
IPv6 Customer Edge Router a node intended for home or small-office |
| 125 |
use that forwards IPv6 packets not |
| 126 |
explicitly addressed to itself. The IPv6 |
| 127 |
CE router connects the end-user network to |
| 128 |
a service provider network. |
| 129 |
|
| 130 |
IPv6 Host any device implementing an IPv6 stack |
| 131 |
receiving IPv6 connectivity through the |
| 132 |
IPv6 CE router. |
| 133 |
|
| 134 |
LAN Interface an IPv6 CE router's attachment to a link in |
| 135 |
the end-user network. Examples are |
| 136 |
Ethernets (simple or bridged), 802.11 |
| 137 |
wireless, or other LAN technologies. An |
| 138 |
IPv6 CE router may have one or more |
| 139 |
network-layer LAN interfaces. |
| 140 |
|
| 141 |
Service Provider an entity that provides access to the |
| 142 |
Internet. In this document, a service |
| 143 |
provider specifically offers Internet |
| 144 |
access using IPv6, and may also offer IPv4 |
| 145 |
Internet access. The service provider can |
| 146 |
provide such access over a variety of |
| 147 |
different transport methods such as DSL, |
| 148 |
cable, wireless, and others. |
| 149 |
|
| 150 |
WAN Interface an IPv6 CE router's attachment to a link |
| 151 |
used to provide connectivity to the service |
| 152 |
provider network; example link technologies |
| 153 |
include Ethernets (simple or bridged), PPP |
| 154 |
links, Frame Relay, or ATM networks, as |
| 155 |
well as Internet-layer (or higher-layer) |
| 156 |
"tunnels", such as tunnels over IPv4 or |
| 157 |
IPv6 itself. |
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Singh, et al. Informational [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Architecture</span> |
| 170 |
|
| 171 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Current IPv4 End-User Network Architecture</span> |
| 172 |
|
| 173 |
An end-user network will likely support both IPv4 and IPv6. It is |
| 174 |
not expected that an end-user will change their existing network |
| 175 |
topology with the introduction of IPv6. There are some differences |
| 176 |
in how IPv6 works and is provisioned; these differences have |
| 177 |
implications for the network architecture. A typical IPv4 end-user |
| 178 |
network consists of a "plug and play" router with NAT functionality |
| 179 |
and a single link behind it, connected to the service provider |
| 180 |
network. |
| 181 |
|
| 182 |
A typical IPv4 NAT deployment by default blocks all incoming |
| 183 |
connections. Opening of ports is typically allowed using a Universal |
| 184 |
Plug and Play Internet Gateway Device (UPnP IGD) [<a href="#ref-UPnP-IGD">UPnP-IGD</a>] or some |
| 185 |
other firewall control protocol. |
| 186 |
|
| 187 |
Another consequence of using private address space in the end-user |
| 188 |
network is that it provides stable addressing; i.e., it never changes |
| 189 |
even when you change service providers, and the addresses are always |
| 190 |
there even when the WAN interface is down or the customer edge router |
| 191 |
has not yet been provisioned. |
| 192 |
|
| 193 |
Rewriting addresses on the edge of the network also allows for some |
| 194 |
rudimentary multihoming, even though using NATs for multihoming does |
| 195 |
not preserve connections during a fail-over event [<a href="./rfc4864" title=""Local Network Protection for IPv6"">RFC4864</a>]. |
| 196 |
|
| 197 |
Many existing routers support dynamic routing, and advanced end-users |
| 198 |
can build arbitrary, complex networks using manual configuration of |
| 199 |
address prefixes combined with a dynamic routing protocol. |
| 200 |
|
| 201 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. IPv6 End-User Network Architecture</span> |
| 202 |
|
| 203 |
The end-user network architecture for IPv6 should provide equivalent |
| 204 |
or better capabilities and functionality than the current IPv4 |
| 205 |
architecture. |
| 206 |
|
| 207 |
The end-user network is a stub network. Figure 1 illustrates the |
| 208 |
model topology for the end-user network. |
| 209 |
|
| 210 |
|
| 211 |
|
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Singh, et al. Informational [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 223 |
|
| 224 |
|
| 225 |
+-------+-------+ \ |
| 226 |
| Service | \ |
| 227 |
| Provider | | Service |
| 228 |
| Router | | Provider |
| 229 |
+-------+-------+ | network |
| 230 |
| / |
| 231 |
| Customer / |
| 232 |
| Internet connection / |
| 233 |
| |
| 234 |
+------+--------+ \ |
| 235 |
| IPv6 | \ |
| 236 |
| Customer Edge | \ |
| 237 |
| Router | / |
| 238 |
+---+-------+-+-+ / |
| 239 |
Network A | | Network B | End-User |
| 240 |
---+-------------+----+- --+--+-------------+--- | network(s) |
| 241 |
| | | | \ |
| 242 |
+----+-----+ +-----+----+ +----+-----+ +-----+----+ \ |
| 243 |
|IPv6 Host | |IPv6 Host | | IPv6 Host| |IPv6 Host | / |
| 244 |
| | | | | | | | / |
| 245 |
+----------+ +-----+----+ +----------+ +----------+ / |
| 246 |
|
| 247 |
Figure 1: An Example of a Typical End-User Network |
| 248 |
|
| 249 |
This architecture describes the: |
| 250 |
|
| 251 |
o Basic capabilities of an IPv6 CE router |
| 252 |
|
| 253 |
o Provisioning of the WAN interface connecting to the service |
| 254 |
provider |
| 255 |
|
| 256 |
o Provisioning of the LAN interfaces |
| 257 |
|
| 258 |
For IPv6 multicast traffic, the IPv6 CE router may act as a Multicast |
| 259 |
Listener Discovery (MLD) proxy [<a href="./rfc4605" title=""Internet Group Management Protocol (IGMP) / Multicast Listener Discovery (MLD)-Based Multicast Forwarding ("">RFC4605</a>] and may support a dynamic |
| 260 |
multicast routing protocol. |
| 261 |
|
| 262 |
The IPv6 CE router may be manually configured in an arbitrary |
| 263 |
topology with a dynamic routing protocol. Automatic provisioning and |
| 264 |
configuration are described for a single IPv6 CE router only. |
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Singh, et al. Informational [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 279 |
|
| 280 |
|
| 281 |
<span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Local Communication</span> |
| 282 |
|
| 283 |
Link-local IPv6 addresses are used by hosts communicating on a single |
| 284 |
link. Unique Local IPv6 Unicast Addresses (ULAs) [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>] are used |
| 285 |
by hosts communicating within the end-user network across multiple |
| 286 |
links, but without requiring the application to use a globally |
| 287 |
routable address. The IPv6 CE router defaults to acting as the |
| 288 |
demarcation point between two networks by providing a ULA boundary, a |
| 289 |
multicast zone boundary, and ingress and egress traffic filters. |
| 290 |
|
| 291 |
A dual-stack host is multihomed to IPv4 and IPv6 networks. The IPv4 |
| 292 |
and IPv6 topologies may not be congruent, and different addresses may |
| 293 |
have different reachability, e.g., ULAs. A host stack has to be able |
| 294 |
to quickly fail over and try a different source address and |
| 295 |
destination address pair if communication fails, as outlined in |
| 296 |
[<a href="#ref-HAPPY-EYEBALLS">HAPPY-EYEBALLS</a>]. |
| 297 |
|
| 298 |
At the time of this writing, several host implementations do not |
| 299 |
handle the case where they have an IPv6 address configured and no |
| 300 |
IPv6 connectivity, either because the address itself has a limited |
| 301 |
topological reachability (e.g., ULA) or because the IPv6 CE router is |
| 302 |
not connected to the IPv6 network on its WAN interface. To support |
| 303 |
host implementations that do not handle multihoming in a multi-prefix |
| 304 |
environment [<a href="#ref-MULTIHOMING-WITHOUT-NAT">MULTIHOMING-WITHOUT-NAT</a>], the IPv6 CE router should not, |
| 305 |
as detailed in the requirements below, advertise itself as a default |
| 306 |
router on the LAN interface(s) when it does not have IPv6 |
| 307 |
connectivity on the WAN interface or when it is not provisioned with |
| 308 |
IPv6 addresses. For local IPv6 communication, the mechanisms |
| 309 |
specified in [<a href="./rfc4191" title=""Default Router Preferences and More-Specific Routes"">RFC4191</a>] are used. |
| 310 |
|
| 311 |
ULA addressing is useful where the IPv6 CE router has multiple LAN |
| 312 |
interfaces with hosts that need to communicate with each other. If |
| 313 |
the IPv6 CE router has only a single LAN interface (IPv6 link), then |
| 314 |
link-local addressing can be used instead. |
| 315 |
|
| 316 |
In the event that more than one IPv6 CE router is present on the LAN, |
| 317 |
then coexistence with IPv4 requires all of them to conform to these |
| 318 |
recommendations, especially requirements ULA-5 and L-4 below. |
| 319 |
|
| 320 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Requirements</span> |
| 321 |
|
| 322 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. General Requirements</span> |
| 323 |
|
| 324 |
The IPv6 CE router is responsible for implementing IPv6 routing; that |
| 325 |
is, the IPv6 CE router must look up the IPv6 destination address in |
| 326 |
its routing table to decide to which interface it should send the |
| 327 |
packet. |
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Singh, et al. Informational [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 335 |
|
| 336 |
|
| 337 |
In this role, the IPv6 CE router is responsible for ensuring that |
| 338 |
traffic using its ULA addressing does not go out the WAN interface, |
| 339 |
and does not originate from the WAN interface. |
| 340 |
|
| 341 |
G-1: An IPv6 CE router is an IPv6 node according to the IPv6 Node |
| 342 |
Requirements [<a href="./rfc4294" title=""IPv6 Node Requirements"">RFC4294</a>] specification. |
| 343 |
|
| 344 |
G-2: The IPv6 CE router MUST implement ICMP according to [<a href="./rfc4443" title=""Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"">RFC4443</a>]. |
| 345 |
In particular, point-to-point links MUST be handled as |
| 346 |
described in <a href="./rfc4443#section-3.1">Section 3.1 of [RFC4443]</a>. |
| 347 |
|
| 348 |
G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between |
| 349 |
its LAN interface(s) and its WAN interface until the router has |
| 350 |
successfully completed the IPv6 address acquisition process. |
| 351 |
|
| 352 |
G-4: By default, an IPv6 CE router that has no default router(s) on |
| 353 |
its WAN interface MUST NOT advertise itself as an IPv6 default |
| 354 |
router on its LAN interfaces. That is, the "Router Lifetime" |
| 355 |
field is set to zero in all Router Advertisement messages it |
| 356 |
originates [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 357 |
|
| 358 |
G-5: By default, if the IPv6 CE router is an advertising router and |
| 359 |
loses its IPv6 default router(s) on the WAN interface, it MUST |
| 360 |
explicitly invalidate itself as an IPv6 default router on each |
| 361 |
of its advertising interfaces by immediately transmitting one |
| 362 |
or more Router Advertisement messages with the "Router |
| 363 |
Lifetime" field set to zero [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 364 |
|
| 365 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. WAN-Side Configuration</span> |
| 366 |
|
| 367 |
The IPv6 CE router will need to support connectivity to one or more |
| 368 |
access network architectures. This document describes an IPv6 CE |
| 369 |
router that is not specific to any particular architecture or service |
| 370 |
provider and that supports all commonly used architectures. |
| 371 |
|
| 372 |
IPv6 Neighbor Discovery and DHCPv6 protocols operate over any type of |
| 373 |
IPv6-supported link layer, and there is no need for a link-layer- |
| 374 |
specific configuration protocol for IPv6 network-layer configuration |
| 375 |
options as in, e.g., PPP IP Control Protocol (IPCP) for IPv4. This |
| 376 |
section makes the assumption that the same mechanism will work for |
| 377 |
any link layer, be it Ethernet, the Data Over Cable Service Interface |
| 378 |
Specification (DOCSIS), PPP, or others. |
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Singh, et al. Informational [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 391 |
|
| 392 |
|
| 393 |
WAN-side requirements: |
| 394 |
|
| 395 |
W-1: When the router is attached to the WAN interface link, it MUST |
| 396 |
act as an IPv6 host for the purposes of stateless [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>] or |
| 397 |
stateful [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] interface address assignment. |
| 398 |
|
| 399 |
W-2: The IPv6 CE router MUST generate a link-local address and |
| 400 |
finish Duplicate Address Detection according to [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>] prior |
| 401 |
to sending any Router Solicitations on the interface. The |
| 402 |
source address used in the subsequent Router Solicitation MUST |
| 403 |
be the link-local address on the WAN interface. |
| 404 |
|
| 405 |
W-3: Absent other routing information, the IPv6 CE router MUST use |
| 406 |
Router Discovery as specified in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] to discover a |
| 407 |
default router(s) and install default route(s) in its routing |
| 408 |
table with the discovered router's address as the next hop. |
| 409 |
|
| 410 |
W-4: The router MUST act as a requesting router for the purposes of |
| 411 |
DHCPv6 prefix delegation ([<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>]). |
| 412 |
|
| 413 |
W-5: DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation |
| 414 |
(IA_PD) SHOULD be done as a single DHCPv6 session. |
| 415 |
|
| 416 |
W-6: The IPv6 CE router MUST use a persistent DHCP Unique Identifier |
| 417 |
(DUID) for DHCPv6 messages. The DUID MUST NOT change between |
| 418 |
network interface resets or IPv6 CE router reboots. |
| 419 |
|
| 420 |
Link-layer requirements: |
| 421 |
|
| 422 |
WLL-1: If the WAN interface supports Ethernet encapsulation, then |
| 423 |
the IPv6 CE router MUST support IPv6 over Ethernet [<a href="./rfc2464" title=""Transmission of IPv6 Packets over Ethernet Networks"">RFC2464</a>]. |
| 424 |
|
| 425 |
WLL-2: If the WAN interface supports PPP encapsulation, the IPv6 CE |
| 426 |
router MUST support IPv6 over PPP [<a href="./rfc5072" title=""IP Version 6 over PPP"">RFC5072</a>]. |
| 427 |
|
| 428 |
WLL-3: If the WAN interface supports PPP encapsulation, in a dual- |
| 429 |
stack environment with IPCP and IPV6CP running over one PPP |
| 430 |
logical channel, the Network Control Protocols (NCPs) MUST be |
| 431 |
treated as independent of each other and start and terminate |
| 432 |
independently. |
| 433 |
|
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Singh, et al. Informational [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 447 |
|
| 448 |
|
| 449 |
Address assignment requirements: |
| 450 |
|
| 451 |
WAA-1: The IPv6 CE router MUST support Stateless Address |
| 452 |
Autoconfiguration (SLAAC) [<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>]. |
| 453 |
|
| 454 |
WAA-2: The IPv6 CE router MUST follow the recommendations in <a href="./rfc5942#section-4">Section</a> |
| 455 |
<a href="./rfc5942#section-4">4 of [RFC5942]</a>, and in particular the handling of the L flag |
| 456 |
in the Router Advertisement Prefix Information option. |
| 457 |
|
| 458 |
WAA-3: The IPv6 CE router MUST support DHCPv6 [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] client |
| 459 |
behavior. |
| 460 |
|
| 461 |
WAA-4: The IPv6 CE router MUST be able to support the following |
| 462 |
DHCPv6 options: IA_NA, Reconfigure Accept [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>], and |
| 463 |
DNS_SERVERS [<a href="./rfc3646" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3646</a>]. |
| 464 |
|
| 465 |
WAA-5: The IPv6 CE router SHOULD support the DHCPv6 Simple Network |
| 466 |
Time Protocol (SNTP) option [<a href="./rfc4075" title=""Simple Network Time Protocol (SNTP) Configuration Option for DHCPv6"">RFC4075</a>] and the Information |
| 467 |
Refresh Time option [<a href="./rfc4242" title=""Information Refresh Time Option for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC4242</a>]. |
| 468 |
|
| 469 |
WAA-6: If the IPv6 CE router receives a Router Advertisement message |
| 470 |
(described in [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]) with the M flag set to 1, the IPv6 |
| 471 |
CE router MUST do DHCPv6 address assignment (request an IA_NA |
| 472 |
option). |
| 473 |
|
| 474 |
WAA-7: If the IPv6 CE router is unable to assign address(es) through |
| 475 |
SLAAC, it MAY do DHCPv6 address assignment (request an IA_NA |
| 476 |
option) even if the M flag is set to 0. |
| 477 |
|
| 478 |
WAA-8: If the IPv6 CE router does not acquire global IPv6 |
| 479 |
address(es) from either SLAAC or DHCPv6, then it MUST create |
| 480 |
global IPv6 address(es) from its delegated prefix(es) and |
| 481 |
configure those on one of its internal virtual network |
| 482 |
interfaces. |
| 483 |
|
| 484 |
WAA-9: As a router, the IPv6 CE router MUST follow the weak host |
| 485 |
(Weak ES) model [<a href="./rfc1122" title=""Requirements for Internet Hosts - Communication Layers"">RFC1122</a>]. When originating packets from an |
| 486 |
interface, it will use a source address from another one of |
| 487 |
its interfaces if the outgoing interface does not have an |
| 488 |
address of suitable scope. |
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Singh, et al. Informational [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 503 |
|
| 504 |
|
| 505 |
Prefix delegation requirements: |
| 506 |
|
| 507 |
WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation |
| 508 |
requesting router behavior as specified in [<a href="./rfc3633" title=""IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6"">RFC3633</a>] (IA_PD |
| 509 |
option). |
| 510 |
|
| 511 |
WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating |
| 512 |
router the size of the prefix it requires. If so, it MUST |
| 513 |
ask for a prefix large enough to assign one /64 for each of |
| 514 |
its interfaces, rounded up to the nearest nibble, and MUST be |
| 515 |
configurable to ask for more. |
| 516 |
|
| 517 |
WPD-3: The IPv6 CE router MUST be prepared to accept a delegated |
| 518 |
prefix size different from what is given in the hint. If the |
| 519 |
delegated prefix is too small to address all of its |
| 520 |
interfaces, the IPv6 CE router SHOULD log a system management |
| 521 |
error. |
| 522 |
|
| 523 |
WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix |
| 524 |
delegation, regardless of the M and O flags in a received |
| 525 |
Router Advertisement message. |
| 526 |
|
| 527 |
WPD-5: If the IPv6 CE router initiates DHCPv6 before receiving a |
| 528 |
Router Advertisement, it MUST also request an IA_NA option in |
| 529 |
DHCPv6. |
| 530 |
|
| 531 |
WPD-6: If the delegated prefix(es) are aggregate route(s) of |
| 532 |
multiple, more-specific routes, the IPv6 CE router MUST |
| 533 |
discard packets that match the aggregate route(s), but not |
| 534 |
any of the more-specific routes. In other words, the next |
| 535 |
hop for the aggregate route(s) should be the null |
| 536 |
destination. This is necessary to prevent forwarding loops |
| 537 |
when some addresses covered by the aggregate are not |
| 538 |
reachable [<a href="./rfc4632" title=""Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan"">RFC4632</a>]. |
| 539 |
|
| 540 |
(a) The IPv6 CE router SHOULD send an ICMPv6 Destination |
| 541 |
Unreachable message in accordance with <a href="./rfc4443#section-3.1">Section 3.1 of |
| 542 |
[RFC4443]</a> back to the source of the packet, if the |
| 543 |
packet is to be dropped due to this rule. |
| 544 |
|
| 545 |
WPD-7: If the IPv6 CE router requests both an IA_NA and an IA_PD |
| 546 |
option in DHCPv6, it MUST accept an IA_PD option in DHCPv6 |
| 547 |
Advertise/Reply messages, even if the message does not |
| 548 |
contain any addresses. |
| 549 |
|
| 550 |
WPD-8: By default, an IPv6 CE router MUST NOT initiate any dynamic |
| 551 |
routing protocol on its WAN interface. |
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Singh, et al. Informational [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 559 |
|
| 560 |
|
| 561 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. LAN-Side Configuration</span> |
| 562 |
|
| 563 |
The IPv6 CE router distributes configuration information obtained |
| 564 |
during WAN interface provisioning to IPv6 hosts and assists IPv6 |
| 565 |
hosts in obtaining IPv6 addresses. It also supports connectivity of |
| 566 |
these devices in the absence of any working WAN interface. |
| 567 |
|
| 568 |
An IPv6 CE router is expected to support an IPv6 end-user network and |
| 569 |
IPv6 hosts that exhibit the following characteristics: |
| 570 |
|
| 571 |
1. Link-local addresses may be insufficient for allowing IPv6 |
| 572 |
applications to communicate with each other in the end-user |
| 573 |
network. The IPv6 CE router will need to enable this |
| 574 |
communication by providing globally scoped unicast addresses or |
| 575 |
ULAs [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>], whether or not WAN connectivity exists. |
| 576 |
|
| 577 |
2. IPv6 hosts should be capable of using SLAAC and may be capable of |
| 578 |
using DHCPv6 for acquiring their addresses. |
| 579 |
|
| 580 |
3. IPv6 hosts may use DHCPv6 for other configuration information, |
| 581 |
such as the DNS_SERVERS option for acquiring DNS information. |
| 582 |
|
| 583 |
Unless otherwise specified, the following requirements apply to the |
| 584 |
IPv6 CE router's LAN interfaces only. |
| 585 |
|
| 586 |
ULA requirements: |
| 587 |
|
| 588 |
ULA-1: The IPv6 CE router SHOULD be capable of generating a ULA |
| 589 |
prefix [<a href="./rfc4193" title=""Unique Local IPv6 Unicast Addresses"">RFC4193</a>]. |
| 590 |
|
| 591 |
ULA-2: An IPv6 CE router with a ULA prefix MUST maintain this prefix |
| 592 |
consistently across reboots. |
| 593 |
|
| 594 |
ULA-3: The value of the ULA prefix SHOULD be user-configurable. |
| 595 |
|
| 596 |
ULA-4: By default, the IPv6 CE router MUST act as a site border |
| 597 |
router according to <a href="./rfc4193#section-4.3">Section 4.3 of [RFC4193]</a> and filter |
| 598 |
packets with local IPv6 source or destination addresses |
| 599 |
accordingly. |
| 600 |
|
| 601 |
ULA-5: An IPv6 CE router MUST NOT advertise itself as a default |
| 602 |
router with a Router Lifetime greater than zero whenever all |
| 603 |
of its configured and delegated prefixes are ULA prefixes. |
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Singh, et al. Informational [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 615 |
|
| 616 |
|
| 617 |
LAN requirements: |
| 618 |
|
| 619 |
L-1: The IPv6 CE router MUST support router behavior according to |
| 620 |
Neighbor Discovery for IPv6 [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 621 |
|
| 622 |
L-2: The IPv6 CE router MUST assign a separate /64 from its |
| 623 |
delegated prefix(es) (and ULA prefix if configured to provide |
| 624 |
ULA addressing) for each of its LAN interfaces. |
| 625 |
|
| 626 |
L-3: An IPv6 CE router MUST advertise itself as a router for the |
| 627 |
delegated prefix(es) (and ULA prefix if configured to provide |
| 628 |
ULA addressing) using the "Route Information Option" specified |
| 629 |
in <a href="./rfc4191#section-2.3">Section 2.3 of [RFC4191]</a>. This advertisement is |
| 630 |
independent of having or not having IPv6 connectivity on the |
| 631 |
WAN interface. |
| 632 |
|
| 633 |
L-4: An IPv6 CE router MUST NOT advertise itself as a default |
| 634 |
router with a Router Lifetime [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>] greater than zero if |
| 635 |
it has no prefixes configured or delegated to it. |
| 636 |
|
| 637 |
L-5: The IPv6 CE router MUST make each LAN interface an advertising |
| 638 |
interface according to [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 639 |
|
| 640 |
L-6: In Router Advertisement messages, the Prefix Information |
| 641 |
option's A and L flags MUST be set to 1 by default. |
| 642 |
|
| 643 |
L-7: The A and L flags' settings SHOULD be user-configurable. |
| 644 |
|
| 645 |
L-8: The IPv6 CE router MUST support a DHCPv6 server capable of |
| 646 |
IPv6 address assignment according to [<a href="./rfc3315" title=""Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3315</a>] OR a stateless |
| 647 |
DHCPv6 server according to [<a href="./rfc3736" title=""Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6"">RFC3736</a>] on its LAN interfaces. |
| 648 |
|
| 649 |
L-9: Unless the IPv6 CE router is configured to support the DHCPv6 |
| 650 |
IA_NA option, it SHOULD set the M flag to 0 and the O flag to |
| 651 |
1 in its Router Advertisement messages [<a href="./rfc4861" title=""Neighbor Discovery for IP version 6 (IPv6)"">RFC4861</a>]. |
| 652 |
|
| 653 |
L-10: The IPv6 CE router MUST support providing DNS information in |
| 654 |
the DHCPv6 DNS_SERVERS and DOMAIN_LIST options [<a href="./rfc3646" title=""DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)"">RFC3646</a>]. |
| 655 |
|
| 656 |
L-11: The IPv6 CE router SHOULD support providing DNS information in |
| 657 |
the Router Advertisement Recursive DNS Server (RDNSS) and DNS |
| 658 |
Search List (DNSSL) options as specified in [<a href="./rfc6106" title=""IPv6 Router Advertisement Options for DNS Configuration"">RFC6106</a>]. |
| 659 |
|
| 660 |
L-12: The IPv6 CE router SHOULD make available a subset of DHCPv6 |
| 661 |
options (as listed in <a href="./rfc3736#section-5.3">Section 5.3 of [RFC3736]</a>) received from |
| 662 |
the DHCPv6 client on its WAN interface to its LAN-side DHCPv6 |
| 663 |
server. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Singh, et al. Informational [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 671 |
|
| 672 |
|
| 673 |
L-13: If the delegated prefix changes, i.e., the current prefix is |
| 674 |
replaced with a new prefix without any overlapping time |
| 675 |
period, then the IPv6 CE router MUST immediately advertise the |
| 676 |
old prefix with a Preferred Lifetime of zero and a Valid |
| 677 |
Lifetime of the lower of the current Valid Lifetime and 2 |
| 678 |
hours (which must be decremented in real time) in a Router |
| 679 |
Advertisement message as described in <a href="#section-5.5.3">Section 5.5.3</a>, (e) of |
| 680 |
[<a href="./rfc4862" title=""IPv6 Stateless Address Autoconfiguration"">RFC4862</a>]. |
| 681 |
|
| 682 |
L-14: The IPv6 CE router MUST send an ICMP Destination Unreachable |
| 683 |
message, code 5 (Source address failed ingress/egress policy) |
| 684 |
for packets forwarded to it that use an address from a prefix |
| 685 |
that has been deprecated. |
| 686 |
|
| 687 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a>. Security Considerations</span> |
| 688 |
|
| 689 |
It is considered a best practice to filter obviously malicious |
| 690 |
traffic (e.g., spoofed packets, "Martian" addresses, etc.). Thus, |
| 691 |
the IPv6 CE router ought to support basic stateless egress and |
| 692 |
ingress filters. The CE router is also expected to offer mechanisms |
| 693 |
to filter traffic entering the customer network; however, the method |
| 694 |
by which vendors implement configurable packet filtering is beyond |
| 695 |
the scope of this document. |
| 696 |
|
| 697 |
Security requirements: |
| 698 |
|
| 699 |
S-1: The IPv6 CE router SHOULD support [<a href="./rfc6092" title=""Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service"">RFC6092</a>]. In particular, |
| 700 |
the IPv6 CE router SHOULD support functionality sufficient for |
| 701 |
implementing the set of recommendations in <a href="./rfc6092#section-4">[RFC6092], |
| 702 |
Section 4</a>. This document takes no position on whether such |
| 703 |
functionality is enabled by default or mechanisms by which |
| 704 |
users would configure it. |
| 705 |
|
| 706 |
S-2: The IPv6 CE router MUST support ingress filtering in accordance |
| 707 |
with <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a> [<a href="./rfc2827" title=""Network Ingress Filtering: Defeating Denial of Service Attacks which employ IP Source Address Spoofing"">RFC2827</a>]. |
| 708 |
|
| 709 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span> |
| 710 |
|
| 711 |
Thanks to the following people (in alphabetical order) for their |
| 712 |
guidance and feedback: |
| 713 |
|
| 714 |
Mikael Abrahamsson, Tore Anderson, Merete Asak, Scott Beuker, Mohamed |
| 715 |
Boucadair, Rex Bullinger, Brian Carpenter, Lorenzo Colitti, Remi |
| 716 |
Denis-Courmont, Gert Doering, Alain Durand, Katsunori Fukuoka, Tony |
| 717 |
Hain, Thomas Herbst, Kevin Johns, Erik Kline, Stephen Kramer, Victor |
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Singh, et al. Informational [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 727 |
|
| 728 |
|
| 729 |
Kuarsingh, Francois-Xavier Le Bail, Arifumi Matsumoto, David Miles, |
| 730 |
Shin Miyakawa, Jean-Francois Mule, Michael Newbery, Carlos Pignataro, |
| 731 |
John Pomeroy, Antonio Querubin, Hiroki Sato, Teemu Savolainen, Matt |
| 732 |
Schmitt, David Thaler, Mark Townsley, Bernie Volz, Dan Wing, James |
| 733 |
Woodyatt, and Cor Zwart. |
| 734 |
|
| 735 |
This document is based in part on CableLabs' eRouter specification. |
| 736 |
The authors wish to acknowledge the additional contributors from the |
| 737 |
eRouter team: |
| 738 |
|
| 739 |
Ben Bekele, Amol Bhagwat, Ralph Brown, Eduardo Cardona, Margo Dolas, |
| 740 |
Toerless Eckert, Doc Evans, Roger Fish, Michelle Kuska, Diego |
| 741 |
Mazzola, John McQueen, Harsh Parandekar, Michael Patrick, Saifur |
| 742 |
Rahman, Lakshmi Raman, Ryan Ross, Ron da Silva, Madhu Sudan, Dan |
| 743 |
Torbet, and Greg White. |
| 744 |
|
| 745 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Contributors</span> |
| 746 |
|
| 747 |
The following people have participated as co-authors or provided |
| 748 |
substantial contributions to this document: Ralph Droms, Kirk |
| 749 |
Erichsen, Fred Baker, Jason Weil, Lee Howard, Jean-Francois Tremblay, |
| 750 |
Yiu Lee, John Jason Brzozowski, and Heather Kirksey. |
| 751 |
|
| 752 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 753 |
|
| 754 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 755 |
|
| 756 |
[<a id="ref-RFC1122">RFC1122</a>] Braden, R., Ed., "Requirements for Internet Hosts - |
| 757 |
Communication Layers", STD 3, <a href="./rfc1122">RFC 1122</a>, October 1989. |
| 758 |
|
| 759 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 760 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 761 |
|
| 762 |
[<a id="ref-RFC2464">RFC2464</a>] Crawford, M., "Transmission of IPv6 Packets over Ethernet |
| 763 |
Networks", <a href="./rfc2464">RFC 2464</a>, December 1998. |
| 764 |
|
| 765 |
[<a id="ref-RFC2827">RFC2827</a>] Ferguson, P. and D. Senie, "Network Ingress Filtering: |
| 766 |
Defeating Denial of Service Attacks which employ IP Source |
| 767 |
Address Spoofing", <a href="https://www.rfc-editor.org/bcp/bcp38">BCP 38</a>, <a href="./rfc2827">RFC 2827</a>, May 2000. |
| 768 |
|
| 769 |
[<a id="ref-RFC3315">RFC3315</a>] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, |
| 770 |
C., and M. Carney, "Dynamic Host Configuration Protocol |
| 771 |
for IPv6 (DHCPv6)", <a href="./rfc3315">RFC 3315</a>, July 2003. |
| 772 |
|
| 773 |
[<a id="ref-RFC3633">RFC3633</a>] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic |
| 774 |
Host Configuration Protocol (DHCP) version 6", <a href="./rfc3633">RFC 3633</a>, |
| 775 |
December 2003. |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Singh, et al. Informational [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 783 |
|
| 784 |
|
| 785 |
[<a id="ref-RFC3646">RFC3646</a>] Droms, R., Ed., "DNS Configuration options for Dynamic |
| 786 |
Host Configuration Protocol for IPv6 (DHCPv6)", <a href="./rfc3646">RFC 3646</a>, |
| 787 |
December 2003. |
| 788 |
|
| 789 |
[<a id="ref-RFC3736">RFC3736</a>] Droms, R., "Stateless Dynamic Host Configuration Protocol |
| 790 |
(DHCP) Service for IPv6", <a href="./rfc3736">RFC 3736</a>, April 2004. |
| 791 |
|
| 792 |
[<a id="ref-RFC4075">RFC4075</a>] Kalusivalingam, V., "Simple Network Time Protocol (SNTP) |
| 793 |
Configuration Option for DHCPv6", <a href="./rfc4075">RFC 4075</a>, May 2005. |
| 794 |
|
| 795 |
[<a id="ref-RFC4191">RFC4191</a>] Draves, R. and D. Thaler, "Default Router Preferences and |
| 796 |
More-Specific Routes", <a href="./rfc4191">RFC 4191</a>, November 2005. |
| 797 |
|
| 798 |
[<a id="ref-RFC4193">RFC4193</a>] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast |
| 799 |
Addresses", <a href="./rfc4193">RFC 4193</a>, October 2005. |
| 800 |
|
| 801 |
[<a id="ref-RFC4242">RFC4242</a>] Venaas, S., Chown, T., and B. Volz, "Information Refresh |
| 802 |
Time Option for Dynamic Host Configuration Protocol for |
| 803 |
IPv6 (DHCPv6)", <a href="./rfc4242">RFC 4242</a>, November 2005. |
| 804 |
|
| 805 |
[<a id="ref-RFC4294">RFC4294</a>] Loughney, J., Ed., "IPv6 Node Requirements", <a href="./rfc4294">RFC 4294</a>, |
| 806 |
April 2006. |
| 807 |
|
| 808 |
[<a id="ref-RFC4443">RFC4443</a>] Conta, A., Deering, S., and M. Gupta, Ed., "Internet |
| 809 |
Control Message Protocol (ICMPv6) for the Internet |
| 810 |
Protocol Version 6 (IPv6) Specification", <a href="./rfc4443">RFC 4443</a>, |
| 811 |
March 2006. |
| 812 |
|
| 813 |
[<a id="ref-RFC4605">RFC4605</a>] Fenner, B., He, H., Haberman, B., and H. Sandick, |
| 814 |
"Internet Group Management Protocol (IGMP) / Multicast |
| 815 |
Listener Discovery (MLD)-Based Multicast Forwarding |
| 816 |
("IGMP/MLD Proxying")", <a href="./rfc4605">RFC 4605</a>, August 2006. |
| 817 |
|
| 818 |
[<a id="ref-RFC4632">RFC4632</a>] Fuller, V. and T. Li, "Classless Inter-domain Routing |
| 819 |
(CIDR): The Internet Address Assignment and Aggregation |
| 820 |
Plan", <a href="https://www.rfc-editor.org/bcp/bcp122">BCP 122</a>, <a href="./rfc4632">RFC 4632</a>, August 2006. |
| 821 |
|
| 822 |
[<a id="ref-RFC4779">RFC4779</a>] Asadullah, S., Ahmed, A., Popoviciu, C., Savola, P., and |
| 823 |
J. Palet, "ISP IPv6 Deployment Scenarios in Broadband |
| 824 |
Access Networks", <a href="./rfc4779">RFC 4779</a>, January 2007. |
| 825 |
|
| 826 |
[<a id="ref-RFC4861">RFC4861</a>] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, |
| 827 |
"Neighbor Discovery for IP version 6 (IPv6)", <a href="./rfc4861">RFC 4861</a>, |
| 828 |
September 2007. |
| 829 |
|
| 830 |
[<a id="ref-RFC4862">RFC4862</a>] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless |
| 831 |
Address Autoconfiguration", <a href="./rfc4862">RFC 4862</a>, September 2007. |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Singh, et al. Informational [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 839 |
|
| 840 |
|
| 841 |
[<a id="ref-RFC4864">RFC4864</a>] Van de Velde, G., Hain, T., Droms, R., Carpenter, B., and |
| 842 |
E. Klein, "Local Network Protection for IPv6", <a href="./rfc4864">RFC 4864</a>, |
| 843 |
May 2007. |
| 844 |
|
| 845 |
[<a id="ref-RFC5072">RFC5072</a>] Varada, S., Ed., Haskins, D., and E. Allen, "IP Version 6 |
| 846 |
over PPP", <a href="./rfc5072">RFC 5072</a>, September 2007. |
| 847 |
|
| 848 |
[<a id="ref-RFC5942">RFC5942</a>] Singh, H., Beebee, W., and E. Nordmark, "IPv6 Subnet |
| 849 |
Model: The Relationship between Links and Subnet |
| 850 |
Prefixes", <a href="./rfc5942">RFC 5942</a>, July 2010. |
| 851 |
|
| 852 |
[<a id="ref-RFC6092">RFC6092</a>] Woodyatt, J., Ed., "Recommended Simple Security |
| 853 |
Capabilities in Customer Premises Equipment (CPE) for |
| 854 |
Providing Residential IPv6 Internet Service", <a href="./rfc6092">RFC 6092</a>, |
| 855 |
January 2011. |
| 856 |
|
| 857 |
[<a id="ref-RFC6106">RFC6106</a>] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, |
| 858 |
"IPv6 Router Advertisement Options for DNS Configuration", |
| 859 |
<a href="./rfc6106">RFC 6106</a>, November 2010. |
| 860 |
|
| 861 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 862 |
|
| 863 |
[<a id="ref-HAPPY-EYEBALLS">HAPPY-EYEBALLS</a>] |
| 864 |
Wing, D. and A. Yourtchenko, "Happy Eyeballs: Trending |
| 865 |
Towards Success with Dual-Stack Hosts", Work in Progress, |
| 866 |
March 2011. |
| 867 |
|
| 868 |
[<a id="ref-MULTIHOMING-WITHOUT-NAT">MULTIHOMING-WITHOUT-NAT</a>] |
| 869 |
Troan, O., Ed., Miles, D., Matsushima, S., Okimoto, T., |
| 870 |
and D. Wing, "IPv6 Multihoming without Network Address |
| 871 |
Translation", Work in Progress, March 2011. |
| 872 |
|
| 873 |
[<a id="ref-RFC6144">RFC6144</a>] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for |
| 874 |
IPv4/IPv6 Translation", <a href="./rfc6144">RFC 6144</a>, April 2011. |
| 875 |
|
| 876 |
[<a id="ref-UPnP-IGD">UPnP-IGD</a>] |
| 877 |
UPnP Forum, "Universal Plug and Play (UPnP) Internet |
| 878 |
Gateway Device (IGD)", November 2001, |
| 879 |
<<a href="http://www.upnp.org/">http://www.upnp.org/</a>>. |
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Singh, et al. Informational [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc6204">RFC 6204</a> IPv6 CE Router Requirements April 2011</span> |
| 895 |
|
| 896 |
|
| 897 |
Authors' Addresses |
| 898 |
|
| 899 |
Hemant Singh |
| 900 |
Cisco Systems, Inc. |
| 901 |
1414 Massachusetts Ave. |
| 902 |
Boxborough, MA 01719 |
| 903 |
USA |
| 904 |
Phone: +1 978 936 1622 |
| 905 |
EMail: [email protected] |
| 906 |
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a> |
| 907 |
|
| 908 |
|
| 909 |
Wes Beebee |
| 910 |
Cisco Systems, Inc. |
| 911 |
1414 Massachusetts Ave. |
| 912 |
Boxborough, MA 01719 |
| 913 |
USA |
| 914 |
Phone: +1 978 936 2030 |
| 915 |
EMail: [email protected] |
| 916 |
URI: <a href="http://www.cisco.com/">http://www.cisco.com/</a> |
| 917 |
|
| 918 |
|
| 919 |
Chris Donley |
| 920 |
CableLabs |
| 921 |
858 Coal Creek Circle |
| 922 |
Louisville, CO 80027 |
| 923 |
USA |
| 924 |
EMail: [email protected] |
| 925 |
|
| 926 |
|
| 927 |
Barbara Stark |
| 928 |
AT&T |
| 929 |
725 W Peachtree St. |
| 930 |
Atlanta, GA 30308 |
| 931 |
USA |
| 932 |
EMail: [email protected] |
| 933 |
|
| 934 |
|
| 935 |
Ole Troan (editor) |
| 936 |
Cisco Systems, Inc. |
| 937 |
Telemarksvingen 20 |
| 938 |
N-0655 OSLO, |
| 939 |
Norway |
| 940 |
EMail: [email protected] |
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
Singh, et al. Informational [Page 17] |
| 949 |
</pre> |