[urn] Re: Registration request for 'urn:stalwart' name space

Mauro De Gennaro <[email protected]> writes:
> I would like to request the registration of the ’stalwart’ URN
> namespace. It will be used by Stalwart Mail & Collaboration Server for
> both custom JMAP extensions as well as for WebDAV tokens. 

I am in favor of the registration in general, but I think the template
needs some clarifications.

> The syntax of the NSS portion of URNs in the 'stalwart' namespace
> conforms to the general URN syntax requirements (RFC 8141). The
> specific structure is:
>
> urn:stalwart:{resource-type}:{specific-identifier}
>
> where:
> - {resource-type} indicates the category of resource being identified (e.g., "jmap", "davlock", "davsync")
> - {specific-identifier} is the unique identifier for the resource within that type
>
> Examples:
> - urn:stalwart:jmap:mailfilter
> - urn:stalwart:davlock:a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6
> - urn:stalwart:davsync:a1b2c3d4e5f6a7b8

As written, the only constraint on "resource-type" is that it conforms
to RFC 8141.  Specifically, there's no statement that it may not contain
':'.  And yet, that constraint is necessary for unambiguously extracting
the "resource-type" from the URN.  And the template says "Additional
characters allowed by the URN syntax may be used in the
specific-identifier portion...", as if some constraint was otherwise in
force, even though no constraint is stated.  So some syntax needs to be
specified for "resource-type" which at least excludes ":".

> URNs in the 'stalwart' namespace are assigned by Stalwart Labs
> LLC. Assignment of URNs within specific resource types follows these
> guidelines:
>
> - For JMAP extensions: Assigned based on the functionality provided by
> the extension, following a naming convention similar to standard JMAP
> capabilities.
> - For WebDAV lock tokens (davlock): Generated as 128-bit numbers
> encoded in hexadecimal format.
> - For WebDAV synchronization tokens (davsync): Generated as 64-bit
> numbers encoded in hexadecimal format.

> Stalwart Labs LLC maintains the registry of all assigned URNs within
> this namespace to ensure uniqueness.

Given that "urn:stalwart:davlock:" URNs contain 32 hex digits, it
strikes me as unlikely that "Stalwart Labs LLC maintains the registry"
of these.  And likely they're generated in large numbers by a large
number of distributed processes, which makes maintaining a registry of
them impossible.

I think you want to say something like:

    Stalwart Labs LLC maintains the registry of all valid
    resource-types, and for each resource type, the syntax of
    specific-identifiers and the processes by which they may be
    assigned.

Dale

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