[urn] Re: Informal URN Namespace Registration Request for Tr ivore Corp.
"Kari Mattsson (Trivore)" <[email protected]> Sun, 11 Jan 2026 16:39:08 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <PAWPR06MB9010D33E968D260811B51A468880A@PAWPR06MB9010.eurprd06.prod.outlook.com> |
Hello Date (and others)!
https://id.trivore.com/apidoc/oidc was geo-blocked, not any more. That IdP instance is our own, and mostly used within Finland only. The service contains PII like all IdPs do. Thus geo-blocking.
Initially the intention was to have documentation always online in the product, for OIDC IdP, the path would be /apidoc/oidc. It is however a good idea to have more permanent single address for documentation of the URN. I amended the application to contain that address <https://doc.trivoreid.com/>. The actual page is not yet there. When a more exact permanent address is created, the documentation section of the application shall be amended.
On exact URNs for scopes and claims, yes your correction is the right one, and it is important on the web page to document this clearly:
urn:trivore:id:scope:<scope-name>
urn:trivore:id:claim:<claim-name>
As the need for other kind of information arises, documentation shall be amended again, and the web page shall be updated.
Case-sensitivity catch was a good one. It was not meant to be like that, as it is way too common place to have human typo errors. This I reworded it for case-insensitivity. And I hope I got it right.
Another good catch was number of sections with ":" as separator. As future needs are currently unknown, it is not wise to limit to only 3 colons. Hierarchy requires more in real life.
Thus, I also amended the Syntax section. I hope I got that right, too.
I defined after consultation max length to be 512 characters for the URN just to be on the safe side on complex use cases.
Attached are (text and PDF) new revisions.
Thanks all for your patience with us 🙂
My best, Kari
________________________________
From: Dale R. Worley <[email protected]>
Sent: 08 January 2026 22:55
To: Kari Mattsson (Trivore) <[email protected]>
Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; URN-admin <[email protected]>
Subject: Re: [urn] Re: Informal URN Namespace Registration Request for Trivore Corp.
"Kari Mattsson (Trivore)" <[email protected]> writes:
> Truth is, we'd like to have a formal namespace "trivore" registered.
That seems like a good choice to me.
> OIDC has concept of Claims and Scopes. And we have so many of those
> built in, and users may also create their own.
> Current list is not very beautiful: https://id.trivore.com/apidoc/oidc
That URL gave me 403.
But if the intention is for the list of trivore URNs to be public at
that URL, why not mention that in the Documentation section of the
registration?
Indeed, why not put the discussion you provided into the registration?
> We are changing those to be URN formatted, thus this application.
> urn:trivore:id:scope:
> urn:trivore:id:claim:
> etc. — I hope you get the idea. Those will be public and publicly documented.
I assume you mean
urn:trivore:id:scope:<scope-name>
urn:trivore:id:claim:<claim-name>
But those don't match the declared syntax; the syntax requires exactly 3
colons in the URN.
> Syntax:
> URNs in this namespace follow the syntax:
> urn:trivore:<NSS>
>
> The Namespace Specific String (NSS) is defined as:
> <NSS> = <resource-type> ":" <resource-id>
> Where <resource-type> and <resource-id> consist of ASCII letters, digits, and the characters “-”, “_”, and “.”.
>
> Maximum length for resource-id is 256 characters.
However, you do not state a maximum length for resource-type, so URNs
have unlimited length. If you expect the URNs to always be considerably
less than 256 characters, it would probably be better to specify that
the maximum length for trivore URNs is 256 characters.
> Lexical equivalence:
> Lexical equivalence follows the rules defined in RFC 8141.
Which means the default applies; the URNs are case-sensitive.
Dale
_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]
IANA URN registration for trivore 2026-01-03.pdf
(application/pdf, 41.7 KB) - not displayed
IANA URN registration for trivore 2026-01-03.txt
(text/plain, 3.9 KB)
Dear IANA URN Namespace Registration Team,
I would like to request the registration of a new Formal URN Namespace Identifier (NID) in accordance with RFC 8141.
---
URN Namespace Registration for Trivore Corp.
Namespace Identifier (NID):
trivore
Registration information:
Version: 1
Revision information: 1
Date: 2026-01-02
Declared registrant of the namespace:
Organization: Trivore Corp.
Contact Role: URN Administrator, urn-admin&trivore.com
Contact Person: Kari Mattsson (URN Administrator)
Address: Helsinginkatu 15, 20500 Turku, Finland
Website: https://www.trivore.com/
Purpose:
This namespace is intended to provide persistent, globally unique, location-independent identifiers for resources defined and managed by the declared registrant. The identifiers are not intended to resolve to network locations.
Main usage is standardising technical definitions of Trivore products, initially Trivore ID OIDC Scopes and Claims, and similar technical definitions for Trivore's IAM product. Long-term purpose is to have coherent definitions.
Syntax:
URNs in this namespace follow the syntax:
urn:trivore:<NSS>
The Namespace Specific String (NSS) is defined as a hierarchical sequence of segments:
<NSS> = <segment> 1*(":" <segment>)
Where:
<segment> consists of ASCII letters, digits, and the characters “-”, “_”, and “.”, and
the NSS must contain at least one colon (implying at least two segments).
Maximum length for the URN is 512 characters.
Namespace semantics:
Each URN identifies exactly one logical resource defined by the registrant. The identifiers are opaque and do not embed personal data.
Assignment:
URNs are assigned exclusively by the declared registrant. Each identifier is guaranteed to be unique within the namespace. Reassignment is not permitted.
Persistence:
URNs in this namespace are intended to be persistent. Once assigned, an identifier will not be reused.
Resolution:
No resolution mechanism is defined for this namespace.
Lexical equivalence:
Lexical equivalence follows the rules defined in RFC 8141. In addition, for this namespace the Namespace Specific String (NSS) is case-insensitive with respect to ASCII letters; two URNs in this namespace are lexically equivalent if their NSS components are equal under case-insensitive comparison after applying the RFC 8141 rules.
Security and privacy considerations:
The namespace does not include secrets, authentication material, or personally identifiable information (PII). Identifiers must not be used as access control mechanisms. The namespace does not encode personal data, and correlation risks are minimized by avoiding meaningful identifiers.
Interoperability:
No external documentation is currently provided. This registration document is the primary documentation for the namespace for the moment. Product (Trivore ID) documentation is located at <https://doc.trivoreid.com/>, and it will contain documentation for this URN namespace.
Documentation:
No external documentation is currently provided. This registration document is the primary documentation for the namespace for the moment. Product (Trivore ID) documentation is located at <https://doc.trivoreid.com/>, and it will contain documentation for its URN subnamespace urn:trivore:id:<NSS>.
Related IAM product documentation shall be located at <https://doc.trivoreiam.com/>, and it will contain documentation for its URN namespace urn:trivore:iam:<NSS>. Other sub namespaces shall contain similar documentation once they are defined and created, and this application section shall be amended accordingly.
IANA considerations:
This document requests the registration of the Formal URN Namespace Identifier “trivore”.
---
Please let me know if any additional information or clarification is required.
Kind regards,
Kari Mattsson
URN Administrator
Trivore Corp.
[email protected]