Using the International Mobile station Equipment Identity(IMEI)URN as an Instance ID
draft-allen-dispatch-imei-urn-as-instanceid-10

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rai area)
Last updated 2013-08-16 (latest revision 2013-07-05)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state (None)
Consensus Yes
Document shepherd Mary Barnes
Shepherd write-up Show (last changed 2013-07-11)
IESG IESG state Waiting for Writeup
Telechat date
Responsible AD Gonzalo Camarillo
Send notices to aallen@blackberry.com, draft-allen-dispatch-imei-urn-as-instanceid@tools.ietf.org
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
Dispatch Working Group                                     A. Allen, Ed.
Internet-Draft                                                Blackberry
Intended status: Informational                              July 6, 2013
Expires: January 7, 2014

Using the International Mobile station Equipment Identity(IMEI)URN as an
                              Instance ID
             draft-allen-dispatch-imei-urn-as-instanceid-10

Abstract

   This specification defines how the Uniform Resource Name namespace
   reserved for the GSMA (GSM Association) identities and its sub-
   namespace for the IMEI (International Mobile station Equipment
   Identity) can be used as an instance-id as specified in RFC 5626 [1]
   and also as used by RFC 5627 [2].  Its purpose is to fulfil the
   requirements in RFC 5626 [1] that state "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."

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 http://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 January 7, 2014.

Copyright Notice

   Copyright (c) 2013 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Allen                    Expires January 7, 2014                [Page 1]
Internet-Draft      Using IMEI URN as an Instance ID           July 2013

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3

   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3

   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . . . 4

   4.  3GPP Use Cases  . . . . . . . . . . . . . . . . . . . . . . . . 5

   5.  User Agent Client Procedures  . . . . . . . . . . . . . . . . . 5

   6.  User Agent Server Procedures  . . . . . . . . . . . . . . . . . 6

   7.  3GPP Registrar Procedures . . . . . . . . . . . . . . . . . . . 6

   8.  IANA considerations . . . . . . . . . . . . . . . . . . . . . . 7

   9.  Security considerations . . . . . . . . . . . . . . . . . . . . 7

   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7

   11. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     11.1.  Normative references . . . . . . . . . . . . . . . . . . . 8
     11.2.  Informative references . . . . . . . . . . . . . . . . . . 8

   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 9

Allen                    Expires January 7, 2014                [Page 2]
Internet-Draft      Using IMEI URN as an Instance ID           July 2013

1.  Introduction

   This specification defines how the Uniform Resource Name namespace
   reserved for GSMA identities and its sub namespace for the IMEI
   (International Mobile station Equipment Identity) as defined in
   draft-montemurro-gsma-imei-urn-15 [3] can be used as an instance-id
   as specified in RFC 5626 [1] and also as used by RFC 5627 [2].

   RFC 5626 [1] defines the "+sip.instance" Contact header field
   parameter which contains a URN as per RFC 2141 [4] defined as an
   instance-id that uniquely identifies a specific UA instance.  This
   instance-id is used as defined in RFC 5626 [1] so that registrar can
   recognize that the contacts from multiple registrations correspond to
   the same UA.  The instance-id is also used as defined by RFC 5627 [2]
   to create Globally Routable User Agent URIs (GRUUs) that can be used
   to uniquely address a UA when multiple UAs are registered with the
Show full document text