IETF Logo Mail Archive

Re: [multipathtcp] [tcpm] Working group acceptance of draft-bonaventure-mptcp-converters ?

Joe Touch <touch@strayalpha.com> Tue, 05 December 2017 00:35 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69B61271FD; Mon, 4 Dec 2017 16:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rA9Pih1zxJFm; Mon, 4 Dec 2017 16:35:55 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A5D1250B8; Mon, 4 Dec 2017 16:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=jQefm2SCWgzbz5nWUCag2qUejybVGk4ycOgpmEuhTuk=; b=jbhp3sMG7Yoi91u3rCgWKuilH2 YUXQ/yXlnJCqTmx2zRH7M0PTUta5RVLraRHVz+cP1813Dz6x06eLz9kKbpR8HGl9TnDcPhAgaAe7y 2pXyMOWkruEobnnUW9ni+2exWuh1hlpLRSOc33l51MGaS/Wr9OUwqQ6Mkqh8Q/qBs8hUQA+W+HHEv 47FOyEnchlduGYyz5OQ75/He78zxtf7DOUEJXMyct9p2gIJ3AcKBo1bUQZr/uVz5C/mpSOeRxMmxC 732+NWvo5iaXZiwDW3OBeSrPczIQIeYFrYL1Qc8wzxl84D+68q7RxxdSWSrhvpEaiCfhmZcWV2PcU FAAHFRbw==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:65245 helo=[192.168.1.189]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <touch@strayalpha.com>) id 1eM1DF-000e1c-Hw; Mon, 04 Dec 2017 19:35:54 -0500
To: mohamed.boucadair@orange.com, "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, "tcpm@ietf.org" <tcpm@ietf.org>, multipathtcp <multipathtcp@ietf.org>
References: <AM5PR0701MB25475FD66E9553F2947DD22C933F0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <AM5PR0701MB25470B276B0889170FC309FE933F0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <1d4eda72-b822-c8b5-1207-d52ce2e3fe62@strayalpha.com> <787AE7BB302AE849A7480A190F8B93300A08560D@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Joe Touch <touch@strayalpha.com>
Message-ID: <fa6df389-a99a-ec13-2bca-63e78b83f211@strayalpha.com>
Date: Mon, 04 Dec 2017 16:35:46 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B93300A08560D@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/YBqeEDSF5adsF3nGC5gWav0TCow>
Subject: Re: [multipathtcp] [tcpm] Working group acceptance of draft-bonaventure-mptcp-converters ?
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Dec 2017 00:35:58 -0000

Hi, Med,


On 12/3/2017 11:00 PM, mohamed.boucadair@orange.com wrote:
> ...
>>   "The client places the destination address and port number of the
>>    target Server in the payload of the SYN sent to the Converter by
>>    leveraging TCP Fast Open [RFC7413]."
>>
>> I disagree with any use of TCP SYN payloads as anything other than
>> application data.
> [Med] The data that are inserted in ONE single SYN is the application (proxy) data. What's is wrong with that?

If this is an application layer proxy, then you have no direct control
over segment contents. The best you can say is that you write this
information to the socket. If you do that, then you are a simple TCP
service, not unlike any other TCP service which uses - but does not
alter - TCP, and not in-scope for TCPM.

To understand why intending to insert out-of-band info in the SYN is a
problem, see Sec 8.7 of draft-ietf-tcpm-tcp-edo.
>  ...
>
> My position is as follows:
>     - I don't think this doc should be adopted by the WG
>     - Whether the doc is adopted or not, I have no interest in
> continuing to try to repair its significant (and IMO fatal) flaws
> [Med] Joe, we have taken into account many of the comments you raised in the past (e.g., define the proposal as an application proxy, make use of a service port, better integrate with TFO). It would be helpful to list some of the "fatal flaws" so that we can determine whether these are new issues. Thank you.

I did, above. Continuing to avoid each fatal flaw does not ensure you
will find a solution that is viable.

Joe

v2.23.0 | Report a Bug | By Email