[trill] FW: New Version Notification for draft-yizhou-trill-tc-awareness-01.txt

Yizhou Li <liyizhou@huawei.com> Tue, 23 October 2012 00:58 UTC

Return-Path: <liyizhou@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D23521F0C51 for <trill@ietfa.amsl.com>; Mon, 22 Oct 2012 17:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c43OMc8ABKcu for <trill@ietfa.amsl.com>; Mon, 22 Oct 2012 17:58:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 788211F0C5F for <trill@ietf.org>; Mon, 22 Oct 2012 17:58:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKV72603; Tue, 23 Oct 2012 00:58:13 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 01:58:07 +0100
Received: from SZXEML424-HUB.china.huawei.com (10.82.67.163) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 08:58:12 +0800
Received: from l63746 (10.138.122.33) by smtpscn.huawei.com (10.82.67.163) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 23 Oct 2012 08:58:09 +0800
From: Yizhou Li <liyizhou@huawei.com>
To: trill@ietf.org
Date: Tue, 23 Oct 2012 08:58:09 +0800
Message-ID: <01c201cdb0b9$7845a180$68d0e480$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac2wGYB9hWtN5OqXQlyz4g2Dn5uS+QAn32Aw
Content-Language: zh-cn
X-Originating-IP: [10.138.122.33]
X-CFilter-Loop: Reflected
Subject: [trill] FW: New Version Notification for draft-yizhou-trill-tc-awareness-01.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 00:58:15 -0000

Hi,

We have posted an updated version of STP topology change awareness by RBridge draft. It incorporated the comments from last meeting.

Your review and feedback are appreciated.

Yizhou

-----Original Message-----
From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
Sent: Monday, October 22, 2012 1:53 PM
To: liyizhou@huawei.com
Cc: anoop@duke.alumni.duke.edu; haoweiguo@huawei.com; naveen@broadcom.com
Subject: New Version Notification for draft-yizhou-trill-tc-awareness-01.txt


A new version of I-D, draft-yizhou-trill-tc-awareness-01.txt
has been successfully submitted by Yizhou Li and posted to the
IETF repository.

Filename:	 draft-yizhou-trill-tc-awareness
Revision:	 01
Title:		 Aware Spanning Tree Topology Change on RBridges
Creation date:	 2012-10-21
WG ID:		 Individual Submission
Number of pages: 14
URL:             http://www.ietf.org/internet-drafts/draft-yizhou-trill-tc-awareness-01.txt
Status:          http://datatracker.ietf.org/doc/draft-yizhou-trill-tc-awareness
Htmlized:        http://tools.ietf.org/html/draft-yizhou-trill-tc-awareness-01
Diff:            http://www.ietf.org/rfcdiff?url2=draft-yizhou-trill-tc-awareness-01

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.

                                                                                  


The IETF Secretariat