From: Flavio Leitner <fbl@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, netdev-owner@vger.kernel.org,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
Subject: Re: possible bug in IPv6 MLD retransmissions
Date: Wed, 22 May 2013 14:27:11 -0300 [thread overview]
Message-ID: <20130522172711.GC17240@obelix.rh> (raw)
In-Reply-To: <OF1A7F184A.4282AFE8-ON85257B73.003E82A8-85257B73.003F3B88@us.ibm.com>
On Wed, May 22, 2013 at 07:30:39AM -0400, David Stevens wrote:
> First, I wouldn't call this a "bug"; it is listed as a "SHOULD", not a
> "MUST", so
> it is not required for compliance, though it is a good feature to add.
>
> Second, I think doing this on all LL addresses unconditionally isn't a
> good
> idea. If some configuration is using thousands of LL addrs for reasons of
> their
> own, they would suddenly be blasted with unexpected MLD reports where
> they have none now. I don't see why tracking it would be such a problem --
> if nothing else, you could simply add a counter for the number of valid LL
> addrs
> incremented on DAD completion, and send these whenever it transitions from
> 0 to 1.
It becomes a bug (and that's why I started with 'possible') if dad
completes after the two MLD reports sent with ``::'' source, because
routers will ignore those initial reports and the system is left out.
Thanks,
--
fbl
next prev parent reply other threads:[~2013-05-22 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 3:24 possible bug in IPv6 MLD retransmissions Flavio Leitner
2013-05-18 17:31 ` Hannes Frederic Sowa
2013-05-21 15:06 ` Flavio Leitner
2013-05-22 0:40 ` Hannes Frederic Sowa
2013-05-22 11:30 ` David Stevens
2013-05-22 12:51 ` Hannes Frederic Sowa
2013-05-22 17:27 ` Flavio Leitner [this message]
2013-05-22 18:24 ` David Stevens
2013-05-22 21:21 ` Flavio Leitner
2013-05-23 20:21 ` Hannes Frederic Sowa
2013-06-23 14:18 ` Hannes Frederic Sowa
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=20130522172711.GC17240@obelix.rh \
--to=fbl@redhat.com \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=hannes@stressinduktion.org \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).