[Teas] Last Call: <draft-ietf-teas-lsp-diversity-08.txt> (Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Path Diversity using Exclude Route) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 10 August 2017 20:20 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-teas-lsp-diversity@ietf.org, lberger@labn.net, teas-chairs@ietf.org, teas@ietf.org, db3546@att.com
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <150239642305.11932.13335922726093665368.idtracker@ietfa.amsl.com>
Date: Thu, 10 Aug 2017 13:20:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/oxkbxYcPqhjKjWuOjiHuBhu3PSk>
Subject: [Teas] Last Call: <draft-ietf-teas-lsp-diversity-08.txt> (Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Path Diversity using Exclude Route) to Proposed Standard

The IESG has received a request from the Traffic Engineering Architecture and
Signaling WG (teas) to consider the following document: - 'Resource
ReserVation Protocol-Traffic Engineering (RSVP-TE) Path
   Diversity using Exclude Route'
  <draft-ietf-teas-lsp-diversity-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-08-24. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   Resource ReserVation Protocol-Traffic Engineering provides support
   for the communication of exclusion information during label switched
   path (LSP) setup. This document specifies two new diversity
   subobjects for the RSVP XRO and EXRS subobjects. Three different
   mechanisms are supported how LSP diversity can be accomplished in
   the provider or core network: the signaled diversity type, indicates
   whether diversity is based on client, path computation engine (PCE),
   or network assigned identifiers.
   The solution described in this document is based on the assumption
   that LSPs are requested sequentially, i.e., the time period between
   the LSP setup requests for the two LSPs may be longer (days, weeks,
   months). Re-routing the first LSP that may have existed for a longer
   period of time is not considered.

   



The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-teas-lsp-diversity/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-teas-lsp-diversity/ballot/

The following IPR Declarations may be related to this I-D:

   https://datatracker.ietf.org/ipr/1943/
   https://datatracker.ietf.org/ipr/2383/

[Teas] Last Call: <draft-ietf-teas-lsp-diversity-… The IESG