RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing
draft-ietf-teas-gmpls-resource-sharing-proc-08

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: db3546@att.com, teas-chairs@ietf.org, teas@ietf.org, vbeeram@juniper.net, "The IESG" <iesg@ietf.org>, draft-ietf-teas-gmpls-resource-sharing-proc@ietf.org, rfc-editor@rfc-editor.org
Subject: Document Action: 'RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing' to Informational RFC (draft-ietf-teas-gmpls-resource-sharing-proc-08.txt)

The IESG has approved the following document:
- 'RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and
   Resource Sharing'
  (draft-ietf-teas-gmpls-resource-sharing-proc-08.txt) as Informational
RFC

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

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-teas-gmpls-resource-sharing-proc/

Ballot Text

Technical Summary

This document reviews how the LSP association is to be provided using
Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
signaling in the context of GMPLS end-to-end recovery scheme when
using restoration LSP where the failed LSP is not torn down.  In
addition, this document discusses resource sharing-based setup and
teardown of LSPs as well as LSP reversion procedures.

Working Group Summary

This document moved from the CCAMP WG to TEAS WG as part of the
Routing Area WG changes. This document has been fairly noncontroversial.

Document Quality

The base GMPLS signaling protocol has been implemented. The procedures
discussed in this document are compatible with earlier implementations.
While there have been no public statements on implementation of these
procedures, the authors are from multiple vendors, and implementation 
is expected - or may even already exist.

Personnel

   Who is the Document Shepherd for this document? Vishnu Pavan Beeram
   Who is the Responsible Area Director? Deborah Brungard

RFC Editor Note