Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Data Center Interconnection
draft-drake-bess-datacenter-gateway-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors John Drake  , Adrian Farrel  , Eric Rosen  , Keyur Patel  , Luay Jalil 
Last updated 2017-04-19 (latest revision 2016-10-16)
Replaced by draft-ietf-bess-datacenter-gateway
Stream (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-drake-bess-datacenter-gateway-02.txt

Abstract

Data centers have become 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 operating 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. 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 data center site to which it provides access, and also to advertise on behalf of each other gateway to the same data center site.

Authors

John Drake (jdrake@juniper.net)
Adrian Farrel (adrian@olddog.co.uk)
Eric Rosen (erosen@juniper.net)
Keyur Patel (keyur@arrcus.com)
Luay Jalil (luay.jalil@verizon.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)