Re: [AVTCORE] Running multiple quic sessions over the same address/port pair

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 28 February 2022 03:54 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F433A08A1 for <avt@ietfa.amsl.com>; Sun, 27 Feb 2022 19:54:18 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 FZRuiBl1hS_5 for <avt@ietfa.amsl.com>; Sun, 27 Feb 2022 19:54:14 -0800 (PST)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (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 4C8A13A0899 for <avt@ietf.org>; Sun, 27 Feb 2022 19:54:14 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id e26so11657293vso.3 for <avt@ietf.org>; Sun, 27 Feb 2022 19:54:14 -0800 (PST)
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=8UylwL4rV/90F9VFLFOsDgE172vypsMEKkOonoDFMZE=; b=Ma32J6SPXsVS9l1cPircvnzp3Dku6zDuY5oNjKtd3F+qm3YSjyr13vN6aM0sqw6oRa hPOsDPL0jh+0lDtOzs2/MiaNvAb2+M1Mbx3paJVw9wXODyuhud2D2zR2bqPJCh9IMxxv Og915imd4uAkBZyICbCv2axoJ6yptP2kcURwlm8hZ0e9kccH7A0TXCBCHpb1pviYAQ41 LtM6WLwHayUuqaN4mwpHt6XpLw1F+XnT2kogLfQBrkGLw5yLLMfjmBkoC3AgUKnLnDts 7AIBEEMSJLMj84+XALp7JYk5h0iLo4dtfTwWrShPGELkxt1o+i9RONAARoTHzgrG4ehQ pBuA==
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=8UylwL4rV/90F9VFLFOsDgE172vypsMEKkOonoDFMZE=; b=2sTBd6pyCcUex7NaRGbn4yyqWIpEQL3drqDxNceQCMMpMIXjNdS5dZl+ZbFiY9UXbE SM/Mp+XHSCifzyIfkARAzmrYZxtbtvnGIR5DvAajPbJhYoE0F8nhVl5zGIVnscsymVib kD3eXX34JlAh8sNBVJhtdNZg4fC4ZCHv4lxGyPyt2zfa1UNFScwLf8/DX0rGUKeWs9vA WMP4ynMH647VhHmA4+SUO1s5oRTf0SOqyQIsMYLTnjvxaZN+IQ8W9szigLK15TjUrnJ4 xgMaCyMvsOPOTZzGzg3Q/QrB3jM3aQ561Wu5ENAtp1kyt4PD5MkmJtYJPo9dCdZKgayu x8AQ==
X-Gm-Message-State: AOAM533TTGYmhxr6c/O7vzRlZjUzWhC7t8MoYY/RhImNCDIqy/KQlmr1 YSVo5lI12uxR4MGi9yB311b6rhwIUp5ftUQekqMFdiT1jVQ=
X-Google-Smtp-Source: ABdhPJyT/D+RhTPC0k4/n0cEUpeISXoUnNYyWBfWP8K9sLbiAqb9E/GBU+UYpmcb1D9It0GpL5Xh2KWhDfanrNYGxJg=
X-Received: by 2002:a67:6dc5:0:b0:31b:f224:5028 with SMTP id i188-20020a676dc5000000b0031bf2245028mr6294581vsc.77.1646020452780; Sun, 27 Feb 2022 19:54:12 -0800 (PST)
MIME-Version: 1.0
References: <CAD5OKxujOvmuNi793cSKfc8A7BkrwxOPmGaRq0QAwGoYXpH2Qw@mail.gmail.com> <F572CCE5-A754-4992-BE1E-FD599A455DFE@gmail.com> <CAD5OKxs8awPt=7vka9tD9Z-ELZO+pGxi0-U8-d-a8c7LnZDwOg@mail.gmail.com>
In-Reply-To: <CAD5OKxs8awPt=7vka9tD9Z-ELZO+pGxi0-U8-d-a8c7LnZDwOg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 27 Feb 2022 21:53:46 -0600
Message-ID: <CAKKJt-dPvthGZOEeXoCBkeq8nW3TgwqZyFZSOVzGdL-JFEX26Q@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, IETF AVTCore WG <avt@ietf.org>, Robin Raymond <robinraymond@microsoft.com>
Content-Type: multipart/alternative; boundary="000000000000618e0505d90c0055"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/4V6nMrS0Syk70_DgDDZaXP4ySaw>
Subject: Re: [AVTCORE] Running multiple quic sessions over the same address/port pair
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2022 03:54:19 -0000

I should add one more point.

On Sat, Feb 26, 2022 at 11:37 PM Roman Shpount <roman@telurix.com> wrote:

> On Sun, Feb 27, 2022 at 12:18 AM Bernard Aboba <bernard.aboba@gmail.com>
> wrote:
>
>> On Feb 26, 2022, at 20:50, Roman Shpount <roman@telurix.com> wrote:
>> [BA] This should be possible. The means will differ depending on whether
>> we are talking about P2P QUIC (where you could use Connection-Id) or
>> something higher up the stack. Multiplexing as defined in rfc7983bis wasn’t
>> implemented in the P2P (g)QUIC Origin trial since the QUIC implementation
>> was pre-standard and lacked the capability. So only one connection was
>> allowed. At the time the focus was on P2P data not media, but in the
>> absence of priority support, it seemed desirable to allow distinct data and
>> media connections that might be constructed to use different cc algorithms.
>>
>>
> This is very interesting and can be one more reason to use QUICK instead
> of DTLS. The problem would be to map a pair of tls-id to a Connection-Id.
>

(After agreeing with Bernard's points)

Within the "Media Over QUIC" conspiracy, we have some folks that are
assuming they would use datagrams ("because datagrams"), and other folks
assuming they would use streams ("because multiplexing"). One of the things
that I'm finding in conversations on that side of the fence is that the
choice isn't obvious (even though it's obvious to everyone, it's not the
same obvious answer).

The QUIC working group started out thinking that they obviously needed some
way to multiplex datagrams, but then discovered that there were a lot of
(potentially conflicting) reasons to want to multiplex datagrams, so they
punted that to the application, in
https://www.ietf.org/archive/id/draft-ietf-quic-datagram-10.html#name-multiplexing-datagrams
.

I wrote about this in more detail, in
https://spencerdawkins.github.io/sdp-rtp-quic-questions/draft-dawkins-sdp-rtp-quic-questions.html#name-quic-datagram-multiplexing
.

(I *really *need to update my sdp-rtp-quic*-questions* draft - I wasn't
expecting that, but I'm happy to do it)

Best,

Spencer


> _____________
> Roman Shpount
>
>