From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Ido Schimmel <idosch@mellanox.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
wkok@cumulusnetworks.com, anuradhak@cumulusnetworks.com,
bridge@lists.linux-foundation.org, davem@davemloft.net,
stephen@networkplumber.org
Subject: Re: [PATCH RFC] net: bridge: don't flood known multicast traffic when snooping is enabled
Date: Sat, 16 Feb 2019 21:04:05 +0100 [thread overview]
Message-ID: <20190216200405.GB25057@otheros> (raw)
In-Reply-To: <733b151e-47dd-ad9a-b112-473cf551fbeb@cumulusnetworks.com>
Hi Nik, hi Ido,
By the way speaking about the IGMP/MLD querier mechanism. Not sure if
you are subscribed to the pim@ietf.org or mcast-wifi@ietf.org mailing lists.
There was a call for volunteers to progress IGMP/MLD to standards
track not that long ago:
"[pim] Volunteers needed for work on progressing IGMP/MLD on the standards track"
https://mailarchive.ietf.org/arch/msg/pim/F5y_w6jnrtzBpEiC7F_TxBv9PXI
I had voiced some concerns regarding the IGMPv2/MLDv1 report
suppression and the querier mechanism and their unfavourable
implications, as well as some issues (or ambiguities at least) with RFC4541:
https://mailarchive.ietf.org/arch/msg/pim/DWWYpnsZsbqHtafwYZ_swhDpbcQ
https://mailarchive.ietf.org/arch/msg/pim/omI4-pg-12vO88YuZcRP5TCz4wY
It seems that some bigger vendors had gathered for a phone call:
https://mailarchive.ietf.org/arch/msg/pim/jPAbf-PHgtgpwe8lgyjOzCHlhc0
But I haven't heard anything back from that meeting on those
lists.
Just wanted to forward this, in case you guys might maybe be
interested to participate there in some way. :-)
Cheers, Linus
next prev parent reply other threads:[~2019-02-16 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 13:04 [PATCH RFC] net: bridge: don't flood known multicast traffic when snooping is enabled Nikolay Aleksandrov
2019-02-15 13:09 ` Nikolay Aleksandrov
2019-02-15 13:53 ` Ido Schimmel
2019-02-15 17:13 ` Linus Lüssing
2019-02-16 8:05 ` Nikolay Aleksandrov
2019-02-16 8:35 ` Nikolay Aleksandrov
2019-02-16 20:04 ` Linus Lüssing [this message]
2019-02-16 18:43 ` Ido Schimmel
2019-02-16 19:15 ` nikolay
2019-02-16 19:27 ` nikolay
2019-02-16 20:37 ` Linus Lüssing
2019-02-17 3:05 ` Florian Fainelli
2019-02-17 10:58 ` Nikolay Aleksandrov
2019-02-18 12:21 ` [RFC v2] " Nikolay Aleksandrov
2019-02-19 8:53 ` Ido Schimmel
2019-02-19 8:57 ` Linus Lüssing
2019-02-19 9:21 ` [Bridge] " Linus Lüssing
2019-02-19 13:31 ` Nikolay Aleksandrov
2019-02-19 15:42 ` Linus Lüssing
2019-02-19 17:26 ` Nikolay Aleksandrov
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=20190216200405.GB25057@otheros \
--to=linus.luessing@c0d3.blue \
--cc=anuradhak@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.org \
--cc=wkok@cumulusnetworks.com \
/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).