Re: [Cellar] Conversation about a NON-IANA request in Matroska

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 19 August 2021 15:22 UTC

Return-Path: <mcr+ietf@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 B5A523A1FA2 for <cellar@ietfa.amsl.com>; Thu, 19 Aug 2021 08:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cB70EDDCuhzv for <cellar@ietfa.amsl.com>; Thu, 19 Aug 2021 08:21:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C6F63A1FA3 for <cellar@ietf.org>; Thu, 19 Aug 2021 08:21:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6276F389B0; Thu, 19 Aug 2021 11:27:02 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id XCufRciQP5C7; Thu, 19 Aug 2021 11:26:57 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6126B389AF; Thu, 19 Aug 2021 11:26:57 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9515A64; Thu, 19 Aug 2021 11:21:46 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Murray S. Kucherawy" <superuser@gmail.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>, Francesca Palombini <francesca.palombini@ericsson.com>
In-Reply-To: <CAL0qLwY6V8eVG56ckhy3GFDwW61-6OD9_h=X-vDWFySM0e3B9A@mail.gmail.com>
References: <CAKKJt-ceukRCPUK=DTvDxDBPw-ddROX-snfZQ-BatSkgVZ0-qw@mail.gmail.com> <CAL0qLwY6V8eVG56ckhy3GFDwW61-6OD9_h=X-vDWFySM0e3B9A@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 19 Aug 2021 11:21:46 -0400
Message-ID: <4945.1629386506@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/WbP-cABRjddbcVbh0nA5sf04nAI>
Subject: Re: [Cellar] Conversation about a NON-IANA request in Matroska
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 19 Aug 2021 15:22:01 -0000

Murray S. Kucherawy <superuser@gmail.com> wrote:
    > So as your AD, I'd be prepared to argue in favor of registering the
    > x-dash name, and including a sentence or two about why we're making an
    > exception with respect to BCP 178 this time.  Of course, we can confirm
    > with the actual media type reviewers that I'm not crazy here.

Could we register "dash" and "x-dash"?


Could we write something like:

Implementations MUST accept both in perpetuity.
(that's easy to implement, and it's an archive format, so disk files and
resource forks...)

Until 2025, implementations SHOULD use video/x-matroska when creating files.
After 2025, implementations SHOULD use video/matroska when creating files.

(or another year sufficiently far in the future)

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide