One document matched: draft-ietf-v6ops-ipv6-cpe-router-05.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC4861 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4861.xml">
<!ENTITY RFC4862 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4862.xml">
<!ENTITY RFC3315 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3315.xml">
<!ENTITY RFC3633 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3633.xml">
<!ENTITY RFC3646 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3646.xml">
<!ENTITY RFC4075 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4075.xml">
<!ENTITY RFC4193 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4193.xml">
<!ENTITY RFC4605 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4605.xml">
<!ENTITY RFC2827 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.2827.xml">
<!ENTITY RFC2464 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.2464.xml">
<!ENTITY RFC5072 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.5072.xml">
<!ENTITY I-D.ietf-v6ops-cpe-simple-security SYSTEM
"http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-v6ops-cpe-simple-security.xml">
<!ENTITY I-D.ietf-6man-ipv6-subnet-model SYSTEM
"http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-6man-ipv6-subnet-model.xml">
<!ENTITY RFC3736 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.3736.xml">
<!ENTITY RFC4779 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4779.xml">
<!ENTITY RFC4864 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4864.xml">
<!ENTITY RFC4242 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4242.xml">
<!ENTITY RFC4632 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4632.xml">
<!ENTITY RFC4443 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.4443.xml">
<!ENTITY RFC1122 SYSTEM
"http://xml.resource.org/public/rfc/bibxml/reference.RFC.1122.xml">
<!ENTITY I-D.ietf-behave-v6v4-framework SYSTEM
"http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-behave-v6v4-framework.xml">
<!ENTITY I-D.ietf-6man-node-req-bis SYSTEM
"http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-6man-node-req-bis.xml">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
(Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space
(using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-ietf-v6ops-ipv6-cpe-router-05" ipr="trust200902">
<!-- category values: std, bcp, info, exp, and historic ipr values:
full3667, noModification3667, noDerivatives3667 you can add the
attributes updates="NNNN" and obsoletes="NNNN" they will automatically be
output with "(if approved)" -->
<!-- ***** FRONT MATTER ***** -->
<front>
<!-- The abbreviated title is used in the page header - it is only
necessary if the full title is longer than 39 characters -->
<title abbrev="IPv6 CE router requirements">Basic Requirements for IPv6
Customer Edge Routers</title>
<!-- add 'role="editor"' below for the editors if appropriate -->
<!-- Another author who claims to be an editor -->
<author initials="H." surname="Singh" fullname="Hemant Singh">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>1414 Massachusetts Ave.</street>
<city>Boxborough</city> <region>MA</region>
<code>01719</code>
<country>USA</country>
</postal>
<phone>+1 978 936 1622</phone>
<email>shemant@cisco.com</email>
<uri>http://www.cisco.com/</uri>
</address>
</author>
<author initials="W." surname="Beebee" fullname="Wes Beebee">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>1414 Massachusetts Ave.</street>
<city>Boxborough</city> <region>MA</region>
<code>01719</code>
<country>USA</country>
</postal>
<phone>+1 978 936 2030</phone>
<email>wbeebee@cisco.com</email>
<uri>http://www.cisco.com/</uri>
</address>
</author>
<author initials='C.D.' surname="Donley" fullname='Chris Donley'>
<organization>CableLabs </organization>
<address>
<postal>
<street>858 Coal Creek Circle</street>
<city>Louisville</city> <region>CO</region>
<code>80027</code>
<country>USA</country>
</postal>
<email>c.donley@cablelabs.com</email>
</address>
</author>
<author initials='B.' surname="Stark" fullname='Barbara Stark'>
<organization>AT&T</organization>
<address>
<postal>
<street>725 W Peachtree St</street>
<city>Atlanta</city> <region>GA</region>
<code>30308</code>
<country>USA</country>
</postal>
<email>barbara.stark@att.com</email>
</address>
</author>
<author fullname="Ole Troan" initials="O." role="editor" surname="Troan">
<organization>Cisco Systems, Inc.</organization>
<address>
<postal>
<street>Veversmauet 8</street>
<code></code>
<city>N-5017 BERGEN</city>
<region></region>
<country>Norway</country>
</postal>
<email>ot@cisco.com</email>
<!-- uri and facsimile elements may also be added -->
</address>
</author>
<date month="May" year="2010" />
<!-- If the month and year are both specified and are the current ones,
xml2rfc will fill in the current day for you. If only the current
year is specified, xml2rfc will fill in the current day and month for
you. If the year is not the current one, it is necessary to specify
at least a month (xml2rfc assumes day="1" if not specified for the
purpose of calculating the expiry date). With drafts it is normally
sufficient to specify just the year. -->
<!-- Meta-data Declarations -->
<area>General</area>
<workgroup>Internet Engineering Task Force</workgroup>
<!-- WG name at the upperleft corner of the doc, IETF is fine for
individual submissions. If this element is not present, the default
is "Network Working Group", which is used by the RFC Editor as a nod
to the history of the IETF. -->
<keyword></keyword>
<!-- Keywords will be incorporated into HTML output files in a meta tag
but they have no effect on text or nroff output. If you submit your
draft to the RFC Editor, the keywords will be used for the search
engine. -->
<abstract>
<t>This document specifies requirements for an IPv6 Customer
Edge (CE) router. Specifically, the current version of this
document focuses on the basic provisioning of an IPv6 CE router
and the provisioning of IPv6 hosts attached to it.</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>This document defines basic IPv6 features for a residential
or small office router referred to as an IPv6 CE
router. Typically these routers also support IPv4.</t>
<t>Mixed environments of dual-stack hosts and IPv6-only hosts
(behind the CE router) can be more complex if the IPv6-only
devices are using a translator to access IPv4 servers <xref
target="I-D.ietf-behave-v6v4-framework"></xref>. Support for
such mixed environments is not in scope of this document.</t>
<t>This document specifies how an IPv6 CE router automatically
provisions its WAN interface, acquires address space for
provisioning of its LAN interfaces and fetches other
configuration information from the service provider
network. Automatic provisioning of more complex topology than a
single router with multiple LAN interfaces is out of scope for
this document.</t>
<t>See <xref target="RFC4779"></xref> for a discussion of options
available for deploying IPv6 in Service Provider access networks.</t>
<section title="Requirements Language">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <xref
target="RFC2119">RFC 2119</xref>.</t>
</section>
</section>
<section title="Terminology">
<t><list hangIndent="26" style="hanging">
<t hangText="End-user Network">one or more links attached to the
IPv6 CE router that connect IPv6 hosts.</t>
<t hangText="IPv6 Customer Edge router">a node intended for home or
small office use which forwards IPv6 packets not explicitly
addressed to itself. The IPv6 CE router connects the end-user
network to a service provider network.</t>
<t hangText="IPv6 host">any device implementing an IPv6 stack
receiving IPv6 connectivity through the IPv6 CE router</t>
<t hangText="LAN interface">an IPv6 CE router's attachment
to a link in the end-user network. Examples are Ethernets
(simple or bridged), 802.11 wireless or other LAN
technologies. An IPv6 CE router may have one or more network
layer LAN Interfaces.</t>
<t hangText="Service Provider">an entity that provides
access to the Internet. In this document, a Service Provider
specifically offers Internet access using IPv6, and may also
offer IPv4 Internet access. The Service Provider can provide
such access over a variety of different transport methods
such as DSL, cable, wireless, and others.</t>
<t hangText="WAN interface">an IPv6 CE router's attachment to a link
used to provide connectivity to the Service Provider network;
example link technologies include Ethernets (simple or bridged), PPP
links, Frame Relay, or ATM networks as well as Internet-layer
(or higher-layer) "tunnels", such as tunnels over IPv4 or IPv6
itself.</t>
</list></t>
</section>
<section title="Architecture">
<section title="Current IPv4 End-user Network Architecture">
<t>An end-user network will likely support both IPv4 and
IPv6. It is not expected that an end-user will change their
existing network topology with the introduction of IPv6. There
are some differences in how IPv6 works and is provisioned
which has implications for the network architecture. A typical
IPv4 end-user network consist of a "plug and play" router with
NAT functionality and a single link behind it, connected to
the Service Provider network.</t>
<t>A typical IPv4 NAT deployment by default blocks all
incoming connections. Opening of ports is typically allowed
using UPnP IGD <xref target="UPnP-IGD"></xref> or some other
firewall control protocol.</t>
<t>Another consequence of using private address space in the
end-user network is that it provides stable addressing,
i.e. it never changes even when you change Service Providers,
and the addresses are always there even when the WAN interface
is down or the customer edge router has not yet been
provisioned.</t>
<t>Rewriting addresses on the edge of the network also allows for some
rudimentary multi-homing; even though using NATs for multi-homing does
not preserve connections during
a fail-over event <xref target="RFC4864"></xref>.</t>
<t>Many existing routers support dynamic routing, and advanced end
users can build arbitrary, complex networks using manual configuration
of address prefixes combined with a dynamic routing protocol.</t>
</section>
<section title="IPv6 End-user Network Architecture">
<t>The end-user network architecture for IPv6 should provide
equivalent or better capabilities and functionality than the
current IPv4 architecture.</t>
<t>The end-user network is a stub network. Figure 1 illustrates the
model topology for the end-user network.</t>
<figure align="center" anchor="sp_architecture">
<preamble>An example of a typical end-user network.</preamble>
<artwork align="left"><![CDATA[
+-------+-------+ \
| Service | \
| Provider | | Service
| Router | | Provider
+-------+-------+ | network
| /
| Customer /
| Internet connection /
|
+------+--------+ \
| IPv6 | \
| Customer Edge | \
| Router | /
+---+-------+-+-+ /
Network A | | Network B | End-User
---+-------------+----+- --+--+-------------+--- |network(s)
| | | | \
+----+-----+ +-----+----+ +----+-----+ +-----+----+ \
|IPv6 Host | |IPv6 Host | | IPv6 Host| |IPv6 Host | /
| | | | | | | | /
+----------+ +-----+----+ +----------+ +----------+/
]]></artwork>
<postamble></postamble>
</figure>
<t>This architecture describes the:<list style="symbols">
<t>Basic capabilities of an IPv6 CE router</t>
<t>Provisioning of the WAN interface connecting to the
Service Provider</t>
<t>Provisioning of the LAN interfaces</t>
</list></t>
<t>Unique Local IPv6 Unicast Addresses (ULA) <xref
target="RFC4193"></xref> are used by hosts communicating within
the End-user Network; this is functionally similar to RFC1918
addresses used within an IPv4 End-user Network. The IPv6 CE
router defaults to acting as the demarcation point between two
networks by providing a ULA boundary, a multicast zone boundary
and ingress and egress traffic filters.</t>
<t>For IPv6 multicast traffic the IPv6 CE router may act as an
MLD proxy <xref target="RFC4605"></xref> and may support a
dynamic multicast routing protocol.</t>
<t>The IPv6 CE router may be manually configured in an arbitrary
topology with a dynamic routing protocol. Automatic provisioning
and configuration is described for a single IPv6 CE router
only.</t>
</section>
</section>
<section title="Requirements">
<section title="General Requirements">
<t>The IPv6 CE router is responsible for implementing IPv6 routing;
that is, the IPv6 CE router must look up the IPv6 Destination address
in its routing table to decide to which interface it should send the
packet.</t>
<t>In this role, the IPv6 CE router is responsible for ensuring that
traffic using its ULA addressing does not go out the WAN interface,
and does not originate from the WAN interface.</t>
<t><list style='format G-%d:'>
<t>An IPv6 CE router is an IPv6 node according to the <xref
target="I-D.ietf-6man-node-req-bis"> IPv6 Node
Requirements</xref> specification.</t>
<t>The IPv6 CE router MUST implement ICMP according to <xref
target="RFC4443"></xref>. In particular point to point links
MUST be handled as described in section 3.1 of <xref
target="RFC4443"></xref>.</t>
<t>The IPv6 CE router MUST NOT forward any IPv6 traffic
between its LAN Interface(s) and its WAN Interface until the
router has successfully completed the IPv6 address
acquisition process.</t>
</list></t>
</section>
<section title="WAN Side Configuration">
<t>The IPv6 CE router will need to support connectivity to one
or more access network architectures. This document describes
an IPv6 CE router that is not specific to any particular
architecture or Service Provider, and supports all commonly
used architectures.</t>
<t>IPv6 Neighbor Discovery and DHCPv6 protocols operate over
any type of IPv6 supported link-layer and there is no need for
a link-layer specific configuration protocol for IPv6 network
layer configuration options as in e.g. PPP IPCP for IPv4. This
section makes the assumption that the same mechanism will work
for any link-layer, be it Ethernet, DOCSIS, PPP or others.</t>
<t>WAN side requirements:
<list style='format W-%d:'>
<t>When the router is attached to the WAN interface link it
MUST act as an IPv6 host for the purposes of stateless or
stateful interface address assignment (<xref
target="RFC4862"></xref>/<xref
target="RFC3315"></xref>).</t>
<t>The IPv6 CE router MUST generate a link-local address and
finish Duplicate Address Detection according to <xref
target="RFC4862"></xref> prior to sending any Router
Solicitations on the interface. The source address used in
the subsequent Router Solicitation MUST be the link-local
address on the WAN interface.</t>
<t>Absent of other routing information the IPv6 CE router
MUST use Router Discovery as specified in <xref
target="RFC4861"></xref> to discover a default router(s) and
install default route(s) in its routing table with the
discovered router's address as the next-hop.</t>
<t>The router MUST act as a requesting router for the
purposes of DHCPv6 prefix delegation (<xref
target="RFC3633"></xref>).</t>
<t>DHCPv6 address assignment (IA_NA) and DHCPv6 prefix
delegation (IA_PD) SHOULD be done as a single DHCPv6
session.</t>
</list></t>
<t>Link-layer requirements:
<list style='format WLL-%d:'>
<t>If the WAN interface supports Ethernet encapsulation,
then the IPv6 CE router MUST support IPv6 over Ethernet
<xref target="RFC2464"></xref>.</t>
<t>If the WAN interface supports PPP encapsulation the IPv6
CE router MUST support IPv6 over PPP <xref
target="RFC5072"></xref>.</t>
<t>If the WAN interface supports PPP encapsulation, in a
dual-stack environment with IPCP and IPV6CP running over one
PPP logical channel, the NCPs MUST be treated as independent
of each other and start and terminate independently.</t>
</list></t>
<t>Address assignment requirements:<list style='format WAA-%d:'>
<t>The IPv6 CE router MUST support SLAAC <xref
target="RFC4862"></xref>.</t>
<t>The IPv6 CE router MUST follow the recommendation in
<xref target="I-D.ietf-6man-ipv6-subnet-model"></xref> and
in particular the handling of the L-flag in the Router
Advertisement Prefix Information Option.</t>
<t>The IPv6 CE router MUST support DHCPv6 <xref
target="RFC3315"></xref> client behavior.</t>
<t>The IPv6 CE router MUST be able to support the
following DHCPv6 options: IA_NA, Reconfigure Accept <xref
target="RFC3315"></xref>, DNS_SERVERS <xref
target="RFC3646"></xref>.</t>
<t>The IPv6 CE router SHOULD support the DHCPv6 SNTP
option <xref target="RFC4075"></xref> and the Information
Refresh Time Option <xref target="RFC4242"></xref>.</t>
<t>If the IPv6 CE router receives an RA message (described
in <xref target="RFC4861"></xref>) with the M-flag set to
1, the IPv6 CE router MUST do DHCPv6 address assignment
(request an IA_NA option).</t>
<t>If the IPv6 CE router is unable to assign address(es)
through SLAAC it MAY do DHCPv6 address assignment (request
an IA_NA) even if the M-flag is set to 0.</t>
<t>If the IPv6 CE router does not acquire global IPv6
address(es) from either SLAAC or DHCPv6, then it MUST
create global IPv6 address(es) from its delegated
prefix(es) and configure those on one of its internal
virtual network interfaces.</t>
<t>As a router the IPv6 CE router MUST follow the weak
host model <xref target="RFC1122"></xref>. When
originating packets out an interface it will use a source
address from another of its interfaces if the outgoing
interface does not have an address of suitable scope.</t>
</list></t>
<t>Prefix Delegation requirements:
<list style='format WPD-%d:'>
<t>The IPv6 CE router MUST support DHCPv6 prefix delegation
requesting router behavior as specified in <xref
target="RFC3633"></xref> (IA_PD option).</t>
<t>The IPv6 CE router MAY indicate as a hint to the
delegating router the size of the prefix it requires. If so,
it MUST ask for a prefix large enough to assign one /64 for
each of its interfaces rounded up to the nearest nibble and
MUST be configurable to ask for more.</t>
<t>The IPv6 CE router MUST be prepared to accept a delegated
prefix size different from what is given in the hint. If the
delegated prefix is too small to address all of its
interfaces, the IPv6 CE router SHOULD log a system
management error.</t>
<t>The IPv6 CE router MUST always initiate DHCPv6 prefix
delegation, regardless of the M and O-flags in a received
Router Advertisement message.</t>
<t>If the IPv6 CE Router initiates DHCPv6 before receiving a
Router Advertisement it MUST also request an IA_NA option in
DHCPv6.</t>
<t>If the delegated prefix(es) are aggregate route(s) of
multiple, more-specific routes, the IPv6 CE router MUST
discard packets that match the aggregate route(s), but not
any of the more-specific routes. In other words, the
next-hop for the aggregate route(s) should be the null
destination. This is necessary to prevent forwarding loops
when some addresses covered by the aggregate are not
reachable <xref target="RFC4632"></xref>.
<list style="format (%c)">
<t>The IPv6 CE router SHOULD send an ICMPv6 Destination
Unreachable according to <xref target="RFC4443">section
3.1</xref> back to the source of the packet, if the packet
is to be dropped due to this rule.</t>
</list></t>
<t>If the IPv6 CE router requests both an IA_NA and an IA_PD
in DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply
messages, even if the message does not contain any addresses
(IA_NA options with status code equal to NoAddrsAvail).</t>
<t>By default an IPv6 CE router MUST NOT initiate any
dynamic routing protocol on its WAN interface.</t>
</list></t>
</section>
<section title="LAN Side Configuration">
<t>The IPv6 CE router distributes configuration information obtained
during WAN interface provisioning to IPv6 hosts and assists IPv6 hosts
in obtaining IPv6 addresses. It also supports connectivity of these
devices in the absence of any working WAN interface.</t>
<t>An IPv6 CE router is expected to support an IPv6 end-user
network and IPv6 hosts that exhibit the following
characteristics:</t>
<t><list style="numbers">
<t>Link-local addresses are insufficient for allowing IPv6
applications to communicate with each other in the
end-user network. The IPv6 CE router will need to enable
this communication by providing globally-scoped unicast
addresses or ULAs <xref target="RFC4193"></xref> whether
or not WAN connectivity exists.</t>
<t>IPv6 hosts should be capable of using SLAAC and may be
capable of using DHCPv6 for acquiring their addresses.</t>
<t>IPv6 hosts may use DHCPv6 for other configuration
information, such as the DNS_SERVERS option for acquiring
DNS information.</t>
</list></t>
<t>Unless otherwise specified, the following requirements
apply to the IPv6 CE router's LAN interfaces only.</t>
<t>Requirements:<list style='format L-%d:'>
<t>The IPv6 CE router MUST support ULA addressing <xref
target="RFC4193"></xref>.</t>
<t>The IPv6 CE router MUST have a ULA prefix that it
maintains consistently across reboots.</t>
<t>The value of the ULA prefix SHOULD be user
configurable.</t>
<t>By default the IPv6 CE router MUST act as a site border
router according to section 4.3 of <xref
target="RFC4193"></xref> and filter packets with Local IPv6
source or destination addresses accordingly.</t>
<t>The IPv6 CE router MUST support router behavior according
to Neighbor Discovery for IPv6 <xref
target="RFC4861"></xref>.</t>
<t>The IPv6 CE router MUST assign a separate /64 from its
delegated prefix(es) (and ULA prefix if configured to
provide ULA addressing) for each of its LAN interfaces.</t>
<t>The IPv6 CE router MUST make each LAN interface an
advertising interface according to [RFC4861].</t>
<t>In Router Advertisements messages, the Prefix Information
Option's A and L-flags MUST be set to 1 by default.</t>
<t>The A and L-flags setting SHOULD be user configurable.</t>
<t>The IPv6 CE router MUST support a DHCPv6 server capable
of IPv6 address assignment according to <xref
target="RFC3315"></xref> OR a stateless DHCPv6 server
according to <xref target="RFC3736"></xref> on its LAN
interfaces.</t>
<t>Unless the IPv6 CE router is configured to support the
DHCPv6 IA_NA option, it SHOULD set M=0 and O=1 in its Router
Advertisement messages <xref target="RFC4861"></xref>.</t>
<t>The IPv6 CE router MUST support providing DNS information
in the DHCPv6 DNS_SERVERS option <xref
target="RFC3646"></xref>.</t>
<t>The IPv6 CE router SHOULD make available a subset of
DHCPv6 options (as listed in section 5.3 of <xref
target="RFC3736"></xref>) received from the DHCPv6 client on
its WAN interface to its LAN side DHCPv6 server.</t>
<t>If the delegated prefix changes, i.e. the current prefix
is replaced with a new prefix without any overlapping time
period, then the IPv6 CE router MUST immediately advertise
the old prefix with a preferred lifetime of 0 and a valid
lifetime of 2 hours (which must be decremented in real
time) in a Router Advertisement message.</t>
<t>The IPv6 CE router MUST send an ICMP Destination
Unreachable Message, code 5 (Source address failed
ingress/egress policy) for packets forwarded to it using an
address from a prefix which has been deprecated.</t>
</list></t>
</section>
<section title="Security Considerations">
<t>It is considered a best practice to filter obviously malicious
traffic (e.g. spoofed packets, "martian" addresses, etc.). Thus, the
IPv6 CE router should support basic stateless egress and ingress
filters. The CE router should also offer mechanisms to filter
traffic entering the customer network; however, the method by which
vendors implement configurable packet filtering is beyond the scope of
this document.</t>
<t>Security requirements:<list style='format S-%d:'>
<t>The IPv6 CE router SHOULD support
<xref target="I-D.ietf-v6ops-cpe-simple-security"></xref>.</t>
<t>The IPv6 CE router MUST support ingress filtering in accordance
with <xref target="RFC2827"></xref>(BCP 38)</t>
</list></t>
</section>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>Thanks to the following people (in alphabetical order) for their
guidance and feedback:</t>
<t>Mikael Abrahamsson, Merete Asak, Scott Beuker, Mohamed
Boucadair, Rex Bullinger, Brian Carpenter, Remi Denis-Courmont,
Gert Doering, Alain Durand, Katsunori Fukuoka, Tony Hain, Thomas
Herbst, Kevin Johns, Stephen Kramer, Victor Kuarsingh,
Francois-Xavier Le Bail, David Miles, Shin Miyakawa,
Jean-Francois Mule, Michael Newbery, Carlos Pignataro, John
Pomeroy, Antonio Querubin, Teemu Savolainen, Matt Schmitt,
Hiroki Sato, Mark Townsley, Bernie Volz, James Woodyatt, Dan
Wing and Cor Zwart</t>
<t>This draft is based in part on CableLabs' eRouter specification. The
authors wish to acknowledge the additional contributors from the eRouter
team:</t>
<t>Ben Bekele, Amol Bhagwat, Ralph Brown, Eduardo Cardona, Margo Dolas,
Toerless Eckert, Doc Evans, Roger Fish, Michelle Kuska, Diego Mazzola,
John McQueen, Harsh Parandekar, Michael Patrick, Saifur Rahman, Lakshmi
Raman, Ryan Ross, Ron da Silva, Madhu Sudan, Dan Torbet and Greg
White</t>
</section>
<section anchor="Contributors" title="Contributors">
<t>The following people have participated as co-authors or provided
substantial contributions to this document: Ralph Droms, Kirk Erichsen,
Fred Baker, Jason Weil, Lee Howard, Jean-Francois Tremblay, Yiu Lee,
John Jason Brzozowski and Heather Kirksey.</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This memo includes no request to IANA.</t>
</section>
</middle>
<!-- *****BACK MATTER ***** -->
<back>
<!-- References split into informative and normative -->
<!-- There are 2 ways to insert reference entries from the citation
libraries: 1. define an ENTITY at the top, and use "ampersand
character"RFC2629; here (as shown) 2. simply use a PI "less than
character"?rfc include="reference.RFC.2119.xml"?> here (for I-Ds:
include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")
Both are cited textually in the same manner: by using xref elements. If
you use the PI option, xml2rfc will, by default, try to find included
files in the same directory as the including file. You can also define
the XML_LIBRARY environment variable with a value containing a set of
directories to search. These can be either in the local filing system or
remote ones accessed by http (http://domain/dir/... ).-->
<references title="Normative References">
<!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->
&RFC2119;
&RFC4861;
&RFC4862;
&RFC3315;
&RFC3633;
&RFC3646;
&RFC4075;
&RFC4193;
&I-D.ietf-6man-node-req-bis;
&RFC4605;
&RFC2827;
&RFC2464;
&RFC5072;
&I-D.ietf-v6ops-cpe-simple-security;
&RFC3736;
&RFC4779;
&RFC4864;
&RFC4242;
&I-D.ietf-6man-ipv6-subnet-model;
&RFC4632;
&RFC4443;
&RFC1122;
</references>
<references title="Informative References">
&I-D.ietf-behave-v6v4-framework;
<reference anchor="UPnP-IGD"
target="http://www.upnp.org/standardizeddcps/igd.asp">
<front>
<title>Universal Plug and Play (UPnP) Internet Gateway Device
(IGD)</title>
<author fullname="UPnP Forum" surname="UPnP Forum">
<organization></organization>
</author>
<date month="November" year="2001" />
</front>
</reference>
</references>
<!-- Change Log
v02 2009-10-26 OTD Initial version. Merged content from Donley, Singh
drafts and new content.
-->
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 04:55:16 |