A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)
RFC 8464

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

• Versions
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18

Internet Engineering Task Force (IETF)                        R. Atarius
Request for Comments: 8464                                September 2018
Category: Informational
ISSN: 2070-1721

A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)

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 3GPP2 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 document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are candidates for any level of Internet
   Standard; see Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   https://www.rfc-editor.org/info/rfc8464.

Atarius                       Informational                     [Page 1]
RFC 8464                     MEID-Based URN               September 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
   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 . . . . . . . . . . . . . . .   4
   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.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security and Privacy Considerations . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Mobile equipment that is either a) single-mode 3GPP using only 3GPP
   technology to transmit and receive voice or data or b) dual-mode
   3GPP/3GPP2 using either 3GPP or 3GPP2 technology to transmit and
   receive voice or data has an International Mobile station Equipment
   Identity (IMEI) to identify it.  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.

Atarius                       Informational                     [Page 2]
RFC 8464                     MEID-Based URN               September 2018

   However, single-mode 3GPP2 mobile equipment that 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] cannot be employed to represent the hexadecimal MEID.

   This document specifies a URN namespace for 3GPP2 and an NSS for the
   MEID as per the namespace registration requirement in [RFC8141].  The
   structure of an MEID is 15 hexadecimal digits long and is defined by
   3GPP2 (see [S.R0048-A]) to uniquely identify each individual piece of