Last Call: <draft-ietf-bess-datacenter-gateway-10.txt> (Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 15 April 2021 12:58 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-bess-datacenter-gateway-10.txt> (Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection) to Proposed Standard
Auto-Submitted: auto-generated
Precedence: bulk
CC: Matthew Bocci <matthew.bocci@nokia.com>, bess-chairs@ietf.org, bess@ietf.org, draft-ietf-bess-datacenter-gateway@ietf.org, martin.vigoureux@nokia.com, matthew.bocci@nokia.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161849148873.28716.13231913918657893460@ietfa.amsl.com>
Date: Thu, 15 Apr 2021 05:58:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MPr9iH23WFZWCKBOJxIPLPhn8_Y>

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-10.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 2021-04-29. 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.

Last Call: <draft-ietf-bess-datacenter-gateway-10… The IESG