IETF Logo Mail Archive

Re: [MMUSIC] New Version Notification for draft-dawkins-avtcore-sdp-rtp-quic-00.txt

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Thu, 03 February 2022 15:33 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A573E3A095F; Thu, 3 Feb 2022 07:33:21 -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, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBuuuIY1Pfyr; Thu, 3 Feb 2022 07:33:16 -0800 (PST)
Received: from mail-ua1-x92a.google.com (mail-ua1-x92a.google.com [IPv6:2607:f8b0:4864:20::92a]) (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 4C76A3A0BF6; Thu, 3 Feb 2022 07:32:34 -0800 (PST)
Received: by mail-ua1-x92a.google.com with SMTP id w21so5812785uan.7; Thu, 03 Feb 2022 07:32:34 -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=kmbdaxxBhw/L99l5rPxF4RK9/KUrCF7zbEoWRqAAGWM=; b=dqeWIPUiRjSxB2fLsz80fPVt6PkRw/YMvsrs8n4lhg1ud4YnFeqxb5hMi8dJ7raGCj 8y8gY5yM81ymciSmtX8hV4ukW5y4goauR12IlYQDi1nOm71nQtLwYKgOpgGHSrIJfg+D KhI9k4LGMznuth0bDpIGrtQd62eCZ7yOKgv4Xi9T98wCb7AYCOelY4SbdzayjdnA6JRU ZtNAxs1TItSDGQieMu+p9fU+CrK2Pbo3ZKh51EYQQCl/ERtOKUQ7oxbcBx8tH92tCVjb l3v40ZRZxay8QEjdiOs1mUrpCUL1tg/lhCU/LhrUwbV8JaZIkUIhMwlrPhDVQaOU+F+w c6Vw==
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=kmbdaxxBhw/L99l5rPxF4RK9/KUrCF7zbEoWRqAAGWM=; b=Oy7b3ApQb2VVkQDEszyWTXufSOFACqyhq+vFmSnD7ds36YaBJDDslFwIyRqyAzu5fV QQFfPe1EiUVJJXmaVvzUqfSyW0+qha+VH2sEikZuL5PpB2HZYrPGyOv3ZnnKgT0Ok44C sok6kXP1aNjequTCpkr26gktrbDPCry4KTY56IxvvRacwMxMTeCrJkh1maneXjrZw6nN kPOEum9S9xzj6Thwxe3dRo8bo++4k6RvL0smN/PWirL2O5lMnVM7MOyC9DuuEYgWbb2y og7VCqBjak3yl5ThK2nqXchjQQjgFfmJ25M5lI4gGhMGeAdIxPa0jybYPt8BO7CxaDaq qy7w==
X-Gm-Message-State: AOAM530WSEzoY8fmllPmRcKXTap4G+CEuvONNDyRx+5toqbi6gILiijn Ld60/ks60yamHaFs7SSLhinwnfZi5p8UrRGaOOK/F6sbCkA=
X-Google-Smtp-Source: ABdhPJy6klQTO9Sr3WjRj4T9Zhr+nsGH/tX3EJAuNmpOIyPyhtulQp8XLFhdNgR/nIwf87A/m0NzqZGxsj0wFXTJQZs=
X-Received: by 2002:a9f:24c6:: with SMTP id 64mr13452675uar.59.1643902352278; Thu, 03 Feb 2022 07:32:32 -0800 (PST)
MIME-Version: 1.0
References: <164338880152.21421.4609222617315309024@ietfa.amsl.com> <CAKKJt-cLPJRkkWruAbD8UkhtAeRptbqUVCdi8sFUu9pC_Zx_sQ@mail.gmail.com> <CAOLzse1c9vz644dFX-hED3Sgb3FDbaq4qo6vd2ZmB_CuLLfPfA@mail.gmail.com>
In-Reply-To: <CAOLzse1c9vz644dFX-hED3Sgb3FDbaq4qo6vd2ZmB_CuLLfPfA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 03 Feb 2022 09:32:06 -0600
Message-ID: <CAKKJt-cm3cdzpfe_4yXw4Vs9Naj2BJBZX5XAFuAKec16RoW7=g@mail.gmail.com>
To: Justin Uberti <juberti@alphaexplorationco.com>
Cc: IETF AVTCore WG <avt@ietf.org>, MOQ Mailing List <moq@ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c0ca5e05d71ed740"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P87ODRoxfW_jSDgN13rI1hOU93I>
Subject: Re: [MMUSIC] New Version Notification for draft-dawkins-avtcore-sdp-rtp-quic-00.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Feb 2022 15:33:22 -0000

Hi, Justin,

On Wed, Feb 2, 2022 at 5:48 PM Justin Uberti <juberti@alphaexplorationco.com>
wrote:

> Spencer, thanks for writing this up. Having some signaling written down
> lets us understand some of the next-level questions here.
>

Thanks for the quick feedback! I'll create issues for each of these in
https://github.com/SpencerDawkins/sdp-rtp-quic.

And then start working on PRs, of course ... 😉

Best,

Spencer


> RTP Profile
> =========
> I think the security aspects discussed in Section 1.5 are a good example
> of this. At first glance, QUIC/RTP/SAVPF feels a lot like the
> UDP/TLS/RTP/SAVPF defined in https://www.rfc-editor.org/rfc/rfc5764.html,
> but the semantics are much different, namely:
> 1) The SRTP encryption process is not used, and instead QUIC's encryption
> and encapsulation process is used.
> 2) The SAVPF profile is meant to be a hint to downstream consumers, per
> Section 1.5, rather than a difference in the wire format.
>
> I think it would be good to align with the precedent set in
> https://www.rfc-editor.org/rfc/rfc7850.html, which indicates that the
> right profile in all cases would be QUIC/RTP/AVPF. Any behaviors required
> of the middlebox seem like they should be indicated by some other explicit
> attribute given the ambiguity associated with overloading the profile.
>
> tls-id
> ====
> It would probably be a good idea for the SDP to include a=tls-id, defined
> in https://datatracker.ietf.org/doc/html/rfc8842, to ensure endpoints can
> tell when the security handshake is being restarted, as discussed in the
> cited RFC. This would probably obivate the need for a=connection:new as
> well (which is not typically used in DTLS-SRTP).
>
> c2s vs p2p
> ========
> For c2s use, the SDP you have outlined should work well. For p2p usage, we
> should include the a=fingerprint mechanism used in
> https://datatracker.ietf.org/doc/html/rfc5763 to allow validation of
> self-signed peer certs.
>
>
>

v2.23.0 | Report a Bug | By Email