IETF Logo Mail Archive

[bess] New version: draft-ietf-bess-datacenter-gateway-07.txt

Adrian Farrel <adrian@olddog.co.uk> Thu, 04 June 2020 17:34 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 1C6763A0959 for <bess@ietfa.amsl.com>; Thu, 4 Jun 2020 10:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 Qqf0nd1rY1Oe for <bess@ietfa.amsl.com>; Thu, 4 Jun 2020 10:34:54 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (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 357833A07C4 for <bess@ietf.org>; Thu, 4 Jun 2020 10:34:47 -0700 (PDT)
Received: from vs1.iomartmail.com (vs1.iomartmail.com [10.12.10.121]) by mta6.iomartmail.com (8.14.4/8.14.4) with ESMTP id 054HYinw009438 for <bess@ietf.org>; Thu, 4 Jun 2020 18:34:44 +0100
Received: from vs1.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 13ADC2203B for <bess@ietf.org>; Thu, 4 Jun 2020 18:34:44 +0100 (BST)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs1.iomartmail.com (Postfix) with ESMTPS id F318B2203A for <bess@ietf.org>; Thu, 4 Jun 2020 18:34:43 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.26.18]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.4/8.14.4) with ESMTP id 054HYgE2018377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <bess@ietf.org>; Thu, 4 Jun 2020 18:34:43 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bess@ietf.org
Date: Thu, 04 Jun 2020 18:34:42 +0100
Organization: Old Dog Consulting
Message-ID: <07d001d63a96$6f375150$4da5f3f0$@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: AdY6lm1YDwTHUbUERMyUEweR/nt78A==
Content-Language: en-gb
X-Originating-IP: 84.93.26.18
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-25462.000
X-TM-AS-Result: No--20.961-10.0-31-10
X-imss-scan-details: No--20.961-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-25462.000
X-TMASE-Result: 10--20.960800-10.000000
X-TMASE-MatchedRID: gCRQGm5UnaIZnuop9luYIDjNGpWCIvfTmxawpTnIv8ZS4PwzM2cbynGC PAh3PmLXYqalFk63HxRfm9XiDIhx1Anj0ajmyPNXDHEg6thbROwZskwWqoib3AbYcy9YQl6eF4B 4/yr5wlQCQ+noxLcPebRYyCSqCpPEyFEagTkCB1vylEfNwb6iLdruvqDzHUPufFsdJbvlSy1PNU GtG9S9hVRgRLfJEqFmvMiPJvFUb7x7e0sj3KOOTOPEkNSS7Y82vGXWWL+M265snR1RUJec9Bpuc UfHeAYFC3M0Nop1pz1nTn0ACasPXP1J/npx6lG1KNfRqDeFqBgYZdGd023v1aQx27RNqoVZW984 V9dpS5AwyHC4Z3Gwzku9yaCA0I5AGfYgPRRDIAZ0Uibeis6dELp+dd7207HmJmE4A+qD79lsLE1 h1tIOy39cUrfwKRxzV69MegT7Z05F7tQ1gvMOS4t6hZFSx91Az3/zJxxP73sy/xh6GqNHVT5STh KV5SgZ6f6eicG50XMVjM0uOpSYeVUsRs8270qXUlu/qwZkdip1zSnwpu89beglv7If8NikhzgLH qCMyqhy2C3A2jRkA5QRNwiwHN0neIOkiRjB5UC8coKUcaOOvVNvMDULT5hzWoQBC/aPk1v3G7Vl vlXNS1qDx2d603z4aK8uWXuH4d1Nfs8n85Te8v7E6GNqs6ce1xY1KATsZBqw7M6dyuYKg/cUt5l c1lLgtT4piLWpY7p+3BndfXUhXQ==
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/X-avSnALTg7F5x0ZnTht_5_noUI>
Subject: [bess] New version: draft-ietf-bess-datacenter-gateway-07.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: Thu, 04 Jun 2020 17:34:56 -0000

Hi,

This late-breaking revision just tweaks for the discussion with Boris.

Thanks,
Adrian

-----Original Message-----
From: BESS <bess-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 04 June 2020 18:33
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Subject: [bess] I-D Action: draft-ietf-bess-datacenter-gateway-07.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-07.txt
	Pages           : 12
	Date            : 2020-06-04

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.

   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-07
https://datatracker.ietf.org/doc/html/draft-ietf-bess-datacenter-gateway-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-datacenter-gateway-07


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/


_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

v2.23.0 | Report a Bug | By Email