Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection
draft-drake-bess-datacenter-gateway-05

Document Type Replaced Internet-Draft (bess WG)
Last updated 2017-10-27 (latest revision 2017-09-19)
Replaced by draft-ietf-bess-datacenter-gateway
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-bess-datacenter-gateway
Consensus Boilerplate Unknown
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-05.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. 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.

Authors

John Drake (jdrake@juniper.net)
Adrian Farrel (afarrel@juniper.net)
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.)