IETF Logo Mail Archive

Re: [AVTCORE] Registering AVP Profiles for RTP over QUIC

Bernard Aboba <bernard.aboba@gmail.com> Thu, 12 May 2022 01:31 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 DBE3EC15E6EF for <avt@ietfa.amsl.com>; Wed, 11 May 2022 18:31:07 -0700 (PDT)
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, RCVD_IN_DNSWL_BLOCKED=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EMVtL1x1uJR4 for <avt@ietfa.amsl.com>; Wed, 11 May 2022 18:31:04 -0700 (PDT)
Received: from mail-vs1-xe2b.google.com (mail-vs1-xe2b.google.com [IPv6:2607:f8b0:4864:20::e2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29B6CC15E6E7 for <avt@ietf.org>; Wed, 11 May 2022 18:31:04 -0700 (PDT)
Received: by mail-vs1-xe2b.google.com with SMTP id z144so3693188vsz.13 for <avt@ietf.org>; Wed, 11 May 2022 18:31:04 -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=NLTRAW9rJ5WyNTiRa1djeu46zAHpMj/UfV25hWesvmM=; b=HkO+qGLJ0wzNNvHgrPOHEYSxcWwQLX/1+4ZVuT7SkOeIDQavVA48wcSVlOWco24isr zaYSbDvu9Ivbr3ORMQCB4c/iev79UP6A1dAsKXFrxHXG45umTppYR8U/f6rv8MV2mqmL RC3sXd59Fmdmwt7p4ZLm+at4OS+FQ+UYwSxlanukxjAYtSp0d5z0qKz3Sa3QMskRBeUA 1GdjnDeEGHyVtpRv6dqpzdt8pYc1rrSHfvEuCnobKWHVGGawpcU1df5wp/1+xrv4rUHq R+PvOpFg2TE2RDKxKKis+UKefgXsZfhRZIzLWVy+kLUwUnMbgwwkAk28v+6ZtBEw5SS5 gAMw==
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=NLTRAW9rJ5WyNTiRa1djeu46zAHpMj/UfV25hWesvmM=; b=NP3suCKbzDAE0zDlgqySowujtRT8V6FS0uOQBO+H6kLEld4kRkTi1wRo7nGUMiPVvu MAqFaBdxI6cZlgFCEUdmteVoi52dJVO4b91iEDvLcDURPCSheA3Y8F5jRLujIDkKbzVu rOVV8crihjn7B4/bAJgK49y44JPylcFpoqitwWoW1xjAm+Ny++j+hdFmHwowvTeqvTmj ibdmTPs1YcSVtP1wLNqU/JWBxy5ji+iIjT7hKf+Ov67R9XVMGvOUH6TP/dvN4i22eIop nssIuzfZuTnTRebm+Xnmbz9NarXuzZHVKfPl2Y3tlReD5MMODGKalLPa88LPoYX3NWpH rDzg==
X-Gm-Message-State: AOAM531/RByPVmmQKunAkiNFg/FZyEo5WH+yLgJTzjgsLSNZNmBVhIYG DQXqzDxOHMjcE0feR8lHWm1gzJ6NeTNZhsXHuXA=
X-Google-Smtp-Source: ABdhPJywtflJJrWLOZ64IdQojytf2jqSqpIPbXF2vzpmcD5KfkKTRKYEapHtINM1tlyDXx1NFOxYhj25iADaSia60WA=
X-Received: by 2002:a05:6102:b13:b0:32d:38bf:1095 with SMTP id b19-20020a0561020b1300b0032d38bf1095mr15244719vst.24.1652319062443; Wed, 11 May 2022 18:31:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-dvotzuaK66T8WQd7YgNLNr_6vqa4W8-z=5FvujpGWA=A@mail.gmail.com> <CAD5OKxvuQ+ng4YUbKE2Do5aB3pOpTs24Y59G1-2QAwSSX6HYkw@mail.gmail.com> <CAKKJt-cXMa8bW7HhwrkzX2-O=kYK2GRNwtB+cHRB-zWn+f0f+g@mail.gmail.com> <CAD5OKxsPd8w=geXBjJwFSSNUhFQ3sc-MMvte3EG6w24=tMvVPQ@mail.gmail.com> <8d20301c-f227-4c0b-aaec-4f1ddf22f782@beta.fastmail.com>
In-Reply-To: <8d20301c-f227-4c0b-aaec-4f1ddf22f782@beta.fastmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 11 May 2022 18:30:51 -0700
Message-ID: <CAOW+2ds4cp6Wgu88+riK5YVa8ywLKTe4jKSwKtV6q_aRTRaAbQ@mail.gmail.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: avt@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c5d1f905dec68248"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/QQtSiMTbXTu_Y2wMTVI5ifw5b58>
Subject: Re: [AVTCORE] Registering AVP Profiles for RTP over QUIC
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 12 May 2022 01:31:07 -0000

On Wed, May 11, 2022 at 18:19 Martin Thomson <mt@lowentropy.net> wrote:

> Hi Roman,
>
> I've always considered QUIC-SRTP to be a viable alternative to DTLS-SRTP.
> The challenge there is that it is not specified as possible.
>
> I think that people here are looking to pick up more of the advantages of
> QUIC though.  That is, even if that means losing some of the advantages of
> existing stuff as SCTP <-> QUIC is not a seamless transition and SRTP/QUIC
> has some interesting properties.
>

[BA] On a spectrum of “add QUIC to an existing RTP/RTCP stack” (so as to be
able to use P2P QUIC immediately without CC modifications) and “use QUIC
for both media and data” (so as to simplify the stack), a QUIC-SRTP use
cases falls somewhere in the middle, potentially lacking in both expediency
and long-term simplicity.




> _________________
> > Audio/Video Transport Core Maintenance
> > avt@ietf.org
> > https://www.ietf.org/mailman/listinfo/avt
>

v2.23.0 | Report a Bug | By Email