Last Call: <draft-ietf-idr-bgp-ls-segment-routing-ext-14.txt> (BGP Link-State extensions for Segment Routing) to Proposed Standard

The IESG <> Thu, 09 May 2019 14:29 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 44A871202A5; Thu, 9 May 2019 07:29:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: "IETF-Announce" <>
Subject: Last Call: <draft-ietf-idr-bgp-ls-segment-routing-ext-14.txt> (BGP Link-State extensions for Segment Routing) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.96.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <>
CC:, Susan Hares <>,,,,
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <>
Date: Thu, 09 May 2019 07:29:59 -0700
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 09 May 2019 14:30:00 -0000

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document: - 'BGP Link-State extensions for Segment
  <draft-ietf-idr-bgp-ls-segment-routing-ext-14.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 mailing lists by 2019-05-23. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.


   Segment Routing (SR) allows for a flexible definition of end-to-end
   paths by encoding paths as sequences of topological sub-paths, called
   "segments".  These segments are advertised by routing protocols e.g.
   by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within
   IGP topologies.

   This draft defines extensions to the BGP Link-state address-family in
   order to carry segment routing information via BGP.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.