RFC 7338: Requirements and Framework for Point-to-Multipoint Pseudowires over MPLS Packet Switched Networks
In plain English — editorial summary, not part of the RFC
This document presents a set of requirements and a framework for providing a point-to-multipoint pseudowire (PW) over MPLS Packet Switched Networks. The requirements identified in this document are related to architecture, signaling, and maintenance aspects of point-to-multipoint PW operation. They are proposed as guidelines for the standardization of such mechanisms. Among other potential applications, point-to-multipoint PWs can be used to optimize the support of multicast Layer 2 services (Virtual Private LAN Service and Virtual Private Multicast Service).
Document record
- Document ID
- RFC7338
- Published
- September 2014
- Authors
- F. Jounay; Y. Kamite; G. Heron; M. Bocci
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7334PCE-Based Computation Procedure to Compute Shortest Constrained Point-to-Multipoint (P2MP) Inter-Domain Traffic Engineering Label Switched PathsCurrent
August 2014
- RFC 7331Bidirectional Forwarding Detection (BFD) Management Information BaseCurrent
August 2014
- RFC 7330Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) ManagementCurrent
August 2014
- RFC 7349LDP Hello Cryptographic AuthenticationCurrent
August 2014
- RFC 7325MPLS Forwarding Compliance and Performance RequirementsCurrent
August 2014
- RFC 7324Updates to MPLS Transport Profile Linear ProtectionCurrent
July 2014
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7356IS-IS Flooding Scope Link State PDUs (LSPs)Current
September 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?