[mpls] RFC 8577 on Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane

rfc-editor@rfc-editor.org Wed, 01 May 2019 05:26 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0396A1200C5; Tue, 30 Apr 2019 22:26:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iWk3y9k8KXpl; Tue, 30 Apr 2019 22:26:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F77B12001E; Tue, 30 Apr 2019 22:26:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 980EFB81E03; Tue, 30 Apr 2019 22:26:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190501052641.980EFB81E03@rfc-editor.org>
Date: Tue, 30 Apr 2019 22:26:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/M4LZuWcN_qPtHZ3fUkDV5CTg6ZI>
Subject: [mpls] RFC 8577 on Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 05:26:55 -0000

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

        RFC 8577

        Title:      Signaling RSVP-TE Tunnels on a 
                    Shared MPLS Forwarding Plane 
        Author:     H. Sitaraman,
                    V. Beeram,
                    T. Parikh,
                    T. Saad
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    harish.ietf@gmail.com, 
        Pages:      24
        Characters: 50113
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-rsvp-shared-labels-09.txt

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

        DOI:        10.17487/RFC8577

As the scale of MPLS RSVP-TE networks has grown, the number of Label
Switched Paths (LSPs) supported by individual network elements has
increased.  Various implementation recommendations have been proposed
to manage the resulting increase in the amount of control-plane state

However, those changes have had no effect on the number of labels
that a transit Label Switching Router (LSR) has to support in the
forwarding plane.  That number is governed by the number of LSPs
transiting or terminated at the LSR and is directly related to the
total LSP state in the control plane.

This document defines a mechanism to prevent the maximum size of the
label space limit on an LSR from being a constraint to control-plane
scaling on that node.  It introduces the notion of preinstalled
'per-TE link labels' that can be shared by MPLS RSVP-TE LSPs that
traverse these TE links.  This approach significantly reduces the
forwarding-plane state required to support a large number of LSPs.
This couples the feature benefits of the RSVP-TE control plane with
the simplicity of the Segment Routing (SR) MPLS forwarding plane.

This document is a product of the Multiprotocol Label Switching 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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC