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

Olivier Bonaventure <olivier.bonaventure@tessares.net> Wed, 06 December 2017 07:47 UTC

Return-Path: <olivier.bonaventure@tessares.net>
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 702B4126FDC for <multipathtcp@ietfa.amsl.com>; Tue, 5 Dec 2017 23:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tessares-net.20150623.gappssmtp.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 MhCGeOfpy23R for <multipathtcp@ietfa.amsl.com>; Tue, 5 Dec 2017 23:47:11 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 431801200C1 for <multipathtcp@ietf.org>; Tue, 5 Dec 2017 23:47:11 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id f206so5385456wmf.5 for <multipathtcp@ietf.org>; Tue, 05 Dec 2017 23:47:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=lLSrF7dtmdxQbXs/70vB2V2vMmCq0cChyLFzAQq96f4=; b=tqE2ly9cSSrbZcRg0xd5x9gDJe2KPsm7k/ewoSO//HReatJCM/kR520jjl3a7lHZOs Z3LxHn6QJxQ+8rKow6uR1AE8D4uTzYUhddyectTgGzhM5KgoNORSBrmIFDeRUwz9Lm/H U4pfVqryKrNNUpldvLIT9x+E88wBBuLrL7ltSMoUQjgdm9CxeRL73c0Y9dXdiKKfxx7E hkKyrjG4JeWBVodaRPmy5MQTvUehjEtuSG6um+TRwhvJmMA3JfWhPV5M31SxcqRhXeOs +PKCS7RkDxyE3iiFlngyU52j+0ZuEejcFjKGC3T9sSzIBIhvmziIiUeBjD9Rq85ZOcAC XucA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=lLSrF7dtmdxQbXs/70vB2V2vMmCq0cChyLFzAQq96f4=; b=n7XAPGm9QVDC9LAgQsxCG2yv1IkoudvJp0ECs0017JuYTa+x6FNoQCcnb5pPVmYenW zb5tJnf2csDLECu7c6v4CaegHrmCYJ6Ceq6wWGmMhK0F3wpnmxxcHzfUX4T1//EoUTuu M6UsbBho78Q8VBrDlDtJGE4nIcVvM8jE31wQRwZUr6Fz+1J23SwDXi2AfOSspObMJfh0 uUYYCPoZYQm0WruSU7X0/fcgvvxUAICkSLXFqdJhV0PDDkQYkB0YyflmbxiXM2ecvGTa /E1NYoOElNTZR8feIBSyxDuL2pCczrq9wk9NKM3pXbY2oFmfophMGzgARZbx+jpZxY5s T+YQ==
X-Gm-Message-State: AJaThX5SN4YhigNZ1U3iQI58efW3nh9SSpovuWfQw2vv0sxadTAwuHQb kFRrhOjH7Ubf+rlUPmvNAYFKqdCWgeSc+1ebOkV6hAem/1J744eZjPLItczBEyQMxNuIqGVFTBs POFqnlmr79tC1
X-Google-Smtp-Source: AGs4zMYpbfCR6aftKxV9gBP0AMqtcDdt1zvTyyIDVINqYjfUXF0XMSLnXsgmcvzce4ubkiTiyDawmQ==
X-Received: by 10.80.182.138 with SMTP id d10mr38360991ede.131.1512546429510; Tue, 05 Dec 2017 23:47:09 -0800 (PST)
Received: from mbpobo.local ([2001:6a8:308f:2:b9cd:286c:bccd:7108]) by smtp.gmail.com with ESMTPSA id h56sm908922eda.97.2017.12.05.23.47.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Dec 2017 23:47:08 -0800 (PST)
To: Joe Touch <touch@strayalpha.com>, "Scharf, Michael (Nokia - DE/Stuttgart)" <michael.scharf@nokia.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.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> <fa6df389-a99a-ec13-2bca-63e78b83f211@strayalpha.com> <787AE7BB302AE849A7480A190F8B93300A086275@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <a089353b-66b4-f6b6-d20f-aed2ffbb7da1@strayalpha.com> <AM5PR0701MB2547CBEF78BEDF7FB784EDE2933D0@AM5PR0701MB2547.eurprd07.prod.outlook.com> <5c189d4f-db3b-e3a5-c6c1-53d1b76e1ddc@strayalpha.com>
From: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Message-ID: <0ac893cf-4456-7e93-b53a-3b4162dd4983@tessares.net>
Date: Wed, 06 Dec 2017 08:47:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <5c189d4f-db3b-e3a5-c6c1-53d1b76e1ddc@strayalpha.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: fr-classic
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/lbFeiWRZjXKhyucSd5plSGb_oIw>
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: Wed, 06 Dec 2017 07:47:13 -0000

Joe, Michael,

>> Regarding "*out of scope for* TCPM":  Whether a document is in scope of TCPM, or not, depends on the TCPM charter wording.
> Although I appreciate that's strictly true, I doubt the charter would
> change to include "haiku development".
 >
> By the same token, IMO, this doc falls into one of two categories:
> 
> 1) if, as is, it proposes direct placement of out-of-band data in the
> SYN payload, I think it is a bad idea and not worth pursuing in TCPM
> 
> 2) if, instead, it is corrected to explain that its use of the data
> channel for proxy information is simply a conventional application data
> path, then it would not be a "modification of TCP" at all (minor or
> otherwise). If that isn't clearly out of scope for TCPM, I do not know
> what is or ever would be (can we start haiku next, in that case?)

The converter draft clearly defines an application level protocol that 
leverages TFO. This draft defines the format of the messages that are 
exchanged at the beginning of the bytestream in both directions. There 
is no out-of-band data in the SYN.

I guess that the main reason why our AD suggested to discuss this draft 
in the tcpm working group is that it could help the deployment of new 
TCP options. History shows that deploying news TCP options on client and 
servers is a very long process. If we can speedup or encourage this 
deployment, then this will be beneficial for TCP even if at this stage 
the main use case comes from Multipath TCP where there is a clear 
benefit in having Multipath TCP on a a subset of the end-to-end path.

I'll let the ADs comment on whether converters are in scope of a 
specific working group.


Olivier

-- 

------------------------------
DISCLAIMER.
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.