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

The information below is for an old version of the document
Document Type Active Internet-Draft (spring WG)
Authors Clarence Filsfils  , Stefano Previdi  , Jon Mitchell  , Ebben Aries  , Petr Lapukhov 
Last updated 2016-04-13
Replaces draft-filsfils-spring-segment-routing-msdc
Stream IETF
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                   C. Filsfils, Ed.
Internet-Draft                                           S. Previdi, Ed.
Intended status: Informational                       Cisco Systems, Inc.
Expires: October 15, 2016                                    J. Mitchell
                                                            Unaffiliated
                                                                E. Aries
                                                             P. Lapukhov
                                                                Facebook
                                                          April 13, 2016

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

Abstract

   This document describes the motivation and benefits for applying
   segment routing in the data-center.  It describes the design to
   deploy segment routing in the data-center, 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 October 15, 2016.

Filsfils, et al.        Expires October 15, 2016                [Page 1]
Internet-Draft      BGP-Prefix SID in large-scale DCs         April 2016

Copyright Notice

   Copyright (c) 2016 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  . . . . . . . . . . . . . . . . . . .   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  . . .  12
   6.  Communicating path information to the host  . . . . . . . . .  13
   7.  Addressing the open problems  . . . . . . . . . . . . . . . .  14
     7.1.  Per-packet and flowlet switching  . . . . . . . . . . . .  14
     7.2.  Performance-aware routing . . . . . . . . . . . . . . . .  15
     7.3.  Non-oblivious routing . . . . . . . . . . . . . . . . . .  16
     7.4.  Deterministic network probing . . . . . . . . . . . . . .  16
   8.  Additional Benefits . . . . . . . . . . . . . . . . . . . . .  16
     8.1.  MPLS Dataplane with operational simplicity  . . . . . . .  16
     8.2.  Minimizing the FIB table  . . . . . . . . . . . . . . . .  17
     8.3.  Egress Peer Engineering . . . . . . . . . . . . . . . . .  17
     8.4.  Incremental Deployments . . . . . . . . . . . . . . . . .  18
     8.5.  Anycast . . . . . . . . . . . . . . . . . . . . . . . . .  18
   9.  Preferred SRGB Allocation . . . . . . . . . . . . . . . . . .  18
   10. Alternative Options . . . . . . . . . . . . . . . . . . . . .  19
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   12. Manageability Considerations  . . . . . . . . . . . . . . . .  20
Show full document text