From: Stephen Hemminger <stephen@networkplumber•org>
To: Ben Hutchings <bhutchings@solarflare•com>
Cc: David Miller <davem@davemloft•net>, <hannes@stressinduktion•org>,
<netdev@vger•kernel.org>, <yoshfuji@linux-ipv6•org>,
<erik.hugne@ericsson•com>
Subject: Re: [PATCH] ipv6: don't accept multicast traffic with scop 0
Date: Mon, 11 Feb 2013 14:42:43 -0800 [thread overview]
Message-ID: <20130211144243.704c6097@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1360621271.2701.20.camel@bwh-desktop.uk.solarflarecom.com>
On Mon, 11 Feb 2013 22:21:11 +0000
Ben Hutchings <bhutchings@solarflare•com> wrote:
> On Mon, 2013-02-11 at 14:52 -0500, David Miller wrote:
> > From: Hannes Frederic Sowa <hannes@stressinduktion•org>
> > Date: Mon, 11 Feb 2013 20:48:35 +0100
> >
> > > On Sun, Feb 10, 2013 at 01:48:51PM +0100, Hannes Frederic Sowa wrote:
> > >> + /*
> > >> + * RFC4291 2.7
> > >> + * Nodes must not originate a packet to a multicast address whose scop
> > >> + * field contains the reserved value 0; if such a packet is received, it
> > >> + * must be silently dropped.
> > >
> > > Just nit-picking: The field is actually called scop without e, as pointed out
> > > by three erratas to RFC4291. :)
> >
> > That's funny because I added the 'e' to your patches while applying
> > them, it just looks completely stupid to refer to this things as
> > 'scop'.
>
> It seems to be a long Unix tradition to creat names with trailing silent
> vowels removed; this is hardly uniq.
>
> Ben.
>
Aussie's would call it scopie
next prev parent reply other threads:[~2013-02-11 22:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 12:48 [PATCH] ipv6: don't accept multicast traffic with scop 0 Hannes Frederic Sowa
2013-02-10 14:56 ` YOSHIFUJI Hideaki
2013-02-11 19:48 ` Hannes Frederic Sowa
2013-02-11 19:52 ` David Miller
2013-02-11 22:21 ` Ben Hutchings
2013-02-11 22:42 ` Stephen Hemminger [this message]
2013-02-11 22:49 ` Dan Williams
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=20130211144243.704c6097@nehalam.linuxnetplumber.net \
--to=stephen@networkplumber$(echo .)org \
--cc=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=erik.hugne@ericsson$(echo .)com \
--cc=hannes@stressinduktion$(echo .)org \
--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