Data Center Interconnect using TRILL
draft-ietf-trill-dci-02

Document Type Active Internet-Draft (trill WG)
Last updated 2017-02-28
Replaces draft-muks-trill-dci
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Susan Hares
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Susan Hares" <shares@ndzh.com.>
INTERNET-DRAFT                                            Mohammed Umair
Intended Status: Informational                  Kingston Smiler Selvaraj
                                                    Shaji Ravindranathan
                                                              IPInfusion
                                                               Lucy Yong
                                                     Donald Eastlake 3rd
                                                     Huawei Technologies
Expires: September 2, 2017                                 March 1, 2017

                 Data Center Interconnect using TRILL 
                     <draft-ietf-trill-dci-02.txt>

Abstract

   This document describes a TRILL based Data Center Interconnect (DCI)
   solution. TRILL is used inside a data center for providing intra-data
   center switching optimally by utilizing multiple links. This draft
   described a way to use TRILL to extend a network across different
   data center via MPLS service provider network using Virtual TRILL
   Service/Switch Domain (VTSD) as described in draft [VTSD]. 

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors. All rights reserved.
 

M.Umair, K.Smiler, et al.Expires September 2, 2017              [Page 1]
INTERNET DRAFT    Data Center Interconnect using TRILL     March 1, 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Date Center Topology . . . . . . . . . . . . . . . . . . . . .  7
   3.  Requirements of DCI Protocol . . . . . . . . . . . . . . . . .  7
     3.1.  Multi-homing with all-active forwarding  . . . . . . . . .  8
     3.2.  Effectively scaling the bandwidth by adding more links . .  8
     3.3.  Auto-discovery of services . . . . . . . . . . . . . . . .  9
     3.4.  Delivering Layer 2 and Layer 3 services over the same 
           interface  . . . . . . . . . . . . . . . . . . . . . . . .  9
     3.5.  BUM traffic optimization . . . . . . . . . . . . . . . . .  9
     3.6.  Control plane learning of MAC  . . . . . . . . . . . . . . 10
     3.7.  Virtualisation and isolation of different instances  . . . 10
     3.8.  MAC mass-withdrawal  . . . . . . . . . . . . . . . . . . . 10
     3.9.  Significantly larger Name-Space in the Overlay (16M 
           segments)  . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.10.  Extensive OAM Capabilities  . . . . . . . . . . . . . . . 11
     3.11.  Supporting Ring topology in the Core Network  . . . . . . 11
   4.  TRILL DCI Operations . . . . . . . . . . . . . . . . . . . . . 11
     4.1. TRILL data center . . . . . . . . . . . . . . . . . . . . . 12
     4.2. Layer2 data center  . . . . . . . . . . . . . . . . . . . . 12
       4.2.1.  TRILL Access load-balancing  . . . . . . . . . . . . . 13
         4.2.1.1.  Appointed Forwarder Mechanism  . . . . . . . . . . 13
         4.2.1.2.  TRILL Active-Active Access . . . . . . . . . . . . 13
       4.2.2. TRILL Pseudowire load-balancing . . . . . . . . . . . . 14
   5. MPLS encapsulation and Loop free provider PSN/MPLS  . . . . . . 15
   6. Frame Processing  . . . . . . . . . . . . . . . . . . . . . . . 15
     6.1. Frame processing between data center T2 switch and TIR. . . 15
     6.2. Frame processing between TIR's  . . . . . . . . . . . . . . 16
Show full document text