Re: [Cellar] [ietf-wg-cellar/ebml-specification] EBML ID 0x80 is marked invalid/reserved but it's used in Matroska (#407)

"Murray S. Kucherawy" <superuser@gmail.com> Tue, 18 May 2021 17:41 UTC

Return-Path: <superuser@gmail.com>
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 DF43A3A1ABB for <cellar@ietfa.amsl.com>; Tue, 18 May 2021 10:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DHdCPj-5b8CN for <cellar@ietfa.amsl.com>; Tue, 18 May 2021 10:41:23 -0700 (PDT)
Received: from mail-vs1-xe35.google.com (mail-vs1-xe35.google.com [IPv6:2607:f8b0:4864:20::e35]) (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 1A6163A1ABA for <cellar@ietf.org>; Tue, 18 May 2021 10:41:22 -0700 (PDT)
Received: by mail-vs1-xe35.google.com with SMTP id j13so5376688vsf.2 for <cellar@ietf.org>; Tue, 18 May 2021 10:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ptbmYyoKAg579sA5s5fLADKmUEBaVuJEguYNee0yHOw=; b=uXHYSPDTFbK9GWOhJ5y3GM3DDN2MzFCROvVe0kQpFJa+Ggol4vH0awygOAUbOapn/Z +ZkqHxr5DxPdLiC7NnAx6T/Bjpv+jXhV/cCr9f2TeVkShwuZNS2fk9O6KFXDvmn2ZgoX MhBtRpzID5j9y1Ol1KwHnCDXYdSATC6CeztlT7b6hLDJVNYJTETAHYvX6ehrCQ6u4gj3 iWAUF08kIFeVejVlDx5jPjWloHdPA4m1HXgZ6qlN0oXZ13GIorGBBGZZKZ76YWC55qw2 jlkJFjei+DJC2arykyEJeVnoX6nFfF2FIXg9pz/Gu1Wtdr8GbvYXPsq4kdYrOyA1rxGD Y1mA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ptbmYyoKAg579sA5s5fLADKmUEBaVuJEguYNee0yHOw=; b=Z/08KbxnVUE9kCTDBzqKv7l5B67CZxJhTnw9zkL/rC1dRxjD0zzSJlTPJ94n3XBGBA WCnW2umF6FcX+YH0hv0PKMgCGZT+7YSona87uggrnplrzUN8/fvcYP1R/PbABZg1PrJw 4yF/zUxMYzJcFkuO0siSl9WlBJcSqxnDrk+N7ejU7QX/6bm/imohDv06Z/wcjAkGk67w LssdMnA6CIiQ921x+RMNT4p+QY1gBwTJMht8SdRxhyZDsQb+XfYhkcEUlSN3up5Qo0xP qLLuYU6p/LSkhU94aGbu/zS6YZZZW3PfFittGhljGaGtfYnnES7nv4l1dLig3bucxgWg n9xA==
X-Gm-Message-State: AOAM530KWNkb5f/PYD78nvtu7mjVY/WqhTox0LWY6IzOxNzmFxilG1Gb oGMXODot6jmLbjRDpWyP/G68mJtiIHcF4cje5sU=
X-Google-Smtp-Source: ABdhPJx405H7d0hwoKREzSZ2yn4LLuTNl7fakafCtxhEQoZB+Vrk8AdNRJLpxc2IwqFBEMr2V5otfzpGZc30R64Q1yM=
X-Received: by 2002:a67:ebd7:: with SMTP id y23mr4461445vso.54.1621359680940; Tue, 18 May 2021 10:41:20 -0700 (PDT)
MIME-Version: 1.0
References: <ietf-wg-cellar/ebml-specification/issues/407@github.com> <21441.1620656178@localhost> <CAKKJt-e5PtTZM=j=Cn_YBPW87ag+oui7mGx=wuxt0JU1KY3SLQ@mail.gmail.com>
In-Reply-To: <CAKKJt-e5PtTZM=j=Cn_YBPW87ag+oui7mGx=wuxt0JU1KY3SLQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 18 May 2021 10:41:09 -0700
Message-ID: <CAL0qLwa7u3C9h1ABJBWO63-nEvmnHVA3=qCrHpW2VYv7tyhGNg@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Michael Richardson <mcr@sandelman.ca>, Codec Encoding for LossLess Archiving and Realtime transmission <cellar@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d5eea705c29e37ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/NF7cVxn5IDs5Hynaus02stTv2A4>
Subject: Re: [Cellar] [ietf-wg-cellar/ebml-specification] EBML ID 0x80 is marked invalid/reserved but it's used in Matroska (#407)
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: Tue, 18 May 2021 17:41:25 -0000

Sorry for the delay replying here.

On Mon, May 10, 2021 at 3:44 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Adding our Loyal AD ... because I could be wrong, and he would know ...
>
> I'm not sure how to deal with this.
>> It may be that we can put these IANA instructions into the Matroska
>> document.
>> Obviously, they would ideally go into an EBML-bis document, and that
>> would be
>> something we'd do if we were revising it now.
>>
>
> That would be perfect (if we were doing an EBML-bis document, but I
> predict that the answer is - the EBML document is a Proposed Standard, so
> any Proposed Standard that (reasonably) updates the instructions to IANA
> should be OK. This update is relevant for Matroska, which is also targeting
> publication as a Proposed Standard, so that's a fine place to put the
> updated IANA instructions.
>
> The EBML RFC IANA instructions would be outdated, but the point of IANA
> registries is that the IANA registries are up to date, and you don't have
> to chase (in some cases) a few dozen RFCs to find all the rules.
>
> Murray, is that about right?
>

It's possible I don't have all the context I need here, in which case this
answer will be nonsense and I'll need ask for more details, but running
with what I've got:

I think you could do an "updates" document to EBML that just makes IANA
registry/policy amendments if you want to do that.  Smaller documents tend
to result in faster processing by the IESG.  The cases where this tends not
to work is where the number of "updates" documents gets large enough that
teasing out reality becomes difficult; at that point it becomes better to
just issue a complete "bis" document.

If you put EBML-specific IANA actions in the Matroska document, and they
are not clearly related, you might encounter some resistance of the form
"What the heck is this doing here?" from the IESG or other reviewers.

If that's not a helpful answer, let me know and I'll get Spencer to give me
more context.

-MSK