[urn] Re: Registration request for AR URN Namespace

Hi Dale and Peter,

Thank you for your feedback, I am preparing an update, sorry for the delay.

Regards
Quoc


From: Dale R. Worley <[email protected]>
Sent: Thursday, 11 December 2025 03:30
To: Quoc Pham <[email protected]>
Cc: [email protected]; Sharon Jonnalagadda <[email protected]>
Subject: Re: [urn] Registration request for AR URN Namespace

"Quoc@ registry. godaddy" <Quoc=40registry. godaddy@ dmarc. ietf. org> writes: > ar_namespace_v1. txt As Peter noted (but mis-spoke), RFC 8141 requies that namespace names must have at least three characters: 3. It MUST be more than two characters
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> writes:

> ar_namespace_v1.txt



As Peter noted (but mis-spoke), RFC 8141 requies that namespace names

must have at least three characters:



    3.  It MUST be more than two characters long, [...]



In regard to the application:



  Syntax:



  urn:ar:params:xml:ns:<extension>, where <extension> is the EPP command

  extension that delivers on specific requirements. All extensions extend on

  the base EPP commands described in RFC5730.



It would be helpful if the acronym "EPP" was expanded at its first use

so the casual reader would understand what the overall purpose is.



The phrase "delivers on specific requirements" sounds like

marketing-speak.  What does it mean?



You need to provide the syntax for the nonterminal "extension".



Dale

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]