From owner-freebsd-net@FreeBSD.ORG  Tue Sep 16 23:23:25 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@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 DE6A382B
 for <freebsd-net@freebsd.org>; Tue, 16 Sep 2014 23:23:25 +0000 (UTC)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com
 [66.111.4.221])
 (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 AEAE3C8A
 for <freebsd-net@freebsd.org>; Tue, 16 Sep 2014 23:23:25 +0000 (UTC)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by gateway2.nyi.internal (Postfix) with ESMTP id B94C6232F
 for <freebsd-net@freebsd.org>; Tue, 16 Sep 2014 19:23:23 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute4.internal (MEProxy); Tue, 16 Sep 2014 19:23:23 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:subject:date:in-reply-to
 :references; s=smtpout; bh=sTwgd8jxtRdHquJI8gg6M6L9Klg=; b=cYRVN
 MZiU7EdF7OlqUQbXI9+fWvbw0FkqEKH8EzeMSQvAejOdFtVUePZgSRs6W3udBHZP
 fjZ2a6VEC5snx+NyLcJpmgxEFwrnaUaY7S2l7xcnnIO6FEY63l9KXsPPCFVpSlMS
 CTd0b5UGfncjzPdRxiin0kW5vXVsqM9wQumJck=
Received: by web3.nyi.internal (Postfix, from userid 99)
 id 7D0D4184C01; Tue, 16 Sep 2014 19:23:23 -0400 (EDT)
Message-Id: <1410909803.3848965.168337885.0D680310@webmail.messagingengine.com>
X-Sasl-Enc: 8QUh2k4GTKq59dZSbNgoeXSwOiJAoJ9/KoHP1fj5pfIU 1410909803
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-net@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-0646565c
Subject: Re: Multipath TCP for FreeBSD v0.4
Date: Tue, 16 Sep 2014 18:23:23 -0500
In-Reply-To: <CAKYr3zz50CEnX44ErmaN38=T0fBDQhGPVEEG9O8hyHzpT_R6Jg@mail.gmail.com>
References: <513CB9AF.3090409@swin.edu.au> <53BF8945.3000802@swin.edu.au>
 <540D0741.6030403@swin.edu.au> <1410907731.1166.13.camel@bruno>
 <CAKYr3zz50CEnX44ErmaN38=T0fBDQhGPVEEG9O8hyHzpT_R6Jg@mail.gmail.com>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 23:23:26 -0000

On Tue, Sep 16, 2014, at 17:59, Outback Dingo wrote:
> >
> Im quite curious why you would want to include something thats been found
> to be broken and not functional
> into mainline.... if it was working sure... im sure we would love it.
> However its been months rolling along to get
> this patch set out after reporting previous bugs that... well... still
> remain. Id suggest to clear up and push
> a functional working implementation, might gather more participants.
> 
> 

This kind of response isn't exactly productive. We need to encourage
those who are working on new features and find a way to easily provide
them with a wide audience of testers.