IETF Logo Mail Archive

[bess] New version of draft-ietf-bess-datacenter-gateway

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 20 August 2019 11:11 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 6AE271200FD for <bess@ietfa.amsl.com>; Tue, 20 Aug 2019 04:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 YGAhbpjX1NiK for <bess@ietfa.amsl.com>; Tue, 20 Aug 2019 04:11:30 -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 2130F1200EB for <bess@ietf.org>; Tue, 20 Aug 2019 04:11:29 -0700 (PDT)
Received: from vs3.iomartmail.com (vs3.iomartmail.com [10.12.10.124]) by mta7.iomartmail.com (8.14.4/8.14.4) with ESMTP id x7KBBRnK000823 for <bess@ietf.org>; Tue, 20 Aug 2019 12:11:27 +0100
Received: from vs3.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 99FD722044 for <bess@ietf.org>; Tue, 20 Aug 2019 12:11:27 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs3.iomartmail.com (Postfix) with ESMTPS id 8ECB722042 for <bess@ietf.org>; Tue, 20 Aug 2019 12:11:27 +0100 (BST)
Received: from LAPTOPK7AS653V ([84.93.32.52]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x7KBBQWQ008044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <bess@ietf.org>; Tue, 20 Aug 2019 12:11:27 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: bess@ietf.org
Date: Tue, 20 Aug 2019 12:11:25 +0100
Organization: Old Dog Consulting
Message-ID: <005d01d55748$02e1ec40$08a5c4c0$@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: AdVXSAGjXBFnZmFqQ2qHkhtP6esXAg==
Content-Language: en-gb
X-Originating-IP: 84.93.32.52
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-24858.006
X-TM-AS-Result: No--22.154-10.0-31-10
X-imss-scan-details: No--22.154-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24858.006
X-TMASE-Result: 10--22.154300-10.000000
X-TMASE-MatchedRID: rrrXSZHbkUDzm/7LINKYQAGdJZ3Knh6hQfblIp3oBdEutoY2UtFqGLCi F7bX+Qs8wc/WHbbhIExudzO08+xOq16roberhuTgnMQdNQ64xfdReWnUUdhI9Z3ls77dbPaIW2g 2r2LI8m2Sb+WUlQg1tb1N5qQ8pGX99le5XmUu9sBO8qlnOXFSzzTQRbVRBkx9ckmGbcDQFh/zw9 wqo6kGZuLSNL7FuDTO6vjXXYVj0zYXH4phgRPpMMmR5yDJkPg4o1bhZ4v5q67uWp2q+W6jbuZ+K lU34IKpVcPBio8j8LTjWGiWQWQVulJz/z7c1mMC96PFswJ1cKinzCrx7ZPUBbKeTtOdjMy6Xlv1 quex2vPxUWs7p13xQoDGySr3NZUto6lLLG1MuSEqeOPg/O5Bhw5k1ea+clp6uhsYdHl6O2veA4v vVAfJy4jM/UH+isikR9eR7TRsHPqQb9DdKFMMTtMrcx6d6fiW4NNiN6MhlPBTq//rncsNWcwh56 Hz+25DMlUQ3EAWuyD+xHGVrWDRPTEgS+x5UNAatT4jIeGRd/UHgh3sKJBzP5u6++Cllkj5x5rrW kzA12Tp1b7KiZSVPhVCpTodm0dLfDDFL+oKuV48FYXQ7T7bc7kjcmSnmog+pjtcfbwefVGjxYyR Ba/qJX3mXSdV7KK4uPItwmogb15TptoDfp6JrMRB0bsfrpPIqxB32o9eGclVaBFytIQUtw==
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/TVtemlylnHEhlxjus0e37cZ-5wM>
Subject: [bess] New version of draft-ietf-bess-datacenter-gateway
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, 20 Aug 2019 11:11:32 -0000

Hi Bess,

This revision is mainly a keep-alive, but I did fix an (embarrassing) bug in
the name of the IANA registry.

Thanks,
Adrian

-----Original Message-----
From: BESS <bess-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: 20 August 2019 12:09
To: i-d-announce@ietf.org
Cc: bess@ietf.org
Subject: [bess] I-D Action: draft-ietf-bess-datacenter-gateway-03.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-03.txt
	Pages           : 12
	Date            : 2019-08-20

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

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


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