A new Request for Comments is now available in online RFC libraries.
RFC 9270
Title: GMPLS Signaling Extensions for Shared
Mesh Protection
Author: J. He,
I. Busi,
J. Ryoo,
B. Yoon,
P. Park
Status: Standards Track
Stream: IETF
Date: August 2022
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 13
Updates: RFC 4872, RFC 4873
I-D Tag: draft-ietf-teas-gmpls-signaling-smp-12.txt
URL: https://www.rfc-editor.org/info/rfc9270
DOI: 10.17487/RFC9270
ITU-T Recommendation G.808.3 defines the generic aspects of a Shared
Mesh Protection (SMP) mechanism, where the difference between SMP and
Shared Mesh Restoration (SMR) is also identified. ITU-T
Recommendation G.873.3 defines the protection switching operation and
associated protocol for SMP at the Optical Data Unit (ODU) layer. RFC
7412 provides requirements for any mechanism that would be used to
implement SMP in a Multi-Protocol Label Switching - Transport Profile
(MPLS-TP) network.
This document updates RFCs 4872 and 4873 to provide extensions for
Generalized Multi-Protocol Label Switching (GMPLS) signaling to
support the control of the SMP mechanism.
This document is a product of the Traffic Engineering Architecture and
Signaling Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
IETF-Announce mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-announce
