Document Action: 'A Uniform Resource Name Namespace for the Device Identity and the Mobile Equipment Identity (MEID)' to Informational RFC (draft-atarius-dispatch-meid-urn-18.txt)

The IESG <iesg-secretary@ietf.org> Mon, 18 June 2018 22:00 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BCBF9130FDC; Mon, 18 Jun 2018 15:00:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'A Uniform Resource Name Namespace for the Device Identity and the Mobile Equipment Identity (MEID)' to Informational RFC (draft-atarius-dispatch-meid-urn-18.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.2
Auto-Submitted: auto-generated
Precedence: bulk
Cc: ben@nostrum.com, aallen@blackberry.com, rfc-editor@rfc-editor.org, draft-atarius-dispatch-meid-urn@ietf.org, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <152935922576.2922.8900030958885183276.idtracker@ietfa.amsl.com>
Date: Mon, 18 Jun 2018 15:00:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ZgSawM3QVfB2aCmL6_Vxhdp5HWE>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.26
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2018 22:00:27 -0000

The IESG has approved the following document:
- 'A Uniform Resource Name Namespace for the Device Identity and the
   Mobile Equipment Identity (MEID)'
  (draft-atarius-dispatch-meid-urn-18.txt) as Informational RFC

This document has been reviewed in the IETF but is not the product of an IETF
Working Group.

The IESG contact person is Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn/





Technical Summary

The document defines and registers with IANA a URN namespace for 3GPP2 and a NSS under that namespace for the Mobile Equipment Identity (MEID) which is used to uniquely identify each individual mobile  equipment within Third Generation Partnership Project 2 (3GPP2) networks. The MEID is 15 hexadecimal encoded digits and includes a manufacturer code that identifies the mobile equipment manufacturer serial number uniquely identifies each mobile equipment within the manufacturer code and a check digit is used as assurance of integrity in error-prone operations.

Working Group Summary

The document was submitted to DISPATCH WG, However after some initial list discussion it was determined that since this was material of interest only to 3GPP/3GPP2 specifications that this should be progressed as an AD sponsored draft. There was no controversy during the DISPATCH discussion.

Document Quality

It is not known if there are existing implementations of draft-atarius-dispatch-meid-urn. However the draft is specified for use by 3GPP2 mobile devices when using IP Multimedia Subsystem  (IMS) networks when the mobile device only has a MEID. Currently IMS networks are in the early stages of deployment and most of these are based on the 3GPP LTE or UMTS (Universal Mobile Telecommunications System) access and use the IMEI (International Mobile Equipment Identity) for device identification. However, there are many telecommunications carriers that have deployed 3GPP2 CDMA based access networks and these carriers may well deploy IMS networks and devices that only support the 3GPP2 MEID. Handset vendors supporting these CDMA carriers are expected to support this specification for such network deployments.  Both myself and Dale Worley have conducted detailed reviews of the technical content of the document that resulted in comments that lead to technical improvements.

Personnel

Andrew Allen is the Document Shepherd.
Ben Campbell is the Responsible Area Director.




RFC Editor Note

Please make the following change in section 3.9 (change "to identity" to "to identify"):

OLD:
   Although both the 3GPP2 Mobile Equipment Identity (MEID) and the 3GPP
   International Mobile station Equipment Identity (IMEI) are used to
   identity mobile equipment, they are separate identifiers and are not
   to be confused.
NEW:
   Although both the 3GPP2 Mobile Equipment Identity (MEID) and the 3GPP
   International Mobile station Equipment Identity (IMEI) are used to
   identify mobile equipment, they are separate identifiers and are not
   to be confused.
END.