Re: Registration request for urn:thread:
"Lars G. Svensson" <[email protected]>
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
To me, that sounds like a good solution that would ensure that the relevant registry data is openly available while still allowing other parts to be members-only. Best, Lars -----Ursprüngliche Nachricht----- Von: urn [mailto:[email protected]] Im Auftrag von Esko Dijk Gesendet: Montag, 29. Januar 2024 09:45 An: Peter Saint-Andre <[email protected]>; Dale R. Worley <[email protected]> Cc: [email protected] Betreff: Re: [urn] Registration request for urn:thread: > Section 5.1 of RFC 8141 states: > > Formal URN namespaces might be appropriate even when some > aspects are not fully open. For example, a URN namespace might make > use of a fee-based, privately managed, or proprietary registry for > assignment of URNs in the URN namespace. However, it might still > benefit some Internet users if the associated services have openly > published names. > > In this case, I would say that the letter of RFC 8141 overrides the > spirit of the IETF. Indeed this section was the basis for including a privately managed (members-only) and non-public registry in the request. (Non-public, because viewing it requires accepting the EULA.) There is a suggestion there to have at least the names - that are in the registry - published. That is something we could add as a requirement for any entries in the internal registry, if that helps? The public version of the registry would be in a separate document that can be downloaded from www.threadgroup.org without providing a name or accepting a EULA. And each registered URN would provide the name and a short description also. Something like the table provided by 3GPP (https://www.3gpp.org/3gpp-groups/core-network-terminals-ct/ct-wg1/uniform-r esource-identifier-uri-list) for example. It would then provide a link / doc-reference pointing into the non-public specification. Esko _______________________________________________ urn mailing list [email protected] https://www.ietf.org/mailman/listinfo/urn