draft-ietf-l3vpn-ospfv3-pece-09.txt   draft-ietf-l3vpn-ospfv3-pece-10.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: March 19, 2012 Pollere, Inc Expires: June 4, 2012 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
September 16, 2011 December 2, 2011
OSPFv3 as a PE-CE routing protocol OSPFv3 as a PE-CE routing protocol
draft-ietf-l3vpn-ospfv3-pece-09 draft-ietf-l3vpn-ospfv3-pece-10
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 2, line 16 skipping to change at page 2, line 16
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 March 19, 2012. This Internet-Draft will expire on June 4, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 6, line 23 skipping to change at page 6, line 23
more VRFs. Each VRF configured on the PE corresponds to a customer more VRFs. Each VRF configured on the PE corresponds to a customer
VPN, and retains the destinations that are reachable within that VPN. VPN, and retains the destinations that are reachable within that VPN.
Each VRF may be associated with one or more interfaces, which allows Each VRF may be associated with one or more interfaces, which allows
multiple sites to participate in the same VPN. If OSPFv3 is multiple sites to participate in the same VPN. If OSPFv3 is
instantiated on an interface associated with a VRF, the VRF will be instantiated on an interface associated with a VRF, the VRF will be
populated with OSPFv3 routing information. populated with OSPFv3 routing information.
As OSPFv3 supports multiple instances on a single interface, it is As OSPFv3 supports multiple instances on a single interface, it is
therefore possible that multiple customer sites can connect to the therefore possible that multiple customer sites can connect to the
same interface of a PE router (e.g., through a layer 2 switch) using same interface of a PE router (e.g., through a layer 2 switch) using
distinct OSPFv3 instances. However, since a PE interface can be distinct OSPFv3 instances. A PE interface can be associated with
associated with only one VRF, all OSPFv3 instances running on the only one VRF, and all OSPFv3 instances running on the same interface
same interface MUST be associated with the same VRF. MUST be associated with the same VRF. Configurations where a PE
interface is associated with multiple VRFs are out of scope for this
document.
4.1.1. Independent OSPFv3 Instances in PEs 4.1.1. Independent OSPFv3 Instances in PEs
Similar to [rfc4577], the PE must associate at least one OSPFv3 Similar to [rfc4577], the PE must associate at least one OSPFv3
instance for each OSPFv3 domain to which it attaches, and each instance for each OSPFv3 domain to which it attaches, and each
instance of OSPFv3 MUST be associated with a single VRF. instance of OSPFv3 MUST be associated with a single VRF.
The support of multiple PE-CE OSPFv3 instances per PE interface does The support of multiple PE-CE OSPFv3 instances per PE interface does
not change the paradigm that an OSPF instance can be associated with not change the paradigm that an OSPF instance can be associated with
only a single VRF. Furthermore, for each instance instantiated on only a single VRF. Furthermore, for each instance instantiated on
skipping to change at page 18, line 33 skipping to change at page 18, line 33
9. Contributors 9. Contributors
Joe Lapolito Joe Lapolito
10. Acknowledgments 10. Acknowledgments
The authors would like to thank Kelvin Upson, Seiko Okano, Matthew The authors would like to thank Kelvin Upson, Seiko Okano, Matthew
Everett, Dr. Vineet Mehta, Paul Wells and Marek Karasek for their Everett, Dr. Vineet Mehta, Paul Wells and Marek Karasek for their
support of this work. Thanks to Peter Psenak, Abhay Roy, Acee support of this work. Thanks to Peter Psenak, Abhay Roy, Acee
Lindem, Nick Weeds and Robert Hanzl for their last call comments. Lindem, Nick Weeds, Robert Hanzl and Daniel Cohn for their last call
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.
 End of changes. 6 change blocks. 
8 lines changed or deleted 11 lines changed or added

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