draft-ietf-l3vpn-ospfv3-pece-05.txt   draft-ietf-l3vpn-ospfv3-pece-06.txt 
Network Working Group P. Pillay-Esnault Network Working Group P. Pillay-Esnault
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track P. Moyer Intended status: Standards Track P. Moyer
Expires: September 9, 2010 Pollere, Inc Expires: March 13, 2011 Pollere, Inc
J. Doyle J. Doyle
Jeff Doyle and Associates Jeff Doyle and Associates
E. Ertekin E. Ertekin
M. Lundberg M. Lundberg
Booz Allen Hamilton Booz Allen Hamilton
March 8, 2010 September 9, 2010
OSPFv3 as a PE-CE routing protocol OSPFv3 as a PE-CE routing protocol
draft-ietf-l3vpn-ospfv3-pece-05 draft-ietf-l3vpn-ospfv3-pece-06
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Originally only IPv4 was supported and it was later extended to Originally only IPv4 was supported and it was later extended to
support IPv6 VPNs as well. Extensions were later added for the support IPv6 VPNs as well. Extensions were later added for the
support of the Open Shortest Path First protocol version 2 (OSPFv2) support of the Open Shortest Path First protocol version 2 (OSPFv2)
as a PE-CE routing protocol for the IPv4 VPNs. This document extends as a PE-CE routing protocol for the IPv4 VPNs. This document extends
those specifications to support OSPF version 3 (OSPFv3) as a PE-CE those specifications to support OSPF version 3 (OSPFv3) as a PE-CE
routing protocol. The OSPFv3 PE-CE functionality is identical to routing protocol. The OSPFv3 PE-CE functionality is identical to
that of OSPFv2 except for the differences described in this document. that of OSPFv2 except for the differences described in this document.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on March 13, 2011.
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 9, 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
skipping to change at page 17, line 15 skipping to change at page 17, line 15
document. document.
When forwarding a packet, if the preferred route for that packet has When forwarding a packet, if the preferred route for that packet has
the sham link as its next hop interface, then the packet MUST be the sham link as its next hop interface, then the packet MUST be
forwarded according to the corresponding BGP route (as defined in forwarded according to the corresponding BGP route (as defined in
[rfc4364] and [rfc4659]). [rfc4364] and [rfc4659]).
6. Multiple Address Family Support 6. Multiple Address Family Support
The support of multiple address families (AF) in OSPFv3 is described The support of multiple address families (AF) in OSPFv3 is described
in [OSPF-AF-ALT]. [OSPF-AF-ALT] differentiates between AF using in [RFC5838]. [RFC5838] differentiates between AF using reserved
reserved ranges of Instance IDs for each AF. ranges of Instance IDs for each AF.
The architecture described in this document is fully compatible with The architecture described in this document is fully compatible with
[OSPF-AF-ALT]. The OSPFv3 PE-CE protocol can support multiple [RFC5838]. The OSPFv3 PE-CE protocol can support multiple address
address families across a MPLS VPN backbone. All AFs redistributed families across a MPLS VPN backbone. All AFs redistributed from
from OSPFv3 into BGP on a PE MUST contain the OSPFv3 Route Extended OSPFv3 into BGP on a PE MUST contain the OSPFv3 Route Extended
Community Attribute. Community Attribute.
Note that since [OSPF-AF-ALT] does not support multiple AFs across Note that since [RFC5838] does not support multiple AFs across
virtual links, this document only addresses support for unicast IPv6 virtual links, this document only addresses support for unicast IPv6
addresses across the sham link. addresses across the sham link.
7. Security Considerations 7. Security Considerations
The extensions described in this document are specific to the use of The extensions described in this document are specific to the use of
OSPFv3 as the PE-CE protocol and do not introduce any concerns OSPFv3 as the PE-CE protocol and do not introduce any concerns
regarding the use of BGP as transport of IPv6 reachability over the regarding the use of BGP as transport of IPv6 reachability over the
MPLS Backbone. The Security considerations for the transport of IPv6 MPLS Backbone. The Security considerations for the transport of IPv6
reachability information using BGP are discussed in Section 11 of reachability information using BGP are discussed in Section 11 of
skipping to change at page 18, line 40 skipping to change at page 18, line 40
Everett, and Dr. Vineet Mehta for their support of this work. Thanks Everett, and Dr. Vineet Mehta for their support of this work. Thanks
to Peter Psenak, Abhay Roy and Acee Lindem for their last call to Peter Psenak, Abhay Roy and Acee Lindem for their last call
comments. comments.
This document was produced using Marshall Rose's xml2rfc tool. This document was produced using Marshall Rose's xml2rfc tool.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFC's to Indicate [RFC2119] Bradner, S., "Key words for use in RFC's to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
an IANA Considerations Section in RFCs", BCP 26, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
RFC 5226, May 2008. May 2008.
[rfc2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [RFC5838] Mirtorabi, S., Roy, A., Barnes, M., Aggarwal, R., and A.
Lindem, "Support of address families in OSPFv3",
April 2010.
[rfc2858] Bates, T., Rehkter, Y., Chandra, R., and D. Katz, [rfc2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
"Multiprotocol Extensions for BGP-4", RFC 2858,
June 2000.
[rfc4360] Sangli, S., Tappan, D., and Y. Rehkter, "BGP Extended [rfc2858] Bates, T., Rehkter, Y., Chandra, R., and D. Katz,
Communities Attribute", RFC 4360, February 2006. "Multiprotocol Extensions for BGP-4", RFC 2858, June 2000.
[rfc4364] Rosen, E. and Y. Rehkter, "BGP/MPLS IP Virtual Private [rfc4360] Sangli, S., Tappan, D., and Y. Rehkter, "BGP Extended
Networks (VPNs)", RFC 4364, February 2006. Communities Attribute", RFC 4360, February 2006.
[rfc4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a [rfc4364] Rosen, E. and Y. Rehkter, "BGP/MPLS IP Virtual Private
Link State Advertisement (LSA) Options Bit to Prevent Networks (VPNs)", RFC 4364, February 2006.
Looping in BGP/MPLS IP Virtual Private Networks
(VPNs)", RFC 4576, June 2006.
[rfc4577] Rosen, E., Psenak, P., and P. Pillay-Esnault, "OSPF as [rfc4576] Rosen, E., Psenak, P., and P. Pillay-Esnault, "Using a
the Provider/Customer Edge Protocol for BGP/MPLS IP Link State Advertisement (LSA) Options Bit to Prevent
Virtual Private Networks (VPNs)", RFC 4577, June 2006. Looping in BGP/MPLS IP Virtual Private Networks (VPNs)",
RFC 4576, June 2006.
[rfc4659] De Clercq, J., Ooms, D., Carugi, M., and F. [rfc4577] Rosen, E., Psenak, P., and P. Pillay-Esnault, "OSPF as the
Lefaucheur, "BGP-MPLS IP Virtual Private Network (VPN) Provider/Customer Edge Protocol for BGP/MPLS IP Virtual
Extension for IPv6 VPN", RFC 4659, September 2006. Private Networks (VPNs)", RFC 4577, June 2006.
[rfc5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, [rfc4659] De Clercq, J., Ooms, D., Carugi, M., and F. Lefaucheur,
"OSPF for IPv6", RFC 5340, July 2008. "BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, September 2006.
[rfc5701] Rehkter, Y., "IPv6 Address Specific BGP Extended [rfc5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
Communities Attribute", November 2009. for IPv6", RFC 5340, July 2008.
11.2. Informative References [rfc5701] Rehkter, Y., "IPv6 Address Specific BGP Extended
Communities Attribute", November 2009.
[OSPF-AF-ALT] Mirtorabi, S., Roy, A., Barnes, M., Aggarwal, R., and 11.2. Informative References
A. Lindem, "Support of address families in OSPFv3",
December 2009, <http://www.ietf.org/internet-drafts/
draft-ietf-ospf-af-alt-10.txt>.
[rfc2547] Rosen, E. and Y. Rehkter, "BGP/MPLS VPNs", RFC 2547, [rfc2547] Rosen, E. and Y. Rehkter, "BGP/MPLS VPNs", RFC 2547,
March 1999. March 1999.
Authors' Addresses Authors' Addresses
Padma Pillay-Esnault Padma Pillay-Esnault
Cisco Systems Cisco Systems
510 McCarty Blvd 510 McCarty Blvd
Milpitas, CA 95035 Milpitas, CA 95035
USA USA
EMail: ppe@cisco.com EMail: ppe@cisco.com
 End of changes. 24 change blocks. 
55 lines changed or deleted 47 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/