Using the Mobile Equipment Identity (MEID) URN as an Instance ID
RFC 8465

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc:,,,, The IESG <>
Subject: Document Action: 'Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID' to Informational RFC (draft-atarius-dispatch-meid-urn-as-instanceid-08.txt)

The IESG has approved the following document:
- 'Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN)
   as an Instance ID'
  (draft-atarius-dispatch-meid-urn-as-instanceid-08.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:

Technical Summary

The document defines how the URN namespace reserved for Third Generation Partnership Project 2 (3GPP2) identities and the NSS under that namespace for the Mobile Equipment Identity (MEID) can be used as a SIP instance-id and fulfils the requirements of RFC 5626 requiring an RFC to be published to define how a URN is used as a SIP instance-id.

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-as-instanceid. 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.  I have conducted detailed reviews of the technical content of the document that resulted in comments that lead to improvements.


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

RFC Editor Note

Please change "" to "".