Closed zzo38 closed 1 year ago
My suggestion of numbers would be 0xF05511 (15750417) for Fossil
That sounds good to me.
0x3C (60; the ASCII code for a less than sign, which all message IDs must start with) for Message-ID.
We try to reserve numbers less than 0x80 (128) for widely used things as they encode as a single byte varint. Hence we ask everyone if a higher number would be OK as well. So I'd propose something that falls into at least the 2 byte varint range.
We try to reserve numbers less than 0x80 (128) for widely used things as they encode as a single byte varint. Hence we ask everyone if a higher number would be OK as well. So I'd propose something that falls into at least the 2 byte varint range.
My idea was to use the less than sign since message IDs must start with it (one of the other codes says "corresponds to /
in ASCII", and I had a similar idea but with <
instead for Message-ID), but if that isn't important then a higher number will be OK instead.
@zzo38 : if you want to move this forward, can you please open a PR and choose a number greater than 128?
Closing due to inactivity, but feel free to move forward with a PR @zzo38!
Suggestion to add multicodec number for Fossil version control system (I use for my own projects, instead of git) and Message-ID (mainly for identifying messages on NNTP, but also applicable to email).
My suggestion of numbers would be 0xF05511 (15750417) for Fossil and 0x3C (60; the ASCII code for a less than sign, which all message IDs must start with) for Message-ID. However, other numbers may also be possible if you believe that these numbers are unsuitable.