Re: [multipathtcp] Preparing for Prague meeting - things to delete or add to MPTCP protocol bis

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Wed, 15 July 2015 15:49 UTC

Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97C8E1B2B04 for <multipathtcp@ietfa.amsl.com>; Wed, 15 Jul 2015 08:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 oq0LLobP-WVW for <multipathtcp@ietfa.amsl.com>; Wed, 15 Jul 2015 08:49:31 -0700 (PDT)
Received: from smtp5.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1B81B2AFF for <multipathtcp@ietf.org>; Wed, 15 Jul 2015 08:49:31 -0700 (PDT)
Received: from mbpobo.dhcp.info.ucl.ac.be (mbpobo.dhcp.info.ucl.ac.be [130.104.228.16]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp5.sgsi.ucl.ac.be) by smtp5.sgsi.ucl.ac.be (Postfix) with ESMTPSA id AC66C1982E0; Wed, 15 Jul 2015 17:49:24 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be AC66C1982E0
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1436975364; bh=RzUniy8p67JlvRPmDj3SYx/978SvUyMQBfr1PGysjLo=; h=Reply-To:Subject:References:To:Cc:From:Message-ID:Date: MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding: Date:From:MIME-Version:To:Subject:References:In-Reply-To: Content-Type:; b=DL3S+B4vVgfYXplWDtiBAHdiiHKSgmvykgidCbvBzuXau1bwESYFwgO4UR+lqoySj W8xhTLelS2QN76v1+VRJIhmb1i69aqpl4o8bN9LtcDJ/BWXGB0o4OOF0NKaC0OO3CZ ikaVcK6CTMQpAiugcv7+MqLJ9jMD7bsmgkwH5WHs=
References: <1436204168109.20146@bt.com> <1436205703501.53882@bt.com> <787AE7BB302AE849A7480A190F8B933005359DAA@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <559FD6FF.3040003@uclouvain.be> <787AE7BB302AE849A7480A190F8B93300535BCE9@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <55A672C8.7060901@uclouvain.be> <20150715154413.GF15860@Chimay.local>
To: Christoph Paasch <cpaasch@apple.com>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <55A68104.8070401@uclouvain.be>
Date: Wed, 15 Jul 2015 17:49:24 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <20150715154413.GF15860@Chimay.local>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99-beta1 at smtp-5.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-MailScanner-ID: AC66C1982E0.A448C
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <http://mailarchive.ietf.org/arch/msg/multipathtcp/ckGJGBGuKifAZdYdfkQSxIngQcA>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Subject: Re: [multipathtcp] Preparing for Prague meeting - things to delete or add to MPTCP protocol bis
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
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, 15 Jul 2015 15:49:32 -0000

Christoph,
>
> On 15/07/15 - 16:48:40, Olivier Bonaventure wrote:
>>>>>                                           +-+-+-+-+
>>>>>
>>>>>         Flags is a set of 4 flags:        |C|r|r|r|
>>>>>
>>>>>                                           +-+-+-+-+
>>>>>
>>>>>         C flag MUST be set to 1 when the address/port are checked.
>>>>>
>>>>>         "rrr" are for future assignment as additional flag bits.
>>>>>
>>>>>         r bits MUST each be sent as zero and MUST be ignored on receipt.
>>>>>
>>>>
>>>> However, I'm stil not convinced by the usefulness of using the C bit
>>>> that you propose. If a host knows that it cannot receive a SYN over a
>>>> given address, then the best solution is to not advertise this address.
>>>
>>> [Med] Agree. An implementation that supports the "C" flag is likely to advertise addresses/ports for which pinholes have been created in NATs/FWs and address/ports that can be used to receive incoming packets successfully.
>>
>>
>>> The issue with the implicit approach (i.e., no C-flag) is at the server side: should the server interpret the advertisement of an address/port as an indication that packets can be sent without experiencing reachability issues or not?
>>
>> This is what RFC6824 assumes today. ADD_ADDR is only a hint about the
>> possibility of trying to reach this address. Anyway it will be a SYN and the
>> host will wait for a SYN+ACK to confirm the reachability
>
> I think, concerning the reachability, what is rather interesting is to
> advertise the secondary address without wanting the peer to even try
> establishing a new subflow to this address. This advertisement is done in
> case the "primary" subflow becomes unreachable. If it becomes unreachable,
> then the peer can use the advertised address to create a new subflow.

You would then propose a kind of "Backup" flag in the ADD_ADDR option 
meaning that this address should only be used to create a subflow if the 
primary subflow fails ?


Olivier