A new Request for Comments is now available in online RFC libraries.

        
        RFC 7571

        Title:      GMPLS RSVP-TE Extensions for Lock 
                    Instruct and Loopback 
        Author:     J. Dong, M. Chen,
                    Z. Li, D. Ceccarelli
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2015
        Mailbox:    [email protected], 
                    [email protected], 
                    [email protected],  
                    [email protected]
        Pages:      9
        Characters: 19767
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-rsvp-te-li-lb-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7571

        DOI:        http://dx.doi.org/10.17487/RFC7571

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.

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/rfc.html

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


Reply via email to