RFC 9039: Uniform Resource Names for Device Identifiers
In plain English — editorial summary, not part of the RFC
This document describes a new Uniform Resource Name (URN) namespace for hardware device identifiers. A general representation of device identity can be useful in many applications, such as in sensor data streams and storage or in equipment inventories. A URN-based representation can be passed along in applications that need the information.
Document record
- Document ID
- RFC9039
- Published
- June 2021
- Authors
- J. Arkko; C. Jennings; Z. Shelby
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8948Structured Local Address Plan (SLAP) Quadrant Selection Option for DHCPv6Current
December 2020
- RFC 9278JWK Thumbprint URICurrent
August 2022
- RFC 8469Recommendation to Use the Ethernet Control WordCurrent
November 2018
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
- RFC 8057Uniform Resource Name (URN) Namespaces for Broadband ForumCurrent
January 2017
- RFC 7302Entertainment Identifier Registry (EIDR) URN Namespace DefinitionObsoleted
July 2014
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 6963A Uniform Resource Name (URN) Namespace for ExamplesCurrent
May 2013
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?