GMPLS RSVP-TE Extensions for Lock Instruct and Loopback
RFC 7571

Document Type RFC - Proposed Standard (July 2015; No errata)
Last updated 2015-10-14
Replaces draft-ietf-ccamp-rsvp-te-li-lb
Stream IETF
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication Jan 2015
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2014-12-30)
IESG IESG state RFC 7571 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Deborah Brungard
Send notices to (None)
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                           J. Dong
Request for Comments: 7571                                       M. Chen
Category: Standards Track                            Huawei Technologies
ISSN: 2070-1721                                                    Z. Li
                                                            China Mobile
                                                           D. Ceccarelli
                                                                Ericsson
                                                               July 2015

        GMPLS RSVP-TE Extensions for Lock Instruct and Loopback

Abstract

   This document specifies extensions to Resource Reservation Protocol -
   Traffic Engineering (RSVP-TE) to support Lock Instruct (LI) and
   Loopback (LB) mechanisms for Label Switched Paths (LSPs).  These
   mechanisms are applicable to technologies that use Generalized MPLS
   (GMPLS) for the control plane.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc7571.

Copyright Notice

   Copyright (c) 2015 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
   (http://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.

Dong, et al.                 Standards Track                    [Page 1]
RFC 7571             RSVP-TE Extensions for LI & LB            July 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Flag Definitions for LI and LB  . . . . . . . . . . . . . . .   3
     2.1.  Lock Instruct Indication  . . . . . . . . . . . . . . . .   3
     2.2.  Extensions for Loopback . . . . . . . . . . . . . . . . .   3
   3.  Operational Procedures  . . . . . . . . . . . . . . . . . . .   3
     3.1.  Lock Instruct . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Loopback  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Attribute Flags . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  RSVP Error Value Sub-Codes  . . . . . . . . . . . . . . .   6
     4.3.  Allocation Rule for ERO Subobjects  . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The requirements for Lock Instruct (LI) and Loopback (LB) in the
   Multiprotocol Label Switching Transport Profile (MPLS-TP) are
   specified in [RFC5860], and the framework of LI and LB is specified
   in [RFC6371].  A Label Switched Path (LSP) that is locked, using LI,
   is prevented from carrying user data traffic.  The LB function can
   only be applied to an LSP that has been previously locked.

   In general, the LI and LB are useful Operations, Administration, and
   Maintenance (OAM) functions for technologies that use Generalized
   MPLS (GMPLS) for the control plane, e.g., time-division multiplexing,
   wavelength-division multiplexing, and packet switching.  It is
   natural to use and extend the GMPLS control-plane protocol to provide
   a unified approach for LI and LB provisioning in all these
   technologies.

   [RFC7487] specifies the RSVP-TE extensions for the configuration of
   proactive MPLS-TP OAM functions, such as Continuity Check (CC),
   Connectivity Verification (CV), Delay Measurement (DM), and Loss
   Measurement (LM).  The provisioning of on-demand OAM functions such
Show full document text