From: Fernando Gont <fgont@si6networks.com>
To: Loganaden Velvindron <loganaden@gmail.com>,
Hagen Paul Pfeifer <hagen@jauu.net>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: stop sending PTB packets for MTU < 1280
Date: Tue, 20 Jan 2015 01:52:35 -0300 [thread overview]
Message-ID: <54BDDF13.9010007@si6networks.com> (raw)
In-Reply-To: <CAOp4FwRdRai8tL5koFvHKr0P=dR6MgT5ZLtMg85drt6LTzYNrQ@mail.gmail.com>
Hi, Loganaden,
On 01/20/2015 01:02 AM, Loganaden Velvindron wrote:
>
> Last time I was inquiring about depracated atomic fragments, people
> were concerned that there wasn't enough practical data to decide
> whether to go forward or not.
What kind of practical data?
FWIW,
<https://tools.ietf.org/id/draft-ietf-6man-deprecate-atomfrag-generation-00.txt>
seems to be good enough when it comes to reasons for deprecating them.
Besides, please check Section 5.2 of
<http://www.ietf.org/id/draft-gont-v6ops-ipv6-ehs-in-real-world-01.txt>
-- my "connection" to kernel.org was vulnerable to such attack.
> Would a sysctl with it turned on by default be a good option, until we
> are 100% sure ?
<https://tools.ietf.org/id/draft-ietf-6man-deprecate-atomfrag-generation-00.txt>
was adopted by the 6man wg last November. While the I-D is not ready an
RFC, and there might be minor modifications, it seems that there's
agreement in not generating atomic fragments.
If you do want to have a sysctl for this, please make it default to "off".
Thanks!
Best regards,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
next prev parent reply other threads:[~2015-01-20 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 21:34 [PATCH net] ipv6: stop sending PTB packets for MTU < 1280 Hagen Paul Pfeifer
2015-01-19 13:55 ` Hannes Frederic Sowa
2015-01-19 14:00 ` Hagen Paul Pfeifer
2015-01-19 19:50 ` David Miller
2015-01-19 20:05 ` Hannes Frederic Sowa
2015-01-19 22:05 ` Hagen Paul Pfeifer
2015-01-20 4:02 ` Loganaden Velvindron
2015-01-20 4:52 ` Fernando Gont [this message]
2015-01-19 19:51 ` David Miller
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=54BDDF13.9010007@si6networks.com \
--to=fgont@si6networks.com \
--cc=davem@davemloft.net \
--cc=hagen@jauu.net \
--cc=hannes@stressinduktion.org \
--cc=loganaden@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stable@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.