draft-ietf-l3vpn-ospfv3-pece-03.txt   draft-ietf-l3vpn-ospfv3-pece-04.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: January 11, 2010 Pollere, Inc Expires: May 28, 2010 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
July 10, 2009 November 24, 2009
OSPFv3 as a PE-CE routing protocol OSPFv3 as a PE-CE routing protocol
draft-ietf-l3vpn-ospfv3-pece-03 draft-ietf-l3vpn-ospfv3-pece-04
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Abstract
Many Service Providers (SPs) offer Virtual Private Network (VPN)
services to their customers using a technique in which Customer Edge
(CE) routers are routing peers of Provider Edge (PE) routers. The
Border Gateway Protocol (BGP) is used to distribute the customer's
routes across the provider's IP backbone network, and Multiprotocol
Label Switching (MPLS) is used to tunnel customer packets across the
provider's backbone. This is known as a "BGP/MPLS IP VPN".
Originally only IPv4 was supported and it was later extended to
support IPv6 VPNs as well. Extensions were later added for the
support of the Open Shortest Path First protocol version 2 (OSPFv2)
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
routing protocol. The OSPFv3 PE-CE functionality is identical to
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 to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 11, 2010. This Internet-Draft will expire on May 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the 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
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Abstract
Many Service Providers (SPs) offer Virtual Private Network (VPN)
services to their customers using a technique in which Customer Edge
(CE) routers are routing peers of Provider Edge (PE) routers. The
Border Gateway Protocol (BGP) is used to distribute the customer's
routes across the provider's IP backbone network, and Multiprotocol
Label Switching (MPLS) is used to tunnel customer packets across the
provider's backbone. This is known as a "BGP/MPLS IP VPN".
Originally only IPv4 was supported and it was later extended to
support IPv6 VPNs as well. Extensions were later added for the
support of the Open Shortest Path First protocol version 2 (OSPFv2)
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
routing protocol. The OSPFv3 PE-CE functionality is identical to
that of OSPFv2 except for the differences described in this document.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Specification of Requirements . . . . . . . . . . . . . . . . 4 2. Specification of Requirements . . . . . . . . . . . . . . . . 4
3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. OSPFv3 Specificities . . . . . . . . . . . . . . . . . . . 5 3.1. OSPFv3 Specificities . . . . . . . . . . . . . . . . . . . 5
4. BGP/OSPFv3 Interaction Procedures for PE Routers . . . . . . . 6 4. BGP/OSPFv3 Interaction Procedures for PE Routers . . . . . . . 6
4.1. VRFs and OSPFv3 Instances . . . . . . . . . . . . . . . . 6 4.1. VRFs and OSPFv3 Instances . . . . . . . . . . . . . . . . 6
4.1.1. Independent OSPFv3 Instances in PEs . . . . . . . . . 6 4.1.1. Independent OSPFv3 Instances in PEs . . . . . . . . . 6
4.1.2. OSPFv3 Domain and PE-PE Link Instance Identifiers . . 7 4.1.2. OSPFv3 Domain and PE-PE Link Instance Identifiers . . 7
skipping to change at page 13, line 38 skipping to change at page 13, line 38
This attribute is MANDATORY for all OSPFv3 routes in a VRF instance This attribute is MANDATORY for all OSPFv3 routes in a VRF instance
on a PE router. The fields of this new BGP Extended Community on a PE router. The fields of this new BGP Extended Community
attribute are described in the following sections. attribute are described in the following sections.
OSPFv3 Domain IDs field : 6 bytes OSPFv3 Domain IDs field : 6 bytes
Each OSPFv3 Instance within a VRF MUST have a Domain ID. The Each OSPFv3 Instance within a VRF MUST have a Domain ID. The
Domain ID may be configured at the VRF level or at the OSPFv3 Domain ID may be configured at the VRF level or at the OSPFv3
Instance level. The OSPFv3 Domain ID is a 6-byte number and its Instance level. The OSPFv3 Domain ID is a 6-byte number and its
default value if none is configured should be NULL. default value is 0.
OSPFv3 Router ID field : 4 bytes OSPFv3 Router ID field : 4 bytes
The OSPFv3 Router ID is a 32 bit number as in OSPFv2. This field The OSPFv3 Router ID is a 32 bit number as in OSPFv2. Setting
is OPTIONAL and may be set to 0. this field is OPTIONAL and its default value is 0.
OSPFv3 Area ID : 4 bytes OSPFv3 Area ID : 4 bytes
The Area ID field indicates the 32-bit Area ID to which the route The Area ID field indicates the 32-bit Area ID to which the route
belongs. belongs.
OSPFv3 Route Types : 1 byte OSPFv3 Route Types : 1 byte
To accommodate OSPFv3 LSA types, the OSPF Route Type field is To accommodate OSPFv3 LSA types, the OSPF Route Type field is
encoded as follows: encoded as follows:
skipping to change at page 19, line 22 skipping to change at page 19, line 22
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFC's to [RFC2119] Bradner, S., "Key words for use in RFC's to
Indicate Requirement Levels", BCP 14, RFC 2119, Indicate Requirement Levels", BCP 14, RFC 2119,
March 1997. March 1997.
[rfc2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998. [rfc2328] Moy, J., "OSPF Version 2", RFC 2328, April 1998.
[rfc2547] Rosen, E. and Y. Rehkter, "BGP/MPLS VPNs",
RFC 2547, March 1999.
[rfc2858] Bates, T., Rehkter, Y., Chandra, R., and D. Katz, [rfc2858] Bates, T., Rehkter, Y., Chandra, R., and D. Katz,
"Multiprotocol Extensions for BGP-4", RFC 2858, "Multiprotocol Extensions for BGP-4", RFC 2858,
June 2000. June 2000.
[rfc4360] Sangli, S., Tappan, D., and Y. Rehkter, "BGP [rfc4360] Sangli, S., Tappan, D., and Y. Rehkter, "BGP
Extended Communities Attribute", RFC 4360, Extended Communities Attribute", RFC 4360,
February 2006. February 2006.
[rfc4364] Rosen, E. and Y. Rehkter, "BGP/MPLS IP Virtual [rfc4364] Rosen, E. and Y. Rehkter, "BGP/MPLS IP Virtual
Private Networks (VPNs)", RFC 4364, Private Networks (VPNs)", RFC 4364,
skipping to change at page 20, line 18 skipping to change at page 20, line 17
[BGP-EXTCOMM-IPV6] Rehkter, Y., "IPv6 Address Specific BGP Extended [BGP-EXTCOMM-IPV6] Rehkter, Y., "IPv6 Address Specific BGP Extended
Communities Attribute", October 2008, <http:// Communities Attribute", October 2008, <http://
www.ietf.org/internet-drafts/ www.ietf.org/internet-drafts/
draft-rekhter-v6-ext-communities-03.txt>. draft-rekhter-v6-ext-communities-03.txt>.
[OSPF-AF-ALT] Mirtorabi, S., Roy, A., Barnes, M., Aggarwal, R., [OSPF-AF-ALT] Mirtorabi, S., Roy, A., Barnes, M., Aggarwal, R.,
and A. Lindem, "Support of address families in and A. Lindem, "Support of address families in
OSPFv3", October 2008, <http://www.ietf.org/ OSPFv3", October 2008, <http://www.ietf.org/
internet-drafts/draft-ietf-ospf-af-alt-07.txt>. internet-drafts/draft-ietf-ospf-af-alt-07.txt>.
[rfc2547] Rosen, E. and Y. Rehkter, "BGP/MPLS VPNs",
RFC 2547, 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. 11 change blocks. 
42 lines changed or deleted 48 lines changed or added

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