IETF Logo Mail Archive

Re: [Cellar] ATRAC1 codec ID for Matroska

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 07 October 2022 09:07 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FFDC1522B6 for <cellar@ietfa.amsl.com>; Fri, 7 Oct 2022 02:07:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 xNU7WOzypl0Y for <cellar@ietfa.amsl.com>; Fri, 7 Oct 2022 02:07:07 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 02DA5C14CE31 for <cellar@ietf.org>; Fri, 7 Oct 2022 02:07:06 -0700 (PDT)
Received: from dooku.sandelman.ca (ip-185-104-137-32.ptr.icomera.net [185.104.137.32]) by relay.sandelman.ca (Postfix) with ESMTPS id A2BDE1F4B5; Fri, 7 Oct 2022 09:07:00 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 536C01A073E; Fri, 7 Oct 2022 10:17:40 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: cellar@ietf.org, sir68k@gmail.com
In-reply-to: <CAO7v-1ReSnABbhCJw2wvx0N6D7TKi0=uojWujO3POYrNkoDUjg@mail.gmail.com>
References: <CAO1ejfRd+1BrJ+w6PMEor3b_8Q6593Mujna1a81AG0CarrGA=w@mail.gmail.com> <CAO7v-1ReSnABbhCJw2wvx0N6D7TKi0=uojWujO3POYrNkoDUjg@mail.gmail.com>
Comments: In-reply-to Kieran O Leary <kieran.o.leary@gmail.com> message dated "Tue, 04 Oct 2022 07:32:30 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7.1; GNU Emacs 27.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 07 Oct 2022 10:17:40 +0200
Message-ID: <213944.1665130660@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/7ZWyGjmEMEfZ6KrGh0Q4Iq9aOZo>
Subject: Re: [Cellar] ATRAC1 codec ID for Matroska
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2022 09:07:08 -0000

On Mon 3 Oct 2022 at 18:55, Sir68k <sir68k@gmail.com> wrote:
> As RAW ATRAC1 isn't common but may become (slightly) more common due to
> the ripping software that we have been creating, we would like to start
> using a decent container format. Matroska already has support for ATRAC3 as
> a format (A_REAL/ATRC), and as such, we would like to request a new codec
> ID for ATRAC1 as well.

As I understand it, you want a new entry in:
https://www.ietf.org/archive/id/draft-ietf-cellar-codec-09.html#name-audio-codec-mappings

or:
https://www.ietf.org/archive/id/draft-ietf-cellar-matroska-14.html#name-chapter-codec-ids-registry

In reviewing this, I'm actually a bit lost, as I thought that the IANA
considerations on Matroska was complete, but now it looks rather incomplete.

At this point, the document is not published, so the IANA process to allocate
you an ID is not live.  But, as a WG, we can add your request to the
document.

I don't see ATRAC3 in the document, but maybe I'm looking in the wrong place.

Please, could the WG clarify where the right registry would be?


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email