IETF Logo Mail Archive

Re: [AVTCORE] QUIC RTP Tunnelling

Bernard Aboba <bernard.aboba@gmail.com> Mon, 02 November 2020 15:54 UTC

Return-Path: <bernard.aboba@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 071313A0CB9 for <avt@ietfa.amsl.com>; Mon, 2 Nov 2020 07:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, MIME_QP_LONG_LINE=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 LcC8WauwXa6Q for <avt@ietfa.amsl.com>; Mon, 2 Nov 2020 07:54:00 -0800 (PST)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 D74043A0B93 for <avt@ietf.org>; Mon, 2 Nov 2020 07:54:00 -0800 (PST)
Received: by mail-pf1-x42d.google.com with SMTP id o129so11470135pfb.1 for <avt@ietf.org>; Mon, 02 Nov 2020 07:54:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=CiK48AXzjSYpeJOKZJeBV7GXt4d2mE07NQ/+fL/g/DE=; b=AIFuX6VaBUBIrwIrcrcLWwD9PcBryUT6WxFyoY88Rehi7Sz/pWLbiWz0qcu6jsRpD4 KGXKNwhA0l/QgxBHD55NMJ/As0GaInHET8Mvx3gCWQjAGJ3bWcJaP4KEhDEQMfwfUXE+ jGOTdSjYeH/lD8GY5eTKI5rtcSgbky6Lo7cD2poQ06Ey9l13gtlzNm0FQ3MzvAJiF0Rj TygCcSb4NumH77DtNKEA0mz9juCi47uR0HYVRzoQ08NZOCIGXXSAin8UA6D0qafKPf+j kumSyWHTbl7oI0w1GGrKW3u+a0BsmG0nvgpl7Vw4e91x4ool9T3sMnMaAwBgtLwIhcHL 9vVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=CiK48AXzjSYpeJOKZJeBV7GXt4d2mE07NQ/+fL/g/DE=; b=elQov5RijXWRfaCDe+8NCi0nqUfsxt8grogY5YM7fzlpxdefo/i4EvG/WEZ4grGE9Q /Evtd1xNDqJm8Lm5yDyIB2oLxkRTXwgJ5YLWZ1mWlQyhB197XtK3ApqMJpHx4inCs6+k SeKf6+0BD3c/qW0XtpO6FR3I8hyh7sNoRH8S6JmC3Coje2wn0uPlI+4Xn4Zg0n33VKtO NguVKXu48AHzSsz2zhOjTTOfiLf6Uy4ljFJmksvSah5oL7pBXPTOrwgpxj8OVlaI5UNc 6xs1Z/I5yq+8Rcy5KCQm5gVCP0JnGNAMVgHP9hDLp8xdLuwA3EkG2V+XZTu8EZpjG0t7 7A9w==
X-Gm-Message-State: AOAM5309e1g7+pEVYpYSzUb1JrJ2PmYs1E/V3zGa4O0r58tjGkHBHjCR p5G8N9CNklP8abMq71GriDBqHe1j7Pmflg==
X-Google-Smtp-Source: ABdhPJyfQREgsmwl23W0fdRl/FUcVzpO8hRvP79spgOGUX335BV5TLgBo+C2SD/qxvFgSDvUSou62g==
X-Received: by 2002:a17:90b:4a07:: with SMTP id kk7mr18409851pjb.92.1604332439899; Mon, 02 Nov 2020 07:53:59 -0800 (PST)
Received: from [192.168.1.134] (c-71-227-236-207.hsd1.wa.comcast.net. [71.227.236.207]) by smtp.gmail.com with ESMTPSA id y10sm291055pjr.2.2020.11.02.07.53.58 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Nov 2020 07:53:59 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Google-Original-From: Bernard Aboba <Bernard.Aboba@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-ADB3AAE2-09B8-4E9D-8D6D-14059DAA9BE4"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Mon, 02 Nov 2020 07:29:07 -0800
Message-Id: <91C47627-9EA3-4C01-9ADD-E7AAE103AD2B@gmail.com>
References: <8dd07103-16a0-ca03-625b-e6c2b4c18008@rd.bbc.co.uk>
Cc: avt@ietf.org
In-Reply-To: <8dd07103-16a0-ca03-625b-e6c2b4c18008@rd.bbc.co.uk>
To: Samuel Hurst <samuelh@rd.bbc.co.uk>
X-Mailer: iPad Mail (18A8395)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/7ZWEx5uiQQJ1aeOO9uFirPY7INg>
Subject: Re: [AVTCORE] QUIC RTP Tunnelling
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, 02 Nov 2020 15:54:03 -0000

A comment on the allocation of QUIC datagram flow identifiers. In pooled transports such as HTTP/3 over QUIC, the datagram flow identifier is used to route datagrams to a particular application, and an additional identifier is provided by the application to identify a particular flow. Therefore in a pooled transport the application will not have the ability to allocate its own application flow identifiers.

https://tools.ietf.org/html/draft-schinazi-quic-h3-datagram-05 Section 3 says:

Even flow identifiers are client-initiated, while odd flow
   identifiers are server-initiated.  This means that an HTTP/3 client
   implementation of the flow identifier allocation service MUST only
   provide even identifiers, while a server implementation MUST only
   provide odd identifiers.  Note that, once allocated, any flow
   identifier can be used by both client and server - only allocation
   carries separate namespaces to avoid requiring synchronization.



> On Nov 2, 2020, at 07:05, Samuel Hurst <samuelh@rd.bbc.co.uk> wrote:
> 
> Hello,
> 
> Apologies if this is not the correct forum for publicising this, but I
> saw from the mailing list archive that there has been previous
> discussion about mapping RTP over QUIC on this list.
> 
> I recently published an I-D that discusses multiplexing RTP sessions
> over a single QUIC Transport connection, a technique I'm calling QUIC
> RTP Tunnelling or "QRT". This uses QUIC DATAGRAM frames to carry RTP and
> RTCP packets, with a custom flow identifier for multiplexing.
> 
> The primary motivation behind the draft is to support live video
> contribution for media productions, but I see that it could have much
> wider-reaching applicability than that. I invite any review comments on
> the draft.
> 
> https://tools.ietf.org/html/draft-hurst-quic-rtp-tunnelling-00
> 
> Best Regards,
> Sam
> 
> -- 
> (he/him)
> Project R&D Engineer
> BCS Internet Distribution
> BBC Research and Development
> 5th Floor Dock House, MediaCityUK
> 
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt

v2.23.0 | Report a Bug | By Email