OSPFv3-Based Layer 1 VPN Auto-Discovery
RFC 5523
Document | Type | RFC - Experimental (April 2009; No errata) | |
---|---|---|---|
Author | Lou Berger | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5523 (Experimental) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | David Ward | ||
Send notices to | (None) |
Network Working Group L. Berger Request for Comment: 5523 LabN Consulting, LLC Category: Experimental April 2009 OSPFv3-Based Layer 1 VPN Auto-Discovery Status of This Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document defines an OSPFv3-based (Open Shortest Path First version 3) Layer 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This document parallels the existing OSPF version 2 L1VPN auto-discovery mechanism. The notable functional difference is the support of IPv6. Berger Experimental [Page 1] RFC 5523 OSPV3-Based Layer 1 VPN Auto-Discovery April 2009 Table of Contents 1. Introduction ....................................................2 1.1. Terminology ................................................2 1.2. Conventions Used in This Document ..........................3 1.3. Overview ...................................................3 2. OSPFv3 L1VPN LSA and Its TLVs ...................................5 2.1. OSPFv3 L1VPN LSA ...........................................5 2.2. L1VPN IPv6 INFO TLV ........................................7 3. OSPFv3 L1VPN LSA Advertising and Processing .....................8 4. Backward Compatibility ..........................................9 5. Manageability Considerations ....................................9 5.1. Coexistence with and Migration from OSPFv2 .................9 6. Security Considerations ........................................10 7. IANA Considerations ............................................11 8. Acknowledgment .................................................11 9. References .....................................................11 9.1. Normative References ......................................11 9.2. Informative References ....................................12 1. Introduction This document defines an OSPFv3-based (Open Shortest Path First version 3) Layer 1 Virtual Private Network (L1VPN) auto-discovery mechanism. This document parallels the existing OSPF version 2 L1VPN auto-discovery mechanism. The notable functional difference is the support of IPv6. 1.1. Terminology The reader of this document should be familiar with the terms used in [RFC4847] and [RFC5251]. The reader of this document should also be familiar with [RFC5340], [RFC5329], and [RFC5252]. In particular, the following terms: L1VPN Layer 1 Virtual Private Network CE Customer (edge) network element directly connected to the Provider network (terminates one or more links to one or more PEs); it is also connected to one or more Cs and/or other CEs. C Customer network element that is not connected to the Provider network but is connected to one or more other Cs and/or CEs. Berger Experimental [Page 2] RFC 5523 OSPV3-Based Layer 1 VPN Auto-Discovery April 2009 PE Provider (edge) network element directly connected to one or more Customer networks (terminates one or more links to one or more CEs associated with the same or different L1VPNs); it is also connected to one or more Ps and/or other PEs. P Provider (core) network element that is not directly connected to any of Customer networks; P is connected to one or more other Ps and/or PEs. LSA OSPF Link State Advertisement. LSDB Link State Database: a data structure supported by an IGP speaker. PIT Port Information Table. CPI Customer Port Identifier. PPI Provider Port Identifier. 1.2. Conventions Used in This Document 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 [RFC2119]. 1.3. Overview The framework for Layer 1 VPNs is described in [RFC4847]. Basic modeShow full document text