Re: [Cbor] List of not-well-formed CBOR and test vectors

I would agree.  I think it is worthwhile to put the reasoning for the reserve into the document.  Perhaps as part of the DE instructions so that it does not accidently get assigned after you retire and stop doing the work.

Jim

-----Original Message-----
From: CBOR <cbor-bounces@ietf.org> On Behalf Of Laurence Lundblade
Sent: Saturday, August 3, 2019 5:01 PM
To: Carsten Bormann <cabo@tzi.org>
Cc: cbor@ietf.org
Subject: Re: [Cbor] List of not-well-formed CBOR and test vectors

OK. I didn’t realize that “Reserved” was a special key word per 8126. I was going by the dictionary definition. Only super hard-core IETF people will ever look at 8126, so most will get this wrong. 

The 5-bit values 28..30 are listed as reserved in one place and unassigned in another. Probably they should be listed as reserved everywhere (change Table 1).There is no assignment procedure for 28..30 in the IANA section.

LL

> On Aug 3, 2019, at 1:12 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On Aug 3, 2019, at 19:07, Carsten Bormann <cabo@tzi.org> wrote:
>> 
>> Well, reserved means “not available for allocation”. 
> 
> (Forgot to cite chapter and verse:)
> 
> https://tools.ietf.org/html/rfc8126#section-6
> 
> Grüße, Carsten
> 
> _______________________________________________
> CBOR mailing list
> CBOR@ietf.org
> https://www.ietf.org/mailman/listinfo/cbor

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