IETF Logo Mail Archive

Re: [multipathtcp] MPTCP Schedulers

Zhen Cao <zhencao.ietf@gmail.com> Sat, 16 February 2019 13:54 UTC

Return-Path: <zhencao.ietf@gmail.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 C4A19130E74 for <multipathtcp@ietfa.amsl.com>; Sat, 16 Feb 2019 05:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bsvtBX5xUrD4 for <multipathtcp@ietfa.amsl.com>; Sat, 16 Feb 2019 05:54:09 -0800 (PST)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900D7130E73 for <multipathtcp@ietf.org>; Sat, 16 Feb 2019 05:54:09 -0800 (PST)
Received: by mail-ot1-x32b.google.com with SMTP id b3so21317406otp.4 for <multipathtcp@ietf.org>; Sat, 16 Feb 2019 05:54:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3TZj7fPZkCDw/Vn3imFyBqgF7tBq7WXDSy7LtoZful0=; b=ctHtA7n5u7ZsF9rnF4GfLqrXSxGvvyKE1bB0mqHQlB42LbhCjykfboAJXMWtwRebQ/ 8pOHUV8vaTpHFn9+B9UiCZ6A6IgNx073iVcrQUdZ47QtX32M6lWSlTRm9rXFuU/BAslI JndPPjo28vCMjZjX/NkurvwZyuHcQOl8aIOel/5gNS7ldJY7YsR78/+HzFyZb4+uj/jn +VfyWoQ07W3Rd6WH/boVQZpmxxf5WO3B3Y6btOeiA3234bPlXpkv1C7HTKMLenYiCgtD 9ygZqchNkkqoa8GOU2t7C615DG2mBP+5Aw6sKVNgcWmuTHGqfKWFLQRwvTdbQXSCzF1r +aOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3TZj7fPZkCDw/Vn3imFyBqgF7tBq7WXDSy7LtoZful0=; b=ThuzuAbrSS5pSPfxLJLWB9s/QXN12xlRtQy+tbpTM2WBKHw+sHCwCZ+ez7UUY0VvSp kWjdpa37AOo0iejTMPPm31qQn8f/0WX09CtkGykHcf2q/2T7AgVaUjq9diJH408+ToRU qqEXU6j7nyg3SXIndBprPdT3hnUequcaTFsUFrc2YwgXo8edbQQ6hIgTbPfvYgGNF/mq /1gwxk1heOkRb8ImQZhRGh4ck7o+OSQpoToBLexZ+Yek39Rf0/SFCaYdw/xVhLGEnzVw vNLdeF5t5tmW1bCYqh4BVwevvD//n4v3NST2R/EirSopuLrCLNsdGoWyHFWo0awm1utZ t2dg==
X-Gm-Message-State: AHQUAuZb7WLg9pGuV2v3hsF/NxxuUKKUIvLo5mCw2gkFvJ+rL0BgLILN tm+hTom03D+GWa4sAIdL4H9V5rgkohshA3ESHT0LIw==
X-Google-Smtp-Source: AHgI3IY+DtCahmvR+lDknN0WTX5UKWc/t0SvMBo1+3XRkWdMoNqwrnm6AWotVxyaeAzt031a9SXCqgs/C8/RSv/zXoc=
X-Received: by 2002:aca:4756:: with SMTP id u83mr8926079oia.60.1550325248713; Sat, 16 Feb 2019 05:54:08 -0800 (PST)
MIME-Version: 1.0
References: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro>
In-Reply-To: <a939bc37-16ed-9d8a-15d7-16dfec630290@cs.pub.ro>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Sat, 16 Feb 2019 21:53:58 +0800
Message-ID: <CAFxP68xhWEktWvJuowMstCBuS=a8Pg+hUD3x-jkFgxhBdFJWyg@mail.gmail.com>
To: Vladimir Olteanu <vladimir.olteanu@cs.pub.ro>
Cc: multipathtcp <multipathtcp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/CbSefp-6FcG2coD7yc99wDpCVXI>
Subject: Re: [multipathtcp] MPTCP Schedulers
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 16 Feb 2019 13:54:12 -0000

On Fri, Feb 15, 2019 at 9:43 PM Vladimir Olteanu
<vladimir.olteanu@cs.pub.ro> wrote:
>
> Hi guys,
>
> I'm trying to tie up any loose ends in the SOCKS 6 draft. There is some
> functionality which lets you change the MPTCP scheduler used by the
> proxy. The available schedulers are basically the ones available in the
> Linux kernel implementation.
> (https://tools.ietf.org/html/draft-olteanu-intarea-socks-6-05#page-20)
>
> Do you think it would be worthwhile to standardize the MPTCP schedulers?
> I think an informational or best practice RFC would be useful.

It's meaningful.  Documenting the existing schedulers (minRTT,
redundant, round robin) as informational documents will help the mptcp
practitioners to get better use of it.

In addition, path manager needs a better specification.  These can be
considered as the input to the co-chairs' ''call for future items of
the working group.  We may discuss it over at the upcoming meeting.

Cheers,
Zhen

> Cheers,
>
> Vlad
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp

v2.23.0 | Report a Bug | By Email