Last Call: <draft-ietf-spring-segment-routing-ldp-interop-11.txt> (Segment Routing interworking with LDP) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 10 May 2018 21:11 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1EA12D779; Thu, 10 May 2018 14:11:47 -0700 (PDT)
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>
Subject: Last Call: <draft-ietf-spring-segment-routing-ldp-interop-11.txt> (Segment Routing interworking with LDP) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: spring@ietf.org, spring-chairs@ietf.org, aretana.ietf@gmail.com, robjs@google.com, draft-ietf-spring-segment-routing-ldp-interop@ietf.org, Rob Shakir <robjs@google.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: <152598670709.10271.7633520636987110007.idtracker@ietfa.amsl.com>
Date: Thu, 10 May 2018 14:11:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3abYwxZdsP8VnsPUkz2E-3xnVN8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 10 May 2018 21:11:47 -0000

The IESG has received a request from the Source Packet Routing in Networking
WG (spring) to consider the following document: - 'Segment Routing
interworking with LDP'
  <draft-ietf-spring-segment-routing-ldp-interop-11.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 2018-05-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


   A Segment Routing (SR) node steers a packet through a controlled set
   of instructions, called segments, by prepending the packet with an SR
   header.  A segment can represent any instruction, topological or
   service-based.  SR allows to enforce a flow through any topological
   path while maintaining per-flow state only at the ingress node to the
   SR domain.

   The Segment Routing architecture can be directly applied to the MPLS
   data plane with no change in the forwarding plane.  This document
   describes how Segment Routing operates in a network where LDP is
   deployed and in the case where SR-capable and non-SR-capable nodes
   coexist.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-ldp-interop/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-ldp-interop/ballot/

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

   https://datatracker.ietf.org/ipr/2456/
   https://datatracker.ietf.org/ipr/2277/