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

Christoph Paasch <cpaasch@apple.com> Sun, 13 November 2016 07:53 UTC

Return-Path: <cpaasch@apple.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 3DB431293DF for <multipathtcp@ietfa.amsl.com>; Sat, 12 Nov 2016 23:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.799
X-Spam-Level:
X-Spam-Status: No, score=-5.799 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, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 mv0zSB8Ddk1J for <multipathtcp@ietfa.amsl.com>; Sat, 12 Nov 2016 23:53:29 -0800 (PST)
Received: from mail-in6.apple.com (mail-out6.apple.com [17.151.62.28]) (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 C818B128B38 for <multipathtcp@ietf.org>; Sat, 12 Nov 2016 23:53:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1479023608; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=eWSCdBtjEkfzehHOP7GlyJMoJbYrkhW/FNpeU8inkB4=; b=VC81Mjt+RkgzJoSrt8VKC+6sN57Dvh5SBl4rMaxQfpZPuvmtue/1cPQwdXdD06F9 6zs9SgtOptxqOM9CaduZtDOhSyI2gUWSR3pBwuLKZj9wEWmAoTX2SsDqKb2tWA4o kNcGLkCyH8r9diYfoyBtilkCsucJfOEvHmmDFPAFI77ZDnHArqcHuIObYATpr/3g 1rMmaSp/ydwLGy9EAWeOLKyhOnTDY/1OApevE7b9zYlNlOj4IcgqPpjqP1/QEJpq jtNLq9uq9cdI/HsBAsLcIMQIRcjDMde2RzsD2oTsWctHgPLJtlmKsYCmHweGsz7U FQDomB44+bPY3sxQrAGxIA==;
Received: from relay6.apple.com (relay6.apple.com [17.128.113.90]) by mail-in6.apple.com (Apple Secure Mail Relay) with SMTP id 19.87.16908.8FB18285; Sat, 12 Nov 2016 23:53:28 -0800 (PST)
X-AuditID: 11973e15-8ada39a00000420c-7f-58281bf8892a
Received: from chive.apple.com (chive.apple.com [17.128.115.15]) by relay6.apple.com (Apple SCV relay) with SMTP id 7E.F6.23613.8FB18285; Sat, 12 Nov 2016 23:53:28 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=iso-8859-1
Received: from localhost ([17.150.210.10]) by chive.apple.com (Oracle Communications Messaging Server 8.0.1.1.0 64bit (built Jun 15 2016)) with ESMTPSA id <0OGK00I06LX3W970@chive.apple.com>; Sat, 12 Nov 2016 23:53:28 -0800 (PST)
Sender: cpaasch@apple.com
Date: Sat, 12 Nov 2016 23:53:27 -0800
From: Christoph Paasch <cpaasch@apple.com>
To: Fabien =?iso-8859-1?Q?Duch=EAne?= <fabien.duchene@uclouvain.be>
Message-id: <20161113075327.GI4269@Chimay.local>
References: <581F243E.2050900@uclouvain.be>
In-reply-to: <581F243E.2050900@uclouvain.be>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUi2FAYpftDWiPC4O10PYt7H6YxWnxefZ3N gcljyZKfTB6vjn1nCWCK4rJJSc3JLEst0rdL4Mo4cP8pW8EpzoppZ6YyNzBeZe9i5OSQEDCR uL36FZDNxSEksJdRYsbrp4xdjBxgiWWL/SHiGxklDlz6ywLSwCsgKPFj8j0WkBpmAXmJI5ey QcLMAtISj/7OYIewdSR6v39jhuh9xSixvu0QWEJYQFKi+84dZhCbRUBV4v+LvawgNpuAlsTb 2+1gtoiAs8SMT7+YIQYZSxzecJsNojdY4vquM2wQNxhIPDzQxgpyg5CAtkTDSrAbOIH2Xuu9 CjZGVEBZ4u/heywQPx5hkziwMX8Co8gsJB/MQvhgFpIPZiH5YAEjyypGodzEzBzdzDwzvcSC gpxUveT83E2MoCiYbie6g/HMKqtDjAIcjEo8vByZ6hFCrIllxZW5hxilOViUxHkzvdQihATS E0tSs1NTC1KL4otKc1KLDzEycXBKNTDG97Mtn5Gy58jN/jPrU9eV7Ky2eFq8WHQL8+0a51W+ VuEv1irmXmk9daFHYp6C4OOvQeXHWUydHz+PXFWU4q2hcez0i4uh5+02Gfrs3nY00SBphfOv FYy85zc7sNxy1xD5rtQ8z87u82Z/tbRnlRNmLy3UbckoNPkq8907KJeLw9FZi0e2dpMSS3FG oqEWc1FxIgARn3sbYwIAAA==
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBIsWRmVeSWpSXmKPExsUi2FDMr/tDWiPC4PQ2eYt7H6YxWnxefZ3N gcljyZKfTB6vjn1nCWCK4rJJSc3JLEst0rdL4Mo4cP8pW8EpzoppZ6YyNzBeZe9i5OCQEDCR WLbYv4uRE8gUk7hwbz1bFyMXh5DARkaJA5f+soAkeAUEJX5MvscCUs8sIC9x5FI2SJhZQFri 0d8Z7BC2jkTv92/MEL2vGCXWtx0CSwgLSEp037nDDGKzCKhK/H+xlxXEZhPQknh7ux3MFhFw lpjx6RczxCBjicMbbrNB9AZLXN91hg3iBgOJhwfaWEFuEBLQlmhYCXYDJ9Dea71XwcaICihL /D18j2UCo9AsJFfPQrh6FpKrZyG5egEjyypGgaLUnMRKM73EgoKcVL3k/NxNjOBwLozawdiw 3OoQowAHoxIP74Y09Qgh1sSy4srcQ4wSHMxKIrx2EhoRQrwpiZVVqUX58UWlOanFhxiTgd6d yCwlmpwPjLW8knhDExMDE2NjM2NjcxNz0oSVxHmvdchHCAmkJ5akZqemFqQWwWxh4uCUamAs bsxTlnvDZsYzVfnjh3eT/7LsNueex2Cu/2ut3W032eKnW3zYvXIM1plamtiErt+yPPQqx+Ra 95dr5aSPcdz17XKV35+1WGhCmOzb2TOCA7/NOfuFa93T8606YhdfHa26EH1iv4rsgos5Hhr8 6+z9Wz2bC8VYp6knRQfvyz09N1tt/jvBY8ZKLMUZiYZazEXFiQBV1R6jqwIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/zv-yJiT0WFkNO4jCxE9nWcgWtNs>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
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: Sun, 13 Nov 2016 07:53:31 -0000

Hello,

On 06/11/16 - 13:38:22, Fabien Duchêne wrote:
> As we agreed in Berlin during IETF96, here are a few email to discuss
> the contributions proposed in
> https://datatracker.ietf.org/doc/draft-duchene-mptcp-add-addr/
> 
> To allow a host to inform the receiving host about the diversity of
> several addresses we propose to modify the ADD_ADDR to include 4 bits
> describing a "Community" associated to this address.
> The community values are an opaque field and it is expected that two
> addresses having the same community share some resources.
> 
> With the community bits, a dual-stack host could elect to regroup all
> the addresses attached to a single interface under the same community,
> allowing the receiving host to decide on which advertised addresses it
> wants to establish new subflows.
> This is because in the case of a dual-stack host, establishing v4 and V6
> subflows
> is not always the best solution.
> The idea here is to design a generic solution to regroup the address
> that shares
> the same forwarding type in a specific class.

I support this. Although, I wonder whether we need to use 4 bits. Maybe 3
are enough? (just trying to spare a bit ;))


Christoph