3 ms·
How about superencoding the number with a letter so nobody confuses rfc822 in this system with what the IETF does.
by ggm 1y ago
How about superencoding the number with a letter so nobody confuses rfc822 in this system with what the IETF does.
- tlhunter 1y agoI did originally plan for every company to be able to configure their own XYZ prefix (there's a vestibule of this that you can see here by replacing `rfc` with any arbitrary acronym like `XYZ`): https://rfchub.app/rfchub/XYZ1-org-batch-markdown-exporter-job https://rfchub.app/rfchub/XYZ1-org-batch-markdown-exporter-j... The overall namespace is the org slug (`rfchub` in this case) so I was going to allow different orgs to choose the same prefix (defaulting to `RFC`). In that respect the actual globally unique identifier for this proposal is `rfchub/rfc1`. But I need to figure out some bigger features first before I add that.