[urn] Re: Registration request for AR URN Namespace
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <PH0PR02MB9364F110B51CC4213DF595DFBD90A@PH0PR02MB9364.namprd02.prod.outlook.com> |
Hi Dale and Peter, Thank you for the clarity, we only ever intent to set our extension to be made up if ALPHA, DIGIT, hyphen and dot and now I fully understand the issue with US 7 bit ASCII. So if I was to include what you have listed in your emails, would that be acceptable (I know that you have tilde I your list but I guess we can keep that in there for our application in case)? Regards Quoc From: Peter Saint-Andre <[email protected]> Sent: Monday, 26 January 2026 13:53 To: Dale R. Worley <[email protected]>; Quoc Pham <[email protected]> Cc: [email protected]; Sharon Jonnalagadda <[email protected]> Subject: Re: [urn] Re: Registration request for AR URN Namespace On 1/25/26 7: 47 PM, Dale R. Worley wrote: > Looking at Appendix A of RFC 3986, I suspect that you want to allow the > extension to be one or more "unreserved" characters: > > unreserved = ALPHA / DIGIT / "-" / ". " / "_" / "~" Agreed. ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd On 1/25/26 7:47 PM, Dale R. Worley wrote: > Looking at Appendix A of RFC 3986, I suspect that you want to allow the > extension to be one or more "unreserved" characters: > > unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" Agreed. Peter _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]