Re: [rbridge] Question on draft-ietf-trill-rbridge-mib-07

Anil Rijhsinghani <anil@charter.net> Fri, 06 April 2012 12:33 UTC

Return-Path: <rbridge-bounces@postel.org>
X-Original-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Delivered-To: ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60E0C21F8546 for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Fri, 6 Apr 2012 05:33:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level:
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=1.334, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9KW8JW+Brepr for <ietfarch-trill-archive-Osh9cae4@ietfa.amsl.com>; Fri, 6 Apr 2012 05:33:29 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id AFD2421F8542 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 6 Apr 2012 05:33:29 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q36CNp9M014764; Fri, 6 Apr 2012 05:23:52 -0700 (PDT)
Received: from mta31.charter.net (mta31.charter.net [216.33.127.82]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id q36CNVTO014445 for <rbridge@postel.org>; Fri, 6 Apr 2012 05:23:40 -0700 (PDT)
Received: from imp10 ([10.20.200.15]) by mta31.charter.net (InterMail vM.8.01.05.02 201-2260-151-103-20110920) with ESMTP id <20120406122329.EGRJ24708.mta31.charter.net@imp10>; Fri, 6 Apr 2012 08:23:29 -0400
Received: from [192.168.1.106] ([71.10.228.40]) by imp10 with smtp.charter.net id ucPV1i0070sw4rK05cPVEF; Fri, 06 Apr 2012 08:23:29 -0400
X-Authority-Analysis: v=1.1 cv=JYQIUidRAECiNa+jsiaNMIhYElg3H2WoMKCJIGO75f4= c=1 sm=1 a=HXW8s7Hvfe4A:10 a=yUnIBFQkZM0A:10 a=8nJEP1OIZ-IA:10 a=uxqmlfvtJbLpRWMvzcSYSQ==:17 a=oEQ2TvfSHUdwZXvcvIEA:9 a=wPNLvfGTeEIA:10 a=uxqmlfvtJbLpRWMvzcSYSQ==:117
Mime-Version: 1.0 (Apple Message framework v1257)
From: Anil Rijhsinghani <anil@charter.net>
In-Reply-To: <CADsdYf2_RxTzgUv-F63RYuXFSmVatcGeipidrcVMXfU3X08XYA@mail.gmail.com>
Date: Fri, 06 Apr 2012 08:23:28 -0400
Message-Id: <1692AF62-B4E9-4148-8A70-9E4A9A7C15D5@charter.net>
References: <CADsdYf3J_7UgGRJuHgecmSaY=qgziHh671EdFt2jrj9_PH_jcQ@mail.gmail.com> <F59C3420-7B85-4E9A-8485-855C1A5949C3@charter.net> <CADsdYf2_RxTzgUv-F63RYuXFSmVatcGeipidrcVMXfU3X08XYA@mail.gmail.com>
To: Mahesh Akula <mahesh.akula36@gmail.com>
X-Mailer: Apple Mail (2.1257)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: anil@charter.net
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id q36CNVTO014445
Cc: rbridge@postel.org
Subject: Re: [rbridge] Question on draft-ietf-trill-rbridge-mib-07
X-BeenThere: rbridge@postel.org
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: "Developing a hybrid router/bridge." <rbridge.postel.org>
List-Unsubscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=unsubscribe>
List-Archive: <http://mailman.postel.org/pipermail/rbridge>
List-Post: <mailto:rbridge@postel.org>
List-Help: <mailto:rbridge-request@postel.org?subject=help>
List-Subscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

On Apr 5, 2012, at 10:08 PM, Mahesh Akula wrote:

> >>   IP multicast data SHOULD only be sent on links where there is either
>    an IP multicast router for that IP type (IPv4 or IPv6) or ..
>  
> As the idea is to forward the data (and reports) only if there is a router for that specific IP type, it looks to me it is more important to capture whether only one IP type of multicast router is attached or both.

After reading the protocol section again, I think I agree with you here and will accommodate the above in yet another revision.
 
> Also, as there can be more than one multicast router of each IP type attached, capturing only one of them may not serve any purpose IMO.

Capturing one is better than all of them, which I think was one of your original issues in this thread. The thought here was to record at least one so that a manager can do some correlation when there's multicasting going on. If a multicast is being forwarded, some additional data on why it's being forwarded would be useful. A switch need only know of one alive on a port, in order to continue multicasting on that port. You're not normally going to have lots of multicast routers on every link in any case. Given your first suggestion, we could add rbridgeSnoopingPortAddrType to the INDEX, thus allowing a single object to be returned per instance: the address of the router. What do you think?

Regards,
Anil


_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge