Re: [PANRG] Path Selection for Multiple Paths

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 02 August 2021 20:43 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: panrg@ietfa.amsl.com
Delivered-To: panrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEC83A1BCA for <panrg@ietfa.amsl.com>; Mon, 2 Aug 2021 13:43:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 6x_ndsjCEA-N for <panrg@ietfa.amsl.com>; Mon, 2 Aug 2021 13:43:53 -0700 (PDT)
Received: from mail-vs1-xe2a.google.com (mail-vs1-xe2a.google.com [IPv6:2607:f8b0:4864:20::e2a]) (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 5AA233A1BC7 for <panrg@irtf.org>; Mon, 2 Aug 2021 13:43:53 -0700 (PDT)
Received: by mail-vs1-xe2a.google.com with SMTP id t2so10224003vsa.11 for <panrg@irtf.org>; Mon, 02 Aug 2021 13:43:53 -0700 (PDT)
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=Bn16lo+b13sbtLxg6usqZVdPib8yGDMC92ROG17Furo=; b=KsaBoeaR3eZ+1duEtOZdq9MPSgVUyUBy0tAzLq9gPn1PqYQqZU/JlmXKRjG2KbgZpx wR6JF4+rUv6hEiqhH8lVKv1aUkFKq7vBLO2zyKNJSdW2OyV0i0nU9kxOl9tVHFC1b6/g r7DKDzZfVjyEVzK3NnYG37e1aMHnYoltnZAfYvPxH/BeBFDIrXGrHUJBELBoN8ygzzDT A8NlM25zACdsRiHQqapEH0Pp8UUJjiCKLMgNanE6pLE6ZYGcS4WLg79lU6otKkec6FwP l+xCD9MsM47S7bd/Q0VfDbObNhIGVwPq6X3+zsImUsAoez7W6bscp+ds2lmtUtIJNiNq R9Lg==
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=Bn16lo+b13sbtLxg6usqZVdPib8yGDMC92ROG17Furo=; b=nj1xdapaoaGLYCNRE6Sz6vKA0sUB0fe5n/bTeTC2HgxwHK9l/W+7yu+gTSGm/go7a6 uU4Hot5T5uVr2lU4QlFbp5AHqd4tflmwxnxcFxCup3uwWs/NhgHCjV1YC9J+eyJXEpwD upYjt8GMUn86jCBs7/txFAe1V5ocfvnhKBiUHgFwug1ilMFGa8HeZom855107PtEvZNL VUvVzKWftl3IPzQHsh4c+ltxY3er3yRG1LaH4l8XH17enLKcXnUa0NTEhfiWMl/cJN6m +cIFqujUjnxkPxYJDIQqrQBeLZObtar/w5ZT/ygguqhblNhpj2Rmtk2Ppx3cr7BimT3Q /pWw==
X-Gm-Message-State: AOAM530DAxIRvJySTZxjqaLOqnCBQsR35OJoIpgsQVkR93yMxOJ2M7ob xpBb3xoKpG2Gi2XHwvW5R+fCwVJWYmXoimAlkSM=
X-Google-Smtp-Source: ABdhPJyyTFJiDieP6R4lgH6L/8Byyudw9gG1wSR+dxPhEeyyd/4BQSq6GM2vLlG5p/3A4OoJw4cfBLnzwl8wNnJ/AuI=
X-Received: by 2002:a67:f7ca:: with SMTP id a10mr3802860vsp.7.1627937031526; Mon, 02 Aug 2021 13:43:51 -0700 (PDT)
MIME-Version: 1.0
References: <FRYP281MB040576E811512C30F25A1833FAEF9@FRYP281MB0405.DEUP281.PROD.OUTLOOK.COM>
In-Reply-To: <FRYP281MB040576E811512C30F25A1833FAEF9@FRYP281MB0405.DEUP281.PROD.OUTLOOK.COM>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 02 Aug 2021 15:43:24 -0500
Message-ID: <CAKKJt-do1qjA9wPbY1z=u6gctu_TPfGErRVT_3Af3v4Lfn58NA@mail.gmail.com>
To: "Amend, Markus" <Markus.Amend@telekom.de>
Cc: panrg@irtf.org
Content-Type: multipart/alternative; boundary="0000000000007b1a8a05c899a0fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/yuBzFSxCRE01RDREj83Wg-fqn3c>
Subject: Re: [PANRG] Path Selection for Multiple Paths
X-BeenThere: panrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Path Aware Networking \(Proposed\) Research Group discussion list" <panrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/panrg>, <mailto:panrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/panrg/>
List-Post: <mailto:panrg@irtf.org>
List-Help: <mailto:panrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/panrg>, <mailto:panrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Aug 2021 20:43:59 -0000

Hi, Markus,

On Mon, Aug 2, 2021 at 10:40 AM <Markus.Amend@telekom.de> wrote:

> Dear Spencer, all,
>
> I just had a look into the IETF111 PANRG recordings and found the
> presentation about Path Selection for Multiple Paths very refreshing. It
> would be good to have a place where multipath challenges and solutions can
> be consolidated in IETF. The challenges you brought up in your presentation
> are related to multipath transport layer approaches like
> MP-TCP/QUIC/SCTP/DCCP, but also (partly) to any other approach on layers
> different to this, e.g. GRE bonding (RFC8157) etc. pp. That's why I
> appreciated your updated presentation title "Path Selection for Multiple
> Paths" instead of "Path Selection for Multiple Paths in QUIC".
>

Thanks for your kind words!


> The individual topics you raised (and I expanded)
>
>   - scheduling
>   - reordering
>   - path estimation by CC or other means
>   - sequencing
>   - loss detection and handling
>   - nested or concatenated CC - e.g. QUIC over MP-DCCP (3GPP ATSSS)
>
> and also their possible interworking is an interesting research area.
>
> In the MP-DCCP development we are quite advanced in the identification of
> this challenges and for some of them we are providing quite efficient
> solutions. Some of them are documented as part of the MP-DCCP protocol
> draft in TSVWG others like scheduling, reordering and fast packet loss
> detection are provided to ICCRG or published in academic paper.
>

I think this is a key question for PANRG (and, more broadly, potentially
for other IRTF research groups). I like your topic list. Do you have
thoughts about which topics involve loss detection and congestion control,
which likely are (should be?) in scope for ICCRG, and which ones are
broader questions?

I made the assertion last week in PANRG that path selection was in scope,
and we seemed to agree on that. I'm also wondering about path estimation
(especially by "other means"), and about nested or concatenated paths
(assuming that not all the issues with nested or concatenated paths are
about CC).

But I'd like to know what you think, and what others think as well.


> I encourage and invite people interested in that research area to look
> into https://multipath-dccp.org as a nice little playground. The provided
> MP-DCCP Linux reference implementation there provides at least initial
> support for all of the topics mentioned above.
>

Very nice! and thank you for posting the pointer here - I also keep an eye
on TSVWG, and I supported the "sense of the room" hum for adoption there.


> So full support from my side, please go ahead with this work!
>
> Is your plan now to shift your work on
> draft-dawkins-quic-multipath-selection to PANRG? And maybe change the title
> of your current draft to a more general title like for example "Path
> Selection in Multipath transport"?
>

Striking out "in QUIC'' in my presentation title on
https://datatracker.ietf.org/doc/draft-dawkins-quic-multipath-selection/
for PANRG was a guess, but it seems to have been a good guess. That's
certainly what I took away from last week's discussion, so, yes. I think
I'm changing the filename to -panrg- in the next submission.


> Btw. it's my first post to the PANRG mailing list 😊
>

Welcome to the party 😂

Best,

Spencer


> Br
>
> Marku
>