I would like to have one unique place where all of these are registered, with a process in place to propose new names, new mappings via PR, with some appointed people to check if that is valid. Finally repos like multihash, multicodec & so on can point to their specific page on this IANA-like repo.
Maybe it is overworking it right now, but when the project outgrows, we should track this
I think "our IANA" is the github repos. Each table is contained in each repo.
Over time, for big things (like multihash) we can actually use proper IANA.
If we think pulling them into one place adds value, i'm ok with it. but i think right now it will be harder to think about than in the same repo as the spec.
Multicodec, multibase, multihash, path namespaces, reserved keywords.
I would like to have one unique place where all of these are registered, with a process in place to propose new names, new mappings via PR, with some appointed people to check if that is valid. Finally repos like multihash, multicodec & so on can point to their specific page on this IANA-like repo.
Maybe it is overworking it right now, but when the project outgrows, we should track this