A Uniform Resource Name Namespace for the Device Identity and the Mobile Equipment Identity (MEID)
draft-atarius-dispatch-meid-urn-17

Document Type Active Internet-Draft (individual in art area)
Last updated 2018-04-12
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Andrew Allen
Shepherd write-up Show (last changed 2015-11-02)
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA - Not OK
IANA action state None
Network Working Group                                         R. Atarius
Internet-Draft                                            April 12, 2018
Intended status: Informational
Expires: October 14, 2018

A Uniform Resource Name Namespace for the Device Identity and the Mobile
                       Equipment Identity (MEID)
                   draft-atarius-dispatch-meid-urn-17

Abstract

   This document defines a Uniform Resource Name (URN) namespace for the
   Third Generation Partnership Project 2 (3GPP2) and a Namespace
   Specific String (NSS) for the Mobile Equipment Identity (MEID).  The
   structure of an MEID is 15 hexadecimal digits long and is defined in
   the Third Generation Partnership Project 2 (3GPP2) (see [S.R0048-A])
   to uniquely identify each individual mobile equipment (e.g., a
   handset or mobile phone).  The 3GPP2 has a requirement to be able to
   use an MEID as a URN.  This document fulfills that requirement.

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."

   This Internet-Draft will expire on October 14, 2018.

Copyright Notice

   Copyright (c) 2018 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

Atarius                 Expires October 14, 2018                [Page 1]
Internet-Draft               MEID Based URN                   April 2018

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Namespace Registration Template . . . . . . . . . . . . . . .   3
   4.  Specification . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  MEID Parameters . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  MEID Format . . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.2.  Manufacturer Code . . . . . . . . . . . . . . . . . .   6
       4.2.3.  Serial Number . . . . . . . . . . . . . . . . . . . .   7
       4.2.4.  Check Digit . . . . . . . . . . . . . . . . . . . . .   7
       4.2.5.  Hexadecimal Encoding  . . . . . . . . . . . . . . . .   7
   5.  Community considerations  . . . . . . . . . . . . . . . . . .   7
   6.  Namespace considerations  . . . . . . . . . . . . . . . . . .   8
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Security and privacy considerations . . . . . . . . . . . . .   8
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   9
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   A single mode 3GPP mobile equipment which uses only 3GPP technology
   to transmit and receive voice or data, or a dual mode 3GPP/3GPP2
   mobile equipment which uses either 3GPP or 3GPP2 technology to
   transmit and receive voice or data has an International Mobile
   station Equipment Identity (IMEI) to identify the mobile equipment.
   A URN Namespace and an NSS for the IMEI are defined in [RFC7254].
   For cases where the mobile equipment uses IMEI as an identity for
   dual mode 3GPP/3GPP2 access the IMEI urn as defined in [RFC7254] can
   be used to identify the mobile equipment.

   However, single mode 3GPP2 mobile equipment which supports only 3GPP2
   access technology to transmit and receive voice or data has a
   hexadecimal MEID.  Since there are fundamental differences between
   MEID and IMEI, i.e. in encoding, format and the ownership, [RFC7254]
Show full document text