[Teas] Last Call: <draft-ietf-teas-sr-rsvp-coexistence-rec-02.txt> (Recommendations for RSVP-TE and Segment Routing LSP co-existence) to Informational RFC

The IESG <iesg-secretary@ietf.org> Fri, 06 April 2018 19:01 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: db3546@att.com, teas-chairs@ietf.org, teas@ietf.org, draft-ietf-teas-sr-rsvp-coexistence-rec@ietf.org, Lou Berger <lberger@labn.net>, lberger@labn.net
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: <152304126566.3911.15707984252253943099.idtracker@ietfa.amsl.com>
Date: Fri, 06 Apr 2018 12:01:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/Ai5-prz1S6UYxmBkUcXZ8zdsQ-M>
Subject: [Teas] Last Call: <draft-ietf-teas-sr-rsvp-coexistence-rec-02.txt> (Recommendations for RSVP-TE and Segment Routing LSP co-existence) to Informational RFC

The IESG has received a request from the Traffic Engineering Architecture and
Signaling WG (teas) to consider the following document: - 'Recommendations
for RSVP-TE and Segment Routing LSP co-existence'
  <draft-ietf-teas-sr-rsvp-coexistence-rec-02.txt> as Informational RFC

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 2018-04-20. 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


   Operators are looking to introduce services over Segment Routing (SR)
   LSPs in networks running Resource Reservation Protocol (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 co-exist
   with RSVP-TE in the same network.  In other cases, services running
   on RSVP-TE might be migrated to run over SR.  Such introduction or
   migration of traffic to SR might require co-existence 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 (TED) consistent across
   the network, accounting for the different bandwidth utilization
   between SR and RSVP-TE.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-teas-sr-rsvp-coexistence-rec/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-teas-sr-rsvp-coexistence-rec/ballot/

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

   https://datatracker.ietf.org/ipr/2827/

[Teas] Last Call: <draft-ietf-teas-sr-rsvp-coexis… The IESG