RFC 8024: Multi-Chassis Passive Optical Network (MC-PON) Protection in MPLS
In plain English — editorial summary, not part of the RFC
Multiprotocol Label Switching (MPLS) is being extended to the edge of operator networks including the network access nodes. Separately, network access nodes such as Passive Optical Network (PON) Optical Line Terminations (OLTs) have evolved to support first-mile access protection, where one or more physical OLTs provide first-mile diversity to the customer edge. Multihoming support is needed on the MPLS-enabled PON OLT to provide resiliency for provided services. This document describes the Multi-Chassis PON (MC-PON) protection architecture in MPLS and also specifies the Inter-Chassis Communication Protocol (ICCP) extension to support it.
Document record
- Document ID
- RFC8024
- Published
- November 2016
- Authors
- Y. Jiang; Y. Luo; E. Mallette; Y. Shen; W. Cheng
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8029Detecting Multiprotocol Label Switched (MPLS) Data-Plane FailuresUpdated
March 2017
- RFC 8014An Architecture for Data-Center Network Virtualization over Layer 3 (NVO3)Current
December 2016
- RFC 8012Label Switched Path (LSP) and Pseudowire (PW) Ping/Trace over MPLS Networks Using Entropy Labels (ELs)Current
November 2016
- RFC 8036Applicability Statement for the Routing Protocol for Low-Power and Lossy Networks (RPL) in Advanced Metering Infrastructure (AMI) NetworksCurrent
January 2017
- RFC 8042OSPF Two-Part MetricCurrent
December 2016
- RFC 8001RSVP-TE Extensions for Collecting Shared Risk Link Group (SRLG) InformationCurrent
January 2017
- RFC 8051Applicability of a Stateful Path Computation Element (PCE)Current
January 2017
- RFC 8059PIM Join Attributes for Locator/ID Separation Protocol (LISP) EnvironmentsUpdated
January 2017
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?