From owner-freebsd-questions@FreeBSD.ORG Fri Aug 8 11:16:07 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E62E705 for ; Fri, 8 Aug 2014 11:16:07 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BAB6522C6 for ; Fri, 8 Aug 2014 11:16:06 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s78BFuf2004358; Fri, 8 Aug 2014 12:15:57 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <53E4B16C.2070109@qeng-ho.org> Date: Fri, 08 Aug 2014 12:15:56 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Steve Burton , Odhiambo Washington , questions Subject: Re: TCP/IP on the way out? References: <53E49129.2020806@sliderule.demon.co.uk> In-Reply-To: <53E49129.2020806@sliderule.demon.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 11:16:07 -0000 On 08/08/2014 09:58, Steve Burton wrote: > On 08/08/2014 08:00, Odhiambo Washington wrote: >> I trust that all is well with everyone. >> >> I have seen this article which sounds much like a dream, but seems true. >> >> http://www.networkworld.com/article/2459286/why-tcp/why-tcp/ip-is-on-the-way-out.html >> >> >> I'd love to hear the views of those who understand the network stack. >> >> > My favourite part of the article is: > > "The key to the process, they say, is a network coding and decoding > element called RLNC, or Random Linear Network Coding. RLNC is the > technology that they've patented and wrapped into C++ software at > Steinwurf called Kodo. Steinwurf plans to sell its technology to > hardware makers." If anyone writing an application wants something like this they can probably code up their own transport protocol using raptor codes over UDP and get 90% of the benefits without having to persuade people that replacing the network stacks of 8-10 billion(*) devices connected to the net is a good idea, economically feasible and can be achieved in a way that doesn't fragment the network for months or years on end. It's rarely the technology that decides anything, it's the economics and politics. That's a lesson most techies seem to have to learn the hard way. (*) Figure taken from http://www.forbes.com/sites/quora/2013/01/07/how-many-things-are-currently-connected-to-the-internet-of-things-iot/