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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual in rai area)
Last updated 2013-10-30 (latest revision 2013-10-18)
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 AD Go-Ahead::External Party
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 Version Changed - Review Needed
IANA action state None
Dispatch Working Group                                     A. Allen, Ed.
Internet-Draft                                                Blackberry
Intended status: Informational                          October 18, 2013
Expires: April 21, 2014

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

Abstract

   This specification specifies how the Uniform Resource Name (URN)
   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.  Its purpose is to fulfil
   the requirements in RFC 5626 [1] that state "If a URN scheme other
   than UUID (Universally unique identifier) is used, the UA (User
   Agent) 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 April 21, 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 April 21, 2014                 [Page 1]
Internet-Draft      Using IMEI URN as an Instance ID        October 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  . . . . . . . . . . . . . . . . . 6

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

   7.  3GPP SIP Registrar Procedures . . . . . . . . . . . . . . . . . 7

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

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

   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 8

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

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

Allen                    Expires April 21, 2014                 [Page 2]
Internet-Draft      Using IMEI URN as an Instance ID        October 2013

1.  Introduction

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

   RFC 5626 [1] specifies the "+sip.instance" Contact header field
   parameter that contains a URN as specified in RFC 2141 [4].  The
   instance-id uniquely identifies a specific UA instance.  This
   instance-id is used as specified in RFC 5626 [1] so that the SIP
   (Session Initiation Protocol) registrar (as specified in RFC 3261
   [5]) 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)
Show full document text