From: Fernando Gont <fgont@si6networks.com>
To: Eric Dumazet <eric.dumazet@gmail.com>, netdev <netdev@vger.kernel.org>
Cc: Yuchung Cheng <ycheng@google.com>, Neal Cardwell <ncardwell@google.com>
Subject: Re: Flaw in RFC793 (Fwd: New Version Notification for draft-gont-tcpm-tcp-seq-validation-03.txt)
Date: Tue, 6 Mar 2018 13:41:30 -0300 [thread overview]
Message-ID: <63c87e0d-3202-1975-5092-7087e7095249@si6networks.com> (raw)
In-Reply-To: <1520354245.109662.19.camel@gmail.com>
On 03/06/2018 01:37 PM, Eric Dumazet wrote:
> On Tue, 2018-03-06 at 04:21 -0300, Fernando Gont wrote:
>> Folks,
>>
>> Dave Borman and me are trying to get this flaw fixed in the TCP spec
>> --
>> this is of particular interest since the IETF finally agreed to
>> revise
>> the old spec. The working copy of our document is:
>> <https://www.si6networks.com/publications/drafts/draft-gont-tcpm-tcp-
>> seq-validation-04.txt>
>>
>> I'm wondering if any Linux TCP expert could help with this:
>>
>> * Would you mind taking a look at our doc, and check if our
>> description
>> of the Linux behavior is correct?
>
> Hi Fernando
>
> I have opened Google Bug # 74230088 and copied your request.
>
> We will take a look at this and will come back to you.
Thank you so much!
Cheers,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
prev parent reply other threads:[~2018-03-06 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <152029339529.12825.5038413838558267392.idtracker@ietfa.amsl.com>
2018-03-06 7:21 ` Flaw in RFC793 (Fwd: New Version Notification for draft-gont-tcpm-tcp-seq-validation-03.txt) Fernando Gont
2018-03-06 16:37 ` Eric Dumazet
2018-03-06 16:41 ` Fernando Gont [this message]
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=63c87e0d-3202-1975-5092-7087e7095249@si6networks.com \
--to=fgont@si6networks.com \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/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