Gateway Auto-Discovery and Route Advertisement for Segment Routing Enabled Domain Interconnection
draft-ietf-bess-datacenter-gateway-09
BESS Working Group A. Farrel
Internet-Draft Old Dog Consulting
Intended status: Standards Track J. Drake
Expires: July 9, 2021 E. Rosen
Juniper Networks
K. Patel
Arrcus, Inc.
L. Jalil
Verizon
January 5, 2021
Gateway Auto-Discovery and Route Advertisement for Segment Routing
Enabled Domain Interconnection
draft-ietf-bess-datacenter-gateway-09
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.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Farrel, et al. Expires July 9, 2021 [Page 1]
Internet-Draft SR DC Gateways January 2021
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 9, 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5
3. SR Domain Gateway Auto-Discovery . . . . . . . . . . . . . . 5
4. Relationship to BGP Link State and Egress Peer Engineering . 7
5. Advertising an SR Domain Route Externally . . . . . . . . . . 7
6. Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . 7
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
8. Security Considerations . . . . . . . . . . . . . . . . . . . 8
9. Manageability Considerations . . . . . . . . . . . . . . . . 9
9.1. Relationship to Route Target Constraint . . . . . . . . . 9
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
11.1. Normative References . . . . . . . . . . . . . . . . . . 10
11.2. Informative References . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Show full document text