[Teas] RFC 8426 on Recommendations for RSVP-TE and Segment Routing (SR) Label Switched Path (LSP) Coexistence

rfc-editor@rfc-editor.org Mon, 30 July 2018 23:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D8ADB1311B5; Mon, 30 Jul 2018 16:23:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ISKKeveMW4Ga; Mon, 30 Jul 2018 16:23:30 -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 A4814131188; Mon, 30 Jul 2018 16:23:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F13A8B810D3; Mon, 30 Jul 2018 16:23:18 -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, teas@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180730232318.F13A8B810D3@rfc-editor.org>
Date: Mon, 30 Jul 2018 16:23:18 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/jYrzkVsdIiJ1In3UMwii-hTRKpk>
Subject: [Teas] =?utf-8?q?RFC_8426_on_Recommendations_for_RSVP-TE_and_Seg?= =?utf-8?q?ment_Routing_=28SR=29_Label_Switched_Path_=28LSP=29_Coexistence?=
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2018 23:23:45 -0000

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

        RFC 8426

        Title:      Recommendations for RSVP-TE and Segment 
                    Routing (SR) Label Switched Path (LSP) 
        Author:     H. Sitaraman, Ed.,
                    V. Beeram,
                    I. Minei,
                    S. Sivabalan
        Status:     Informational
        Stream:     IETF
        Date:       July 2018
        Mailbox:    hsitaraman@juniper.net, 
        Pages:      12
        Characters: 26052
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-sr-rsvp-coexistence-rec-04.txt

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

        DOI:        10.17487/RFC8426

Operators are looking to introduce services over Segment Routing (SR)
Label Switched Paths (LSPs) in networks running Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) LSPs.  In some instances,
operators are also migrating existing services from RSVP-TE to SR
LSPs.  For example, there might be certain services that are well
suited for SR and need to coexist with RSVP-TE in the same network.
Such introduction or migration of traffic to SR might require
coexistence with RSVP-TE in the same network for an extended period
of time, depending on the operator's intent.  The following document
provides solution options for keeping the traffic engineering
database consistent across the network, accounting for the different
bandwidth utilization between SR and RSVP-TE.

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

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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