[rtcweb] HEVC-WebRTC, Issue 22: Issues with Receive-only codecs
Bernard Aboba <bernard.aboba@gmail.com> Mon, 12 February 2024 06:14 UTC
Return-Path: <bernard.aboba@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 2B73FC14F5E4; Sun, 11 Feb 2024 22:14:41 -0800 (PST)
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 YmPyQQMYEpSB; Sun, 11 Feb 2024 22:14:40 -0800 (PST)
Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 80F8EC14F5E0; Sun, 11 Feb 2024 22:14:40 -0800 (PST)
Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-5cdbc4334edso1670043a12.3; Sun, 11 Feb 2024 22:14:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1707718479; x=1708323279; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=QWLbAd5laLdBbrScHRfjXZF0kh/R3UFvB+Oyoz3Ez4U=; b=GdnEZGcqUc4fXSj06V1el3r2ZABaBA+YY0q/8BQp7wzEoK8IKok9w0ZkgGLaPuPywn wCKlojspIss+RCSGRjt9wMmUmokCYwL3XWyv/Gjdjnl0cZ0rwsNAHJaTlGLeMzp6AqgE uSZHZHR6ePzyXzOOfAefB4JXc4rrs70pDmJ3+SueYtafj45qIs23bWQwx7n9O2U4MWgQ tYp+QQ9iASKRiTecVsU6gf3j4fIecrj/T3iFgIEqLDNBfobYGG9YO16+Svnq/bA8jFQ7 Yddn2Mc4uXRPJyydXhIR7AZOjHeMcmZ3KDDT+jl+JzV3B/+HOrFIpytyFRfavTku5Llr 7XLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707718479; x=1708323279; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=QWLbAd5laLdBbrScHRfjXZF0kh/R3UFvB+Oyoz3Ez4U=; b=aUtX1iMUp+iQ/pGZenDyx0Xo4cY4L6rd57Tt/fUK0HhcC8fnSw5v915elTXgQ5B94+ WKlPyv5orpKj0+xwiB/ESZRpaKt8Jy9GPv9i74Xo7jUzjsiAunaID3tr8F9tS5Z4VDvm pp1dK+juoiEy6vCfwdfv2hW9pYy5xv85Obm6WwEYf+I2slGXzLhanFObNCgNVCNWp/UD w0xdWfjZMAUxSZoud8TRe6OKsi/VUNZ2OfupUKcP2JjxzChdgZg56ZS+0Xy1U4xHK/jq Aqc/fVzva3dnbIp1IbVKeFOQbPbur1fSxout02cgsS5I3vx5exBxlqUMvEt7vLXQOjJV tm1A==
X-Forwarded-Encrypted: i=1; AJvYcCWnhbPme8TdP9XmyrCh2ITn4047rNNGUtm6SVY+2WDw5mJZdCWwMBLYZHaXjghqJ+HRZ9qvvc7T3mTC9n5sWCo=
X-Gm-Message-State: AOJu0YyvWMnK8dYEi9RxdhOrztVp4WfDC/no88mjd7OwqcR1h9uwokZf 0YcNitGyv3t2IxU6Vuz8BSB7CejBau5OIvTmusO2WxGtceoLx/+AjofdBOlq0go58flMzwLpiiH esnEk1KTek7l+Nb5eomv8OVkF5C6tmoYAjwmTag==
X-Google-Smtp-Source: AGHT+IG5OPuv2tlch/lhtL/Wza0b7gM8sj6FL8Xi3hQxwWNDRZFaI3NWramRda3Vj9yUGO1YLcf0cYaeb05tGfv383U=
X-Received: by 2002:a05:6a20:e68e:b0:19c:b1f0:9848 with SMTP id mz14-20020a056a20e68e00b0019cb1f09848mr5706501pzb.7.1707718479277; Sun, 11 Feb 2024 22:14:39 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Sun, 11 Feb 2024 22:14:28 -0800
Message-ID: <CAOW+2duMXWAUmPJ9dLYYhE07SO0d_NgRzW5UX4TJYp1Ajwgzyg@mail.gmail.com>
To: IETF AVTCore WG <avt@ietf.org>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000557db6061129319f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/NR-OFcIsteq54UkUeKVX0-XnW84>
Subject: [rtcweb] HEVC-WebRTC, Issue 22: Issues with Receive-only codecs
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, 12 Feb 2024 06:14:41 -0000
Link: https://github.com/aboba/hevc-webrtc/issues/22 Problems have been found in the W3C WebRTC-PC specification as well as the implementation of the WebRTC API (setCodecPreferences) when receive-only codecs are present. This problem surfaced originally in H.264, but is also affecting H.265. The concern is whether an implementation that only supports receiving H.265 (e.g. Chrome) can successfully negotiate HEVC reception with an implementation that can both send and receive (e.g. Safari Tech Preview). References w3c/webrtc-pc#2936 w3c/webrtc-pc#2933 w3c/webrtc-pc#2935 w3c/webrtc-pc#2888
- [rtcweb] HEVC-WebRTC, Issue 22: Issues with Recei… Bernard Aboba