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

Document Type RFC - Informational (September 2018; No errata)
Last updated 2018-09-13
Stream IETF
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 RFC 8465 (Informational)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
IANA action state No IANA Actions
Internet Engineering Task Force (IETF)                   R. Atarius, Ed.
Request for Comments: 8465                                September 2018
Category: Informational
ISSN: 2070-1721

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

Abstract

   This document specifies how the Uniform Resource Name (URN) namespace
   reserved for the Third Generation Partnership Project 2 (3GPP2)
   identities and its Namespace Specific String (NSS) for the Mobile
   Equipment Identity (MEID) can be used as an Instance ID.  The purpose
   of this Instance ID is to fulfill the requirements for defining how a
   specific URN needs to be constructed and used in the "+sip.instance"
   Contact header field parameter for outbound behavior.

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/rfc8465.

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.

Atarius                       Informational                     [Page 1]
RFC 8465               MEID URN as an Instance ID         September 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  3GPP2 Use Cases . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  User Agent Client Procedures  . . . . . . . . . . . . . . . .   5
   6.  User Agent Server Procedures  . . . . . . . . . . . . . . . .   5
   7.  3GPP/3GPP2 SIP Registrar Procedures . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document specifies how the Uniform Resource Name (URN) namespace
   reserved for Third Generation Partnership Project 2 (3GPP2)
   identities and its Namespace Specific String (NSS) for the Mobile
   Equipment Identity (MEID) as specified in RFC 8464 [10] can be used
   as an Instance ID as specified in RFC 5626 [4] and also as used by
   RFC 5627 [5].

   RFC 5626 [4] specifies the "+sip.instance" Contact header field
   parameter that contains a URN as specified in RFC 8141 [6].  The
   Instance ID uniquely identifies a specific User Agent (UA) instance.
   This Instance ID is used as specified in RFC 5626 [4] so that the
   Session Initiation Protocol (SIP) registrar (as specified in RFC 3261
   [2]) can recognize that the contacts from multiple registrations
   correspond to the same UA.  The Instance ID is also used as specified
   by RFC 5627 [5] to create Globally Routable User Agent URIs (GRUUs)
   that can be used to uniquely address a UA when multiple UAs are
   registered with the same Address of Record (AoR).

   RFC 5626 [4] requires that a UA SHOULD create a Universally Unique
   Identifier (UUID) URN as specified in RFC 4122 [9] as its Instance ID
   but allow for the possibility to use other URN schemes.

   RFC 5626 [4] states:

      If a URN scheme other than UUID is used, the UA MUST only use URNs
      for which an RFC (from the IETF stream) defines how the specific
      URN needs to be constructed and used in the "+sip.instance"
      Contact header field parameter for outbound behavior.

Atarius                       Informational                     [Page 2]
RFC 8465               MEID URN as an Instance ID         September 2018
Show full document text