[bess] My fumbled answer :-)

"Adrian Farrel" <adrian@olddog.co.uk> Thu, 20 July 2017 14:29 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC6B126CD6 for <bess@ietfa.amsl.com>; Thu, 20 Jul 2017 07:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CHIrqU69cb_e for <bess@ietfa.amsl.com>; Thu, 20 Jul 2017 07:29:37 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D311120725 for <bess@ietf.org>; Thu, 20 Jul 2017 07:29:37 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v6KETZqk027517; Thu, 20 Jul 2017 15:29:35 +0100
Received: from 950129200 (dhcp-8d56.meeting.ietf.org [31.133.141.86]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v6KETYmc027507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jul 2017 15:29:35 +0100
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Henderickx, Wim \(Nokia - BE/Antwerp\)'" <wim.henderickx@nokia.com>
Cc: <bess@ietf.org>
Date: Thu, 20 Jul 2017 15:29:32 +0100
Message-ID: <0c4801d30164$9b4eb3a0$d1ec1ae0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdMBZIG1HJDKKBPDTTero/etpbh0xQ==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23206.007
X-TM-AS-Result: No--6.570-10.0-31-10
X-imss-scan-details: No--6.570-10.0-31-10
X-TMASE-MatchedRID: llTo18AJfvEywgv2Ga0K1KKBmXefhKfGulm2y6HpdqWKCBzmA+/wb6eV Fdx0aeyr1LPCH1Pww2F3Ujz9Y2wFbrx5piiZMGTkz5r5y9mouSCbQfYveSNCCpJ5XtPVefA98e5 o7bxlBxCvJ2px0MfWonyI5P+Rj6u04KLDX3m0YKBmVHNo7XGknRLXa2P1m93zC9/FfQ/6pO2jxY yRBa/qJX3mXSdV7KK4OubYLCVnBVEgBwKKRHe+r/CbbsAX9JbZrZcwpb1LR7hsfLqMj179LNUgU XzjqdPQU9NFqzWXJTA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/uyietjsVuxJgKNOYW8GUXqQy3SI>
Subject: [bess] My fumbled answer :-)
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:29:39 -0000

Hi Wim,

That wasn't my most glorious moment :-)

I don't think that draft-drake-bess-datacenter-gateway and
draft-ietf-idr-segment-routing-te-policy are anything other than complementary.
Nor, apparently does Eric as he is a co-author of both documents :-)

I think high-level document names can sometimes lead to some confusion, but the
combination of "BGP", "SR", and "TE" in the same overviews only goes to show
that they are in the same general space, not that they overlap.

If you take a look at draft-farrel-spring-sr-domain-interconnect-00 you'll see
it references [I-D.previdi-idr-segment-routing-te-policy] (now adopted by the
IDR working group) as the assumed mechanism for advertising intra-AS links that
are SR TE policies. We also note that
[I-D.previdi-idr-segment-routing-te-policy] offers a method for label stack
compression.

I think the two mechanisms provide different functions, but functions that could
(or even should) be integrated into a deployable solution.

Thanks (and sorry again),

Adrian