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

Steve Lhomme <slhomme@matroska.org> Wed, 25 August 2021 07:03 UTC

Return-Path: <slhomme@matroska.org>
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 600BE3A0B3C for <cellar@ietfa.amsl.com>; Wed, 25 Aug 2021 00:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=matroska-org.20150623.gappssmtp.com
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 9ck6HKHCl5Yu for <cellar@ietfa.amsl.com>; Wed, 25 Aug 2021 00:03:50 -0700 (PDT)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0523B3A0B37 for <cellar@ietf.org>; Wed, 25 Aug 2021 00:03:49 -0700 (PDT)
Received: by mail-wm1-x32c.google.com with SMTP id v20-20020a1cf714000000b002e71f4d2026so3036913wmh.1 for <cellar@ietf.org>; Wed, 25 Aug 2021 00:03:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=matroska-org.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=eYJTODi+i7hGEoHfct3mN++lgnmMsJ68s37ghpZh9d8=; b=g1lQTeZwkzckUGRnCnMTMb3T/tFV9wbO4V8kQ9SLzoEPdQD9JaUXibQH3ZWoJwackQ r/8S4ZTYyl2eS/feKxSUr6WI2gfEKfKYf8qt/qfq3vDLZZg0J3j0NpK8WEPQ2Ge646cQ j2ZF5Wdp8vsWvxovBFTKae4ZL7eDe5JE442eH+tmzyWgBOG2GAcYXRGzTBAuY1SgjRIu 6QnU+H3afWT8KtbWBgymyR2NuuJWWyJobEWiYsEYSIZl8wWOyK2u8AJU7AiakpEipkx3 8uwEhplFBNkDsoPxTNrslV0re0T7bMWLQKKGDktcGba2RL5N6B2RjvZrj67NkdcOtgKh O3Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=eYJTODi+i7hGEoHfct3mN++lgnmMsJ68s37ghpZh9d8=; b=hq3JZt99HlWPoNToTkqUTBzWyRmCkNSBZ5zJGhkjr6gl4aFSO5OGl1cr55/yU5KlQs mIqNbokBRrwK8eGhLWnLoGvdq4Yfl/HZkKpT+4RjYvmdLhEkPG4S9qyqG486eRiBuwck WWDuHzJQ18lopu1Sh0VZJbG0dDlkArhVRK8QoshkrOUgG+HWdvR6fw3GcZ2FReFRAk1N 7fRS8GTnUKvpEWEbXQD8guRNWFvO3wUCun34qBCqgju2z9WKJoqRPNoAKc5QO6QCJRCI IxJb1Qwg9fmaAsa0UjSsEaMtplrRO7KmL+zFPm7rwVmIA6pAPpgRPIgOsVk8oHZBef+H oqUQ==
X-Gm-Message-State: AOAM531fnSG3YM+kglJwnKJLATdDazdMCPsxmhwfTAFak+Ziq0jZnb+6 VAKIhZjX8KtwKrDDUAovGWvQzQ==
X-Google-Smtp-Source: ABdhPJzmynsWcgdBlR663pRVlV0SL7GUmdr6drrNT+K7Y4WtZ/RYg7PWnAbTSamxPU9nRmcblx6Wrw==
X-Received: by 2002:a7b:c041:: with SMTP id u1mr7389626wmc.95.1629875023368; Wed, 25 Aug 2021 00:03:43 -0700 (PDT)
Received: from ?IPv6:2a01:cb0c:20:e900:e4c9:8e45:d76b:34fd? (2a01cb0c0020e900e4c98e45d76b34fd.ipv6.abo.wanadoo.fr. [2a01:cb0c:20:e900:e4c9:8e45:d76b:34fd]) by smtp.gmail.com with ESMTPSA id l15sm4245902wms.38.2021.08.25.00.03.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 Aug 2021 00:03:43 -0700 (PDT)
To: Michael Richardson <mcr@sandelman.ca>, "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>
References: <CAKKJt-ceukRCPUK=DTvDxDBPw-ddROX-snfZQ-BatSkgVZ0-qw@mail.gmail.com> <CAL0qLwY6V8eVG56ckhy3GFDwW61-6OD9_h=X-vDWFySM0e3B9A@mail.gmail.com> <4945.1629386506@localhost> <CAL0qLwZeE1qZ+5wLnCMFoCcvP2cf5=9Y+g5Lx3k5iqxF7gAw5g@mail.gmail.com> <22109.1629403274@localhost> <CAL0qLwbUk7QLiCEESqbEknUELSgure+MrdvLXBK+hkRV_GxVxQ@mail.gmail.com> <31989.1629428105@localhost> <CAOXsMF+j8T+H1HZoJKsRsyb_VehNn0y1981WGcX+G0EHGHq1TQ@mail.gmail.com> <14770.1629838918@localhost>
From: Steve Lhomme <slhomme@matroska.org>
Message-ID: <26ac55ea-2f04-d21a-8dee-ef819fa249c2@matroska.org>
Date: Wed, 25 Aug 2021 09:03:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <14770.1629838918@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/UD8JlFCYDjcqDVBQDBAbzOuL-D0>
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: Wed, 25 Aug 2021 07:03:58 -0000

Hi,

On 2021-08-24 23:01, Michael Richardson wrote:
> 
> Steve Lhomme <slhomme@matroska.org> wrote:
>      > Given one of the goal on this Matroska specification is long time
>      > preservation, that would seem odd to design something that renders
>      > older systems incompatible with the current/new specifications. If any
>      > of the MIME types we have in attachments were to become invalid all of
>      > a sudden we wouldn't like it.
> 
> That's not what I suggested.

Sorry for misinterpreting your words.

> I suggested that every reader would always accept both values.
> 
> But that, at some date in the future, writers would start using the new
> values.  I suggested that the date be decided now in order to:
>    a) establish a deadline for readers to get updated.
>    b) allow writing software to gracefully transition without having to be updated.
>    (of course, such software could also have an option)
> 
> We assume that the files are forever, but that the software that reads them
> will get updated now and then.
> 
> In reality, the mime type doesn't really go anywhere specific unless the file
> is being transfered over email or http.  On MAC, with HFS, the MIME type
> might lookup a resource type which gets associated with the file.
> 
> But I suspect that one can associate two things with one resource, and I also
> suspect (having really never coded for MacOS) that it doesn't take mime types
> as input anyway.

I agree with that. But I have the same concern as Murray that a 
hardcoded deadline may not really work.

It also doesn't seem like how our RFCs are designed, where we have some 
legacy values that should not be used throughout the Matroska format. 
Then we would also need to set some deadline for these values not be 
allowed to be written.

In the end when we say it SHOULD NOT be used, it applies right away, not 
some date in the future. That's the same approach I took with the 
transition of MIME types. Just like updating muxers may take some time, 
updating web servers and UPNP servers to update they MIME database will 
take some time.

> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [
>