[AVTCORE] Mapping RTP onto QUIC
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 15 September 2020 15:42 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 5225D3A0A13 for <avt@ietfa.amsl.com>; Tue, 15 Sep 2020 08:42:15 -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 dtPGn1cAy6JX for <avt@ietfa.amsl.com>; Tue, 15 Sep 2020 08:42:13 -0700 (PDT)
Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (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 8A8353A0A01 for <avt@ietf.org>; Tue, 15 Sep 2020 08:42:13 -0700 (PDT)
Received: by mail-yb1-xb35.google.com with SMTP id 67so2978353ybt.6 for <avt@ietf.org>; Tue, 15 Sep 2020 08:42:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xSffPHBhMzgc9lUXbx16499gQiJeM4Ze93qfobDMYGg=; b=hs2NvUQosWsjxhlE3Q9H5tLf6ONVyY5I8FeOUFsWehA0mUZW+a9JHFBdDzpmaNEAdK cbdML4Vb4uUFVLAYiA1MxPJFv8O9cYMEyOFddsKCV2e38ScmpUm+cSTJb+P3G519ZCBx TIQiAHs8QMkyP95J8cMEM0LQ8pMlHYrXvHNgbaLx2UqEl3Yn7aDlqXX6Kq+SaArHNRio MpS2dsyYbVPB8z4NbS2uFKJqlXLVnBwJO4E+AzlR182QOeb/6LatWAC/RqmDfIZWfyp8 rs9tb/1zQIvAANN1EfvbR7SMlfL/1LQBGHnjvggRnhzg2KSvJs26MLWLnijZvOhoJDFm 2A1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xSffPHBhMzgc9lUXbx16499gQiJeM4Ze93qfobDMYGg=; b=RkMjpwyNRQHAdArGq/CsGbq5lgsXuors4ZjHNeJqTiKxKZT1/HGg6wnhUXck+GkSMm hgyBf1v8JwJA8+hPUH5BIaN/FOVEBc/A5TXYKbPMn2SANSixPUBiu5PSC51V8Y/8xkpP lUeAEa8jP30pjcRB6emHbSZP1C+wWVP7NegsNVtLi51eHQO6VJs6gZjJmCJzlEvwCnX4 F4TMZIlwGCZicxJlgh4TLUALfWiRdXqhVixdHPrNArOcwT/everW6BnA4iTzS2WDZkDG 85eifWPSFHbH0uiuqlDoaN7NxnoN+AbvGQ9Q0fuAYKZBAO10v4LlVYjNXOceOaQti6kd Za2A==
X-Gm-Message-State: AOAM533DKvj2D3KpINMLUv4ThJR91A507+r6B/bjEfI8siPdTNvQU2cE QEJv9I8NKo0c/DsoTNw1PN7dxFUn9BDROaeiHx0GLFfWjs4=
X-Google-Smtp-Source: ABdhPJwU7pok6VAFNFPdYbpu9UtmUaH08qVApZ7lbj7vh3z9rY7A/FeiakhP8S+n3p6JXle1iF3YXNFk/ccn4SCsdEg=
X-Received: by 2002:a25:ea0c:: with SMTP id p12mr11010365ybd.245.1600184532535; Tue, 15 Sep 2020 08:42:12 -0700 (PDT)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 15 Sep 2020 10:41:46 -0500
Message-ID: <CAKKJt-dC9ndv6d=vgGUZ2WLFc__joNjGRWAq98mKLXdr=7oeLg@mail.gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a30e1805af5bfe01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/HNV6uQQHCwUV1b3we-23OGqcO68>
Subject: [AVTCORE] Mapping RTP onto QUIC
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: Tue, 15 Sep 2020 15:42:15 -0000
Dear AVTCORE,
As part of the set of ideas included in the IETF 107 RIPT BOF [1] there was
a proposal [2] to use HTTP/3 for media {"when it is available, falling back
to media byways when it is not").
As best I can decode from the discussion during the RIPT BOF [3], and
subsequent non-chartering, the RIPT BOF participants didn't support moving
forward, but we didn't really converge in those discussions on whether we
should be looking at HTTP/3 for media, or a more conservative mapping of
RTP directly onto QUIC transport.
I know there have been proposals for an RTP mapping onto QUIC (most notably
[4]). Are some people in AVTCORE interested in pursuing that
alternative, now that QUICv1 is banging around in WGLC?
Best,
Spencer, sending this e-mail to AVTCORE at the suggestion of the ART and
TSV ADs
[1} https://datatracker.ietf.org/group/ript/meetings/
[2]
https://tools.ietf.org/html/draft-rosenbergjennings-dispatch-ript-00#section-8.8
[3] https://www.ietf.org/proceedings/107/minutes/minutes-107-ript-00
[4] https://tools.ietf.org/html/draft-rtpfolks-quic-rtp-over-quic-01
- [AVTCORE] Mapping RTP onto QUIC Spencer Dawkins at IETF
- Re: [AVTCORE] Mapping RTP onto QUIC Bernard Aboba
- Re: [AVTCORE] Mapping RTP onto QUIC Spencer Dawkins at IETF
- Re: [AVTCORE] Mapping RTP onto QUIC Bernard Aboba