Re: partial comments on section 5 of ibif

"Randy Presuhn" <[email protected]>
Newsgroups gmane.ietf.ipoib
Message-ID <002001c38e8a$6bd5a360$7f1afea9@oemcomputer>
Hi -

> From: "Vandana Rao" <[email protected]>
> To: "Randy Presuhn" <[email protected]>; <[email protected]>
> Cc: "'Bert Wijnen'" <[email protected]>
> Sent: Thursday, October 09, 2003 8:11 AM
> Subject: Re: [Ipoverib] partial comments on section 5 of ibif
...
> >OK, so these counters should simply not change because the event
> >they would count is physically impossible.  It probably wouldn't hurt
> >to say something like "Since multicast is not defined for InifiniBand,
> >there is nothing for this counter to count."
>
> IBTA does define multicast , however, there are no IBTA counters defined
> for multicast packets.
> I think the description for  ifInMulticastPkts and the other mcast counters
> should be left as defined,

If by "left as defined" you mean what's in RFC 2863, I agree.
If you mean what's in draft-ietf-ipoib-ibif-mib-05.txt, then I disagree.

If multicast is defined for this interface type, it seems  clear
that ifInMulticastPkts must be incremented each time such
a packet is delivered to a higher sub-layer.  Same reasoning
goes for the Out and HC counters.

>   as it is possible for implementations to provide proprietary counters
> which count multicast packets.
...

Putting this information in a vendor-specific MIB, and mandating an
incorrect implementation of the IF-MIB standard, would seem to me
to be the worst possible solution.

Randy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.