Last Call: <draft-ietf-idr-bgpls-segment-routing-epe-18.txt> (BGP-LS extensions for Segment Routing BGP Egress Peer Engineering) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 03 April 2019 16:30 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 274B8120046; Wed, 3 Apr 2019 09:30:39 -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-idr-bgpls-segment-routing-epe-18.txt> (BGP-LS extensions for Segment Routing BGP Egress Peer Engineering) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: idr@ietf.org, Susan Hares <shares@ndzh.com>, idr-chairs@ietf.org, shares@ndzh.com, aretana.ietf@gmail.com, draft-ietf-idr-bgpls-segment-routing-epe@ietf.org
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155430903908.22744.16152379367225417415.idtracker@ietfa.amsl.com>
Date: Wed, 03 Apr 2019 09:30:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/AKmUIoU-pXUjjRVwpvyOz4PU0vY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 03 Apr 2019 16:30:39 -0000

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document: - 'BGP-LS extensions for Segment Routing BGP
Egress Peer Engineering'
  <draft-ietf-idr-bgpls-segment-routing-epe-18.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 2019-04-17. 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


   Segment Routing (SR) leverages source routing.  A 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 segments allow
   steering a flow through any topological path and service chain while
   maintaining per-flow state only at the ingress node of the SR domain.

   This document describes an extension to BGP Link State (BGP-LS) for
   advertisement of BGP Peering Segments along with their BGP peering
   node information so that efficient BGP Egress Peer Engineering (EPE)
   policies and strategies can be computed based on Segment Routing.





The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/ballot/

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

   https://datatracker.ietf.org/ipr/2721/
   https://datatracker.ietf.org/ipr/2611/