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

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

• Versions
• 01
• 02
• 03
• 04
• 05

Network Working Group                                           J. Arkko
Internet-Draft                                                  Ericsson
Intended status: Informational                               C. Jennings
Expires: January 4, 2018                                           Cisco
                                                               Z. Shelby
                                                               Sensinode
                                                            July 3, 2017

             Uniform Resource Names for Device Identifiers
                      draft-arkko-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 January 4, 2018.

Copyright Notice

   Copyright (c) 2017 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 January 4, 2018                [Page 1]
Internet-Draft                   DEV URN                       July 2017

   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  . . . . . . . . . . . . . . . . . . . . .   3
   4.  DEV URN Subtypes  . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  MAC Addresses . . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  1-Wire Device Identifiers . . . . . . . . . . . . . . . .   5
   5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Changes from Previous Version  . . . . . . . . . . .   9
   Appendix B.  Acknowledgments  . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This memo describes a new Uniform Resource Name (URN) [RFC2141]
   [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], [I-D.ietf-core-senml], [I-D.arkko-core-sleepy-sensors]
   [I-D.arkko-core-security-arch].  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
   [RFC2616], [RFC3261], [RFC7252].  Finally, URNs can also be easily
   carried and stored in formats such as XML [W3C.REC-xml-19980210] or
   JSON [I-D.ietf-core-senml] [RFC4627].  Using URNs in these formats is
   often preferable as they are universally recognized, self-describing,
   and therefore avoid the need for agreeing to interpret an octet
   string as a specific form of a MAC address, for instance.

   This memo defines identity URN types for situations where no such
   convenient type already exist.  For instance, [RFC6920] defines
   cryptographic identifiers, [RFC7254] defines International Mobile
   station Equipment Identity (IMEI) identifiers for use with 3GPP
   cellular systems, and [I-D.atarius-dispatch-meid-urn] defines Mobile