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

Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be> Fri, 10 July 2015 14:31 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 3EBF71B2C89 for <multipathtcp@ietfa.amsl.com>; Fri, 10 Jul 2015 07:31:39 -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 1GJfqp_LBg-b for <multipathtcp@ietfa.amsl.com>; Fri, 10 Jul 2015 07:31:34 -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 298751A9153 for <multipathtcp@ietf.org>; Fri, 10 Jul 2015 07:30:28 -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 DD2E31982B3; Fri, 10 Jul 2015 16:30:21 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.3 smtp5.sgsi.ucl.ac.be DD2E31982B3
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1436538621; bh=l07zaTqyxdPXJjEMxcqykzqS4GD60Hg5st3Si4oDLKg=; h=Reply-To:Subject:References:To: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=Q7qnaiTCWLB2uziB2mUclpbHxj4n7JmiLWpj6KLnPq7Vp/3Aypplal+xqjzdR4r9C 5+qscbClaJnIyjcQJ+YFGFWizfcYTNlxg+Ba0FlpIrCCYrAjUnWEI09hyuRruf+frQ YTCwfUVb4cxRnc+oChvtJ6ZSQD3Uvnu/2Eje+XSQ=
References: <1436204168109.20146@bt.com> <1436205703501.53882@bt.com> <787AE7BB302AE849A7480A190F8B933005359DAA@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
To: mohamed.boucadair@orange.com, "philip.eardley@bt.com" <philip.eardley@bt.com>, "multipathtcp@ietf.org" <multipathtcp@ietf.org>
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
Message-ID: <559FD6FF.3040003@uclouvain.be>
Date: Fri, 10 Jul 2015 16:30:23 +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: <787AE7BB302AE849A7480A190F8B933005359DAA@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
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: DD2E31982B3.A2D58
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/KqmSezXWuJGM8XtXMyYTrscyxzo>
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: Fri, 10 Jul 2015 14:31:39 -0000

Med,

>
> A change was proposed in
> (https://tools.ietf.org/html/draft-boucadair-mptcp-symmetric-02) to
> redefine IPVer field of ADD_ADDR as a set of flag bits (see below). This
> change applies also for ADD_ADDR2.


I think that replacing the IP version with a set of flags (at least in 
ADD_ADDR2 to prevent backward compatibility problems with the existing 
ADD_ADDR implementation) would make sense.

>                                          +-+-+-+-+
>
>        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. 
This will typically be the case when a host is behind a NAT or a 
firewall (I guess that at some point middlebox vendors will include 
software to parse ADD_ADDR and remove the ADD_ADDR that correspond to 
addresses that are not reachable accoring to their policies)


Olivier