-
Notifications
You must be signed in to change notification settings - Fork 0
uri schemes that we want numbers for
Carsten Bormann edited this page Dec 16, 2022
·
8 revisions
Collect uri-schemes here
Sorted by likely encoding we want to go for
URI scheme | CRI value | Reference |
---|---|---|
coap | -1 | [RFCthis] |
coaps | -2 | [RFCthis] |
http | -3 | [RFCthis] |
https | -4 | [RFCthis] |
urn | -5 | [RFCthis] |
did | -6 | [RFCthis] |
coap+tcp | -7 | [RFCthis] |
coaps+tcp | -8 | [RFCthis] |
coap+ws | -9 | [RFCthis] |
coaps+ws | -10 | [RFCthis] |
14 slots left.
Note that MQTT:// (and possibly MQTTS:// ???) are not in here as these are not registered at all, so these numbers can be registered with the url-scheme registration.
(There was an entry for http here -- for consistency, we put this into the 1+0 group.)
Bluetooth SIG did this exercise already at https://www.bluetooth.com/wp-content/uploads/2022/11/assigned_numbers_release-1.pdf#page=35 -- but with no priorities in assigning numeric ranges.