[urn] Re: URN Namespace Registration for SAID (Self-Addres sing Identifiers)
"Lars G. Svensson" <[email protected]> Mon, 2 Feb 2026 15:10:59 +0100
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
Hi Wenjing, On Samstag, 31. Januar 2026 00:25, Wenjing Chu wrote: Like Dale, I don't see anything that makes me opposing the registration of this namespace. However, I have one question and one comment. Question: > The hash/digest algorithm is encoded in the SAID, at least partially, for cryptographic agility. Applications may use different > digest functions over a long period of time. Data with different digests may also merge. Self-encoding allows the overall > system to evolve gracefully. Another example is PQC. I just want to understand how the hash/digest algorithm is encoded. It doesn't seem to be descrbed explicitely in the registration, and I looked at the CESR documentation but couldn't find it there, either. Can you expand a bit on how this encoding is done and how verification algorithms can find that informtion? Comment: You point to documentation that is on GitHub. My concern is about the long-term accessibility to that documentation (e. g. If GitHub goes out of business...). You might want to consider to use an address that you control (e. g. under the domain trustoverip.org) and then redirect that to GitHub (or wherever the documentation might be in future). That way you need not update the registration just because a third party platform goes out of business. Best, Lars _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]