public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion•org>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6•org>
Cc: Erik Hugne <erik.hugne@ericsson•com>, netdev@vger•kernel.org
Subject: Re: [IPv6] interface-local multicast escapes the local node
Date: Thu, 7 Feb 2013 02:00:10 +0100	[thread overview]
Message-ID: <20130207010010.GD19537@order.stressinduktion.org> (raw)
In-Reply-To: <51128985.2010701@linux-ipv6.org>

On Thu, Feb 07, 2013 at 01:49:09AM +0900, YOSHIFUJI Hideaki wrote:
> >>
> >> NAK.
> >>
> >> Well, do you have relevant RFC?
> >> RFC4291 says that we should drop ff00::/16, but not ff01::/16.
> > 
> > I know what you mean, the RFC does not state it directly. Hm, the BSDs seem to
> > drop such destination addresses, too, if they don't originate from a loopback
> > interface. Or did you mean that there is a flaw in the skb->pkt_type !=
> > PACKET_LOOPBACK condition?
> 
> We do not drop ff01::/16, because RFC is silent about it.

I just did a little bit of research on this topic and found this:

RFC4541 3. IPv6 Considerations:

   MLD messages are also not sent regarding groups with addresses in the
   range FF00::/15 (which encompasses both the reserved FF00::/16 and
   node-local FF01::/16 IPv6 address spaces).  These addresses should
   never appear in packets on the link.

It gives a strong indication that we should drop these packets. What do you
think?

Thanks,

  Hannes

  reply	other threads:[~2013-02-07  1:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  8:49 [IPv6] interface-local multicast escapes the local node Erik Hugne
2013-02-06 12:12 ` Hannes Frederic Sowa
2013-02-06 13:07   ` Erik Hugne
2013-02-06 13:49     ` Hannes Frederic Sowa
2013-02-06 15:06       ` Erik Hugne
2013-02-06 15:12         ` Hannes Frederic Sowa
2013-02-06 15:32       ` YOSHIFUJI Hideaki
2013-02-06 16:04         ` Hannes Frederic Sowa
2013-02-06 16:18           ` Eric Dumazet
2013-02-06 16:25             ` Hannes Frederic Sowa
2013-02-06 16:49           ` YOSHIFUJI Hideaki
2013-02-07  1:00             ` Hannes Frederic Sowa [this message]
2013-02-07  7:28               ` Erik Hugne
2013-02-07 15:41                 ` YOSHIFUJI Hideaki
2013-02-06 15:24   ` YOSHIFUJI Hideaki
2013-02-06 16:54     ` Hannes Frederic Sowa
2013-02-09 12:10       ` Hannes Frederic Sowa
2013-02-09 14:12         ` YOSHIFUJI Hideaki
2013-02-09 23:08           ` Hannes Frederic Sowa
2013-02-10  9:59           ` Hannes Frederic Sowa
2013-02-10 10:57             ` YOSHIFUJI Hideaki
2013-02-10 15:32           ` Hannes Frederic Sowa
2013-02-10 18:42             ` YOSHIFUJI Hideaki
2013-02-10 18:49               ` Hannes Frederic Sowa
2013-02-11 11:13                 ` [PATCH RFC 1/2] ipv6: introdcue __ipv6_addr_needs_scope_id and ipv6_iface_scope_id helper functions Hannes Frederic Sowa
2013-02-11 13:36                   ` YOSHIFUJI Hideaki
2013-02-11 11:13                 ` [PATCH RFC 2/2] ipv6: use newly introduced helper functions __ipv6_addr_needs_scope_id and ipv6_iface_scope_id Hannes Frederic Sowa
2013-02-09 15:50         ` [IPv6] interface-local multicast escapes the local node YOSHIFUJI Hideaki

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=20130207010010.GD19537@order.stressinduktion.org \
    --to=hannes@stressinduktion$(echo .)org \
    --cc=erik.hugne@ericsson$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=yoshfuji@linux-ipv6$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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