Registration of URI scheme: udna

*Dear IANA and IETF URI Review Group,*

Pursuant to RFC 7595, I am submitting a request for the registration of a
new URI scheme: *udna* (Universal DID-Native Addressing).

This scheme is a core project of the *W3C Universal DID-Native Addressing
(UDNA) Community Group*. UDNA represents a fundamental architectural
reconstruction of digital addressing, establishing *Decentralized
Identifiers (DIDs)* as the primary addressing primitive. By supplanting
location-based IP addresses and URLs with cryptographic identity, UDNA
enables a "connect to entity" rather than a "connect to server" paradigm.

Below is the formal registration template:
*URI Scheme Registration Template*

   -

   *Scheme name:* udna
   -

   *Status:* Permanent
   -

   *Contact:* Amir Hameed Mir ( amir@sirraya.org )
   -

   *Change controller:* W3C UDNA Community Group (
   https://www.w3.org/groups/cg/did-native-addr/)
   -

   *Scheme syntax:* The udna URI follows the generic syntax defined in RFC
   3986: udna://{authority}/{path}?{query}#{fragment}

   The {authority} component MUST be a valid, percent-encoded Decentralized
   Identifier (DID) as defined by the W3C DID Core Specification. (Example:
   udna://did%3Aweb%3Auser.example/services/communication).
   -

   *Scheme semantics:* The udna scheme identifies resources and
   capabilities relative to a cryptographic identity. Resolution involves:
   1.

      *Identity-First Routing:* Resolving the DID in the authority
      component to a DID Document.
      2.

      *Verifiable Discovery:* Utilizing service endpoints and verification
      methods (supporting Post-Quantum standards like ML-DSA and
ML-KEM) defined
      in the document to interact with the resource.
      3.

      *Capability-Based Access:* The URI path and query parameters identify
      specific capabilities or resources associated with the identity.
      -

   *Encoding considerations:* udna URIs are subject to the encoding rules
   defined in RFC 3986.
   -

   *Interoperability considerations:* Method-agnostic and designed for
   cross-platform compatibility across all W3C-compliant DID methods.
   -

   *Security considerations:* Trust is rooted in cryptographic proofs
   within the DID Document. The architecture is designed to be
   quantum-resistant and supports pairwise pseudonymous identifiers to
   minimize systemic metadata leakage and correlation. Authentication is
   inherent to the addressing architecture rather than a supplementary
   protocol layer.
   -

   *Relevant publications:*  W3C UDNA Group:
   https://www.w3.org/groups/cg/did-native-addr/
   -

      Technical Specification & Architecture: https://github.com/w3c-cg/udna

I am available to provide further technical details or participate in the
review discourse as required.

*Best regards,*

*Amir Hameed Mir*

Chair, W3C UDNA Community Group