IETF Logo Mail Archive

Fwd: New Version Notification for draft-dawkins-quic-multipath-selection-00.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 02 June 2021 13:55 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08113A43BE for <quic@ietfa.amsl.com>; Wed, 2 Jun 2021 06:55:33 -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, 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 M1dlri4_EW_I for <quic@ietfa.amsl.com>; Wed, 2 Jun 2021 06:55:29 -0700 (PDT)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 36A613A43BD for <quic@ietf.org>; Wed, 2 Jun 2021 06:55:29 -0700 (PDT)
Received: by mail-yb1-xb32.google.com with SMTP id x6so3922106ybl.9 for <quic@ietf.org>; Wed, 02 Jun 2021 06:55:29 -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; bh=zGubncZfDKcBoSXnjOfUkcNSs6uBmlb/t7qF2XEPuoo=; b=IEYsu87f/hoHlUkCZNravdZue2FMFstgAHJItjLAkiu4FiAcATA3oHVchPg7sQVXIH MK2pLPIfPVDvoTtNGHu+WjXDybpjZxRq1+tro8JWMqmnzCjpCuWxSN4BeWk6BmB8w5oD 5f+QjDQfa5ms4kNFTTo65nfdrs68rtjfhRM9Opgpvk/OHwc/lVSYGsd+F69s5SDVankT U2Y25quTT+cAa/o6C9c+LiurDAUmWSVvr/bB5BzzfAUq+4nAyDQPXezaaskdF6lL9cvU TtZKrvDbFWvGeWpCjl/mQRsVl4ncxYXRn3Hwc7cMPLn2L7oLzUBICFHJreL28yC3zrfP CpUg==
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; bh=zGubncZfDKcBoSXnjOfUkcNSs6uBmlb/t7qF2XEPuoo=; b=ew2s5Tai4mgCgP/gUW0VjL4PyWj2uIs8wJmNfLBJw8slM4iOUFOy23dCXWtbBFYQBH ank0X68hdGNkmJxDe2iK9CL3//vLhiS17Dox7WHBQjahu8/0XO37tchBRO7oPgEv3DT+ oHGNMXLS/MKCjp5En7MaVucOTOHBizNgNpU5MPfc7F6mIaRspCH6EUj0UXQNa1V9lGyc eYK2F1j8wK1KLEjUt2ftf3lYms7KGAXIJM2wOHDdJfaV+h/NWH1I9Bu+Yu24LQ1WcRAC DY1zusGdpEdMxeR12rlWOD4oBYVKdqi9mCoW4HJN3fApLT8YUeBsxRhh3jaPZy5kBvMB sG7g==
X-Gm-Message-State: AOAM531Hs4i5LSj0xCeeIQhrdDmMnG4izm6i6WsB9Xe7CJsrZx9BjpZ5 rRq9RaJwuUDCw5jQnyMn5niRxmtPblUZjZ+7UNfRErjthDI=
X-Google-Smtp-Source: ABdhPJxxF5y0iUp1tPi069Ct6PgjHdf1s1jVxdchSWUwxvAGDz3Lhxb/LWLVgBcXd+YG+D6kn/YSzTLC1l2PKG7aeLE=
X-Received: by 2002:a25:3746:: with SMTP id e67mr20907284yba.297.1622642127076; Wed, 02 Jun 2021 06:55:27 -0700 (PDT)
MIME-Version: 1.0
References: <162264185269.11534.14006814092093131959@ietfa.amsl.com>
In-Reply-To: <162264185269.11534.14006814092093131959@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 02 Jun 2021 08:55:01 -0500
Message-ID: <CAKKJt-fqriVF=h4YeLxhd8-CDH07ud1eK-m9TfUu7BWBSoAbvQ@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-dawkins-quic-multipath-selection-00.txt
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000094fede05c3c8cf15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hfR45BjZg9d7C9jZ6FXqIGPG56Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2021 13:55:34 -0000

Dear QUIC working group,

Just to let people know, I've continued to look at the way various QUIC
proposals have described using multiple paths, and looked for common
elements. This individual draft is the result.

I hope this is useful for the working group.

>From the draft:

   This document is under development in the Github repository at
   https://github.com/SpencerDawkins/draft-dawkins-quic-multipath-
   selection.

   Readers are invited to open issues and send pull requests with
   contributed text for this document, but since the document is
   intended to guide discussion for the QUIC working group, substantial
   discussion of this document should take place on the QUIC working
   group mailing list (quic@ietf.org).  Mailing list subscription and
   archive details are at https://www.ietf.org/mailman/listinfo/quic.

Best,

Spencer

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Wed, Jun 2, 2021 at 8:50 AM
Subject: New Version Notification for
draft-dawkins-quic-multipath-selection-00.txt
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>



A new version of I-D, draft-dawkins-quic-multipath-selection-00.txt
has been successfully submitted by Spencer Dawkins and posted to the
IETF repository.

Name:           draft-dawkins-quic-multipath-selection
Revision:       00
Title:          Path Selection for Multiple Paths In QUIC
Document date:  2021-06-02
Group:          Individual Submission
Pages:          13
URL:
https://www.ietf.org/archive/id/draft-dawkins-quic-multipath-selection-00.txt
Status:
https://datatracker.ietf.org/doc/draft-dawkins-quic-multipath-selection/
Htmlized:
https://datatracker.ietf.org/doc/html/draft-dawkins-quic-multipath-selection


Abstract:
   In QUIC working group discussions about proposals to use multiple
   paths, an obvious question came up - given multiple paths, how does
   QUIC select paths to send packets over?

   The answer to that question may inform decisions in the QUIC working
   group about the scope of any multipath extensions considered for
   experimentation and adoption.

   This document is intended to summarize aspects of path selection from
   those contributions and conversations.

   It is recognized that path selection is not the only important open
   question about QUIC Multipath, but other open questions are out of
   scope for this document.




The IETF Secretariat

v2.23.0 | Report a Bug | By Email