Coordinated Multicast Trees (CMT) for TRILL
draft-ietf-trill-cmt-02

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2014-03-28 (latest revision 2013-10-02)
Replaces draft-tissa-trill-cmt
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Dec 2014 - Submit Active-Active... )
Document shepherd Donald Eastlake
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL Working Group                                  Tissa Senevirathne
Internet Draft                                                    CISCO
Intended status: Standard Track                    Janardhanan Pathangi
Updates: 6325                                                      DELL
                                                             Jon Hudson
                                                                Brocade

                                                        October 2, 2013
Expires: April 2014

                Coordinated Multicast Trees (CMT) for TRILL
                        draft-ietf-trill-cmt-02.txt

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), 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/ietf/1id-abstracts.txt

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

   This Internet-Draft will expire on March 2, 2009.

Copyright Notice

   Copyright (c) 2013 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

Senevirathne            Expires April 2, 2014                  [Page 1]
Internet-Draft  Coordinated Multicast Trees for TRILL      October 2013

   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.

Abstract

   TRILL facilitates loop free connectivity to non-TRILL legacy
   networks via choice of an Appointed Forwarder for a set of VLANs.
   Appointed Forwarder provides load sharing based on VLAN with an
   active-standby model. Mission critical operations such as High
   Performance Data Centers require active-active load sharing model.
   Active-Active load sharing model can be accomplished by representing
   any given non-TRILL legacy network with a single virtual RBridge.
   Virtual representation of the non-TRILL legacy network with a single
   RBridge poses serious challenges in multi-destination RPF (Reverse
   Path Forwarding) check calculations. This document specifies
   required enhancements to build Coordinated Multicast Trees (CMT)
   within the TRILL campus to solve related RPF issues. CMT provides
   flexibility to RBridges in selecting  desired path of association to
   a given TRILL multi-destination distribution tree.

Table of Contents

   1. Introduction...................................................3
      1.1. Scope and Applicability...................................5
      1.2. Contributors..............................................5
   2. Conventions used in this document..............................5
      2.1. Acronyms..................................................5
   3. The AFFINITY sub-TLV...........................................6
   4. Multicast Tree Construction and Use of Affinity Sub-TLV........6
      4.1. Update to RFC 6325........................................7
      4.2. Announcing virtual RBridge nickname.......................8
      4.3. Affinity Sub-TLV Capability...............................8
   5. Theory of operation............................................9
      5.1. Distribution Tree provisioning............................9
      5.2. Affinity Sub-TLV advertisement............................9
      5.3. Affinity sub-TLV conflict resolution......................9
      5.4. Ingress Multi-Destination Forwarding.....................10
         5.4.1. Forwarding when n < k...............................10
      5.5. Egress Multi-Destination Forwarding......................11
         5.5.1. Traffic Arriving on an assigned Tree to RBk-RBv.....11
         5.5.2. Traffic Arriving on other Trees.....................11
      5.6. Failure scenarios........................................11
         5.6.1. Edge RBridge RBk failure............................11

Senevirathne            Expires April 2, 2014                  [Page 2]
Show full document text