datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Aware Spanning Tree Topology Change on RBridges
draft-yizhou-trill-tc-awareness-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-11-21
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

TRILL Working Group                                          Yizhou Li
Internet Draft                                              Weiguo Hao
Intended status: Standards Track                   Huawei Technologies
                                                            Jon Hudson
                                                               Brocade
                                                          Naveen Nimmu
                                                              Broadcom
                                                        Anoop Ghanwani
                                                                  DELL

Expires: May 25, 2014                                November 21, 2013

              Aware Spanning Tree Topology Change on RBridges
                  draft-yizhou-trill-tc-awareness-03.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 May 21, 2009.

Copyright Notice

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

Li, et al.              Expires May 25, 2014                  [Page 1]
Internet-Draft      STP Topology Change Awareness        November 2013

   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.

Abstract

   When a local LAN running spanning tree protocol connecting to TRILL
   campus via more than one RBridge, there are several ways to perform
   loop avoidance. One of them illustrated by RFC6325 [RFC6325] A.3 was
   to make relevant ports on edge RBridges involving in spanning tree
   calculation. When edge RBridges are emulated as a single highest
   priority root, the local bridged LAN will be naturally partitioned
   after running spanning tree protocol. This approach achieves better
   link utilization and intra-VLAN load balancing in some scenarios.
   This document describes how the edge RBridges react to topology
   change occurring in bridged LAN in order to make the abovementioned
   spanning tree approach function correct.

Table of Contents

   1. Introduction ............................................. 3
      1.1. Motivations ......................................... 5
   2. Conventions used in this document ........................ 6
   3. BPDU RBridge Channel and TLVs ............................ 6
      3.1. BPDU TLV ............................................ 7
      3.2. Authentication Information TLV ...................... 7
   4. Operations ............................................... 8
      4.1. Sending BPDU using RBridge channel .................. 9
      4.2. Receiving BPDU in RBridge channel................... 10
      4.3. Informing the remote site .......................... 11
   5. Security Considerations ................................. 13
   6. IANA Considerations ..................................... 13
   7. References .............................................. 13
      7.1. Normative References ............................... 13
      7.2. Informative References.............................. 14
   8. Acknowledgments ......................................... 14

Li, et al.              Expires May 21, 2014                  [Page 2]
Internet-Draft      STP Topology Change Awareness        November 2013

1. Introduction

   The TRILL protocol [RFC6325] provides the appointed forwarder
   mechanism [RFC6439] for loop avoidance where, for part of the loop,
   the frame would be in TRILL encapsulated format, for example in the

[include full document text]