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

Alvaro Retana <> Wed, 03 April 2019 21:26 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 78F35120048; Wed, 3 Apr 2019 14:26:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eu8ucWPnPr3r; Wed, 3 Apr 2019 14:26:22 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::333]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EBD7612018E; Wed, 3 Apr 2019 14:26:21 -0700 (PDT)
Received: by with SMTP id u15so344879otq.10; Wed, 03 Apr 2019 14:26:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=5Gp69vhJOgHZGy+Z5wAJBcn6AYIHehNWpbpQ31+R4Os=; b=A1oOokS3awow8LNvRHAQmf0lxeksA5WRiaS3aNCRb27LQWuuNvqH1B0hv/29DnNfWx eXM/+SVRkC765N2B333Vjp7J2GQGyAsXJhijM1x10wIw1yh3h13HIN7iyqodJXXI6Qf+ LtBJ5ePUFEwj6+f/23tnfX+AlXHmBX/RtJZ6KpmGvMNcj7jOmCAGuYoYHt1qbtHBQy9X LR74HlwM+Vjrw9XNnL1eF8yfpKPPE8UCMbR/Fb6aJ8fc/DtOvtdP3zY+jsmC7T3UeK8p FUcTeR/eH3C9OCBTi+JuBbUQX8daCls0iITS2MaD+MLyC2QFscW+Ac3ocQ72Q4vaMNA8 iTYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=5Gp69vhJOgHZGy+Z5wAJBcn6AYIHehNWpbpQ31+R4Os=; b=Mr0Y5roOmwkua+tBeAQXZ765f707sDGz638NrG1f72imfQYRv4cAb8bdcCPe7SwllA LYm2UBHxG68xtnTnbPHe0GAm/e4o0FNQlIJYdEyXzbKT3mbQXxQQHmZOAj7y7J5FNAsA DoHaBDsbOql3AGBhvEI5T4oSNfW/XeXvmlHxWUCUewXE3enqQxRQFoYdOq1eAD1i3B9l 2fY8WyHxpFBl2uuHRk4HbRKGd+/S4+8ZN0jBe0CaH0K/0YMFVzH9S1Yh//e8WMGiUGPC hOVyK2rhD/QGRqYlYrGpbgb1CrGLFK0em0OFLtD/E30Coh56LOW9hKschX7L9P6jc+qD 8Tfw==
X-Gm-Message-State: APjAAAXFVkSyJ8vchOCUSgIV8xN9f0+y/axdtxfUDKsGBPPlr6esX1/q ZImhl8I2ysj1eksWOM/jPQeLYt1LCmhTdVoTn+7NpA==
X-Google-Smtp-Source: APXvYqwrkn+w+trwBVXQaluhdUIVbm8ildKFwIpqAyK1nWSozEl+6+b7qjb+B9XA3HJKoBEND7zGtMIpUoRHIzgI2bo=
X-Received: by 2002:a9d:30d8:: with SMTP id r24mr1581410otg.100.1554326781184; Wed, 03 Apr 2019 14:26:21 -0700 (PDT)
Received: from 1058052472880 named unknown by with HTTPREST; Wed, 3 Apr 2019 14:26:20 -0700
From: Alvaro Retana <>
In-Reply-To: <>
References: <>
MIME-Version: 1.0
Date: Wed, 03 Apr 2019 14:26:20 -0700
Message-ID: <>
Cc: Susan Hares <>,,,
Content-Type: multipart/alternative; boundary="000000000000a851ba0585a6e72c"
Archived-At: <>
Subject: Re: [Idr] 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-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Apr 2019 21:26:25 -0000


On April 3, 2019 at 12:30:39 PM, The IESG ( wrote:

The IESG has received a request from the Inter-Domain Routing WG (idr) to
consider the following document: - 'BGP-LS extensions for Segment Routing
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 mailing lists by 2019-04-17. Exceptionally, comments may be
sent to instead. In either case, please retain the beginning
the Subject line to allow automated sorting.


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

IESG discussion can be tracked via

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