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
RFC Editor Note
Please make the following changes:
- Section 2: Please use the RFC 8174 boilerplate.
- Section 3.8: Please correct the section reference:
OLD:
3.8. Security and Privacy
See Section 8 of RFC XXXX.
NEW:
3.8. Security and Privacy
See Section 6 of RFC XXXX.
End.
- 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.
- Section 8.1: Please correct the following reference:
OLD:
[SC.R4002-0]
3GPP2, "SC.R4002-0: GHA (Global Hexadecimal Administrator)
Assignment Guidelines and Procedures for Mobile Equipment
Identifier (MEID) and Short Form Expanded UIM Identifier
(SF_EUIMID), Version 12.0", 3GPP2 TS SC.R4002-0 10.0,
December 2013, <http://www.3gpp2.org/Public_html/Specs/SC.
R4002-0_v12.0_GHA_%20Guidelines_for_MEID_December_2016.pdf
.NEW:
[SC.R4002-0]
3GPP2, "SC.R4002-0: GHA (Global Hexadecimal Administrator)
Assignment Guidelines and Procedures for Mobile Equipment
Identifier (MEID) and Short Form Expanded UIM Identifier
(SF_EUIMID), Version 12.0", 3GPP2 TS SC.R4002-0 10.0,
December 2016, <http://www.3gpp2.org/Public_html/Specs/SC.
R4002-0_v12.0_GHA_%20Guidelines_for_MEID_December_2016.pdf
End.