Prerequisites to getting shorter service and characteristic IDs
Currently the draft uses 128 bit UUIDs for service and characteristic. These impractically long, especially the service identifier that's part of the advertisement and thus takes space from other usages such as #6.
What do we need to do to get a 16- or 32-bit "UUID" assigned?
Can we do this at an early stage (because changing the length later would change properties such as how long the hashes of #6 can be), or is there a 16/32bit UUID that is for "experimental use"?
I don't think that CoAP-over-GATT will meet with the SIG's approval if it needs any (because it's picking the IETF "using a network" approach over Bluetooth's "we provide a batteries-included full stack"), but maybe there is a process that's just like IANA's FCFS or Expert Review ... or it's just through SIG membership anyway, and we'd need a member that just says "we need this" and it gets assigned.