Re: [trill] Any comments on Coordinated Multicast Trees (CMT) for TRILL - draft-ietf-trill-cmt-00

liao.ting@zte.com.cn Thu, 16 August 2012 08:40 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 0770A21F84B6; Thu, 16 Aug 2012 01:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.635
X-Spam-Level:
X-Spam-Status: No, score=-97.635 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_DOUBLE_IP_LOOSE=0.76, 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 cUp2r2DpgIWO; Thu, 16 Aug 2012 01:40:42 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id BDC8621F856D; Thu, 16 Aug 2012 01:40:37 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 107231455586978; Thu, 16 Aug 2012 16:26:48 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 67006.2396507873; Thu, 16 Aug 2012 16:40:21 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q7G8eP35042534; Thu, 16 Aug 2012 16:40:25 +0800 (GMT-8) (envelope-from liao.ting@zte.com.cn)
In-Reply-To: <502C1EA0.7050305@acm.org>
To: Erik Nordmark <nordmark@acm.org>
MIME-Version: 1.0
X-KeepSent: AD84654D:B1E3EDC6-48257A5C:002E0F85; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFAD84654D.B1E3EDC6-ON48257A5C.002E0F85-48257A5C.002FA5A0@zte.com.cn>
From: liao.ting@zte.com.cn
Date: Thu, 16 Aug 2012 16:40:16 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-08-16 16:40:07, Serialize complete at 2012-08-16 16:40:07
Content-Type: multipart/alternative; boundary="=_alternative 002FA59D48257A5C_="
X-MAIL: mse01.zte.com.cn q7G8eP35042534
Cc: trill-bounces@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] Any comments on Coordinated Multicast Trees (CMT) for TRILL - draft-ietf-trill-cmt-00
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: Thu, 16 Aug 2012 08:40:43 -0000

I have read this draft and have a question about section 5.1, 
it describes how to distribute the trees among edge RB members of a group 
as follow:
     Assign each tree to RBi such that tree number { (tree_number) %
     k}+1 is assigned to RBridge i for tree_number from 1 to n. where n
     is the number of trees and k is the number of RBridges considered
     for tree allocation.

And in RFC 6325 section 4.5 describes:
   a good choice is the tree whose root is least cost
   from the ingress RBridge and that is the default for an ingress
   RBridge that uses a single tree to distribute multi-destination
   frames.

So, if a network has two trees, the first tree root is RBi and the second 
tree root is RBj,
a group has two member RBridges RB1 and RB2, numerically ascending order 
by SystemID such that RB1<RB2,
RBi is assigned to RB1 and RBj is assigned to RB2 as described in this 
draft, 
but maybe RB1 is closer to RBj and RB2 is closer to RBi, does the solution 
care about this?




Erik Nordmark <nordmark@acm.org> 
发件人:  trill-bounces@ietf.org
2012-08-16 06:11

收件人
"trill@ietf.org" <trill@ietf.org>
抄送

主题
[trill] Any comments on Coordinated Multicast Trees (CMT) for TRILL     - 
draft-ietf-trill-cmt-00







We are trying to understand if this document is getting close to WG last 
call, but we don't know how many have read the document.

If you have reviewed the document, please let us know.
If not, this might be a good time to review the document and provide 
comments.

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