Uniform Resource Names for Device Identifiers
draft-ietf-core-dev-urn-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04

Network Working Group                                           J. Arkko
Internet-Draft                                                  Ericsson
Intended status: Informational                               C. Jennings
Expires: June 15, 2020                                             Cisco
                                                               Z. Shelby
                                                                     ARM
                                                       December 13, 2019

             Uniform Resource Names for Device Identifiers
                       draft-ietf-core-dev-urn-04

Abstract

   This memo 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 equipment inventories.  A URN-based
   representation can be easily passed along in any application that
   needs the information.

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 http://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."

   This Internet-Draft will expire on June 15, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (http://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

Arkko, et al.             Expires June 15, 2020                 [Page 1]
Internet-Draft                   DEV URN                   December 2019

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements language . . . . . . . . . . . . . . . . . . . .   3
   3.  DEV URN Definition  . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Purpose . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.3.  Assignment  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.4.  Security and Privacy  . . . . . . . . . . . . . . . . . .   6
     3.5.  Interoperability  . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Resolution  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.7.  Documentation . . . . . . . . . . . . . . . . . . . . . .   6
     3.8.  Additional Information  . . . . . . . . . . . . . . . . .   7
     3.9.  Revision Information  . . . . . . . . . . . . . . . . . .   7
   4.  DEV URN Subtypes  . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  MAC Addresses . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  1-Wire Device Identifiers . . . . . . . . . . . . . . . .   7
     4.3.  Organization-Defined Identifiers  . . . . . . . . . . . .   8
     4.4.  Organization Serial Numbers . . . . . . . . . . . . . . .   8
     4.5.  Organization Product and Serial Numbers . . . . . . . . .   8
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Appendix A.  Changes from Previous Version  . . . . . . . . . . .  14
   Appendix B.  Acknowledgments  . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   This memo describes a new Uniform Resource Name (URN) [RFC8141]
   [RFC3406] 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 equipment inventories
   [RFC7252], [RFC8428].  A URN-based representation can be easily
   passed along in any application that needs the information, as it
   fits in protocols mechanisms that are designed to carry URNs