From owner-freebsd-questions@FreeBSD.ORG Fri Aug 8 14:40:29 2014 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76E68C56 for ; Fri, 8 Aug 2014 14:40:29 +0000 (UTC) Received: from mail.ssimicro.com (mail.ssimicro.com [64.247.129.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.ssimicro.com", Issuer "RapidSSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 194BA2AFD for ; Fri, 8 Aug 2014 14:40:28 +0000 (UTC) Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by mail.ssimicro.com (8.14.7/8.14.7) with ESMTP id s78EeKjd039581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 8 Aug 2014 08:40:21 -0600 (MDT) Message-ID: <53E4E154.40008@corp.ssimicro.com> Date: Fri, 08 Aug 2014 08:40:20 -0600 From: markham breitbach User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: questions Subject: Re: TCP/IP on the way out? References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 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 14:40:29 -0000 I can think of many reasons why TCP/IP won't go away, and while this might find some very small niche markets, but the fact that it is patent encumbered will keep it from ever replacing TCP/IP. -M On 2014-08-08, 1:00 AM, 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. > >