Re: [rbridge] Last Call: draft-ietf-trill-routing-reqs (TRILL Routing Requirements in Support of RBridges) to Informational RFC
caowayne <caowayne@huawei.com> Thu, 22 March 2007 11:27 UTC
Return-path: <ietf-announce-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HULSZ-0007Ex-G8; Thu, 22 Mar 2007 07:27:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTz3u-0002Uo-A0; Wed, 21 Mar 2007 07:33:02 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTz3L-0000cj-Hq; Wed, 21 Mar 2007 07:33:02 -0400
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0JF900C7I3OCG1@szxga03-in.huawei.com>; Wed, 21 Mar 2007 19:24:12 +0800 (CST)
Received: from jys6053946 (dhcp-4009.ietf68.org [130.129.64.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0JF900L4H3NHBG@szxga03-in.huawei.com>; Wed, 21 Mar 2007 19:24:12 +0800 (CST)
Date: Wed, 21 Mar 2007 19:23:31 +0800
From: caowayne <caowayne@huawei.com>
To: "Eric Gray (LO/EUS)" <eric.gray@ericsson.com>, Dinesh G Dutt <ddutt@cisco.com>, ietf@ietf.org
Message-id: <009101c76bab$63717cb0$fa01000a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
X-Priority: 3
X-MSMail-priority: Normal
References: <E1HSKM4-0001KO-4Q@stiedprstage1.ietf.org> <46009976.5030007@cisco.com> <941D5DCD8C42014FAF70FB7424686DCF9EAE91@eusrcmw721.eamcs.ericsson.se>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
X-Mailman-Approved-At: Thu, 22 Mar 2007 07:27:55 -0400
Cc: rbridge@postel.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [rbridge] Last Call: draft-ietf-trill-routing-reqs (TRILL Routing Requirements in Support of RBridges) to Informational RFC
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org
----- Original Message ----- From: "Eric Gray (LO/EUS)" <eric.gray@ericsson.com> To: "Dinesh G Dutt" <ddutt@cisco.com>; <ietf@ietf.org> Cc: <rbridge@postel.org>; "IETF-Announce" <ietf-announce@ietf.org> Sent: Wednesday, March 21, 2007 6:48 PM Subject: Re: [rbridge] Last Call: draft-ietf-trill-routing-reqs (TRILL Routing Requirements in Support of RBridges) to Informational RFC > Dinesh, > > Thank you for your comments. Please see below... > > Thanks! > > -- > Eric Gray > Principal Engineer > Ericsson > >> -----Original Message----- >> From: rbridge-bounces@postel.org >> [mailto:rbridge-bounces@postel.org] On Behalf Of Dinesh G Dutt >> Sent: Tuesday, Maroposed in the current solution is to run a spanning tree >> protocol instance per port which maybe not scalable. >> >> I think something like "It's strongly desirable to minimize the >> interaction between the bridges and Rbridges and constrain a >> spanning tree" is more appropriate. >> > > Yet it is difficult to imagine how this would translate to a > requirement that would make sense to someone evaluating the > acceptability of a routing protocol for the TRILL problem-space. > Perhaps it would be simpler to omit the offending text? > OK with me. Dinesh -- We make our world significant by the courage of our questions and by the depth of our answers. - Carl Sagan _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce