[urn] Re: Request for globalplatform URN

--===============6639977269457478116==

> On 7/13/26 9:45 AM, Jeremy O'Donoghue wrote:
>> I would like to register a URN namespace for use in GlobalPlatform 
>> specifications. GlobalPlatform is a non-profit industry body publishing 
>> specifications for security components. The public website is at 
>> https://globalplatform.org <https://globalplatform.org>
>> 
>> Below information follows the RFC8141 template:

Does this registration has any relationship to the effort discussed in
Kate Gray's e-mail
https://mailarchive.ietf.org/arch/msg/urn/RiNCn4BYeY6xoilYpiGdDBUd0QQ
et seq.?

>> Namespace Identifier:  Requested of IANA (formal): globalplatform 
>> Version:  1 Date:  2026-08-30 Registrant:
>> 
>>   *
>>     GlobalPlatform Inc.
>>     544 Hillside Rd., Redwood City, CA 94062-3345
>>     United States of America
>>   *
>>     Contact: [email protected]
>> 
>> Purpose:
>> 
>>   *
>>     GlobalPlatform uses IETF specifications as a basis to provide
>>     interoperability with other ecosystems. It typically defines
>>     profiles of IETF specifications which provide specific support for
>>     GlobalPlatform secure components. IETF specifications often prefer
>>     URN namespaces for such profiles. Use of an allocated URN is
>>     therefore desirable for interoperability.
>>   *
>>     The specific initial need is to define RFC9711 compliant profiles
>>     for GlobalPlatform Trusted Execution Environment and Secure Element
>>     components. 
>> 
>> Syntax:
>> URNs compliant with this specification SHALL use only ASCII upper and 
>> lower case characters, the digits 0-9 and the '/', '-', ':' and '.' 
>> characters. Upper-case ASCII characters SHALL be transformed into their 
>> lower case equivalents before processing.
>> Assignment:
>> 
>>   *
>>     Closed assignment in GlobalPlatform specifications. 
>> 
>> Security and Privacy:
>> 
>>   *
>>     URNs in this namespace SHALL NOT be used as security capabilities
>>   *
>>     URNs MAY be distributed to untrusted entities
>>   *
>>     URNs in this namespace SHOULD NOT be used to convey information that
>>     can uniquely identify a specific instance of a GlobalPlatform Secure
>>     Component
>>   *
>>     Incorrect or ambiguous resolution of URN-equivalence SHALL 

This sentence seems to be incomplete.

>> Interoperability:
>> 
>>   *
>>     None known 
>> 
>> Resolution:
>> 
>>   *
>>     Not anticipated
>> 
>> Documentation:
>> 
>>   *
>>     None currently available as we have no URN namespace identifier as
>>     yet. A specification will be published listing all assigned values
>>     in this namespace.
>> 
>> Additional Information:
>> 
>>   *
>>     N/A
>> 
>> Revision Information:
>> 
>>   *
>>     N/A
>> 
>> 
>> As the requester, I am editor of the GlobalPlatform Entity Attestation 
>> Protocol Specification and was one of the editors of RFC9711. The 
>> GlobalPlatform Entity Attestation Protocol specification plans to 
>> include RFC9711-compliant EAT profiles which can be interoperably 
>> identified by verifiers through the eat_profile claim.
>> 
>> Assuming this allocation is granted, the profile identifiers will be for 
>> the form: "urn:globalplatform:profile:<profile_name>:<profile_version>" 
>> where <profile_name> is replaced with the profile name and 
>> <profile_version> is replaces with the version number of the profile.

It would be useful if this verbal description was turned into ABNF.  But
as written, it seems to be very restrictive.  Are there long-term plans
that would cause other categories of URNs in this namespace to be
issued?  That would require updating the registration.

Dale


--===============6639977269457478116==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp
bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1
cm4tbGVhdmVAaWV0Zi5vcmcK

--===============6639977269457478116==--