Re: [PANRG] Question regarding multi-link work

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 01 April 2022 15:17 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 1CEAB3A1731 for <panrg@ietfa.amsl.com>; Fri, 1 Apr 2022 08:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 y6h7t_WfNIvA for <panrg@ietfa.amsl.com>; Fri, 1 Apr 2022 08:17:12 -0700 (PDT)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (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 2A4C43A15FE for <panrg@irtf.org>; Fri, 1 Apr 2022 08:17:12 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id t123so2936366vst.13 for <panrg@irtf.org>; Fri, 01 Apr 2022 08:17:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UOm8pdDjlLLhDegfVtksQOPYVUrShAQUhF+611duLPc=; b=jBdzLGjYSfcTr2xVZUPvPLrWks/OsvGkGeuUvAIFEefDzoOhK8VJhHv0w2QAmzwv1C bUHZ1ODrbdWDNXyy4VL7l/Ycc0PWfMWkMxEFD/Oa/8RQiGh2kZ3J2S1z8EfVuFW2+QVy lLOqEw4J8QTxq22QcVdW8yIlIQBXp7pMvCO64RMeNjcG3anM5MIrHM2RhwQENrSErm3r phbpL/nkAG+zHhbASitxismEhPwhM7DqW64WkRs5oO1fZJRXULS4T6AXztM2cp9R6xQN 9RiEQy+dW8oYVbIdqzVQ8zza2XhrcTH2VdlGjFsx6flyZDji4XP7EkbXTtSgoq/DkjlB Vncw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UOm8pdDjlLLhDegfVtksQOPYVUrShAQUhF+611duLPc=; b=rXcuHWF2mBfkQZy6+C3ieYN9u9j8lHjOaW4VBow6kD33ZSJDKSx3jFpkRiNXXtS2GY A7R/N6CfKgHpPMnQ+4ObkSfl3gjlSOHuNIIqT68t/TPpv6gyqgpGoPY6ixUjnt5wO8cz EqOUMmzTq9GE58xrypt0FijRZ9T0u3r/pbY82fN+vRLaLBp4XEw2RYhmS+bpDY1vNS/N IZo7oF4DJp32PM/f1xtCA6zIGm1bvSDN5B0bL7hCMFRj3CjPiu3rAOm7mSccV8rZoBkj DZpsRZqbbDpTThFW7eQPrWfl5Mc5IgC1q25O1XvHbRowzBjLbYvwqyMiCISnFVD2G2DG jmLw==
X-Gm-Message-State: AOAM530Ykt/OZpujhTKBLk3UG4jN0/PBfOcYQJfS6OMFeXKfGMkcORED +GeYp6l1ps7dLH0bZ1H4DheCTKg/bsGbN6wOclTc0b7Z
X-Google-Smtp-Source: ABdhPJz/gEb9m7JWFvkYr9eMV3grZ9zIBfNVhxX79Ygw6/Vvebu7uCnFE3V1kV/UBzxUaTTo+KrhlgsxbLKw/t7zM9w=
X-Received: by 2002:a67:b306:0:b0:325:57ff:86dd with SMTP id a6-20020a67b306000000b0032557ff86ddmr3868709vsm.29.1648826230475; Fri, 01 Apr 2022 08:17:10 -0700 (PDT)
MIME-Version: 1.0
References: <j-_2qPQi05DTbuloyM_w7LpiqpJTTvSlAjPlVupc0Dn8Y80aeW1YMiY6Kl2kpkEMbvTXfB4c7UZu9Tcc8j4wCG1pgJS_vk9sg6uyZdZ7dhc=@interpeer.io>
In-Reply-To: <j-_2qPQi05DTbuloyM_w7LpiqpJTTvSlAjPlVupc0Dn8Y80aeW1YMiY6Kl2kpkEMbvTXfB4c7UZu9Tcc8j4wCG1pgJS_vk9sg6uyZdZ7dhc=@interpeer.io>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 01 Apr 2022 10:16:44 -0500
Message-ID: <CAKKJt-c25gAcb6zYTF9XXaCsrhEFQis+WpNCnQW91jwwFZ-WcA@mail.gmail.com>
To: Jens Finkhaeuser <jens@interpeer.io>
Cc: panrg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000c3901505db9945cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/fJi7WbrgZbmGnNU3MQzzScttzW4>
Subject: Re: [PANRG] Question regarding multi-link work
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: Fri, 01 Apr 2022 15:17:17 -0000

Hi, Jens,

On Thu, Mar 24, 2022 at 12:00 PM Jens Finkhaeuser <jens@interpeer.io> wrote:

> Hi all,
>
> I'm new to the lists (tsvwg and panrg), and have been pointed here for
> multi-path related topics. I have a question if there is interest in
> something.
>
> A couple of years ago I created a very simple tunneling protocol with
> multi-link capabilities. From that I started writing a paper, which never
> ended up getting published. I was wondering if that paper might generate
> some interest as an internet draft, in which case I'd put effort into
> converting it.
>
> The work was borne out of experiences with MP-TCP for tunneling on the one
> hand, and requirements from drone communications links on the other. In
> particular, the latter requires very fast fail- or switchover between
> links, while the tunneling application makes TCP a little less than ideal.
>
> In its concrete (prototype) implementation, the protocol is UDP-based, so
> is probably comparable to MP-UDP efforts (at first glance).
>
> However, the paper concerns itself quite deliberately with the abstract
> state machine(s) and messages. As such it does not place any requirements
> on UDP/IP addressing and could just as easily be applied to serial links,
> Ethernet or any communications channel that can be identified somehow. In
> fact, I would consider its main contribution that it is as agnostic of the
> message transport as I deemed possible. This is also why I have been
> avoiding the "path" term a little.
>
> Similarly, it is not particularly concerned with bidirectional
> communications. It takes the view that a multi-link is established if at
> least one egress and one ingress link is viable.
>
> Since multi-path concerns have been discussed here, I can see few better
> places to take this. But with how far removed the paper is from any
> protocols in development at the IETF, I still wanted to sound out interest
> before taking on the work in converting this into an Internet draft.
>

Speaking only as one participant in PANRG, I think PANRG is a fine place,
at least to start, because the multipath work in IETF (at the transport
layer) is pretty much tied to a specific protocol that's being multi-pathed
- Multipath TCP is in TCPM, Multipath QUIC is in QUIC, Multipath DCCP is in
TSVWG, and if a new home for SCTP is created, as was discussed in
TSVAREA last week, that would be a fourth home.

And, surprising literally no one, I'm interested in learning more about
your thoughts.

I didn't see a link to your work-in-progress - could you share it, whether
with me or with PANRG?

Best,

Spencer


> Thank you for your initial feedback!
>
> Jens
> _______________________________________________
> Panrg mailing list
> Panrg@irtf.org
> https://www.irtf.org/mailman/listinfo/panrg
>