IETF Logo Mail Archive

Re: [Cellar] [Matroska-Org/ebml-specification] IANA considerations for Element ID allocation (#179)

Dave Rice <dave@dericed.com> Wed, 13 June 2018 17:48 UTC

Return-Path: <dave@dericed.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 B0C74130F5B for <cellar@ietfa.amsl.com>; Wed, 13 Jun 2018 10:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level:
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] autolearn=no 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 WxTV2NAWq23C for <cellar@ietfa.amsl.com>; Wed, 13 Jun 2018 10:47:59 -0700 (PDT)
Received: from server172-3.web-hosting.com (server172-3.web-hosting.com [68.65.122.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEB58130F3A for <cellar@ietf.org>; Wed, 13 Jun 2018 10:47:59 -0700 (PDT)
Received: from [146.96.19.240] (port=4371 helo=[10.10.201.39]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <dave@dericed.com>) id 1fT9s9-0027BW-I0; Wed, 13 Jun 2018 13:47:58 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Dave Rice <dave@dericed.com>
In-Reply-To: <25624.1528903398@localhost>
Date: Wed, 13 Jun 2018 13:47:52 -0400
Cc: Matroska-Org/ebml-specification <reply+000064ae11970caa961c4b93d7159044226848ffb348ae6892cf000000011730623892a169ce13acc13a@reply.github.com>, cellar@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9EFC9B3B-F622-4085-8ABD-2AB056952D8A@dericed.com>
References: <Matroska-Org/ebml-specification/pull/179@github.com> <Matroska-Org/ebml-specification/pull/179/review/126618692@github.com> <5086.1528391325@localhost> <541FED05-BFD2-4BF9-A054-0D241107CD0D@dericed.com> <25624.1528903398@localhost>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.3273)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/MbMwatMWJ7CuuqxYuXidv2n40b0>
Subject: Re: [Cellar] [Matroska-Org/ebml-specification] IANA considerations for Element ID allocation (#179)
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.26
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, 13 Jun 2018 17:48:01 -0000

> On Jun 13, 2018, at 11:23 AM, Michael Richardson <mcr@sandelman.ca> wrote:
> 
> 
> Dave Rice <dave@dericed.com> wrote:
>>> I don't think it leaves any: it's all experimental.
> 
>> This may be related to the off by one issue. If "Five Byte Element IDs
>> (values from 268435457 upwards) are reserved for Experimental use.”
>> Both 268435456 and 268435457 require a five element id, so in my first
>> reading it seems like this sentence was saying that:
> 
>> 268435456, reservation status unknown
>> 268435457, reservation status unknown
> 
> I would mark them as simply RESERVED, that way nobody can get the encoding
> wrong.
> 
>>> Do we really need that any Five Byte Element IDs in specifications?
> 
>> I don’t need five byte element IDs in this specification, but a user
>> defining an EBML Document Type should be able to read this document and
>> understand if and how they can create their own identifiers at any
>> length.
> 
> The First Come First Served space is usually easiest.
> 
> If you feel that the text needs to be friendly, or explain things better to
> non-IETF types, that's completely reasonable.
> My goal is to write text that *IANA* will understand, and that represents the
> rough consensus of the group.
> So, again, are there any objections to the essential plan?

The essential plan sounds fine with me. Looking forward to reviewing an updated pull request.
Dave

v2.23.0 | Report a Bug | By Email