Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID
draft-atarius-dispatch-meid-urn-as-instanceid-05

Document Type Active Internet-Draft (individual in art area)
Last updated 2017-11-09 (latest revision 2017-10-09)
Stream IETF
Intended RFC status Informational
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 In Last Call (ends 2017-12-08)
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 None
Dispatch Working Group                                   R. Atarius, Ed.
Internet-Draft                                           October 9, 2017
Intended status: Informational
Expires: April 12, 2018

 Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN)
                           as an Instance ID
            draft-atarius-dispatch-meid-urn-as-instanceid-05

Abstract

   This specification 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.  Its
   purpose 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 12, 2018.

Copyright Notice

   Copyright (c) 2017 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

Atarius                  Expires April 12, 2018                 [Page 1]
Internet-Draft      Using MEID URN as an Instance ID        October 2017

   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.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  3GPP2 Use Cases . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  User Agent Client Procedures  . . . . . . . . . . . . . . . .   4
   6.  User Agent Server Procedures  . . . . . . . . . . . . . . . .   5
   7.  3GPP/3GPP2 SIP Registrar Procedures . . . . . . . . . . . . .   5
   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  Security considerations . . . . . . . . . . . . . . . . . . .   6
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative references . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative references . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This specification specifies how the URN namespace reserved for 3GPP2
   identities and its NSS for the MEID as specified in draft-atarius-
   dispatch-meid-urn [8] can be used as an instance-id as specified in
   RFC 5626 [2] and also as used by RFC 5627 [3].

   RFC 5626 [2] specifies the "+sip.instance" Contact header field
   parameter that contains a URN as specified in RFC 8141 [4].  The
   instance-id uniquely identifies a specific User Agent (UA) instance.
   This instance-id is used as specified in RFC 5626 [2] so that the
   Session Initiation Protocol (SIP) registrar (as specified in RFC 3261
   [1]) can recognize that the contacts from multiple registrations
   correspond to the same UA.  The instance-id is also used as specified
   by RFC 5627 [3] 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 [2] requires that a UA SHOULD create a Universally Unique
   Identifier (UUID) URN as specified in RFC 4122 [7] as its instance-id
   but allows for the possibility to use other URN schemes.  "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
Show full document text