[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <576B94DA.7070804@nod.at>
Date: Thu, 23 Jun 2016 09:50:50 +0200
From: Richard Weinberger <richard@....at>
To: David Miller <davem@...emloft.net>
Cc: tom@...bertland.com, netdev@...r.kernel.org, kernel-team@...com
Subject: Re: [PATCH net-next 0/8] tou: Transports over UDP - part I
Am 23.06.2016 um 09:40 schrieb David Miller:
> From: Richard Weinberger <richard.weinberger@...il.com>
> Date: Thu, 23 Jun 2016 00:15:04 +0200
>
>> On Thu, Jun 16, 2016 at 7:51 PM, Tom Herbert <tom@...bertland.com> wrote:
>>> Transports over UDP is intended to encapsulate TCP and other transport
>>> protocols directly and securely in UDP.
>>>
>>> The goal of this work is twofold:
>>>
>>> 1) Allow applications to run their own transport layer stack (i.e.from
>>> userspace). This eliminates dependencies on the OS (e.g. solves a
>>> major dependency issue for Facebook on clients).
>>
>> Facebook on clients would be a Facebook app on mobile devices?
>> Does that mean that the Facebook app is so advanced and complicated
>> that it needs a special TCP stack?!
>
> No, the TCP stack in the android/iOS/Windows kernel is so out of date
> that in order to get even moderately recent TCP features it is
> necessary to do this.
I see.
So the plan is bringing TOU into almost every kernel out there
and then ship Apps with their own TCP stacks since vendors are unable
to deliver decent updates.
I didn't realize that the situation is *that* worse. :(
Thanks,
//richard
Powered by blists - more mailing lists