draft-ietf-v6ops-ipv6-cpe-router-05.txt   draft-ietf-v6ops-ipv6-cpe-router-06.txt 
Internet Engineering Task Force H. Singh Internet Engineering Task Force H. Singh
Internet-Draft W. Beebee Internet-Draft W. Beebee
Intended status: Informational Cisco Systems, Inc. Intended status: Informational Cisco Systems, Inc.
Expires: November 12, 2010 C. Donley Expires: December 6, 2010 C. Donley
CableLabs CableLabs
B. Stark B. Stark
AT&T AT&T
O. Troan, Ed. O. Troan, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
May 11, 2010 June 4, 2010
Basic Requirements for IPv6 Customer Edge Routers Basic Requirements for IPv6 Customer Edge Routers
draft-ietf-v6ops-ipv6-cpe-router-05 draft-ietf-v6ops-ipv6-cpe-router-06
Abstract Abstract
This document specifies requirements for an IPv6 Customer Edge (CE) This document specifies requirements for an IPv6 Customer Edge (CE)
router. Specifically, the current version of this document focuses router. Specifically, the current version of this document focuses
on the basic provisioning of an IPv6 CE router and the provisioning on the basic provisioning of an IPv6 CE router and the provisioning
of IPv6 hosts attached to it. of IPv6 hosts attached to it.
Status of this Memo Status of this Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 12, 2010. This Internet-Draft will expire on December 6, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 16 skipping to change at page 7, line 16
IPv6 supported link-layer and there is no need for a link-layer IPv6 supported link-layer and there is no need for a link-layer
specific configuration protocol for IPv6 network layer configuration specific configuration protocol for IPv6 network layer configuration
options as in e.g. PPP IPCP for IPv4. This section makes the 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 assumption that the same mechanism will work for any link-layer, be
it Ethernet, DOCSIS, PPP or others. it Ethernet, DOCSIS, PPP or others.
WAN side requirements: WAN side requirements:
W-1: When the router is attached to the WAN interface link it MUST W-1: When the router is attached to the WAN interface link it MUST
act as an IPv6 host for the purposes of stateless or stateful act as an IPv6 host for the purposes of stateless or stateful
interface address assignment ([RFC4862]/[RFC3315]). interface address assignment ([RFC4862] / [RFC3315]).
W-2: The IPv6 CE router MUST generate a link-local address and W-2: The IPv6 CE router MUST generate a link-local address and
finish Duplicate Address Detection according to [RFC4862] prior finish Duplicate Address Detection according to [RFC4862] prior
to sending any Router Solicitations on the interface. The to sending any Router Solicitations on the interface. The
source address used in the subsequent Router Solicitation MUST source address used in the subsequent Router Solicitation MUST
be the link-local address on the WAN interface. be the link-local address on the WAN interface.
W-3: Absent of other routing information the IPv6 CE router MUST use W-3: Absent of other routing information the IPv6 CE router MUST use
Router Discovery as specified in [RFC4861] to discover a Router Discovery as specified in [RFC4861] to discover a
default router(s) and install default route(s) in its routing default router(s) and install default route(s) in its routing
skipping to change at page 11, line 45 skipping to change at page 11, line 45
traffic entering the customer network; however, the method by which traffic entering the customer network; however, the method by which
vendors implement configurable packet filtering is beyond the scope vendors implement configurable packet filtering is beyond the scope
of this document. of this document.
Security requirements: Security requirements:
S-1: The IPv6 CE router SHOULD support S-1: The IPv6 CE router SHOULD support
[I-D.ietf-v6ops-cpe-simple-security]. [I-D.ietf-v6ops-cpe-simple-security].
S-2: The IPv6 CE router MUST support ingress filtering in accordance S-2: The IPv6 CE router MUST support ingress filtering in accordance
with [RFC2827](BCP 38) with [RFC2827] (BCP 38)
5. Acknowledgements 5. Acknowledgements
Thanks to the following people (in alphabetical order) for their Thanks to the following people (in alphabetical order) for their
guidance and feedback: guidance and feedback:
Mikael Abrahamsson, Merete Asak, Scott Beuker, Mohamed Boucadair, Rex Mikael Abrahamsson, Merete Asak, Scott Beuker, Mohamed Boucadair, Rex
Bullinger, Brian Carpenter, Remi Denis-Courmont, Gert Doering, Alain Bullinger, Brian Carpenter, Remi Denis-Courmont, Gert Doering, Alain
Durand, Katsunori Fukuoka, Tony Hain, Thomas Herbst, Kevin Johns, Durand, Katsunori Fukuoka, Tony Hain, Thomas Herbst, Kevin Johns,
Stephen Kramer, Victor Kuarsingh, Francois-Xavier Le Bail, David Stephen Kramer, Victor Kuarsingh, Francois-Xavier Le Bail, David
skipping to change at page 14, line 37 skipping to change at page 14, line 37
May 2007. May 2007.
[RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over [RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over
PPP", RFC 5072, September 2007. PPP", RFC 5072, September 2007.
8.2. Informative References 8.2. Informative References
[I-D.ietf-behave-v6v4-framework] [I-D.ietf-behave-v6v4-framework]
Baker, F., Li, X., Bao, C., and K. Yin, "Framework for Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", IPv4/IPv6 Translation",
draft-ietf-behave-v6v4-framework-08 (work in progress), draft-ietf-behave-v6v4-framework-09 (work in progress),
March 2010. May 2010.
[UPnP-IGD] [UPnP-IGD]
UPnP Forum, "Universal Plug and Play (UPnP) Internet UPnP Forum, "Universal Plug and Play (UPnP) Internet
Gateway Device (IGD)", November 2001, Gateway Device (IGD)", November 2001,
<http://www.upnp.org/standardizeddcps/igd.asp>. <http://www.upnp.org/standardizeddcps/igd.asp>.
Authors' Addresses Authors' Addresses
Hemant Singh Hemant Singh
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 7 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/