GMPLS Signaling Extensions for Shared Mesh Protection
draft-ietf-teas-gmpls-signaling-smp-04
TEAS Working Group J. He
Internet-Draft I. Busi
Intended status: Standards Track Huawei Technologies
Expires: March 12, 2021 J. Ryoo
B. Yoon
ETRI
P. Park
KT
September 8, 2020
GMPLS Signaling Extensions for Shared Mesh Protection
draft-ietf-teas-gmpls-signaling-smp-04
Abstract
ITU-T Recommendation G.808.3 [G808.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 [G873.3] defines the protection
switching operation and associated protocol for SMP at the Optical
Data Unit (ODU) layer. RFC 7412 [RFC7412] 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 RFC 4872 [RFC4872] to provide the extensions to
the Generalized Multi-Protocol Label Switching (GMPLS) signaling to
support the control of the shared mesh protection.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 12, 2021.
He, et al. Expires March 12, 2021 [Page 1]
Internet-Draft GMPLS Extension for SMP September 2020
Copyright Notice
Copyright (c) 2020 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
(https://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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. SMP Definition . . . . . . . . . . . . . . . . . . . . . . . 3
4. GMPLS Signaling Extension for SMP . . . . . . . . . . . . . . 4
4.1. Identifiers . . . . . . . . . . . . . . . . . . . . . . . 6
4.2. Signaling Primary LSPs . . . . . . . . . . . . . . . . . 7
4.3. Signaling Secondary LSPs . . . . . . . . . . . . . . . . 7
4.4. SMP APS Configuration . . . . . . . . . . . . . . . . . . 8
5. Updates to PROTECTION Object . . . . . . . . . . . . . . . . 8
5.1. New Protection Type . . . . . . . . . . . . . . . . . . . 8
5.2. Other Updates . . . . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. Contributor . . . . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
RFC 4872 [RFC4872] defines extension of Resource Reservation Protocol
- Traffic Engineering (RSVP-TE) to support Shared Mesh Restoration
(SMR) mechanism. SMR can be seen as a particular case of pre-planned
Label Switched Path (LSP) rerouting that reduces the recovery
resource requirements by allowing multiple protecting LSPs to share
common link and node resources. The recovery resources for the
protecting LSPs are pre-reserved during the provisioning phase, and
an explicit restoration signaling is required to activate (i.e.,
Show full document text