Re: [trill] [rbridge] Queries on draft-ietf-trill-esadi-00
Donald Eastlake <d3e3e3@gmail.com> Tue, 03 July 2012 19:53 UTC
Return-Path: <d3e3e3@gmail.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 59EF411E8189 for <trill@ietfa.amsl.com>; Tue, 3 Jul 2012 12:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.22
X-Spam-Level:
X-Spam-Status: No, score=-103.22 tagged_above=-999 required=5 tests=[AWL=-0.221, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyxndpmF73EG for <trill@ietfa.amsl.com>; Tue, 3 Jul 2012 12:53:13 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id EC30411E8185 for <trill@ietf.org>; Tue, 3 Jul 2012 12:53:12 -0700 (PDT)
Received: by yhq56 with SMTP id 56so7878568yhq.31 for <trill@ietf.org>; Tue, 03 Jul 2012 12:53:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=WuqYinId/200Jg7qdNxeZRtn0FurmaM2sTgKyUyGusk=; b=toBL0R+LS/mRxri0bHhaoZ1M+M/gW28Dc7drxPFFgMJAxQFCkOujplMQloEivgNVTj ZyoSEE0ChQ56mT2oKOaVVJdqoDXdVhZR8beRVPIfq23mjH7Jwy7DmlGMNUPttyk8AF/7 sdK7dbkSXCTq9g6t3e+bV02Wl9TuajzONhZmag6mE+66W8cei39qXMToawGfwi4jeIlf NgAPsC8ZQsPwDSwtnhx7yQUPjI78GViYJ/DCmathZA7dx9XyTUk+p1SFr+7A7yDjkdIW Yoa6+IWLFc3Lk2NUTOPtNuBQHkvg9uYpqqpQwJzvbbSUOI6tN+hs4CgH5qqZD/xnn+Ln Ba5g==
Received: by 10.43.106.1 with SMTP id ds1mr9747692icc.24.1341345201065; Tue, 03 Jul 2012 12:53:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.16.227 with HTTP; Tue, 3 Jul 2012 12:53:00 -0700 (PDT)
In-Reply-To: <CAPFewY2gqiquhB7AqKCYE-14+b_iOu59QmF+w9GBziWKVhnT7g@mail.gmail.com>
References: <CAPFewY2gqiquhB7AqKCYE-14+b_iOu59QmF+w9GBziWKVhnT7g@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 03 Jul 2012 15:53:00 -0400
Message-ID: <CAF4+nEGG1GeXzKO17zFFMFZQ1DgoG0eCG-_r3x4dfU-xkdw4kg@mail.gmail.com>
To: somnath chatterjee <somnath.chatterjee01@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: trill@ietf.org
Subject: Re: [trill] [rbridge] Queries on draft-ietf-trill-esadi-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: Tue, 03 Jul 2012 19:53:14 -0000
Hi Somnath, On Tue, Jul 3, 2012 at 8:36 AM, somnath chatterjee <somnath.chatterjee01@gmail.com> wrote: > Hi Authors, > > I have few queries regarding ESADI protocol as per > draft-ietf-trill-esadi-00, base RFC 6325 and RFC 6165. > > 1>In base RFC 6325 Section 4.2.4.4 (5.4) > > "In addition, the LSP contains the following information on a per- VLAN basis: > 5.4. Per-VLAN ESADI protocol participation flag, priority, and > holding time. If this flag is one, it indicates that the RBridge > wishes to receive such TRILL ESADI frames" > > The per vlan ESADI protocol participation flag is send via "Interested > VLANs and Spanning Tree Roots Sub-TLV" in TRILL LSP.The per vlan ESADI > priority is send via "ESADI Parameter APPsub-TLV" in ESADI LSP 0. Is > the "holding time" same as "CSNP time" field in "ESADI Parameter > APPsub-TLV"? Yes, that is the intent. This draft proposes changes to ESADI from the specification in RFC 6325. > 2>The Inner.VLAN tag for ESADI LSP indicates the VLAN to which the > ESADI-LSP applies, the vlan in MAC-Reachability TLV is unused.Why do > not we use the MAC-Reachability TLV's vlan field ? If we use > MAC-Reachability TLV's vlan field we can merge multiple ESADI-LSPs to > one ESADI LSP and reduce number of ESADI LSPs. Currently if we have 4k > VLANs enabled on an ESADI RBridge it has to send 4k ESADI LSPs. This > can be reduced using the MAC-Reachability TLV's vlan field. That's only true if the ESADI RBridge is participating in ESADI for all of those VLANs. And there are two reasons (1) draft-ietf-trill-rbridge-vlan-mapping, and (2) if there were information in an ESADI-LSP PDU for say, two different VLANs, only one of these could appear at the VLAN ID in the Inner.VLAN so there is no way to guarantee that the PDU would get to RBridges participating in ESADI only for the other VLAN due to distribution tree pruning (see your question 4 below). > 3> What should be the deciding factor behind unicast-ing a ESADI LSP > and sending it on a DTree? Should it be the number of ESADI RBridges > in the campus? The text related to this aspect of the current ESADI draft could probably do with review and clarification. Obviously, all the destination ESADI RBridges have to indicate that they support unicast receipt. I would say that, to a first approximation, it is best to use unicast if their is one intended recipient and a distribution tree if there are multiple recipients. There being only one intended recipient for a particular ESADI-LSP does not imply that there are only two ESADI RBridges for that VLAN. > 4> If DTrees are already pruned, it would be good to send ESADI LSPs > on vlan pruned Dtree. Can we further prune these vlan pruned DTrees > based on the RBridges participating in ESADI for a particular clan. Since ESADI--LSP PDUs are treated by transit RBridges like any other multi-destination TRILL Data packet, they will automatically use any distribution tree VLAN pruning available. Further pruning those trees based on ESADI participation is an obvious improvement that will work fine whether it is implemented for all or some of the RBridges in a campus. But this wasn't included in the TRILL specifications because it did not, at the time, seem worth the additional complexity. It seemed like that in a well configured network, either none of the RBridges interested in a particular VLAN would be ESADI participants for that VLAN or all or almost all of them would be. Pruning on ESADI participation does no good in the none or all cases and probably helps most somewhere in the middle. Thanks, Donald ============================= Donald E. Eastlake 3rd +1-508-333-2270 (cell) 155 Beaver Street, Milford, MA 01757 USA d3e3e3@gmail.com > Thank you, > Regards, > Somnath
- [trill] [rbridge] Queries on draft-ietf-trill-esa… somnath chatterjee
- Re: [trill] [rbridge] Queries on draft-ietf-trill… Donald Eastlake