From: Fernando Gont <fernando@gont.com.ar>
To: Loganaden Velvindron <loganaden@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Date: Sat, 31 Aug 2013 02:22:51 -0300 [thread overview]
Message-ID: <52217DAB.5090502@gont.com.ar> (raw)
In-Reply-To: <20130815102507.GA24122@order.stressinduktion.org>
On 08/15/2013 07:25 AM, Hannes Frederic Sowa wrote:
>
>> 3) What will/could break with this diff in a production environment ?
>
> RA messages could get fragmented if a speaker puts lots of options in it. I
> hope all RA speakers already spread the options over multiple RAs, but I don't
> know. In case the RA is fragmented it will now be dropped silently.
My understanding is that some implementations were already dropping
fragmented RAs... so you better avoid fragmentation. Put another way:
you're already in trouble if you rely on fragmented ND messages.
Cheers,
--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
next prev parent reply other threads:[~2013-08-31 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130813221321.AEA1AB1E003@rfc-editor.org>
2013-08-14 8:19 ` Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery Fernando Gont
2013-08-14 23:06 ` Hannes Frederic Sowa
2013-08-15 6:28 ` Fernando Gont
2013-08-15 10:04 ` Hannes Frederic Sowa
2013-08-15 10:14 ` Loganaden Velvindron
2013-08-15 10:25 ` Hannes Frederic Sowa
2013-08-18 20:52 ` Loganaden Velvindron
2013-08-22 5:39 ` Loganaden Velvindron
2013-08-31 5:22 ` Fernando Gont [this message]
[not found] ` <CAOp4FwSatwRtx_O4Aio4e0HmahxdwiY9JToc8E+1rMT9oCjLrA@mail.gmail.com>
2013-08-31 5:20 ` Fernando Gont
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=52217DAB.5090502@gont.com.ar \
--to=fernando@gont.com.ar \
--cc=loganaden@gmail.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.