From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cyrus Sh <sirus.shahini@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
davem@davemloft.net
Cc: shiraz.saleem@intel.com, jgg@ziepe.ca, arnd@arndb.de,
netdev@vger.kernel.org, sirus@cs.utah.edu
Subject: Re: [PATCH] Clock-independent TCP ISN generation
Date: Tue, 3 Sep 2019 18:42:26 +0200 [thread overview]
Message-ID: <3fc44b3a-3ac0-d008-272a-e7acb98ad761@gmail.com> (raw)
In-Reply-To: <e02c0aac-05c5-e0a4-9ae1-57685a0c3160@gmail.com>
On 9/3/19 6:27 PM, Cyrus Sh wrote:
>
>
> On 9/3/19 10:17 AM, Eric Dumazet wrote:
>
>> Do you have a real program showing us how this clock skew can be used practically ?
> This is a well studied issue. You can take a look at this presentation as an
> example:
> http://caia.swin.edu.au/talks/CAIA-TALK-080728A.pdf
2008 ? Really ?
I do not want an example, I want a proof that current systems are
exhibiting all the needed behavior.
I do not have time to spend hours reading old stuff based
on old architectures.
>
>> You will have to convince people at IETF and get a proper RFC
> No I won't. A lot of these standards have been written at a time that anonymity
> networks were not of big importance. Now that they are, we try to lessen the
> negative impacts of some RFC deficiencies by improving the implementation. It's
> up to you whether to want to keep using a problematic code that may endanger
> users or want to do something about it since we won't insist on having a patch
> accepted.
>
Then this is the end. linux wont change something as fundamental without
proper feedback from the community.
next prev parent reply other threads:[~2019-09-03 16:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 5:06 [PATCH] Clock-independent TCP ISN generation Cyrus Sh
2019-09-03 7:41 ` Eric Dumazet
2019-09-03 15:39 ` Cyrus Sh
2019-09-03 15:59 ` Eric Dumazet
2019-09-03 16:06 ` Cyrus Sh
2019-09-03 16:17 ` Eric Dumazet
2019-09-03 16:27 ` Cyrus Sh
2019-09-03 16:42 ` Eric Dumazet [this message]
2019-09-03 22:45 ` David Miller
2019-09-04 0:45 ` Cyrus Sh
2019-09-03 22:43 ` David Miller
2019-09-03 16:12 ` Cyrus Sh
2019-09-03 16:16 ` Eric Dumazet
2019-09-03 7:45 ` kbuild test robot
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=3fc44b3a-3ac0-d008-272a-e7acb98ad761@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jgg@ziepe.ca \
--cc=netdev@vger.kernel.org \
--cc=shiraz.saleem@intel.com \
--cc=sirus.shahini@gmail.com \
--cc=sirus@cs.utah.edu \
/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.