Re: [bess] I-D Action: draft-ietf-bess-datacenter-gateway-02.txt
"Adrian Farrel" <adrian@olddog.co.uk> Tue, 26 February 2019 19:05 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 1E8D51288BD for <bess@ietfa.amsl.com>; Tue, 26 Feb 2019 11:05:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 I5wN_qWnoJpo for <bess@ietfa.amsl.com>; Tue, 26 Feb 2019 11:05:19 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (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 521CF1277CC for <bess@ietf.org>; Tue, 26 Feb 2019 11:05:19 -0800 (PST)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x1QJ5Hmm015410 for <bess@ietf.org>; Tue, 26 Feb 2019 19:05:17 GMT
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 46C1C22042 for <bess@ietf.org>; Tue, 26 Feb 2019 19:05:17 +0000 (GMT)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs1.iomartmail.com (Postfix) with ESMTPS id 3136122040 for <bess@ietf.org>; Tue, 26 Feb 2019 19:05:17 +0000 (GMT)
Received: from LAPTOPK7AS653V ([87.112.237.8]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.4/8.14.4) with ESMTP id x1QJ5Geo012887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <bess@ietf.org>; Tue, 26 Feb 2019 19:05:16 GMT
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bess@ietf.org
References: <155120766677.859.17127383839257223548@ietfa.amsl.com>
In-Reply-To: <155120766677.859.17127383839257223548@ietfa.amsl.com>
Date: Tue, 26 Feb 2019 19:05:16 -0000
Organization: Old Dog Consulting
Message-ID: <045f01d4ce06$35c36330$a14a2990$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI+xCcSX+K/BkGG58OppJyY3YGBXqUeg2tA
Content-Language: en-gb
X-Originating-IP: 87.112.237.8
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24458.001
X-TM-AS-Result: No--11.658-10.0-31-10
X-imss-scan-details: No--11.658-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24458.001
X-TMASE-Result: 10--11.658000-10.000000
X-TMASE-MatchedRID: gjZGo2H/wj/xIbpQ8BhdbOkUKYj1RzKcnJ4I+NS+sw4a/zWbQz3vDoL8 17LE9TTs7g/t+9VbXEk8kgolvDdqQ6murVLksCxGNlkA5i6kjNofOdo4H355iI5t/XRqktxJXa2 +zE1cP+VP4834tptSoEb5H/7zTJtB2bdtIO/olCK4jAucHcCqnVF5adRR2Ej12dP9ypSe+fdIy6 wlSm1KQpv2dk8cRmOJKfTYexrZ9L3VBANPT9ZmP0AvdL4TzpZNFvpGqmIVP/O77ExFvcxKEzQW+ aV0tF9eNJT/Oxw8hivtq4u3MdErWBnrFEMoRsxosyNb+yeIRAoC5AMlEyiBEmA5wZjJx9GwQW9f AKJG7FMDOgwgxb60wzFFGHGZWPw9JOn9szyfQQ1wUSK4/EeOxUDBsHf0BXCWyPRAwD/3abaDkW1 /3UqQvZWv7UXUPzhwKPxiJXXDy6F48YB5KfXbgoDqq/69HfgsD2lsxv9ktobM7zpEspqG/5hBoC A93CpD9SqedkZx0DmRk6XtYogiarQ/aqQZTRfKlsAQtLYksyuLZAVphLW/bSq2rl3dzGQ1DBbGv tcMofynayWyuG1yY1ima5Y5QtRkCG9gwc8n6fGVtZREDPeFthluWZ+j/z/1
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/6dR38DOH7HZREBe5bgYJkmXTwDk>
Subject: Re: [bess] I-D Action: draft-ietf-bess-datacenter-gateway-02.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: Tue, 26 Feb 2019 19:05:22 -0000
Hi, We let this draft expire, which is bad of us because it is a WG draft. I have woken it up, cleaned some nits, updated the references, fixed some author coordinates, and added a little Manageability text. The authors think this is pretty complete. We're wondering whether to apply for the FCFS codepoint now or let it run. Thanks, Adrian -----Original Message----- From: I-D-Announce <i-d-announce-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org Sent: 26 February 2019 19:01 To: i-d-announce@ietf.org Cc: bess@ietf.org Subject: I-D Action: draft-ietf-bess-datacenter-gateway-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the BGP Enabled ServiceS WG of the IETF. Title : Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection Authors : Adrian Farrel John Drake Eric Rosen Keyur Patel Luay Jalil Filename : draft-ietf-bess-datacenter-gateway-02.txt Pages : 12 Date : 2019-02-26 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 popular protocol mechanism for use within a data center, but 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. Segment Routing may also be operated in other domains, such as access networks. Those domains 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 in the Segment Routing domains to which it provides access, and also to advertise on behalf of each other gateway to the same Segment Routing domain. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-bess-datacenter-gateway/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-bess-datacenter-gateway-02 https://datatracker.ietf.org/doc/html/draft-ietf-bess-datacenter-gateway-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-datacenter-gateway-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
- [bess] I-D Action: draft-ietf-bess-datacenter-gat… internet-drafts
- Re: [bess] I-D Action: draft-ietf-bess-datacenter… Adrian Farrel