BGP-Prefix Segment in large-scale data centers
draft-ietf-spring-segment-routing-msdc-05

Document Type Active Internet-Draft (spring WG)
Last updated 2017-06-20
Replaces draft-filsfils-spring-segment-routing-msdc
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Bruno Decraene
Shepherd write-up Show (last changed 2017-03-13)
IESG IESG state Publication Requested
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alvaro Retana
Send notices to (None)
Network Working Group                                   C. Filsfils, Ed.
Internet-Draft                                           S. Previdi, Ed.
Intended status: Informational                       Cisco Systems, Inc.
Expires: December 22, 2017                                   J. Mitchell
                                                            Unaffiliated
                                                                E. Aries
                                                        Juniper Networks
                                                             P. Lapukhov
                                                                Facebook
                                                           June 20, 2017

             BGP-Prefix Segment in large-scale data centers
               draft-ietf-spring-segment-routing-msdc-05

Abstract

   This document describes the motivation and benefits for applying
   segment routing in BGP-based large-scale data-centers.  It describes
   the design to deploy segment routing in those data-centers, for both
   the MPLS and IPv6 dataplanes.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 http://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 December 22, 2017.

Filsfils, et al.        Expires December 22, 2017               [Page 1]
Internet-Draft      BGP-Prefix SID in large-scale DCs          June 2017

Copyright Notice

   Copyright (c) 2017 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
   (http://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.  Large Scale Data Center Network Design Summary  . . . . . . .   3
     2.1.  Reference design  . . . . . . . . . . . . . . . . . . . .   4
   3.  Some open problems in large data-center networks  . . . . . .   5
   4.  Applying Segment Routing in the DC with MPLS dataplane  . . .   6
     4.1.  BGP Prefix Segment (BGP-Prefix-SID) . . . . . . . . . . .   6
     4.2.  eBGP Labeled Unicast (RFC3107)  . . . . . . . . . . . . .   7
       4.2.1.  Control Plane . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Data Plane  . . . . . . . . . . . . . . . . . . . . .   9
       4.2.3.  Network Design Variation  . . . . . . . . . . . . . .  10
       4.2.4.  Global BGP Prefix Segment through the fabric  . . . .  10
       4.2.5.  Incremental Deployments . . . . . . . . . . . . . . .  11
     4.3.  iBGP Labeled Unicast (RFC3107)  . . . . . . . . . . . . .  12
   5.  Applying Segment Routing in the DC with IPv6 dataplane  . . .  14
   6.  Communicating path information to the host  . . . . . . . . .  14
   7.  Addressing the open problems  . . . . . . . . . . . . . . . .  15
     7.1.  Per-packet and flowlet switching  . . . . . . . . . . . .  15
     7.2.  Performance-aware routing . . . . . . . . . . . . . . . .  16
     7.3.  Deterministic network probing . . . . . . . . . . . . . .  17
   8.  Additional Benefits . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  MPLS Dataplane with operational simplicity  . . . . . . .  18
     8.2.  Minimizing the FIB table  . . . . . . . . . . . . . . . .  18
     8.3.  Egress Peer Engineering . . . . . . . . . . . . . . . . .  18
     8.4.  Anycast . . . . . . . . . . . . . . . . . . . . . . . . .  19
   9.  Preferred SRGB Allocation . . . . . . . . . . . . . . . . . .  19
Show full document text