Application of Ethernet Pseudowires to MPLS Transport Networks
RFC 5994
Document | Type | RFC - Informational (October 2010; Errata) | |
---|---|---|---|
Authors | Rao Cherukuri , Monique Morrow , Thomas Nadeau , George Swallow , Neil Harrison , Ben Niven-Jenkins , Stewart Bryant | ||
Last updated | 2020-01-21 | ||
Replaces | draft-bryant-pwe3-mpls-transport | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized with errata bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5994 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) S. Bryant, Ed. Request for Comments: 5994 M. Morrow Category: Informational G. Swallow ISSN: 2070-1721 Cisco Systems R. Cherukuri Juniper Networks T. Nadeau Huawei Technologies N. Harrison BT B. Niven-Jenkins Velocix October 2010 Application of Ethernet Pseudowires to MPLS Transport Networks Abstract Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks, e.g., IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. Many of the requirements for the services provided by the mechanisms explained in this document are also recognized by the MPLS transport profile (MPLS-TP) design effort formed jointly by the IETF and ITU-T. The solution described here does not address all of the MPLS-TP requirements, but it provides a viable form of packet transport service using tools that are already available. This document also serves as an indication that existing MPLS techniques form an appropriate basis for the design of a fully- featured packet transport solution addressing all of the requirements of MPLS-TP. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Bryant, et al. Informational [Page 1] RFC 5994 Eth PWs to MPLS Transport Ntwks October 2010 Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5994. Copyright Notice Copyright (c) 2010 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 (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents 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 Simplified BSD License. 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. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 5 2. PWE3 Configuration . . . . . . . . . . . . . . . . . . . . . . 5 3. Operations, Administration, and Maintenance (OAM) . . . . . . 5 3.1. VCCV Profile 1: BFD without IP/UDP Headers . . . . . . . . 6 3.2. VCCV Profile 2: BFD with IP/UDP Headers . . . . . . . . . 6 4. MPLS Layer . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1. External Configuration . . . . . . . . . . . . . . . . . . 6 4.2. Control Plane Configuration . . . . . . . . . . . . . . . 7 5. Congestion Considerations . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8Show full document text