Re: [urn] NEW NAMESPACE REGISTRATION: KNX

[Michael Critchfield <[e-mail]>]

Hi Peter,
Thanks for your kind reply and support on this.
I attach the Specification in its current state and as it should be available via knxcloud.org (Server is down).
The recommended changes are being processed internally as we speak.

Regarding your question on the special meaning of certain characters of the NSS, we were referring to language we have specified and will be using within our namespace.
Examples are urn:knx:fb for Functional Block or urn:knx:dpt for Datapoint Type.

I hope this clarifies it a bit more. Please don’t hesitate to get back me if you need more info, like you did before.

Best regards,
Michael

-----Ursprüngliche Nachricht-----
Von: Peter Saint-Andre <[e-mail]> 
Gesendet: Donnerstag, 14. September 2023 18:20
An: Michael Critchfield <[e-mail]>; [e-mail]
Cc: Joost Demarest <[e-mail]>; André Hänel <[e-mail]>; Steven De Bruyne <[e-mail]>; W. van der Beek <[e-mail]>
Betreff: Re: [urn] NEW NAMESPACE REGISTRATION: KNX

Hi Michael & all,

Although we typically like registrations to include a higher level of detail, I think we can approve this registration.

I do have one further question about the following text under Security and Privacy:

"The KNX Association may assign special meaning to certain characters of the Namespace Specific String (NSS) in its specifications."

Because knxcloud.org is not responding to HTTP requests right now, I cannot download and check the specification for a description of this "special meaning"; however, what kind of security or privacy implications might there be?

Peter

On 9/7/23 1:16 AM, Michael Critchfield wrote:
> Dear URN Team,
>
> As KNX Association cvba, we would like to register the following 
> Namespace from our KNX IoT Point API Specification with you for 
> listing in Uniform Resource Names (URN) Namespaces (iana.org) 
> <https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml>
>
> Reference is our KNX IoT Point API Specification available on 
> https://schema.knx.org <https://schema.knx.org>.
>
> Specifically, the KNX IoT Point API Specification is found under this 
> link https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download
> <https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download>.
>
> Please note that as per our previous discussions via eMail, these 
> publicly available PDFs will undergo editorial changes to reflect your 
> latest recommendations of
>
>   * replacing “relative URN” with “truncated URN” and
>   * streamlining the use of {...} vs. <...> for the
>     definitions/uses/examples of urn:knx.
>
> These Changes are not yet reflected on the publicly available PDFs.
>
>   * Namespace Identifier: knx (example „urn:knx:dpa“)
>   * Version: 1
>   * Date: 2023-09-07
>   * Registrant: KNX Association cvba, De Kleetlaan 5, B-1831
>     Brussels-Diegem, Belgium
>       o Joost Demarest [e-mail]
>         <mailto:[e-mail]>
>   * Purpose: KNX IoT Point API, as specified on https://schema.knx.org
>     <https://schema.knx.org> (specifically
>     https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download
>     <https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download>) and
>     future EN50090-4-4, see note above on pending editorial changes.
>   * Syntax: urn:knx:<NSS> where the syntax of "<NSS>" is specified in
>     Section 2.2 of the URN Syntax requirements [RFC8141].
>   * Assignment: Assignment done by KNX Association through KNX
>     Specifications.
>   * Security and Privacy:
>       o There are no additional security considerations other than those
>         normally associated with the use and resolution of URNs in
>         general, which are described in [RFC1737
>         <https://www.rfc-editor.org/rfc/rfc1737>] and [RFC8141
>         <https://www.rfc-editor.org/rfc/rfc8141>].
>       o This document registers a namespace for URNs.  KNX Association
>         may assign special meaning to certain characters of the
>         Namespace Specific String (NSS) in its specifications.
>   * Interoperability: No known issues related to interoperability.
>   * Resolution: Not applicable; the "knx" namespace is not listed with a
>     Resolution Discovery System.
>   * Documentation: KNX IoT Point API, as specified on
>     https://schema.knx.org <https://schema.knx.org> (specifically
>     https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download
>     <https://knxcloud.org/index.php/s/KNjAyyO0ojm5LSc/download>) and
>     future EN50090-4-4, see note above on pending editorial changes.
>   * Additional Information: Not applicable
>   * Revision Information: Not applicable
>
> In the meantime, please contact me for any registration related 
> questions in this regard.
>
> Bestregards,
>
> *MICHAEL CRITCHFIELD *
>
> ETS Product Management
>
> [e-mail] <mailto:[e-mail]>• T 
> +49
> 151 50 666255
>
> **
>
> *KNX Association*
>
> De Kleetlaan 5, B-1831 Brussels-Diegem • Belgium
>
> www.knx.org <http://www.knx.org/>
>
> <https://knxperience.knx.org/>
>
>
> _______________________________________________
> urn mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/urn

This email comes from outside KNX organization.
Do not click links (with or without explicit IP addresses) or open attachments unless it is an email you expected to receive.