From nobody Tue Aug 29 14:34:39 2023 Return-Path: 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 60452C14CE5F for ; Tue, 29 Aug 2023 14:34:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.105 X-Spam-Level: X-Spam-Status: No, score=-7.105 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 55_uERSRyf4i for ; Tue, 29 Aug 2023 14:34:34 -0700 (PDT) Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 705D7C151062 for ; Tue, 29 Aug 2023 14:34:23 -0700 (PDT) Received: by mail-pj1-x1029.google.com with SMTP id 98e67ed59e1d1-26f38171174so3117230a91.3 for ; Tue, 29 Aug 2023 14:34:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693344862; x=1693949662; darn=ietf.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=HDmgM7b2gkU5dM90n7K/VCZ7LsyeLuWGJp3mMDHh3ro=; b=Jrwbe+H65dwvungmPxiZrOEFa1nSdzHeekT9TkGl9+iBMbu8zzRG/H9lr/67/GLvt8 l/WizB/APIv+ze4URoVWPmxoPlltblR0dR9/aXhfE7m89TbYksn5YulUyav6/yPo7uTt bLcExj42YP0I4AG8hxL6ohbANdfD7Tlu5jjnl+dKIg+fWoATRwbOi5DQHFnNgzBVeqiC mcoCiMPDUuTHpbgUiPPojW2s660NXx+0C3bYl+RDKk/5SmySoPhp0lUnluTb8rdacmXa dry1ZFvHRs2qs12owS7QU9uIBhB4YDvr+9G/qwcMxEcrn2gQi9PgnbmhdWestZdAbUwX RqPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693344862; x=1693949662; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=HDmgM7b2gkU5dM90n7K/VCZ7LsyeLuWGJp3mMDHh3ro=; b=PrA0itQq7x1lj0nxiD30UKou+Wkm2lQM8kAYhl2XYOvVA1uQohA8nNZfU7KMQ8yzEc jIjrFP8mpPRO1e68Vb2kgeYEF0RIHQ5ahMkXDAsWzrHQxnrknYkMMv1iFrELjZ6jiZ3C dEQ/oQsckLZ+cuuYf/m5cya74KulXBfZ/bGaOnxXuvnPoxUHzgYZgDoAC7qBomH4A6h2 +Fn5vdcDJp88hbnMm8zWp88CAsYziUS6+CEhiWiUa1kfZ7m8+e6rAN6kbBKtndHr1Ro7 reIOCJQJnv+dQPb9NtcYEBbgVLILz6qiRmXqrVo6F2mOH8MI4ON2LRWr1pwdjkZMzpD0 Wzzg== X-Gm-Message-State: AOJu0Yzq9ezbRekat4PPEMYKru3vUhMSyIf9Lf1RSU2rhskJUpA40eTS GJO1U5MKPSEfMeTMzYjIMTE35MdyAr0YoY0cHpFmMagk3KK6Og== X-Google-Smtp-Source: AGHT+IHoOIIFqj5TJPNQkRJgKBcMBKgBk/w1CStGf9omll0impN8o0oqnikPbSpR46Hn65X4lgSO/D3jypp+0wNtoaY= X-Received: by 2002:a17:90b:1953:b0:269:4886:b388 with SMTP id nk19-20020a17090b195300b002694886b388mr432833pjb.16.1693344862500; Tue, 29 Aug 2023 14:34:22 -0700 (PDT) MIME-Version: 1.0 From: Bernard Aboba Date: Tue, 29 Aug 2023 14:34:11 -0700 Message-ID: To: IETF AVTCore WG Cc: Philipp Hancke Content-Type: multipart/alternative; boundary="00000000000002fc5d060416936b" Archived-At: Subject: [AVTCORE] Missing RTP payload format media type registrations X-BeenThere: avt@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Audio/Video Transport Core Maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2023 21:34:38 -0000 --00000000000002fc5d060416936b Content-Type: text/plain; charset="UTF-8" A recent post to the W3C public-webrtc mailing list points out a potential issue with IANA RTP payload format media type registrations: https://lists.w3.org/Archives/Public/public-webrtc/2023Aug/0033.html Apparently, the AV1, VP8, HEVC and VVC codecs are not included in the IANA list of RTP payload media types: https://www.iana.org/assignments/rtp-parameters/rtp-parameters.xhtml#rtp-parameters-2 However, they are registered in the mime-types registry under video: https://www.iana.org/assignments/media-types/media-types.xhtml Is this something we need to correct? --00000000000002fc5d060416936b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
A recent post to the W3C public-webrtc mailing list points= out a potential issue with IANA RTP payload format media type registration= s:=C2=A0

Apparently, the AV1, VP8, HEVC an= d VVC codecs are not included in the IANA list of RTP payload media types:= =C2=A0