Re: [Cbor] CBOR tag range IANA allocation policy

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