CoAP content-formats registration

[thomas-fossati]

Feedback from the CoAP Content-Format registry expert:

The request looks correct. However it does request 2 numbers from the 0-255 range without any motivation. And for a content type that is quite specific/exotic that would not be the right range.

We can assign (1) a short option value (1 byte, 0-255) with a good reason or (2) the longer option value (2 bytes, from one of the below ranges) for which no reason is required:

256-9999 IETF Review or IESG Approval (the former is unavailable, so IANA would submit an approval request to the IESG that's separate from the conflict review) 10000-64999 First Come First Served

If the authors can provide some background information - e.g. when & how often the PSA token is expected to be exchanged over CoAP, that would help deciding the range.

So approved as far as I'm concerned, but the exact range to select should still be considered.

While we could argue for the shorter encoding, I think it's not worth the effort.

I suggest we change the request to utilize the $$[256,9999]$$ range instead.

---

For completeness, the available ranges are as follows:

Range	Registration Procedures
0-255	Expert Review
256-9999	IETF Review or IESG Approval
10000-64999	First Come First Served
65000-65535	Experimental use (no operational use)

[thomas-fossati]

I have prepared the PR (#146) just in case.

[adrianlshaw]

While we could argue for the shorter encoding, I think it's not worth the effort. I suggest we change the request to utilize the

Makes sense to me

[thomas-fossati]

Eliot suggested to use the First Come First Serve (FCFS) range instead.

It is also 2 bytes, so there is no difference on the wire.

Besides, re-reading the relevant bits of RFC7252:

"The identifiers between 256 and 9999 are reserved for future use in IETF specifications (IETF Review or IESG Approval)."

which makes (256,9999) unapplicable to our document - an ISE document.