[Sandbox-mailoutput] [Django development] Last Call: <draft-ietf-bess-datacenter-gateway-08.txt> (Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection) to Proposed Standard

IETF Secretariat <ietf-secretariat-reply@ietf.org> Wed, 09 December 2020 19:13 UTC

Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: sandbox-mailoutput@ietfa.amsl.com
Delivered-To: sandbox-mailoutput@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBF213A1710 for <sandbox-mailoutput@ietfa.amsl.com>; Wed, 9 Dec 2020 11:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 oDZiQRq9GM-P for <sandbox-mailoutput@ietfa.amsl.com>; Wed, 9 Dec 2020 11:13:15 -0800 (PST)
Received: from mailtest.ietf.org (sandbox.ietf.org [4.31.198.57]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A74D3A107E for <sandbox-mailoutput@ietf.org>; Wed, 9 Dec 2020 11:13:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sandbox.amsl.com (Postfix) with ESMTP id 6CB7023C7 for <sandbox-mailoutput@ietf.org>; Wed, 9 Dec 2020 11:13:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at mailtest.ietf.org
Received: from mailtest.ietf.org ([4.31.198.57]) by localhost (mailtest.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ln5vWlPgggHP for <sandbox-mailoutput@ietf.org>; Wed, 9 Dec 2020 11:13:14 -0800 (PST)
Received: from sandbox.amsl.com (localhost [IPv6:::1]) by sandbox.amsl.com (Postfix) with ESMTP id AC8B323D1 for <sandbox-mailoutput@ietf.org>; Wed, 9 Dec 2020 11:13:04 -0800 (PST)
Content-Type: multipart/mixed; boundary="===============8728526150302902483=="
MIME-Version: 1.0
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: sandbox-mailoutput@ietf.org
Message-ID: <160754118469.10030.15808555182729653872@sandbox.amsl.com>
Date: Wed, 09 Dec 2020 11:13:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sandbox-mailoutput/Wzy_GpwE2gHsIB9MdNCPR-as5Mo>
Subject: [Sandbox-mailoutput] [Django development] Last Call: <draft-ietf-bess-datacenter-gateway-08.txt> (Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection) to Proposed Standard
X-BeenThere: sandbox-mailoutput@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <sandbox-mailoutput.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sandbox-mailoutput>, <mailto:sandbox-mailoutput-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sandbox-mailoutput/>
List-Post: <mailto:sandbox-mailoutput@ietf.org>
List-Help: <mailto:sandbox-mailoutput-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sandbox-mailoutput>, <mailto:sandbox-mailoutput-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Dec 2020 19:13:18 -0000

The attached message would have been sent, but the tracker is in development mode.
It was not sent to anybody.

--- Begin Message ---
The IESG has received a request from the BGP Enabled ServiceS WG (bess) to
consider the following document: - 'Gateway Auto-Discovery and Route
Advertisement for Segment Routing
   Enabled Domain Interconnection'
  <draft-ietf-bess-datacenter-gateway-08.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-12-23. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-bess-datacenter-gateway/



No IPR declarations have been submitted directly on this I-D.




--- End Message ---