Re: [trill] draft-ietf-trill-cmt

liao.ting@zte.com.cn Mon, 26 November 2012 01:19 UTC

Return-Path: <liao.ting@zte.com.cn>
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 7D52021F8668; Sun, 25 Nov 2012 17:19:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.753
X-Spam-Level:
X-Spam-Status: No, score=-94.753 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, MIME_BASE64_TEXT=2.796, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
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 YE0PLz4F7MTp; Sun, 25 Nov 2012 17:19:58 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 443E721F855A; Sun, 25 Nov 2012 17:19:51 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id ACB0C441443; Mon, 26 Nov 2012 09:21:19 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id C9C0217BB560; Mon, 26 Nov 2012 09:17:43 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id qAQ1JTj0070921; Mon, 26 Nov 2012 09:19:29 +0800 (GMT-8) (envelope-from liao.ting@zte.com.cn)
In-Reply-To: <FBEA3E19AA24F847BA3AE74E2FE193562886B03E@xmb-rcd-x08.cisco.com>
To: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
MIME-Version: 1.0
X-KeepSent: EF810EE3:52F5AE7A-48257AC2:0005CA21; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFEF810EE3.52F5AE7A-ON48257AC2.0005CA21-48257AC2.00074716@zte.com.cn>
From: liao.ting@zte.com.cn
Date: Mon, 26 Nov 2012 09:19:28 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-11-26 09:19:17, Serialize complete at 2012-11-26 09:19:17
Content-Type: multipart/alternative; boundary="=_alternative 0007471548257AC2_="
X-MAIL: mse01.zte.com.cn qAQ1JTj0070921
Cc: trill-bounces@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] draft-ietf-trill-cmt
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: Mon, 26 Nov 2012 01:19:58 -0000

Hi,Tissa

Yes,that's exactly what I mean. :)
Should the CMT take this scenario into account?

Thanks,
Tina



"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> 
发件人:  trill-bounces@ietf.org
2012-11-26 00:50

收件人
"liao.ting@zte.com.cn" <liao.ting@zte.com.cn>
抄送
"trill@ietf.org" <trill@ietf.org>
主题
Re: [trill] draft-ietf-trill-cmt






Hi Tina
 
I am not sure I completely understand your question. Are you referring to 
a scenario where some of the members (e.g. RB1 ) are using some manual 
configuration and other is using the proposed method (e.g. RB2) in the CMT 
draft ?
 
PS: Both RB1 and RB2 are members of the virtual RBridge RBv
 
From: liao.ting@zte.com.cn [mailto:liao.ting@zte.com.cn] 
Sent: Thursday, November 22, 2012 10:05 PM
To: Tissa Senevirathne (tsenevir)
Cc: trill@ietf.org; trill-bounces@ietf.org
Subject: Re: [trill] draft-ietf-trill-cmt
 

Hi,Tissa 

Section 5.1 provides a simple general method to assign different trees to 
different members and it is easy to employ. 
But in my opinion, it could be better to allow co-existence of default 
manner(cmt) and manual configuration 
for distribution tree choosing,otherwise if some member RBs are manually 
configured and others are not configured at all, 
compatibility problem with the current algorithm could occur. 
So, maybe we should provide a unified tree distribution method which is 
compatible 
with manual configuration and can ensure different member RBs obtain 
different  distribution tree? 

Thanks,
Tina _______________________________________________
trill mailing list
trill@ietf.org
https://www.ietf.org/mailman/listinfo/trill