[urn] Re: improved management of registration requests
Peter Saint-Andre <[email protected]> Wed, 25 Mar 2026 08:51:30 -0600
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
On 3/24/26 5:26 AM, Lars G. Svensson wrote: > On Dienstag, 17. März 2026 15:34, Peter Saint-Andre [mailto:[email protected]] wrote: > >> Hi Lars, thanks for the feedback. :-) > > Hi Peter, happy to help! > >>>> (c) I usually reformat approved registration requests before final >>>> submission to IANA (for instance to keep line lengths to >>>> 72 characters and to ensure consistency across registrations); it >>>> would be better if these changes, though relatively minor, were done >>>> in the open >>> >>> I belive this is something that GitHub could automate... > >> Some of it, yes (e.g., line lengths). I sometimes also make slight >> editorial fixes (e.g., typos, grammar). > > Re-reading this discussion, I realise that there is an important difference between urn namespace registration requests and RFCs in that we (i.e. IETF) actually don't have any change control for the registration requests. This lies completely with the registrants. So the question arises if we want to mandate this. As you've probably noticed, sometimes registrants keep their requests under source control (usually GitHub), so it could be confusing to keep the same request under source control in two different repositories. This is one reason why I have not been consistent in using the person respository I set up. I'm not yet sure how to approach this issue, but I suppose there is no harm in having the same document in two places. >> I did set up a repository [1] but I haven't been consistent >> about using that for registration requests and I will make >> an effort to do so from now on. > > That would of course give us a possibility to execute change control but it would happen in your personal repo without any formal connection to the IETF. Maybe we can ask for a sub-repo of the ietf [1]. When I inquired about this a few years ago, I was told that there were no plans to provide repositories under the IETF GitHub org for expert review teams. I still think that would be the best approach, so I will inquire again. Peter _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]