IETF Logo Mail Archive

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

"Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com> Mon, 26 November 2012 15:44 UTC

Return-Path: <tsenevir@cisco.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 463EA21F85B1 for <trill@ietfa.amsl.com>; Mon, 26 Nov 2012 07:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.395
X-Spam-Level:
X-Spam-Status: No, score=-6.395 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_HI=-8]
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 aroy+lz4wkmj for <trill@ietfa.amsl.com>; Mon, 26 Nov 2012 07:44:37 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2D29021F859D for <trill@ietf.org>; Mon, 26 Nov 2012 07:44:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16226; q=dns/txt; s=iport; t=1353944677; x=1355154277; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gAPDeusfK7kcyrygJevRaNN4pf4VKkkJMqi1DPLK3nc=; b=mere+sb7vClkl6SQbDlUqtuJLosBzGlpX3m3Qk7wLMYX3O1hMwK+IKSm OcGxX9Z35TppBFVwmcWsF/H4Fn06mc4SjYD68bEd7g8U+DRZpJgw68qSb iWibo1ntDblngYLoB/ejzxpYC+NGHXf9J7nxHw7bttf1eji42G7KTXXj7 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAPiNs1CtJXG//2dsb2JhbABEgkmDX7kFdRZzgh4BAQEEAQEBKkELEAIBBgIRBAEBCwsSBQICJQsUCQgBAQQOBQiIBQytIgiSRASMN4EOghw2YQOmRYJvgh0
X-IronPort-AV: E=McAfee;i="5400,1158,6907"; a="146011950"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 26 Nov 2012 15:44:19 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id qAQFiJNj025919 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 26 Nov 2012 15:44:19 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.130]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.001; Mon, 26 Nov 2012 09:44:18 -0600
From: "Tissa Senevirathne (tsenevir)" <tsenevir@cisco.com>
To: "liao.ting@zte.com.cn" <liao.ting@zte.com.cn>
Thread-Topic: [trill] draft-ietf-trill-cmt
Thread-Index: Ac2+FF0H+VMAhVydQOe90fdycFINlgLXltQAAG52p5AAHnL5AAARf38A
Date: Mon, 26 Nov 2012 15:44:18 +0000
Message-ID: <FBEA3E19AA24F847BA3AE74E2FE1935628873461@xmb-rcd-x08.cisco.com>
References: <FBEA3E19AA24F847BA3AE74E2FE193562886B03E@xmb-rcd-x08.cisco.com> <OFEF810EE3.52F5AE7A-ON48257AC2.0005CA21-48257AC2.00074716@zte.com.cn>
In-Reply-To: <OFEF810EE3.52F5AE7A-ON48257AC2.0005CA21-48257AC2.00074716@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.119.17]
Content-Type: multipart/alternative; boundary="_000_FBEA3E19AA24F847BA3AE74E2FE1935628873461xmbrcdx08ciscoc_"
MIME-Version: 1.0
Cc: "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 15:44:38 -0000

Hi Tina

Answer is no need and it is already built in. Here is why. We propose to announce the Affinity Capability.  CMT specification is that RBridge announcing that capability must follow the specified tree allocation. If some RBridge is announcing the affinity capability and yet doing manual allocation then it is an implementation error or local policy/administrative matter.

Thanks
Tissa

From: liao.ting@zte.com.cn [mailto:liao.ting@zte.com.cn]
Sent: Sunday, November 25, 2012 5:19 PM
To: Tissa Senevirathne (tsenevir)
Cc: trill@ietf.org; trill-bounces@ietf.org
Subject: Re: [trill] draft-ietf-trill-cmt


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<mailto:tsenevir@cisco.com>>
发件人:  trill-bounces@ietf.org<mailto:trill-bounces@ietf.org>

2012-11-26 00:50

收件人

"liao.ting@zte.com.cn<mailto:liao.ting@zte.com.cn>" <liao.ting@zte.com.cn<mailto:liao.ting@zte.com.cn>>

抄送

"trill@ietf.org<mailto:trill@ietf.org>" <trill@ietf.org<mailto: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> [mailto:liao.ting@zte.com.cn]
Sent: Thursday, November 22, 2012 10:05 PM
To: Tissa Senevirathne (tsenevir)
Cc: trill@ietf.org<mailto:trill@ietf.org>; trill-bounces@ietf.org<mailto: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<mailto:trill@ietf.org>
https://www.ietf.org/mailman/listinfo/trill

v2.23.0 | Report a Bug | By Email