RFC 8149 on RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)
rfc-editor@rfc-editor.org Thu, 20 April 2017 00:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FA9F12EAF1; Wed, 19 Apr 2017 17:18:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoV_UsnJkfDL; Wed, 19 Apr 2017 17:18:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5C9812EADD; Wed, 19 Apr 2017 17:18:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 476C0B8015A; Wed, 19 Apr 2017 17:17:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8149 on RSVP Extensions for Reoptimization of Loosely Routed Point-to-Multipoint Traffic Engineering Label Switched Paths (LSPs)
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
Message-Id: <20170420001759.476C0B8015A@rfc-editor.org>
Date: Wed, 19 Apr 2017 17:17:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Ph4troH5U-zkTzicXg7tC5y2iVs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 00:18:29 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8149
Title: RSVP Extensions for Reoptimization of
Loosely Routed Point-to-Multipoint
Traffic Engineering Label
Switched Paths (LSPs)
Author: T. Saad, Ed.,
R. Gandhi, Ed.,
Z. Ali,
R. Venator,
Y. Kamite
Status: Standards Track
Stream: IETF
Date: April 2017
Mailbox: tsaad@cisco.com,
rgandhi@cisco.com,
zali@cisco.com,
robert.h.venator.civ@mail.mil,
y.kamite@ntt.com
Pages: 17
Characters: 37916
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-p2mp-loose-path-reopt-09.txt
URL: https://www.rfc-editor.org/info/rfc8149
DOI: 10.17487/RFC8149
The reoptimization of a Point-to-Multipoint (P2MP) Traffic Engineering
(TE) Label Switched Path (LSP) may be triggered based on the need to
reoptimize an individual source-to-leaf (S2L) sub-LSP or a set of
S2L sub-LSPs, both using the Sub-Group-based reoptimization method, or
the entire P2MP-TE LSP tree using the Make-Before-Break (MBB) method.
This document discusses the application of the existing mechanisms
for path reoptimization of loosely routed Point-to-Point (P2P) TE
LSPs to the P2MP-TE LSPs, identifies issues in doing so, and defines
procedures to address them. When reoptimizing a large number of S2L
sub-LSPs in a tree using the Sub-Group-based reoptimization method,
the S2L sub-LSP descriptor list may need to be semantically
fragmented. This document defines the notion of a fragment
identifier to help recipient nodes unambiguously reconstruct the
fragmented S2L sub-LSP descriptor list.
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/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