Re: [Cbor] CBOR tag range IANA allocation policy

Jim Schaad <ietf@augustcellars.com> Fri, 26 July 2019 12:22 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85D391202E0 for <cbor@ietfa.amsl.com>; Fri, 26 Jul 2019 05:22:05 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 lEjFAjKdtB8s for <cbor@ietfa.amsl.com>; Fri, 26 Jul 2019 05:22:03 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BA3312029A for <cbor@ietf.org>; Fri, 26 Jul 2019 05:22:03 -0700 (PDT)
Received: from Jude (31.133.136.216) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 26 Jul 2019 05:21:56 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Carsten Bormann' <cabo@tzi.org>, 'Sean Leonard' <dev+ietf@seantek.com>
CC: 'Thiago Macieira' <thiago.macieira@intel.com>, 'Ira McDonald' <blueroofmusic@gmail.com>, <cbor@ietf.org>
References: <07D48905-77B6-447B-8CEB-971CD0568FB9@seantek.com> <10096467.9kdZcmANtY@tjmaciei-mobl1> <CAN40gSt-h+HGLJuTUFMHn3jjOqMJyJjetdSiW1e-o3uZcZ8a3A@mail.gmail.com> <584C141B-9704-4BA2-BD30-21E2FE4D6F90@seantek.com> <1A8A7E20-A92C-4242-92EB-950CD1F93B27@tzi.org>
In-Reply-To: <1A8A7E20-A92C-4242-92EB-950CD1F93B27@tzi.org>
Date: Fri, 26 Jul 2019 08:21:53 -0400
Message-ID: <045601d543ac$b79f3d40$26ddb7c0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQI1+RqtKmMqPa99WI8bvfzd2IMJ1QHaPyU6AaIhjlIC19vEzQKJvFsIpdR2lvA=
Content-Language: en-us
X-Originating-IP: [31.133.136.216]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/IhlxDxV41r6NNPbBdFXoY-Pe-VQ>
Subject: Re: [Cbor] CBOR tag range IANA allocation policy
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jul 2019 12:22:06 -0000

I think that RFC Required might be overkill.  As this is a specification required, there is already a requirement for Expert Review as well.  The easier thing might be to add language to the reviewer instructions along the lines of:

Reviewers should be reluctant to assign code points in the 24-255 range to specifications that are not RFC documents.  In the event that it is deemed wise to assign such a point anyway the CBOR working group mailing list should be advised of this and allowed to give input over a short period of time (in the order of 3-5 days).

Jim


-----Original Message-----
From: CBOR <cbor-bounces@ietf.org>; On Behalf Of Carsten Bormann
Sent: Thursday, July 25, 2019 6:25 PM
To: Sean Leonard <dev+ietf@seantek.com>;
Cc: Thiago Macieira <thiago.macieira@intel.com>;; Ira McDonald <blueroofmusic@gmail.com>;; cbor@ietf.org
Subject: Re: [Cbor] CBOR tag range IANA allocation policy

On Jul 25, 2019, at 18:19, Sean Leonard <dev+ietf@seantek.com>; wrote:
> 
> 24-255 = RFC Required

I like that.
(That includes the independent stream.  But there is a level of quality checking in publishing an RFC, so only high quality specifications will get these.  Of course, the designated expert *could* do the same quality checking, but there may be a slightly higher tendency to just give in among us weaker DEs.)

Grüße, Carsten

_______________________________________________
CBOR mailing list
CBOR@ietf.org
https://www.ietf.org/mailman/listinfo/cbor