Re: [bess] New Version Notification for draft-ietf-bess-datacenter-gateway-11.txt

Adrian Farrel <adrian@olddog.co.uk> Wed, 19 May 2021 22: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 61EEC3A2198; Wed, 19 May 2021 15:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.051
X-Spam-Level:
X-Spam-Status: No, score=-1.051 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAY_BE_FORGED=0.846, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 JLoTB-yUcf82; Wed, 19 May 2021 15:29:19 -0700 (PDT)
Received: from mta7.iomartmail.com (mta7.iomartmail.com [62.128.193.157]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D738B3A2195; Wed, 19 May 2021 15:29:18 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id 14JMTFKe031524; Wed, 19 May 2021 23:29:15 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 497E94604B; Wed, 19 May 2021 23:29:15 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3CF9A46043; Wed, 19 May 2021 23:29:15 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs4.iomartmail.com (Postfix) with ESMTPS; Wed, 19 May 2021 23:29:15 +0100 (BST)
Received: from LAPTOPK7AS653V (65.151.51.84.dyn.plus.net [84.51.151.65] (may be forged)) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id 14JMTDJr029678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 May 2021 23:29:14 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'The IESG' <iesg@ietf.org>
Cc: bess@ietf.org, bess-chairs@ietf.org, 'Gyan Mishra' <hayabusagsm@gmail.com>, draft-ietf-bess-datacenter-gateway@ietf.org
References: <162145927693.9993.4934999663225374706@ietfa.amsl.com>
In-Reply-To:
Date: Wed, 19 May 2021 23:29:13 +0100
Organization: Old Dog Consulting
Message-ID: <050801d74cfe$6615ae20$32410a60$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQCuSp3MLeaMIbqiZw8/tUIDyqERFq09VLIQgAASY/A=
Content-Language: en-gb
X-Originating-IP: 84.51.151.65
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2034-8.6.0.1017-26168.003
X-TM-AS-Result: No--23.909-10.0-31-10
X-imss-scan-details: No--23.909-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2034-8.6.1017-26168.003
X-TMASE-Result: 10--23.908500-10.000000
X-TMASE-MatchedRID: yebcs53SkkBor4mPA3EMtnFPUrVDm6jtUd7Bjfo+5jSg9i3Io5f/AJsD hxcWKvJnHXMa97z00a9z8mPUh95Jg4KsC92uhkQmfOaYwP8dcX6M4p7EnPqPPSJcTqMCib7FSQa sdMia34IJesv4+wXIsf/bF3jI5UCzg3TczpWnIudBDn6Fjq77jqGnvnr+szpSz5ZiODdbPIpPFK 6BTThqey/D9F7ZlC5r02PVzFmzBApLwfJP5txUKsFY+9G+fhHzJih/yo+OvlUW6M2A15L1QMWw4 RsjxSGCrOOppPTYnng+a4w/i+jj3Wpe0b/o/MnFwY28o+cGA5oh/JA0dHadpjQ8uDLsJowAyd/K bG4VElv+hfO6MSmSwbi7nokIUYhscvOwC8ct4oArT6V6InEuV6ccEhvIyMIUvXjbE7bwQ96qdm0 pyBsnlrNT8povc+7RlT66WknpkfVAjTccdWiAVQzrPeIO/OIHIE/7F7Rl63+eRi5b04l62IRMyN /ppM4nQtT6w9dw4Gl6NsNc/7lLyXcSETR+ksZrhQwmwdAU7bJzmB71otxffL+Z3Zp2Td1Eqyaxu HxiXhODKydm0O6U3sa2fv38BYVK0jsAiAX+LhleYVWU5uHQ/DMGCkO64jn6hPZpQncwUfbfl0Pv qvMF9+Tk64tSPfwHr8xQtTFbZWFSi2muUIH5qyp44+D87kGHDmTV5r5yWnq6Gxh0eXo7a94Di+9 UB8nLiMz9Qf6KyKSUb6LwX8t9THDa7cTNOVY8NqGNk8Sh2Rc/Dyy30snbb8j0QMA/92m2HNvI96 cmr3fl5F+AHkFf7tfb7zy1Jn9yfDDFL+oKuV6eAiCmPx4NwKn+YfuBb3+ABTmtD+MNluqOhzOa6 g8KrZRMZUCEHkRt
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/O8m85EOyf5nFmgdQLZ5QAm6-iiE>
Subject: Re: [bess] New Version Notification for draft-ietf-bess-datacenter-gateway-11.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 May 2021 22:29:25 -0000

Dang! 
Now sending to the IESG not the Secretariat.
Adrian

-----Original Message-----
From: Adrian Farrel <adrian@olddog.co.uk> 
Sent: 19 May 2021 22:31
To: iesg-secretary@ietf.org
Cc: 'bess@ietf.org' <bess@ietf.org>; 'bess-chairs@ietf.org' <bess-chairs@ietf.org>; 'Gyan Mishra' <hayabusagsm@gmail.com>; 'draft-ietf-bess-datacenter-gateway@ietf.org' <draft-ietf-bess-datacenter-gateway@ietf.org>
Subject: FW: New Version Notification for draft-ietf-bess-datacenter-gateway-11.txt

Hi all,

This revision attempts to address John Scudder's Discuss and Comment including changes discussed by email and in person (by John Drake). It also addresses the updated version of Gyan's GenArt review comments, incorporating most of the changes he suggested in his most recent email. Thanks to John (S) and Gyan for the amount of time and effort they spent reaching resolutions with the authors - a long and somewhat bumpy road, but a better document as a result.

No changes are made for Roman's Discuss (see recent email).

I believe that Warren's Discuss is also addressed partly by answering John's Discuss, but also by the change of terminology to "site" from the incorrect "SR domain".

As noted in email, this revision fixes one grammar point (a missing comma) and fixes the two out-dated references pointed out in Lars' Comment.

Per email, Erik and Alvaro's Comments are addressed by the change in domain/site terminology.

I think the actionable parts of Eric's Comment is also handled with the text change suggested in email.

Lastly, I think Rob's Comment has been closed through email.


Please let us know if you think more action is needed.

Many thanks to you all for the time and effort you've put in to reviewing this document.

Adrian

-----Original Message-----
From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
Sent: 19 May 2021 22:21
To: Adrian Farrel <adrian@olddog.co.uk>; Eric Rosen <erosen52@gmail.com>; John Drake <jdrake@juniper.net>; Keyur Patel <keyur@arrcus.com>; Luay Jalil <luay.jalil@verizon.com>
Subject: New Version Notification for draft-ietf-bess-datacenter-gateway-11.txt


A new version of I-D, draft-ietf-bess-datacenter-gateway-11.txt
has been successfully submitted by Adrian Farrel and posted to the
IETF repository.

Name:		draft-ietf-bess-datacenter-gateway
Revision:	11
Title:		Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Site Interconnection
Document date:	2021-05-19
Group:		bess
Pages:		13
URL:            https://www.ietf.org/archive/id/draft-ietf-bess-datacenter-gateway-11.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bess-datacenter-gateway/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-bess-datacenter-gateway
Htmlized:       https://tools.ietf.org/html/draft-ietf-bess-datacenter-gateway-11
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-datacenter-gateway-11

Abstract:
   Data centers are critical components of the infrastructure used by
   network operators to provide services to their customers.  Data
   centers are attached to the Internet or a backbone network by gateway
   routers.  One data center typically has more than one gateway for
   commercial, load balancing, and resiliency reasons.

   Segment Routing is a protocol mechanism that can be used within a
   data center, and also for steering traffic that flows between two
   data center sites.  In order that one data center site may load
   balance the traffic it sends to another data center site, it needs to
   know the complete set of gateway routers at the remote data center,
   the points of connection from those gateways to the backbone network,
   and the connectivity across the backbone network.

   Other sites, such as access networks, also need to be connected
   across backbone networks through gateways.

   This document defines a mechanism using the BGP Tunnel Encapsulation
   attribute to allow each gateway router to advertise the routes to the
   prefixes reachable in the site to which it provides access, including
   advertising them on behalf of each other gateway to the same site.

                                                                                  


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat