From: Andrew Lunn <andrew@lunn.ch>
To: Philip Downey <pdowney@Brocade.com>
Cc: David Miller <davem@davemloft.net>,
"kuznet@ms2.inr.ac.ru" <kuznet@ms2.inr.ac.ru>,
"jmorris@namei.org" <jmorris@namei.org>,
"yoshfuji@linux-ipv6.org" <yoshfuji@linux-ipv6.org>,
"kaber@trash.net" <kaber@trash.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] IGMP: Inhibit reports for local multicast groups
Date: Thu, 13 Aug 2015 18:06:26 +0200 [thread overview]
Message-ID: <20150813160626.GF32484@lunn.ch> (raw)
In-Reply-To: <57f72e6a6f024628bd18ef4b139ac31e@EMEAWP-EXMB12.corp.brocade.com>
On Thu, Aug 13, 2015 at 02:48:23PM +0000, Philip Downey wrote:
> Hi David
> Thanks for taking the time to review and comment.
> This is my first upstream request so please forgive any ignorance on my part. I have added a new proposed commit wording below with a view to agreeing the content before resubmitting the patch.
> I hope it is sufficient to address your concerns.
>
> IGMP: Inhibit reports for local multicast groups
>
> The range of addresses between 224.0.0.0 and 224.0.0.255
> inclusive, is reserved for the use of routing protocols and other
> low-level topology discovery or maintenance protocols, such as
> gateway discovery and group membership reporting. Multicast
> routers should not forward any multicast datagram with destination
> addresses in this range, regardless of its TTL.
>
> Currently, IGMP reports are generated for this reserved range of
> addresses even though a router will ignore this information since
> it has no purpose.
Hi Philip
What about switches which are doing IGMP snooping?
Andrew
next prev parent reply other threads:[~2015-08-13 16:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 16:13 [PATCH] IGMP: Inhibit reports for local multicast groups Philip Downey
2015-08-12 23:45 ` David Miller
2015-08-13 14:48 ` Philip Downey
2015-08-13 16:06 ` Andrew Lunn [this message]
2015-08-13 16:52 ` Philip Downey
2015-08-13 17:01 ` Andrew Lunn
2015-08-13 18:08 ` Thadeu Lima de Souza Cascardo
2015-08-14 8:55 ` Philip Downey
2015-08-14 8:56 ` Philip Downey
2015-08-14 13:35 ` Andrew Lunn
2015-08-14 14:36 ` Philip Downey
[not found] <1>
2015-08-24 11:39 ` Philip Downey
2015-08-25 21:20 ` David Miller
2015-08-26 9:23 ` Philip Downey
2015-08-27 15:46 ` Philip Downey
2015-08-28 20:29 ` David Miller
2015-08-28 21:19 ` Cong Wang
2015-08-31 10:33 ` Philip Downey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150813160626.GF32484@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pdowney@Brocade.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).