IETF Logo Mail Archive

Re: [rtcweb] JSEPbis: Questions about send-only/recv-only codecs and Section 4.2.6

"Murray S. Kucherawy" <superuser@gmail.com> Mon, 18 March 2024 23:54 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B880C14F71B for <rtcweb@ietfa.amsl.com>; Mon, 18 Mar 2024 16:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 6k99mfFGvliI for <rtcweb@ietfa.amsl.com>; Mon, 18 Mar 2024 16:54:48 -0700 (PDT)
Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (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 3797DC14F69A for <rtcweb@ietf.org>; Mon, 18 Mar 2024 16:54:48 -0700 (PDT)
Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-a467bd57898so137466066b.1 for <rtcweb@ietf.org>; Mon, 18 Mar 2024 16:54:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710806085; x=1711410885; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=e80Wn9VmOKRzkMNxX/SR02uhRwkDu+8QRzk3yEFMJJw=; b=L0EDIWYSWSQNgCCkT29hPIo0je3aNNLQ7p5i7OpHJj7723oP/G/nvbrvLMS4D7ovMV exOl2bpexGHh7qYNttjtZaWqB9OETkAc3HUNE7l2Nz4aWmDSAlTHK3llfrXGTLKZmAHi HkhC1iQ3EzNtt74R61Wm1ujArjfinIPfNHx+9zvo9aGQyVtIVDJy7cUGgV/+0KjvKnhR njzYJAvzMpFGoqZVQM9/RF+yE0wMNxxpd4KN4aiQ7INAwe3VrCONyHkbUqMD1D08Eek6 soomT8NGwNjD0mzD5jd4vsb2CJWVoMkhTa63N23kgEYWCEHCN+YK/JeBSKIhevupQK4l tV2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710806085; x=1711410885; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=e80Wn9VmOKRzkMNxX/SR02uhRwkDu+8QRzk3yEFMJJw=; b=P8yki7Yuc9H53djP+0INkD7fY329HhARplZSXIxzsY3VytOOL/8gpMlpVoMM3/Euf2 +ROMbwmg7RTkpS5GF3mTplqO4MhismOSeXVJIji8Y+xksuUSXPmWR4etiNO7jDPwnnyx vtoeCfVvxaatH3JiZaV5ggHJQgs89+J75JZlYE06cH5otM7y9kZtgiY0S1PzyE1A6/Tu vtr6oaXX4CYvaWIQBXKAEo7l/0TpbrNYjgt3w6ELMtAj6sYgBVDmlnOERk5qVdzC8JMs bN/ExVvzZQ4XP+jcWKyknMl8Q5WTc5TLtih/u4VzgS9lyyN0YtcLkHQmvpcwsPfJE4E6 QwGQ==
X-Forwarded-Encrypted: i=1; AJvYcCUuIPxZae7OZsTyweSpqWHVoxAGZ8a6IoPgmtyf3RmAx78aYK9FjlGvmqJSzQf2HyS7DIuKHBDT7YsXhCiVmjM=
X-Gm-Message-State: AOJu0YxO5XmEtaH1aae5c62XpVrJY3D2B7SwoEsCSo+JjAHebru+Ygvt 9YQqt9Vp/8hUL7DzV9H0SWMrIyDuAx4wBcaBvZ+V+8gJZCh7YYkfrounHcLeDRdc7V86eUjUo0Z VrlIUfIiR2GsETfE8A1BJDgesYps=
X-Google-Smtp-Source: AGHT+IHBIj4edOA5ybwpGqIQay6RK5kI65qnq90tGNu/RrPiWPUZdAxTWxwr/eMEy58pfokwC9zpKoIWcEDeVpa7sls=
X-Received: by 2002:a17:907:86a8:b0:a46:b2e4:909f with SMTP id qa40-20020a17090786a800b00a46b2e4909fmr4299168ejc.1.1710806085115; Mon, 18 Mar 2024 16:54:45 -0700 (PDT)
MIME-Version: 1.0
References: <CAOW+2dud=K0TuQ5s-MKgmnuvxR-DebFFhquigUbsiKQB3RjdNw@mail.gmail.com> <CAOqqYVGhwsxxj1AnUU+Qk5A9DcqnaGCc5YGo9ntd-CvrY0v6Nw@mail.gmail.com> <CAOW+2duhtXRx6_kDgS6CvwnwgwGK8JH+QkODNEpa1=0r=TQDeA@mail.gmail.com> <CADxkKi+F-Zu6HQFTtAxUE_UsSiVpV5J_zpNYxK1b44Qg_5i0HA@mail.gmail.com> <CAPn_nMOMPDRCkDxk3qRqhz6xw79NTq8gqJdTMtsehwNtY2U8vQ@mail.gmail.com>
In-Reply-To: <CAPn_nMOMPDRCkDxk3qRqhz6xw79NTq8gqJdTMtsehwNtY2U8vQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 19 Mar 2024 09:54:32 +1000
Message-ID: <CAL0qLwa02W3DmhTabLh2avpxFKpSqXqcozCedbcSUiNbghrmOA@mail.gmail.com>
To: Justin Uberti <justin=40fixie.ai@dmarc.ietf.org>
Cc: Philipp Hancke <philipp.hancke=40googlemail.com@dmarc.ietf.org>, Harald Alvestrand <hta@google.com>, Henrik Boström <hbos@google.com>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fba6f30613f8144b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Xe7sdLduWk1rOG-Bvco2oKM-KeI>
Subject: Re: [rtcweb] JSEPbis: Questions about send-only/recv-only codecs and Section 4.2.6
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2024 23:54:50 -0000

On Mon, Mar 4, 2024 at 3:57 PM Justin Uberti <justin=
40fixie.ai@dmarc.ietf.org> wrote:

> The idea behind the text in red is an explicit callout to the fact that
> the implementation may decide to use other mechanisms (e.g.,
> RtcRtpSender.setParameters, CPU or bandwidth limitations, etc) to decide
> exactly what should be sent over the wire.
>
> Also, this API is intended to directly influence signaling, i.e., the set
> of codecs that are offered. It is not intended to directly control
> RtpSender settings.
>
> I agree with the point that the operation here may seem a bit weird for a
> sendonly m= line. That said, I think it is entirely consistent with RFC
> 3264 S 5.1, where a) what is offered is primarily intended as a guide for
> what the answerer will actually send and b) the answerer may choose to send
> whatever it wants as long as it uses a format from the offer.
>
> I think keeping sCP focused on what goes into the actual offer will make
> it easier to reason about this API.
>

Are there any required changes to RFC8829bis, which is in AUTH48?

-MSK

v2.23.0 | Report a Bug | By Email