SPICE GLUE: GLobal Unique Enterprise Identifiers
draft-zundel-spice-glue-id-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
|
|
|---|---|---|---|
| Author | Brent Zundel | ||
| Last updated | 2024-07-05 | ||
| Replaced by | draft-ietf-spice-glue-id | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-zundel-spice-glue-id-00
Secure Patterns for Internet CrEdentials B. Zundel
Internet-Draft mesur.io
Intended status: Informational 5 July 2024
Expires: 6 January 2025
SPICE GLUE: GLobal Unique Enterprise Identifiers
draft-zundel-spice-glue-id-00
Abstract
This specification defines the glue URI scheme and the rules for
encoding these URIs. It also establishes the registries necessary
for management of this scheme.
About This Document
This note is to be removed before publishing as an RFC.
The latest revision of this draft can be found at https://mesur-
io.github.io/draft-zundel-spice-glue-id/draft-zundel-spice-glue-
id.html. Status information for this document may be found at
https://datatracker.ietf.org/doc/draft-zundel-spice-glue-id/.
Discussion of this document takes place on the Secure Patterns for
Internet CrEdentials Working Group mailing list
(mailto:spice@ietf.org), which is archived at
https://mailarchive.ietf.org/arch/browse/spice/. Subscribe at
https://www.ietf.org/mailman/listinfo/spice/.
Source for this draft and an issue tracker can be found at
https://github.com/mesur-io/draft-zundel-spice-glue-id.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
Zundel Expires 6 January 2025 [Page 1]
Internet-Draft SPICE GLUE: GLobal Unique Enterprise Ide July 2024
This Internet-Draft will expire on 6 January 2025.
Copyright Notice
Copyright (c) 2024 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions and Definitions . . . . . . . . . . . . . . . . . 3
3. Core Concepts . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Text Encoding of glue URIs . . . . . . . . . . . . . . . . . 3
4.1. glue URI Sceme Text Syntax . . . . . . . . . . . . . . . 3
5. DIDs and glue . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
7.1. 'glue' Scheme URI authority registry . . . . . . . . . . 4
7.2. Guidance for Designated Experts . . . . . . . . . . . . . 4
8. Normative References . . . . . . . . . . . . . . . . . . . . 4
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
Enterprise entity identifiers are myriad. With the increasing use of
digitial credentials, there is a need for a common methodology for
expressing these identifiers such that claims about and by such
entities can be made in a consistent and interoperable manner.
This specification defines a URI scheme that standardizes the
expression of existing company entity identifers and establishes a
registry for managing how these existing identifiers relate to this
scheme.
Zundel Expires 6 January 2025 [Page 2]
Internet-Draft SPICE GLUE: GLobal Unique Enterprise Ide July 2024
2. Conventions and Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
For the remainder of this document, the term "glue URI" is used to
refer to a URI that uses the glue scheme.
3. Core Concepts
Every glue URI, whether expressed as a string or encoded in binary
MUST be comprised of the following components:
* The Authority Identifier
* The External Number
The Authority Identifier indicates the external authority responsible
for assigning the External Number and the scheme used to do so.
The External Number is the identifier assigned to the company by the
external authority.
4. Text Encoding of glue URIs
All glue URIs comply with [RFC3986] and are therefore represented by
a scheme identifier and a scheme-specific part. The scheme
identifier is: glue, and the scheme-specific parts are represented as
a sequence of alphanumeric components separated by the '.' character.
A formal definition is provided in the next section, but it can
informally be considered as:
glue:<authority-identifier>.<external-number>
The Authority Identifier MUST be an alphanumeric string from the
"Scheme" field of the glue URI Authority Identifier registry. The
External Number MUST be the identifier assigned to the company by the
external authority under the identified scheme.
4.1. glue URI Sceme Text Syntax
TODO ABNF
Zundel Expires 6 January 2025 [Page 3]
Internet-Draft SPICE GLUE: GLobal Unique Enterprise Ide July 2024
5. DIDs and glue
TODO DIDs and glue
6. Security Considerations
TODO Security
7. IANA Considerations
The following sections detail requests to IANA for the creation of a
new registry.
7.1. 'glue' Scheme URI authority registry
IANA is requested to create a new registry entitled "'glue' Scheme
URI Authority Identifiers". The registration policy for this
registry is Expert Review as defined in [RFC8126].
Each entry in this registry associates one or more Authority
Identifiers with a single organization. Within the registry, the
organization is identified using the "Name" field. Each identified
organization will be associated with one or more number of company
identification schemes, which are listed in the "Scheme" field. A
reference for each scheme is listed in the "Reference" field of the
registry.
The initial values for the registry are:
+==================+========+===========================================+
| Name | Scheme | Reference |
| | | |
+==================+========+===========================================+
| GS1 | gln | https://www.gs1.org/standards/id-keys/gln |
| | | |
+------------------+--------+-------------------------------------------+
| GLEIF | lei | https://www.iso.org/standard/78829.html |
| | | |
+------------------+--------+-------------------------------------------+
| Dun & Bradstreet | duns | https://www.dnb.com/duns.html |
| | | |
+------------------+--------+-------------------------------------------+
7.2. Guidance for Designated Experts
TODO guidance for designated experts
8. Normative References
Zundel Expires 6 January 2025 [Page 4]
Internet-Draft SPICE GLUE: GLobal Unique Enterprise Ide July 2024
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/rfc/rfc2119>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005,
<https://www.rfc-editor.org/rfc/rfc3986>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/rfc/rfc8126>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/rfc/rfc8174>.
Acknowledgments
TODO acknowledge.
Author's Address
Brent Zundel
mesur.io
Email: brent.zundel@gmail.com
Zundel Expires 6 January 2025 [Page 5]