[urn] Re: Request for globalplatform URN
Jeremy O'Donoghue <[email protected]> Tue, 28 Jul 2026 11:34:48 +0000
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <LV5PR02MB10852B28E17723BB9618368FDF2CB2@LV5PR02MB10852.namprd02.prod.outlook.com> |
--===============8814919187876454668==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_LV5PR02MB10852B28E17723BB9618368FDF2CB2LV5PR02MB10852na_"
--_000_LV5PR02MB10852B28E17723BB9618368FDF2CB2LV5PR02MB10852na_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Peter,
1.
The proposed NSS structure is shown below in ABNF. Definitions from RFC3986=
are used. The below is not optimized but hopefully shows our intent.
NSS =3D go-document / gp-code
gp-document =3D "doc" ":" gp-doc-id "definition-name" [ "#" doc-version ]
gp-doc-id =3D 1*( ALPHA / DIGIT / "_" )
definition-name =3D 1*( ALPHA / DIGIT / "_" / "-" )
doc-version =3D 1*DIGIT "." 1*DIGIT "." 1*DIGIT [ "." 1*DIGIT ]
gp-code =3D "code" ":" gp-project ":" authority path-abempty ":" definition=
-name [ "#" version-tag ]
gp-project =3D unreserved
version-tag=3D 1*pchar
There are two proposed sub-spaces:
*
gp-document is used for identifiers defined in GlobalPlatform documents. In=
this scheme:
*
Each document that requires a URN is responsible for managing its uniquenes=
s within the document.
*
GlobalPlatform has a document identifier scheme for all issued documents, s=
o uniqueness is managed across all GlobalPlatform document.
*
For a given specification, the document identifier stays constant when the =
document is revised - instead we change the document version. Where no expl=
icit version number is given in the URN, the reference is to the latest ver=
sion of the document. Thus uniqueness across document versions can be manag=
ed if required.
*
gp-code is used for identifiers defined in Open-Source projects. In this sc=
heme:
*
gp-project identifies the project within GlobalPlatform.
*
The combination of authority and path-abempty (both with semantics defined =
in RFC3986) locates the file in which the definition is found.
*
definition-name is managed as unique to the file. In practice we mandate th=
at each Open Source project will manage its URN namespace so that identifie=
rs are unique across the project.
*
version-tag can optionally be used where a definition is tied to an explici=
t commit, or versioning system tag. If it is not provided the reference res=
olves to the default code branch, most recent commit of the file containing=
the definition.
While it is impossible to bound the length of the above namespaces, the fol=
lowing examples are indicative for the two proposed schemes (assuming assig=
nment of the "globalplatform" NID). Note that the first style is expected t=
o be by far the more widely used:
*
"urn:globalplatform:doc:gpp_spe_001:tee_profile#1.0.0"
*
"urn:globalplatform:code:tps-apis://githib.com/tps-api-reference-implementa=
tions/blob/main/rot13_service/src/lib.rs:GPP_ROT13_SERVICE_NAME"
2. It is too early to tell whether we would need to define a second version=
of the registration. I have planned the above to meet foreseeable needs wi=
thin the organization rather than what is needed for a specific document, s=
o I am hopeful that our needs are covered for some time.
I plan to create a small document outlining the management of URNs within G=
lobalPlatform as guidance for the organization, which we will publish, and =
which will be referenced in our document management guide (this is not a pu=
blic document but is available to all members and provides guidance to edit=
ors and WG chairs).
3. GlobalPlatform specifications, including the intended specification, are=
available at no cost from the GlobalPlatform website at https://globalplat=
form.org.
GlobalPlatform has managed other globally significant namespaces in other c=
ontexts (e.g. OID namespace, ISO 7816-5 RID) for many years. We will adopt =
similar processes to ensure that the namespace is managed over time. There =
is a formal deprecation process for documents no-longer maintained, and we =
will add URN management to this process.
Please let me know if you have any other questions.
Best regards
Jeremy
________________________________
From: Peter Saint-Andre <[email protected]>
Sent: Monday, July 27, 2026 20:54
To: Jeremy O'Donoghue <[email protected]>; [email protected] <[email protected]=
rg>
Cc: [email protected] <[email protected]>
Subject: Re: [urn] Request for globalplatform URN
WARNING: This email originated from outside of Qualcomm. Please be wary of =
any links or attachments, and do not enable macros.
Hi Jeremy, thanks for this submission. Although it appears to be
straightforward, I have a few small questions.
1. Would it be possible to provide more detailed information regarding
the syntax (e.g., allowable length and internal structure of the NSS)?
ABNF preferred if that's not too much trouble.
2. It might be too early to tell, but do you plan to submit a revised
version 2 of the registration once GlobalPlatform has registered the
namespace and proceeds with its standardization process?
3. Where will the intended specification be published? To be clear,
we're less concerned about a complete list of all assigned values and
more concerned about understanding the assignment process, avoidance of
duplicates or reassignment, and such (i.e., active management of the
namespace).
Peter
On 7/13/26 9:45 AM, Jeremy O'Donoghue wrote:
> Hi URN experts.
>
> 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:
>
> 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
>
> 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.
>
> Best regards
>
> Jeremy O'Donoghue
> Director, GSoC Security Architecture
> [email protected]
>
> _______________________________________________
> urn mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
--_000_LV5PR02MB10852B28E17723BB9618368FDF2CB2LV5PR02MB10852na_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo=
ttom:0;} </style>
</head>
<body dir=3D"ltr">
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Hi Peter,</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<ol start=3D"1" data-editing-info=3D"{"applyListStyleFromLevel":f=
alse,"orderedStyleType":1}" style=3D"margin-top: 0px; margin-bott=
om: 0px; list-style-type: decimal;">
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin=
-top: 0px; margin-bottom: 0px;">
<div class=3D"elementToProof" role=3D"presentation">The proposed NSS struct=
ure is shown below in ABNF. Definitions from RFC3986 are used. The below is=
not optimized but hopefully shows our intent.</div>
</li></ol>
<div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, =
Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
NSS =3D go-document / gp-code</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
gp-document =3D "doc" ":" gp-doc-id "definition-na=
me" [ "#" doc-version ]</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
gp-doc-id =3D 1*( ALPHA / DIGIT / "_" )</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
definition-name =3D 1*( ALPHA / DIGIT / "_" / "-" )</di=
v>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
doc-version =3D 1*DIGIT "." 1*DIGIT "." 1*DIGIT [ "=
;." 1*DIGIT ]</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
gp-code =3D "code" ":" gp-project ":" authori=
ty path-abempty ":" definition-name [ "#" version-tag ]=
</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
gp-project =3D unreserved</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Consolas, Courier, monospace; font-size: 10pt; color: rgb(0, =
0, 0);">
version-tag=3D 1*pchar</div>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
There are two proposed sub-spaces:</div>
<ul data-editing-info=3D"{"applyListStyleFromLevel":true}" style=
=3D"margin-top: 0px; margin-bottom: 0px; list-style-type: disc;">
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin=
-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
<span style=3D"font-family: Consolas, Courier, monospace;">gp-document</spa=
n> is used for identifiers defined in GlobalPlatform documents. In this sch=
eme:</div>
</li><ul data-editing-info=3D"{"applyListStyleFromLevel":true}" s=
tyle=3D"margin-top: 0px; margin-bottom: 0px; list-style-type: circle;">
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin=
-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
Each document that requires a URN is responsible for managing its uniquenes=
s within the document.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m=
argin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
GlobalPlatform has a document identifier scheme for all issued documents, s=
o uniqueness is managed across all GlobalPlatform document.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m=
argin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
For a given specification, the document identifier stays constant when the =
document is revised - instead we change the document version. Where no expl=
icit version number is given in the URN, the reference is to the latest ver=
sion of the document. Thus uniqueness
across document versions can be managed if required.</div>
</li></ul>
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin=
-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
<span style=3D"font-family: Consolas, Courier, monospace;">gp-code</span> i=
s used for identifiers defined in Open-Source projects. In this scheme:</di=
v>
</li><ul data-editing-info=3D"{"applyListStyleFromLevel":true}" s=
tyle=3D"margin-top: 0px; margin-bottom: 0px; list-style-type: circle;">
<li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, C=
alibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); margin=
-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
<span style=3D"font-family: Consolas, Courier, monospace;">gp-project</span=
> identifies the project within GlobalPlatform.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m=
argin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
The combination of <span style=3D"font-family: Consolas, Courier, monospace=
;">authority</span> and
<span style=3D"font-family: Consolas, Courier, monospace;">path-abempty </s=
pan>(both with semantics defined in RFC3986) locates the file in which the =
definition is found.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m=
argin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
<span style=3D"font-family: Consolas, Courier, monospace;">definition-name<=
/span> is managed as unique to the file. In practice we mandate that each O=
pen Source project will manage its URN namespace so that identifiers are un=
ique across the project.</div>
</li><li style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontServi=
ce, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); m=
argin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em;">
<span style=3D"font-family: Consolas, Courier, monospace;">version-tag</spa=
n> can optionally be used where a definition is tied to an explicit commit,=
or versioning system tag. If it is not provided the reference resolves to =
the default code branch, most recent
commit of the file containing the definition.</div>
</li></ul>
</ul>
<div class=3D"elementToProof" style=3D"margin-top: 1em; margin-bottom: 1em;=
font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helv=
etica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
While it is impossible to bound the length of the above namespaces, the fol=
lowing examples are indicative for the two proposed schemes (assuming assig=
nment of the "globalplatform" NID). Note that the first style is =
expected to be by far the more widely used:</div>
<ul data-editing-info=3D"{"applyListStyleFromLevel":true}" style=
=3D"margin-top: 0px; margin-bottom: 0px; list-style-type: disc;">
<li style=3D"font-family: Consolas, Courier, monospace; font-size: 12pt; co=
lor: rgb(0, 0, 0); margin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFont=
Service, Calibri, Helvetica, sans-serif;">
<span style=3D"font-family: Consolas, Courier, monospace;">"urn:global=
platform:doc:gpp_spe_001:tee_profile#1.0.0"</span></div>
</li><li style=3D"font-family: Consolas, Courier, monospace; font-size: 12p=
t; color: rgb(0, 0, 0); margin-top: 1em; margin-bottom: 1em;">
<div class=3D"elementToProof" role=3D"presentation" style=3D"margin-top: 1e=
m; margin-bottom: 1em; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFont=
Service, Calibri, Helvetica, sans-serif;">
<span style=3D"font-family: Consolas, Courier, monospace;">"urn:global=
platform:code:tps-apis://githib.com/tps-api-reference-implementations/blob/=
main/rot13_service/src/lib.rs:GPP_ROT13_SERVICE_NAME"</span></div>
</li></ul>
<div style=3D"font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, =
Calibri, Helvetica, sans-serif; font-size: 12pt;">
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<span style=3D"font-family: Consolas, Courier, monospace;"></span>2. It is =
too early to tell whether we would need to define a second version of the r=
egistration. I have planned the above to meet foreseeable needs within the =
organization rather than what is needed
for a specific document, so I am hopeful that our needs are covered for so=
me time.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
I plan to create a small document outlining the management of URNs within G=
lobalPlatform as guidance for the organization, which we will publish, and =
which will be referenced in our document management guide (this is not a pu=
blic document but is available to
all members and provides guidance to editors and WG chairs).</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
3. GlobalPlatform specifications, including the intended specification, are=
available at no cost from the GlobalPlatform website at https://globalplat=
form.org. </div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
GlobalPlatform has managed other globally significant namespaces in other c=
ontexts (e.g. OID namespace, ISO 7816-5 RID) for many years. We will adopt =
similar processes to ensure that the namespace is managed over time. There =
is a formal deprecation process
for documents no-longer maintained, and we will add URN management to this=
process.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Please let me know if you have any other questions.</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Best regards</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
Jeremy</div>
<div class=3D"elementToProof" style=3D"font-family: Aptos, Aptos_EmbeddedFo=
nt, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; c=
olor: rgb(0, 0, 0);">
<br>
</div>
<hr style=3D"display: inline-block; width: 98%;">
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<b>From:</b> Peter Saint-Andre <[email protected]><br>
<b>Sent:</b> Monday, July 27, 2026 20:54<br>
<b>To:</b> Jeremy O'Donoghue <[email protected]>; [email protected]=
g <[email protected]><br>
<b>Cc:</b> [email protected] <gil.bernabeu@globalplatform.=
org><br>
<b>Subject:</b> Re: [urn] Request for globalplatform URN </div>
<div style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-size=
: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style=3D"font-size: 11pt;">WARNING: This email originated from outside=
of Qualcomm. Please be wary of any links or attachments, and do not enable=
macros.<br>
<br>
Hi Jeremy, thanks for this submission. Although it appears to be<br>
straightforward, I have a few small questions.<br>
<br>
1. Would it be possible to provide more detailed information regarding<br>
the syntax (e.g., allowable length and internal structure of the NSS)?<br>
ABNF preferred if that's not too much trouble.<br>
<br>
2. It might be too early to tell, but do you plan to submit a revised<br>
version 2 of the registration once GlobalPlatform has registered the<br>
namespace and proceeds with its standardization process?<br>
<br>
3. Where will the intended specification be published? To be clear,<br>
we're less concerned about a complete list of all assigned values and<br>
more concerned about understanding the assignment process, avoidance of<br>
duplicates or reassignment, and such (i.e., active management of the<br>
namespace).<br>
<br>
Peter<br>
<br>
On 7/13/26 9:45 AM, Jeremy O'Donoghue wrote:<br>
> Hi URN experts.<br>
><br>
> I would like to register a URN namespace for use in GlobalPlatform<br>
> specifications. GlobalPlatform is a non-profit industry body publishin=
g<br>
> specifications for security components. The public website is at<br>
> <a href=3D"https://globalplatform.org" id=3D"OWAdcfd506e-c451-2b69-72b=
0-2e8811eb1470" class=3D"OWAAutoLink" data-auth=3D"NotApplicable">
https://globalplatform.org</a> <<a href=3D"https://globalplatform.org" i=
d=3D"OWA853587a8-5458-747b-40b5-45bc6570d9eb" class=3D"OWAAutoLink" data-au=
th=3D"NotApplicable">https://globalplatform.org</a>><br>
><br>
> Below information follows the RFC8141 template:<br>
><br>
> Namespace Identifier: Requested of IANA (formal): globalplatform=
<br>
> Version: 1 Date: 2026-08-30 Registrant:<br>
><br>
> *<br>
> GlobalPlatform Inc.<br>
> 544 Hillside Rd., Redwood City, CA 94062-3345<=
br>
> United States of America<br>
> *<br>
> Contact: [email protected]<br>
><br>
> Purpose:<br>
><br>
> *<br>
> GlobalPlatform uses IETF specifications as a b=
asis to provide<br>
> interoperability with other ecosystems. It typ=
ically defines<br>
> profiles of IETF specifications which provide =
specific support for<br>
> GlobalPlatform secure components. IETF specifi=
cations often prefer<br>
> URN namespaces for such profiles. Use of an al=
located URN is<br>
> therefore desirable for interoperability.<br>
> *<br>
> The specific initial need is to define RFC9711=
compliant profiles<br>
> for GlobalPlatform Trusted Execution Environme=
nt and Secure Element<br>
> components.<br>
><br>
> Syntax:<br>
> URNs compliant with this specification SHALL use only ASCII upper and<=
br>
> lower case characters, the digits 0-9 and the '/', '-', ':' and '.'<br=
>
> characters. Upper-case ASCII characters SHALL be transformed into thei=
r<br>
> lower case equivalents before processing.<br>
> Assignment:<br>
><br>
> *<br>
> Closed assignment in GlobalPlatform specificat=
ions.<br>
><br>
> Security and Privacy:<br>
><br>
> *<br>
> URNs in this namespace SHALL NOT be used as se=
curity capabilities<br>
> *<br>
> URNs MAY be distributed to untrusted entities<=
br>
> *<br>
> URNs in this namespace SHOULD NOT be used to c=
onvey information that<br>
> can uniquely identify a specific instance of a=
GlobalPlatform Secure<br>
> Component<br>
> *<br>
> Incorrect or ambiguous resolution of URN-equiv=
alence SHALL<br>
><br>
> Interoperability:<br>
><br>
> *<br>
> None known<br>
><br>
> Resolution:<br>
><br>
> *<br>
> Not anticipated<br>
><br>
> Documentation:<br>
><br>
> *<br>
> None currently available as we have no URN nam=
espace identifier as<br>
> yet. A specification will be published listing=
all assigned values<br>
> in this namespace.<br>
><br>
> Additional Information:<br>
><br>
> *<br>
> N/A<br>
><br>
> Revision Information:<br>
><br>
> *<br>
> N/A<br>
><br>
><br>
> As the requester, I am editor of the GlobalPlatform Entity Attestation=
<br>
> Protocol Specification and was one of the editors of RFC9711. The<br>
> GlobalPlatform Entity Attestation Protocol specification plans to<br>
> include RFC9711-compliant EAT profiles which can be interoperably<br>
> identified by verifiers through the eat_profile claim.<br>
><br>
> Assuming this allocation is granted, the profile identifiers will be f=
or<br>
> the form: "urn:globalplatform:profile:<profile_name>:<pr=
ofile_version>"<br>
> where <profile_name> is replaced with the profile name and<br>
> <profile_version> is replaces with the version number of the pro=
file.<br>
><br>
> Best regards<br>
><br>
> Jeremy O'Donoghue<br>
> Director, GSoC Security Architecture<br>
> [email protected]<br>
><br>
> _______________________________________________<br>
> urn mailing list -- [email protected]<br>
> To unsubscribe send an email to [email protected]<br>
<br>
</div>
</body>
</html>
--_000_LV5PR02MB10852B28E17723BB9618368FDF2CB2LV5PR02MB10852na_--
--===============8814919187876454668==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdXJuIG1haWxp
bmcgbGlzdCAtLSB1cm5AaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFpbCB0byB1
cm4tbGVhdmVAaWV0Zi5vcmcK
--===============8814919187876454668==--