Re: [trill] Query on rbridgeSnoopingPortEntry in draft-ietf-trill-rbridge-mib
wenyu zou <nkzouwenyu@gmail.com> Sun, 14 October 2012 14:20 UTC
Return-Path: <nkzouwenyu@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 59AF121F845E for <trill@ietfa.amsl.com>; Sun, 14 Oct 2012 07:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 3f3BBSV4tC3D for <trill@ietfa.amsl.com>; Sun, 14 Oct 2012 07:20:18 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id B217C21F847D for <trill@ietf.org>; Sun, 14 Oct 2012 07:20:18 -0700 (PDT)
Received: by mail-gh0-f172.google.com with SMTP id g10so1154386ghb.31 for <trill@ietf.org>; Sun, 14 Oct 2012 07:20:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LivCcMCKZtL0IuciUYRVQaeR75MlCwvv/+RRhTYue7k=; b=Z2z+jDer6EOvnXlxqb5a8pFqhUJpOQDupwan3pm+ZF+G51yrj3uyeEeAN5Nn00JwP2 L+KFrg0i26i8Xs/tkoTo4ZHY4/kqV677TUx3WP1Zv9cfsaNeCu7ufQpTFw+iP73znKS5 iv1lCdz7xySqni1P4goq3G8uo2QDG3AMK2iMsTY++BCzgxJdxid33rpKumLsuRJUZg3U OvJxIHV5CIM/ux/CMKIM4Gd3wmQMryeVn2Khq/AxSZN6aHXzgEAuUI+d8tmCF9+f2liE Vx3fNIHzREX2XlpNmaCMQI/hN0htw/+xeGWe4Sg3GbGiPtWopIl60BI3AONep7N3W8Qu t0kw==
MIME-Version: 1.0
Received: by 10.100.78.13 with SMTP id a13mr2605272anb.13.1350224417982; Sun, 14 Oct 2012 07:20:17 -0700 (PDT)
Received: by 10.147.157.35 with HTTP; Sun, 14 Oct 2012 07:20:17 -0700 (PDT)
In-Reply-To: <6B477636-3892-4666-AE8B-3D6BAE8A917D@charter.net>
References: <CA+7+8TSqrW7vuHneeVzyi1g7Wcy9YYuubMV2WecB71po8+1CdA@mail.gmail.com> <6B477636-3892-4666-AE8B-3D6BAE8A917D@charter.net>
Date: Sun, 14 Oct 2012 22:20:17 +0800
Message-ID: <CA+7+8TQSzYpHini5LVSwU1bMe7Vh=oUebTVfNU4fV5Ex4vHRgA@mail.gmail.com>
From: wenyu zou <nkzouwenyu@gmail.com>
To: Anil R <anil@charter.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: trill@ietf.org
Subject: Re: [trill] Query on rbridgeSnoopingPortEntry in draft-ietf-trill-rbridge-mib
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: Sun, 14 Oct 2012 14:20:19 -0000
Hi Anil,
1. If the rbridgeSnoopingPortAddr can be any one of the routers
that has been detected on that port, I think it's not useful and could
be deleted from the rbridgeSnoopingPortTable.
2. Although the IP address of the routers is not important, what's
about the vlan information? Is it necessary to show the vlan
information of the routers? In RFC 6325, Section 4.5.3, paragraph 2,
"Further pruning SHOULD be done in two cases ... Each of these cases
is scoped per VLAN". So I think the rbridgeSnoopingPortEntry should be
indexed by port and vlan informations.
3. rbridgeSnoopingPortAddrType is InetAddressType. What's the value
of rbridgeSnoopingPortAddrType if there are both IPv4 and IPv6 routers
on one port?
In RFC 6326, Section 2.3.6, the M4 or M6 flag can be set seperately.
So there is three possiblilities on one port: only IPv4 router, only
IPv6 routers, both IPv4 and IPv6 routers.
Thanks.
Regards,
wenyu
2012/10/12, Anil R <anil@charter.net>:
> Hi Wenyu,
>
> The purpose of rbridgeSnoopingPortTable is only to show which RBridge ports
> have at least one multicast router connected, and hence need to be included
> in forwarding of multicast packets. Exactly how many multicast routers are
> there on a port is not important for this table. The purpose is not to give
> a list of multicast routers, but a list of ports on which at least one
> multicast router has been detected. You need only one multicast router on a
> port, for that port to be included in the list of ports where IP multicast
> is forwarded. Hence, the value of the IP address in this table can be any
> one of the routers that has been detected on that port.
>
> This is not a IP Multicast snooping MIB, so you will not have all IP
> Multicast snooping information included in this group. You will get only the
> multicast snooping information relevant to the operation of a TRILL
> switch/RBridge.
>
> Regards,
> Anil
>
> On Oct 8, 2012, at 8:52 AM, wenyu zou wrote:
>
>> Hi Authors,
>> I have a questions about rbridgeSnoopingPortEntry in
>> draft-ietf-trill-rbridge-mib, which is indexed by rbridgeBasePort. For
>> one port, it maybe have many Multicast Routers in different VLANs. The
>> current structure of rbridgeSnoopingPortEntry set a limitation that
>> there is only one Multicast Router for one port. Why don't
>> rbridgeSnoopingPortEntry indexed by rbridgeVlanIndex like
>> rbridgeSnoopingAddrEntry?
>>
>> Thanks.
>> Regards,
>> wenyu
>> _______________________________________________
>> trill mailing list
>> trill@ietf.org
>> https://www.ietf.org/mailman/listinfo/trill
>
>