Re: [Moq] Fwd: New Version Notification for draft-dawkins-sdp-rtp-quic-questions-01.txt

Bernard Aboba <bernard.aboba@gmail.com> Wed, 27 October 2021 15:02 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: moq@ietfa.amsl.com
Delivered-To: moq@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 772FD3A0D91 for <moq@ietfa.amsl.com>; Wed, 27 Oct 2021 08:02:23 -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 oi5WkPpgQP0Z for <moq@ietfa.amsl.com>; Wed, 27 Oct 2021 08:02:21 -0700 (PDT)
Received: from mail-ua1-x934.google.com (mail-ua1-x934.google.com [IPv6:2607:f8b0:4864:20::934]) (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 065213A0D7C for <moq@ietf.org>; Wed, 27 Oct 2021 08:02:21 -0700 (PDT)
Received: by mail-ua1-x934.google.com with SMTP id u9so5472185uac.8 for <moq@ietf.org>; Wed, 27 Oct 2021 08:02:20 -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=dkJeuXfgToMFMuLMKB2t8qgmVFjCQhxPyUcfGIXX+g8=; b=ayAuIyuaZ3wa31dmEk0HIXSx1nZaK2qge2+PUG+IdHQMutrtNwRd8osJ711yYxxDen x35wL1YM694lnLghZLFzzA3oR7Bi3pqxdpDxlE1rFdfzrU3kp1bycwdndRFQxp80donE MRSAjyd9huHJAyNr5fY0kRNmfHNvHzBvpy0iThAIQ6F9SsS+2Ioj1tUj84/8FbCHTtk2 LXevEjQHTfYtlAX19N0MkDoAVuBk04F5fh+grReaWbgjtGOyjVc528r+cmACOqfPZl9j x8nf/W0urHLKZjmYiKkMYf7LXp5IoSOxDzXOgRqks3l6h97RuLEseG1xnxC9jQ0UycNo NWfw==
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=dkJeuXfgToMFMuLMKB2t8qgmVFjCQhxPyUcfGIXX+g8=; b=qcAuXjOXGcEdteasjmNJDP+t4P1PR2AtTq+icGps6hJsXtzrtfpav90wVOd59axZCd FNITF5HN0KoCYuFS7Ne9d//1awm6uA8d8T31+rgo5FrFiq+NYDkbiR5COLkxBcfxpyXv xFEsuUZ+CrVSnnJ9Mo7q/tZW/j2xIJb0wgVZBPI1poXjNaj6/lclt7wt1IHcbXvOF7gi Ps0x+P1tNYgTJ+j7nIEnz809r1J56avdqfzP3Z/Va5TlQVUSAkHCCxvl8QfYPzb0nNQ8 sRg5B8/95hMZpWp6/akDqbSeKddLhFvyN5mGIJaGOrSrkS86MQmEL7ickML0ps36GuSh JP9g==
X-Gm-Message-State: AOAM530nWrehu1AgSykul6nViiyjt555RRFYUC16fXN0+XkVgpmkV5Hz 76JvsDgfbY2Q96H4yP5aQb/YKvKOAZxvE4G9BPM=
X-Google-Smtp-Source: ABdhPJxE4dKD/2TG+bkDCAHkt+OKN4k9MS/EXKOTh6FbKPJvdH+e3A4jqKapw4nN+FVOCnxFpTfvxZLu9gkizLF8A7A=
X-Received: by 2002:a67:fd4c:: with SMTP id g12mr18464425vsr.22.1635346934855; Wed, 27 Oct 2021 08:02:14 -0700 (PDT)
MIME-Version: 1.0
References: <163518349400.19493.4114152406197548259@ietfa.amsl.com> <CAKKJt-fP_mqMqL7k6Bi4VbQyswD3XHN7Vmvw0L7mRM379F8p6w@mail.gmail.com> <CA+ag07Z3MmNne_9MDN+yJ5j23x5Pq4zoOWnxQoqwdX+Jry1raQ@mail.gmail.com>
In-Reply-To: <CA+ag07Z3MmNne_9MDN+yJ5j23x5Pq4zoOWnxQoqwdX+Jry1raQ@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 27 Oct 2021 08:02:04 -0700
Message-ID: <CAOW+2dt3c=wcSj28qAFrK4+a-ww+S2Oa57YrjjX-4FWBuH-Uww@mail.gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000024981c05cf56e156"
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/vIIshn68PvfAYXRJbeFZeQpweF8>
Subject: Re: [Moq] Fwd: New Version Notification for draft-dawkins-sdp-rtp-quic-questions-01.txt
X-BeenThere: moq@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Media over QUIC <moq.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/moq>, <mailto:moq-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/moq/>
List-Post: <mailto:moq@ietf.org>
List-Help: <mailto:moq-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/moq>, <mailto:moq-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2021 15:02:23 -0000

Sergio said:

"We should only support RTP over quick datagram, what about
webtransport support?"

[BA] Currently there are issues with WebTransport support for Web realtime
communications in the client -> server direction, summarized here:
https://docs.google.com/presentation/d/1SG1FUvn9UKGx_gAqWnCzPHlsIXkDUXctZPs7blfqS5k/

While the metrics issue is unique to WebTransport, the issues with QUIC
congestion control will also affect realtime media directly over QUIC.  The
biggest issue is slow recovery of media quality after packet loss. Without
probing similar to what is done in WebRTC today, recovering media quality
will be slow, particularly when simulcast or SVC is used.

"We need to define how ICE and QUIC over RTP interact together (should be
fairly simple)"

[BA]  The basics of QUIC over ICE were demonstrated in the RTCQuicTransport
Origin trial:
https://developers.google.com/web/updates/2019/01/rtcquictransport-api

I don't think that RTP adds any complexities.

A specification for QUIC multiplexing with STUN/TURN is available here:
https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rfc7983bis











On Wed, Oct 27, 2021 at 7:39 AM Sergio Garcia Murillo <
sergio.garcia.murillo@gmail.com> wrote:

> Hi Spencer,
>
> Great to see a proposal in this direction! I was tempted to
> propose something similar, so I will be willing to collaborate. Do you have
> any github project were we could propose changes or raise issues?
>
> Here are some of my preliminar thoughts:
>
> - We should only support RTP over quick datagram, what about
> webtransport support?
> - IMHO the name should be UDP/QUIC/RTP/AVPF (SAVPF is for SRTP which we
> don't use as the security is provided by the underlying QUIC transport)
> - We need to define how ICE and QUIC over RTP interact together (should be
> fairly simple)
> - Do we want to specify how to reuse an established QUIC (or web
> transport connection) for sending RTP within it? This may be impacted by
> the ability to do datagram multiplexing.
> - How about Datachannels over QUIC?
>
> Last, even if this list is for media over quic, this proposal seems that
> could be better suited for avtcore or mmusic discussion.
>
> Best regards
> Sergio
>
>
> El mar, 26 oct 2021 a las 23:37, Spencer Dawkins at IETF (<
> spencerdawkins.ietf@gmail.com>) escribió:
>
>> Dear MOQ subscribers,
>>
>> Just to follow on James' excellent lead, I've also revised this draft,
>> which is an attempt to identify the requirements that RTP over QUIC will
>> place on SDP signaling for this type of media traffic.
>>
>> As James said about our mutual draft, my understanding is that we're
>> expected to have conversations about "Media Over QUIC" on this mailing
>> list. If anyone has a different understanding, please let the mailing list
>> know, so that we can Do The Right Thing.
>>
>> Otherwise, let's be thinking how to move this work forward in the IETF
>> 112 timeframe.
>>
>> Best,
>>
>> Spencer
>>
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org>
>> Date: Mon, Oct 25, 2021 at 12:38 PM
>> Subject: New Version Notification for
>> draft-dawkins-sdp-rtp-quic-questions-01.txt
>> To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
>>
>>
>>
>> A new version of I-D, draft-dawkins-sdp-rtp-quic-questions-01.txt
>> has been successfully submitted by Spencer Dawkins and posted to the
>> IETF repository.
>>
>> Name:           draft-dawkins-sdp-rtp-quic-questions
>> Revision:       01
>> Title:          SDP Offer/Answer for RTP using QUIC as Transport - Design
>> Questions
>> Document date:  2021-10-25
>> Group:          Individual Submission
>> Pages:          13
>> URL:
>> https://www.ietf.org/archive/id/draft-dawkins-sdp-rtp-quic-questions-01.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-dawkins-sdp-rtp-quic-questions/
>> Html:
>> https://www.ietf.org/archive/id/draft-dawkins-sdp-rtp-quic-questions-01.html
>> Htmlized:
>> https://datatracker.ietf.org/doc/html/draft-dawkins-sdp-rtp-quic-questions
>> Diff:
>> https://www.ietf.org/rfcdiff?url2=draft-dawkins-sdp-rtp-quic-questions-01
>>
>> Abstract:
>>    This document is a companion document to "SDP Offer/Answer for RTP
>>    using QUIC as Transport".  That document focuses on the description
>>    and registration of SDP "proto" attribute parameters with IANA, to
>>    allow applications that rely on SDP Offer/Answer to negotiate the
>>    QUIC protocol as an encapsulation for RTP.
>>
>>    In writing that document, it became obvious that decisions about an
>>    appropriate SDP description would depend on decisions about the way
>>    RTP would be encapsulated in QUIC, and different proposals for those
>>    encapsulations had made different assumptions.  Given that none of
>>    these proposals have been adopted by an IETF working group yet, it's
>>    not appropriate to try to base a general-purpose set of "QUIC/RTP"
>>    IANA registrations on any one of them, so this document includes the
>>    questions that have come up, and (as discussions progress) suggested
>>    answers for those questions.
>>
>>
>>
>>
>> The IETF Secretariat
>>
>>
>> --
>> Moq mailing list
>> Moq@ietf.org
>> https://www.ietf.org/mailman/listinfo/moq
>>
> --
> Moq mailing list
> Moq@ietf.org
> https://www.ietf.org/mailman/listinfo/moq
>