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

<Markus.Brunner3@swisscom.com> Tue, 15 November 2016 07:49 UTC

Return-Path: <Markus.Brunner3@swisscom.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 1B956129516 for <multipathtcp@ietfa.amsl.com>; Mon, 14 Nov 2016 23:49:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.716
X-Spam-Level:
X-Spam-Status: No, score=-5.716 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
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 6DTVITm1jMBt for <multipathtcp@ietfa.amsl.com>; Mon, 14 Nov 2016 23:49:50 -0800 (PST)
Received: from mail.swisscom.com (outmail100.swisscom.com [193.222.81.100]) (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 8896E1294F3 for <multipathtcp@ietf.org>; Mon, 14 Nov 2016 23:49:49 -0800 (PST)
Received: by mail.swisscom.com; Tue, 15 Nov 2016 08:49:46 +0100
From: <Markus.Brunner3@swisscom.com>
To: <alan.ford@gmail.com>, <fabien.duchene@uclouvain.be>
Thread-Topic: [multipathtcp] Multipath TCP Address advertisement 4/5 - Priorities
Thread-Index: AQHSOCkvDD7+wvdxwECEz2fLcyUOvKDWhHmAgAEvuACAAEdhgIABvcQA
Date: Tue, 15 Nov 2016 07:49:45 +0000
Message-ID: <59A9F7DC-7B46-4C31-BE2F-48F64B9631AC@swisscom.com>
References: <581F2334.8010403@uclouvain.be> <20161113075145.GH4269@Chimay.local> <826bf9ab-e9b7-a89b-28de-676deece8a4b@uclouvain.be> <D0FA35FF-B17F-4F7F-92E1-D9FBB6E735A7@gmail.com>
In-Reply-To: <D0FA35FF-B17F-4F7F-92E1-D9FBB6E735A7@gmail.com>
Accept-Language: de-CH, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [138.190.134.10]
Content-Type: multipart/alternative; boundary="_000_59A9F7DC7B464C31BE2F48F64B9631ACswisscomcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/GoSf_LiBVmHjrxwRVb_2kc96h64>
Cc: multipathtcp@ietf.org
Subject: Re: [multipathtcp] Multipath TCP Address advertisement 4/5 - Priorities
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: Tue, 15 Nov 2016 07:49:53 -0000

Hi,

we are happy with a solution with the characteristics of (b) for the moment, not sure whether other use cases would need something else. Plus we had a lot of discussions on what „full“ would mean spcifically.

Marcus


Von: multipathtcp <multipathtcp-bounces@ietf.org> im Auftrag von Alan Ford <alan.ford@gmail.com>
Datum: Montag, 14. November 2016 um 07:14
An: Fabien Duchêne <fabien.duchene@uclouvain.be>
Cc: "multipathtcp@ietf.org" <multipathtcp@ietf.org>
Betreff: Re: [multipathtcp] Multipath TCP Address advertisement 4/5 - Priorities

Hi all,

After discussion at IETF97, I think it’s clear that this proposal - the idea of “priority” - means different things to different people. For example:

a) A percentage split - but would that only kick in when one link is full? Or would all traffic always be split?
b) Prioritising subflows, overflowing only when one is full
c) QoS (latency, bandwidth, etc) values
d) etc etc

Personally I think only (b) makes sense at the subflow level, everything else is far too complex to signal in a few bits. Whether it is of use to people in the real world, however, I don’t know, however!

I also think it’s entirely feasible to achieve a lot of the traffic engineering here by using TCP control signals - ACKs and window size - to slow down communications. As a sender you can already control rate based on your local policy, and at the receiving end you could use ACKs, ECN, window, etc.

This proposal needs a much clearer idea of what it’s trying to achieve before we could consider it for merging.

Regards,
Alan

On 14 Nov 2016, at 01:58, Fabien Duchêne <fabien.duchene@uclouvain.be<mailto:fabien.duchene@uclouvain.be>> wrote:

Hello,

Inline,

On 11/13/2016 08:51 AM, Christoph Paasch wrote:

Hello,
while I support adding more info to MPTCP to allow a finer-grained control
of the peer's scheduling, I think the priority-bits should be defined in a
more precise way.

I see the this work here as a way to allow for a more deterministic behavior
when an MPTCP-client connects to a MPTCP-server. As of today, when I on my
mobile device connect to a server that is outside of my control, the only
way I can tell the server to schedule traffic in a certain way is by using
the backup-bit. Upon which I can expect the server to not send traffic on
this subflow unless the primary subflow is broken.
This kind of "configuration" is not sufficient for most use-cases.
I see the priorities as a way for the client to tell the server exactly
what kind of scheduling it expects to meet a certain "QoS-requirement".
So, we should clearly specify what each priority means.
The way I wrote the draft was more like "ok, let's tell the server that, if possible,
I'd like to receive most on the trafic on this subflow, then this one, then this one".
This is why I wrote

"The priority field MUST be interpreted as an unsigned integer value with the highest
numerical value being the most preferred one."

While I agree that we should be as specific as possible, I wonder how we could be more
explicit about this. Any idea?
If we are too specific, like saying "always schedule on the highest priority subflow,
until the windows is full, then skip to the next one" we are actually writing a strict priority
scheduler, and I was hoping that we could leave the priority open to more creative ways
of handling the priorities.
It's a MAY because I'm not sure that making the respect of the priority a MUST would
be interesting, for backward compatibility, but also because the priorities of one host
could clash with the other's own interest.


If we leave the interpretation of the priority-bits open to the
implementation, hosts still cannot rely on getting a certain service by
the peer when set the priority bits.


Thoughts?



Cheers,
Christoph
Cheers!

Fabien

_______________________________________________
multipathtcp mailing list
multipathtcp@ietf.org<mailto:multipathtcp@ietf.org>
https://www.ietf.org/mailman/listinfo/multipathtcp