Problem Statement: TRILL Active/Active Edge
draft-zhang-trill-aggregation-03

INTERNET-DRAFT                                              Mingui Zhang
Intended Status: Proposed Standard                       Donald Eastlake
Expires: August 22, 2013                                          Huawei
                                                       February 18, 2013

              Problem Statement: TRILL Active/Active Edge
                  draft-zhang-trill-aggregation-03.txt

Abstract

   This document specifies TRILL active/active edge which allows
   multiple RBridges concurrently forward data frames of the same VLAN
   on links bundled by Link Aggregation. With this kind of connection,
   end nodes may increase the bandwidth and reliability of the access at
   the edge of TRILL campuses. It's required that no loop or duplication
   is caused by this new connection type. Besides this basic
   requirement, this document outlines other potential issues associated
   with TRILL active/active edge and investigates how these issues may
   be addressed.

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) 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
 

Mingui Zhang, et al     Expires August 22, 2013                 [Page 1]
INTERNET-DRAFT          TRILL Active/Active Edge       February 18, 2013

   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. Acronyms and Terminology  . . . . . . . . . . . . . . . . . . .  3
     2.1. Acronyms  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   3. Overview  . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4. Frame Processing  . . . . . . . . . . . . . . . . . . . . . . .  6
     4.1. Unicast Ingressing  . . . . . . . . . . . . . . . . . . . .  6
     4.2. Unicast Egressing . . . . . . . . . . . . . . . . . . . . .  6
     4.3. Multicast Ingressing  . . . . . . . . . . . . . . . . . . .  6
     4.4. Multicast Egressing . . . . . . . . . . . . . . . . . . . .  6
   5. DRB and Pseudonode  . . . . . . . . . . . . . . . . . . . . . .  7
   6. MAC Addresses Sharing . . . . . . . . . . . . . . . . . . . . .  8
   7. Failures and Self-healing . . . . . . . . . . . . . . . . . . .  9
     7.1. Link Failure  . . . . . . . . . . . . . . . . . . . . . . .  9
     7.2. Node Failure  . . . . . . . . . . . . . . . . . . . . . . .  9
   8. Reverse Path Forwarding Check . . . . . . . . . . . . . . . . .  9
   9. Security Considerations . . . . . . . . . . . . . . . . . . . . 11
   10. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     11.1. Normative References . . . . . . . . . . . . . . . . . . . 11
     11.2. Informative References . . . . . . . . . . . . . . . . . . 11
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

 

Mingui Zhang, et al     Expires August 22, 2013                 [Page 2]
INTERNET-DRAFT          TRILL Active/Active Edge       February 18, 2013

1. Introduction

   TRILL makes use of the ISIS link state routing to provide least cost
   paths between TRILL switches (a.k.a. Routing Bridge, RBridge). When a
   multi-access LAN link connects end-stations to multiple RBridges, a
   single RBridge has to be appointed as the frame forwarder for each