[urn] Re: URN namespace registration request - Wi-Fi Allianc e

Hi Dale,

Thanks for the review. While all existing NSSes in Wi-Fi Alliance specifications take the ":" as a hierarchical delimiter, we realize that RFC 8141 states that this character, by default, does not take any specific meaning when appearing in the NSS. Therefore, I am submitting an updated v2 of our URN namespace registration request, with an added statement explicitly disallowing ":" in <resource-type>. 

Thanks,
Peng
--

Namespace Registration for Wi-Fi Alliance 

Namespace Identifier:

  wfa

Version:

  2

Date:

  2026-08-14

Registrant:
  
  Name:

    Wi-Fi Alliance
  
  Address:

    10900-A Stonelake Boulevard, Suite 195, Austin, Texas 78759 U.S.A.
    Phone: +1 512 498 9434 (498-WIFI)
    Fax: +1 512 498 9435

  Designated contact:

    Role: Technical Officer
    Email: [email protected]
  
  Organization Type:

    Standards Development Organization (non-profit corp)
    (requesting fast-track registration procedure)

Purpose:
 
  Wi-Fi Alliance is a global non-profit industry association that owns the Wi-Fi and Wi-Fi CERTIFIED trademarks and oversees the certification of Wi-Fi products. Wi-Fi Alliance work includes development of Wi-Fi technologies, requirements, and certifications that promote a robust global Wi-Fi ecosystem in which interoperability of devices is ensured with certification and data modelling using YANG and TR-181.

  The specifications for some Wi-Fi Alliance certifications require identifiers in a managed namespace so that they are unique and persistent.  To ensure that the uniqueness is absolute, the registration of a specific Uniform Resource Name (URN) [RFC8141] Namespace Identifier (NID) of "wfa" for use by Wi-Fi Alliance is being specified in this submission, in full conformance with the NID registration process specified in §6.4 of [RFC8141].

Syntax:

  URNs assigned by Wi-Fi Alliance will have the following structure based on the organizational structure of the resources specified in the Wi-Fi Alliance specifications:

         urn:wfa:{NSS}

where the syntax of "NSS" follows Section 2 of the URN Syntax requirements [RFC8141]. Wi-Fi Alliance further details:

        urn:wfa:<resource-type>:<resource-path>
        
where:
        <resource-type> uniquely identifies the type of resource being named and shall be defined by Wi-Fi Alliance. The colon character (":") shall not appear in the <resource-type> string.
        <resource-path> uniquely identifies the resource within the specified resource type. It may consist of one or more hierarchical components. The structure of the components within <resource-path> shall be defined by Wi-Fi Alliance for each applicable <resource-type>.

  Examples:
        urn:wfa:mo:hotspot2dot0-perprovidersubscription:1.0
        urn:wfa:mo-ext:hotspot2dot0-devdetail-ext:1.0
        urn:wfa:yang:wfa-dataelements
        urn:wfa:yang:wfa-dataelements:rpc
        urn:wfa:yang:wfa-dataelements:templates

Assignment:
 
  The individual URNs of the wfa namespace shall be solely managed by Wi-Fi Alliance.  The latest information about Wi-Fi Alliance defined standards and specifications, can be found at https://www.wi-fi.org/specifications 

Security and Privacy:
 
  No potential issues related to security and privacy.

Interoperability:
 
  There are no known interoperability issues for the requested urn namespace.

Resolution:

  The namespace is not listed with a resolution discovery system; this is not applicable for this URN registration.

-----Original Message-----
From: Dale R. Worley <[email protected]> 
Sent: Saturday, August 8, 2026 3:43 PM
To: Peng Yan <[email protected]>
Cc: [email protected]
Subject: Re: [urn] Re: URN namespace registration request - Wi-Fi Alliance

[You don't often get email from [email protected]. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

Peng Yan <[email protected]> writes:
>          urn:wfa:{NSS}
>
> where the syntax of "NSS" follows Section 2 of the URN Syntax 
> requirements [RFC8141]. Wi-Fi Alliance further details:
>
>         urn:wfa:<resource-type>:<resource-path>

At the least, you should provide a syntax for resource-type that shows that ":" can't appear in resource-type.  You really want that so that someone receiving a wfa URN can extract the resource-type and resource-path unambiguously even if they don't know the complete list of assigned resource-types.

Dale

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