[urn] Re: Updated request: URN Namespace Registration Requ est for "PNO"

Hallo Guenter,

Overall the details look fine to me. If you would be so kind, please 
format the registration request in accordance with Appendix A of RFC 
8141. [1] This will expedite the process of registration with IANA.

Kind Regards,

Peter

[1] https://www.rfc-editor.org/rfc/rfc8141#appendix-A

On 5/13/24 6:55 AM, Steindl, Guenter wrote:
> Dear IETF / IANA,
> 
> we would like to request the registration of a URN namespace with the 
> following details:
> 
> *1. Namespace Identifier (NID):*
> 
> The PROFIBUS Nutzerorganisation e.V. (PNO) [PNO] is an international 
> association that promotes and supports the development of PROFIBUS and 
> PROFINET, industrial communication protocols used in automation technology.
> 
> We provide standards, certification programs, and resources to ensure 
> product interoperability and reliability, fostering collaboration among 
> manufacturers, system integrators, and end-users.
> 
> The Namespace Identifier (NID) of all URNs that are defined by the PNO is:
> 
>   * NID: pno
> 
> *2. Intended Purpose:*
> 
> The "pno" namespace is intended to provide a unique identifier for 
> resources related to our organization PNO.
> 
> These resources may include documents, software artifacts, and other 
> digital assets produced or managed by PNO.
> 
> *3. Guidelines for URN Structure:*
> 
> URNs within the "pno" namespace will follow the following structure:
> 
>   * urn:pno:{PNOresource}:{ResourceSpecificString}
> 
> where "PNOresource" is a US-ASCII string that conforms to the URN syntax 
> requirements [RFC8141] and defines a specific class of resource type. 
> Each resource type has a specific labeling scheme that is covered by 
> "ResourceSpecificString", which also conforms to the naming requirements 
> [RFC8141].
> 
> PNO maintains a registration authority, the PNO Registration Authority 
> (PNO CO), that will manage the assignment of "PNOresource“, and the 
> specific registration values assigned for each resource class.
> 
> *4. Example:*
> 
> The following examples are representative URNs that could be assigned by 
> the PNO CO.
> 
>   * urn:pno:profinet:yang
>   * urn:pno:foobar
> 
> *5. Additional Information*
> 
> These (PNO) / (PI) specified URNs will be part of next editions of e.g., 
> “PROFINET” as part of the IEC61158/IEC61784 at the IEC.
> 
> *6. Contact Information:*
> 
>   * Organization: PROFIBUS Nutzerorganisation e.V. (PNO)
>   * Email: [email protected] <mailto:[email protected]>
>   * Phone: +49 721 986197 0
> 
> We believe that the registration of the "pno" namespace will facilitate 
> the management and identification of resources associated with PNO.
> 
> Please let us know if any additional information or documentation is 
> required for the registration process.
> 
> Thank you for your attention to this matter.
> 
> Sincerely,
> 
> Günter Steindl
> 
> Committee B “PROFINET” Chair
> 
> PROFIBUS Nutzerorganisation e.V. (PNO)
> 
> With best regards,
> Guenter Steindl
> 
> Siemens AG
> Digital Industries
> Factory Automation
> Industrial Communications
> DI FA CTR ICO
> Werner-von-Siemens-Str. 50
> 92224 Amberg, Germany
> Mobile: +49 (173) 9137406
> mailto:[email protected] <mailto:[email protected]>
> www.twitter.com/siemens <www.twitter.com/siemens>
> www.siemens.com <www.siemens.com>
> Logo
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim 
> Hagemann Snabe; Managing Board: Roland Busch, Chairman, President and 
> Chief Executive Officer; Cedrik Neike, Matthias Rebellius, Ralf P. 
> Thomas, Judith Wiese; Registered offices: Berlin and Munich, Germany; 
> Commercial registries: Berlin-Charlottenburg, HRB 12300, Munich, HRB 
> 6684; WEEE-Reg.-No. DE 23691322
> 
> 
> _______________________________________________
> urn mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

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