Re: [multipathtcp] Multipath TCP Address advertisement 5/5 - Communities

Fabien Duchêne <fabien.duchene@uclouvain.be> Mon, 14 November 2016 07:10 UTC

Return-Path: <fabien.duchene@uclouvain.be>
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 E57331295D1 for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 23:10:02 -0800 (PST)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 XV-kFTM8Bg_J for <multipathtcp@ietfa.amsl.com>; Sun, 13 Nov 2016 23:10:01 -0800 (PST)
Received: from smtp4.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3150129459 for <multipathtcp@ietf.org>; Sun, 13 Nov 2016 23:10:00 -0800 (PST)
Received: from [31.133.134.81] (dhcp-8651.meeting.ietf.org [31.133.134.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: duchenef@smtp4.sgsi.ucl.ac.be) by smtp4.sgsi.ucl.ac.be (Postfix) with ESMTPSA id BFEFD67D9D8 for <multipathtcp@ietf.org>; Mon, 14 Nov 2016 08:09:53 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.9.2 smtp4.sgsi.ucl.ac.be BFEFD67D9D8
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1479107394; bh=UI2mjuohn3Knbk/H8RG3Q3y3IC0ltEOG0So+UVi8P6o=; h=Subject:To:References:From:Date:In-Reply-To; b=mWwlluC4aX7xpu2tB2mifjZxEUXvSvk8VByoLUvdJMBKi2CjSrQuIwJsYQO2QBXQ6 j3LBn5MXxNKLoepzyO43CgvOuOvFWokfZYDSFm+KCytQGzH4H1gnOux1W2wsXWM+ED 0aXH6k8Jiw/YHsNgB1CIY58wg46ehnjBlQvIt3i0=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.2 at smtp-4
To: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
References: <581F243E.2050900@uclouvain.be> <DFC6E044-74AD-42FC-8450-C5910083BC35@gmail.com>
From: =?UTF-8?Q?Fabien_Duch=c3=aane?= <fabien.duchene@uclouvain.be>
Message-ID: <e88a58d6-a468-e22c-4ec4-81c6698b7cbe@uclouvain.be>
Date: Mon, 14 Nov 2016 16:09:50 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.2.0
MIME-Version: 1.0
In-Reply-To: <DFC6E044-74AD-42FC-8450-C5910083BC35@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sgsi-Spamcheck: SASL authenticated,
X-SGSI-Information:
X-SGSI-MailScanner-ID: BFEFD67D9D8.A127D
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: fabien.duchene@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/smBSBrSRLJIGqlff7L9mD5SzoHM>
Subject: Re: [multipathtcp] Multipath TCP Address advertisement 5/5 - Communities
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 14 Nov 2016 07:10:03 -0000


On 11/14/2016 04:05 PM, Alan Ford wrote:
> Hi all,
>
> But if you as a server know your IPv6 and IPv4 share a path, you may choose not to use one or the other. Same for the client. So under what circumstances does signalling this to the far end actually help?
mm thinking about it:
let's say that you have a v4 and a v6 that share a path, so you don't 
announce the v6. What happen if the v4 fails if you didn't announce your v6?
>
> Regards,
> Alan
>