[urn] Informal URN Namespace Registration Request
Gowtham Rao <[email protected]> Fri, 29 May 2026 08:13:50 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <LV5PR08MB108215C414D942779EF3EC6F2E9162@LV5PR08MB10821.namprd08.prod.outlook.com> |
--===============8445166949945683325== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_LV5PR08MB108215C414D942779EF3EC6F2E9162LV5PR08MB10821na_" --_000_LV5PR08MB108215C414D942779EF3EC6F2E9162LV5PR08MB10821na_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To whom it may concern: ------------------------------------------------------------------------- Namespace ID: Informal/blank Registration Information: Name: Gowtham Rao Affiliation: CoReason, Inc. Contact Email: [email protected] Declared registrant of the namespace: CoReason, Inc. Declaration of syntactic structure: The Namespace Specific String (NSS) of all URNs assigned within this namesp= ace will conform to the standard URN syntax defined in RFC 8141. Identifier= s will take the form of alphanumeric strings or standard UUIDs. Relevant ancillary documentation: None specified. Identifier uniqueness considerations: Identifiers are generated and managed via a central internal registry to gu= arantee global uniqueness and ensure no duplicate identifiers are issued. Identifier persistence considerations: Identifiers are intended to be persistent indefinitely for internal data tr= acking and system profiling. Process of identifier assignment: Identifiers are assigned automatically by our internal database systems upo= n the creation of a new record or entity within the system. Process for identifier resolution: These URNs are not currently resolvable via public global infrastructure. T= hey are resolved via internal APIs and data pipelines within our organizati= on. Rules for Lexical Equivalence: Lexical equivalence is based on exact case-sensitive string matching. Conformance with URN Syntax: There are no known exceptions to the URN syntax rules outlined in RFC 8141. Validation mechanism: None specified outside of standard internal database validation. Scope: Private --_000_LV5PR08MB108215C414D942779EF3EC6F2E9162LV5PR08MB10821na_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof" style=3D"font-size: 11pt;">To whom it may con= cern:<br> <br> -------------------------------------------------------------------------<b= r> <br> Namespace ID: Informal/blank<br> Registration Information: </div> <div class=3D"elementToProof" style=3D"font-size: 11pt;"><br> Name: Gowtham Rao<br> Affiliation: CoReason, Inc.<br> Contact Email: [email protected]<br> <br> Declared registrant of the namespace: CoReason, Inc.</div> <div class=3D"elementToProof" style=3D"font-size: 11pt;"><br> Declaration of syntactic structure:<br> The Namespace Specific String (NSS) of all URNs assigned within this namesp= ace will conform to the standard URN syntax defined in RFC 8141. Identifier= s will take the form of alphanumeric strings or standard UUIDs.<br> Relevant ancillary documentation:<br> None specified.<br> Identifier uniqueness considerations:<br> Identifiers are generated and managed via a central internal registry to gu= arantee global uniqueness and ensure no duplicate identifiers are issued.<b= r> Identifier persistence considerations:<br> Identifiers are intended to be persistent indefinitely for internal data tr= acking and system profiling.<br> Process of identifier assignment:<br> Identifiers are assigned automatically by our internal database systems upo= n the creation of a new record or entity within the system.<br> Process for identifier resolution:<br> These URNs are not currently resolvable via public global infrastructure. T= hey are resolved via internal APIs and data pipelines within our organizati= on.<br> Rules for Lexical Equivalence:<br> Lexical equivalence is based on exact case-sensitive string matching.<br> Conformance with URN Syntax:<br> There are no known exceptions to the URN syntax rules outlined in RFC 8141.= <br> Validation mechanism:<br> None specified outside of standard internal database validation.<br> Scope:<br> Private<br> <br> <br> </div> </body> </html> --_000_LV5PR08MB108215C414D942779EF3EC6F2E9162LV5PR08MB10821na_-- --===============8445166949945683325== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1 cm4tbGVhdmVAaWV0Zi5vcmcK --===============8445166949945683325==--