Skip to main content

GMPLS Signaling Extensions for Shared Mesh Protection
draft-ietf-teas-gmpls-signaling-smp-12

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, draft-ietf-teas-gmpls-signaling-smp@ietf.org, jgs@juniper.net, rfc-editor@rfc-editor.org, teas-chairs@ietf.org, teas@ietf.org, vbeeram@juniper.net
Subject: Protocol Action: 'GMPLS Signaling Extensions for Shared Mesh Protection' to Proposed Standard (draft-ietf-teas-gmpls-signaling-smp-12.txt)

The IESG has approved the following document:
- 'GMPLS Signaling Extensions for Shared Mesh Protection'
  (draft-ietf-teas-gmpls-signaling-smp-12.txt) as Proposed Standard

This document is the product of the Traffic Engineering Architecture and
Signaling Working Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-gmpls-signaling-smp/


Ballot Text

Technical Summary

   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 RFC 4872 to provide the extensions to the
   Generalized Multi-Protocol Label Switching (GMPLS) signaling to
   support the control of the SMP.

Working Group Summary

There was notable debate on how pre-emption is handled in the Shared
Mesh Protection signaling procedures. The authors addressed all of these 
concerns by adding relevant text to the document.

Document Quality

The document has been discussed and reviewed thoroughly by the WG. While
there have been no official statements on implementation of this 
new framework, some of the authors are from a vendor, and implementation 
is expected.

Personnel

>   Who is the Document Shepherd?
Vishnu Pavan Beeram

> Who is the Responsible Area Director?
John Scudder

RFC Editor Note