idnits 2.17.1
draft-allen-dispatch-imei-urn-as-instanceid-01.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
** The abstract seems to contain references ([2], [1]), which it shouldn't.
Please replace those with straight textual mentions of the documents in
question.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
== Line 219 has weird spacing: '... Mobile stati...'
-- The document date (October 25, 2010) is 4933 days in the past. Is this
intentional?
Checking references for intended status: Informational
----------------------------------------------------------------------------
== Outdated reference: A later version (-20) exists of
draft-montemurro-gsma-imei-urn-05
** Obsolete normative reference: RFC 2141 (ref. '4') (Obsoleted by RFC 8141)
-- Obsolete informational reference (is this intentional?): RFC 2246 (ref.
'11') (Obsoleted by RFC 4346)
Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 Dispatch Working Group A. Allen, Ed.
3 Internet-Draft Research in Motion (RIM)
4 Intended status: Informational October 25, 2010
5 Expires: April 28, 2011
7 Using the International Mobile station Equipment Identity(IMEI)URN as an
8 Instance ID
9 draft-allen-dispatch-imei-urn-as-instanceid-01
11 Abstract
13 This specification defines how the Uniform Resource Name namespace
14 reserved for GSMA (Global Sstandard for Mobiles Association)
15 identities and its sub namespace for the IMEI (International Mobile
16 station Equipment Identity) can be used as an instance-id as
17 specified in RFC 5626 [1] and also as used by RFC 5627 [2].
19 Status of this Memo
21 This Internet-Draft is submitted in full conformance with the
22 provisions of BCP 78 and BCP 79.
24 Internet-Drafts are working documents of the Internet Engineering
25 Task Force (IETF). Note that other groups may also distribute
26 working documents as Internet-Drafts. The list of current Internet-
27 Drafts is at http://datatracker.ietf.org/drafts/current/.
29 Internet-Drafts are draft documents valid for a maximum of six months
30 and may be updated, replaced, or obsoleted by other documents at any
31 time. It is inappropriate to use Internet-Drafts as reference
32 material or to cite them other than as "work in progress."
34 This Internet-Draft will expire on April 28, 2011.
36 Copyright Notice
38 Copyright (c) 2010 IETF Trust and the persons identified as the
39 document authors. All rights reserved.
41 This document is subject to BCP 78 and the IETF Trust's Legal
42 Provisions Relating to IETF Documents
43 (http://trustee.ietf.org/license-info) in effect on the date of
44 publication of this document. Please review these documents
45 carefully, as they describe your rights and restrictions with respect
46 to this document. Code Components extracted from this document must
47 include Simplified BSD License text as described in Section 4.e of
48 the Trust Legal Provisions and are provided without warranty as
49 described in the Simplified BSD License.
51 Table of Contents
53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
57 3. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 4
59 4. User Agent Client Procedures . . . . . . . . . . . . . . . . . 5
61 5. Security considerations . . . . . . . . . . . . . . . . . . . . 5
63 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5
65 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
66 7.1. Normative references . . . . . . . . . . . . . . . . . . . 6
67 7.2. Informative references . . . . . . . . . . . . . . . . . . 6
69 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
71 1. Introduction
73 This specification defines how the Uniform Resource Name namespace
74 reserved for GSMA identities and its sub namespace for the IMEI
75 (International Mobile station Equipment Identity) as defined in
76 draft-montemurro-gsma-imei-urn-05 [3] can be used as an instance-id
77 as specified in RFC 5626 [1] and also as used by RFC 5627 [2].
79 RFC 5626 [1] defines the "+sip.instance" Contact header field
80 parameter which contains a URN as per RFC 2141 [4] defined as an
81 instance-id that uniquely identifies a specific UA instance. This
82 instance-id is used as defined in RFC 5626 [1] so that registrar can
83 recognize that the contacts from multiple registrations correspond to
84 the same UA. The instance-ID is also used as defined by RFC 5627 [2]
85 to create Globally Routable User Agent URIs (GRUUs) that can be used
86 to uniquely address a UA when multiple UAs are registered with the
87 same Address of Record (AoR).
89 RFC 5626 [1] defines that a UA SHOULD create a Universally Unique
90 Identifier (UUID) URN as defined in RFC 4122 [6] as its instance-id
91 but allows for the possibility of other URN schemes to be used. If a
92 URN scheme other than UUID is used, the UA MUST only use URNs for
93 which an RFC (from the IETF stream) defines how the specific URN
94 needs to be constructed and used in the "+sip.instance" Contact
95 header field parameter for outbound behavior. This specification
96 meets this requirement by specifying how the GSMA IEMEI URN is used
97 in the "+sip.instance" Contact header field parameter for outbound
98 behavior and draft-montemurro-gsma-imei-urn-05 [3] defines how the
99 GSMA IMEI URN is constructed
101 The GSMA IMEI is an identifier for a namespace for the IMEI a
102 globally unique identifier that identifies Mobile Equipment used in
103 Global System for Mobile (GSM), Universal Mobile Telecommunications
104 System (UMTS) and 3GPP LTE (Long Term Evolution)networks. The IMEI
105 allocation is managed by the GSMA to ensure that the IMEI values are
106 globally unique. Details of the formatting of the IMEI as a URN are
107 defined in draft-montemurro-gsma-imei-urn-05 [3] and the definition
108 of the IMEI is contained in 3GPP TS 23.003 [7]. Further details
109 about the GSMA role in allocating the IMEI and the IMEI allocation
110 guidelines can be found in GSMA PRD DG.06 [8]
112 2. Terminology
114 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
115 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
116 document are to be interpreted as described in [5].
118 3. Background
120 GSM and UMTS capable mobile devices represent 90% of the mobile
121 devices in use worldwide. GSM and UMTS mobile devices each have a
122 unique IMEI allocated which uniquely identifies the mobile device
123 from all other GSM/UMTS mobile devices deployed. Amongst other
124 things in some regulatory jurisdictions the IMEI is used to identify
125 a stolen mobile is being used and help to identify the subscription
126 that is using it and to prevent its use. Whilst GSM was originally a
127 circuit switched system enhancements such as GPRS (General Packet
128 Radio Service) and UMTS have added IP data capabilities which along
129 with the definition of the IP Multimedia Subsystem (IMS) has made SIP
130 based calls and IP multimedia sessions from mobile devices possible.
131 The latest enhancment known as LTE will introduce even higher data
132 rates and dispenses with the circuit switched domain completely
133 meaning that with LTE voice calls will need to be conducted using IP
134 and IMS. However, the transition to all IP, SIP based IMS networks
135 worldwide will take a great many years and mobile devices being
136 mobile will need to operate in both IP/SIP/IMS mode and circuit
137 switched mode. In fact calls and sessions will need to be handed
138 over between IP/SIP/IMS mode and circuit switched mode during a call.
139 Also as many existing GSM and UMTS radio access networks are unable
140 to support IP/SIP/IMS based voice services in a commercially
141 acceptable manner some sessions may have some media types delivered
142 via IP/IMS simultaneously with voice media delivered via circuit
143 switched with the same mobile device simultaneously attached via both
144 the IP/SIP/IMS domain and the circuit switched domain. To meet this
145 need 3GPP has specified how to maintain session continuity between
146 the IP/SIP/IMS domain and the circuit switched domain in 3GPP TS
147 24.237 [9] and how to access IMS hosted services via both the IP/SIP/
148 IMS domain and the circuit switched domain in 3GPP TS 24.292 [10].
150 In order for the the mobile device to access SIP/IMS services via the
151 circuit switched domain 3GPP has defined a MSC (Mobile switching
152 Center) server enhanced for ICS which controls mobile voice call
153 setup over the circuit switched radio access while establishing the
154 corresponding voice session in the core network using SIP/IMS. To
155 enable this the MSC server enhanced for ICS (IMS centralized
156 services) performs SIP registration on behalf of the mobile device
157 which may simultaneously also be directly registered with the IP/SIP/
158 IMS domain. The SIP/IMS network needs to be able to identify that
159 both of these SIP registrations are from the same UA instance and
160 also correctly handle sessions establishment requests addressed using
161 GRUUs as defined in RFC 5627 [2] when the mobile device is attached
162 using the circuit switched domain. The only mobile device identifier
163 that is transportable using GSM/UMTS/LTE signaling is the IMEI
164 therefore the instance-id used by the MSC server enhanced for ICS
165 when registering on behalf of the mobile device and the instance-id
166 when the mobile device registers directly needs to be based on the
167 IMEI.
169 Additionally in order to meet the regulatory requirements to use the
170 IMEI to identify a stolen mobile is being used and help to identify
171 the subscription that is using it and to prevent its use the same
172 IMEI that is obtained from the circuit switched signaling needs to be
173 obtainable from SIP signaling.
175 3GPP TS 24.237 [9] and 3GPP TS 24.292 [10] already define the use of
176 the URN namespace for the GSMA and IMEI as defined in
177 draft-montemurro-gsma-imei-urn-05 [3] as the instance-id used by
178 mobile devices and the MSC server enhanced for ICS for SIP/IMS
179 registrations for these reasons.
181 4. User Agent Client Procedures
183 A UAC that has an IMEI as defined in 3GPP TS 23.003 [7] SHALL include
184 in the "sip.instance" media feature tag the GSMA IMEI URN according
185 to the syntax defined in draft-montemurro-gsma-imei-urn-05 [3] when
186 performing the registration procedures defined in RFC 5626 [1] or RFC
187 5627 [2] or any other procedure requiring including the
188 "sip.instance" media feature tag. If the UAC includes the "vers"
189 and/or the "svn" parameters of this URN in the "sip.instance" media
190 feature tag then the UAC MUST always include these parameters in the
191 "sip.instance" media feature tag in the same sequence order as in the
192 first usage in order to provide lexically equivalent URNs in each
193 registration.
195 5. Security considerations
197 In order to protect from tampering the register requests containing
198 the GSMA IMEI URN SHOULD be sent using a security mechanism such as
199 TLS [11] (or other security mechanism that provides equivalent levels
200 of protection).
202 6. Acknowledgements
204 The author would like to thank Paul Kyzivat and Dale Worley for
205 reviewing this draft and providing their comments.
207 7. References
208 7.1. Normative references
210 [1] Jennings, C., Mahy, R., and F. Audet, "Managing Client-
211 Initiated Connections in the Session Initiation Protocol
212 (SIP)", RFC 5626, October 2009.
214 [2] Rosenberg, J., "Obtaining and Using Globally Routable User
215 Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)",
216 RFC 5627, October 2009.
218 [3] Montemurro, M., "A Uniform Resource Name Namespace For The GSM
219 Association (GSMA) and the International Mobile station
220 Equipment Identity(IMEI), work in progress", Internet
221 Draft draft-montemurro-gsma-imei-urn-05, September 2010.
223 [4] Moats, R., "URN Syntax", RFC 2141, May 1997.
225 [5] Bradner, S., "Key words for use in RFCs to Indicate Requirement
226 Levels", BCP 14, RFC 2119, March 1997.
228 7.2. Informative references
230 [6] Leach, P., Mealling, M., and R. Salz, "A Universally Unique
231 IDentifier (UUID) URN Namespace", RFC 4122, July 2005.
233 [7] 3GPP, "TS 23.003: Numbering, addressing and identification
234 (Release 8)", 3GPP 23.003, September 2008,
235 .
237 [8] GSMA Association, "IMEI Allocation and Approval Guidelines",
238 PRD DG.06 version 3.6, February 2008,
239 .
241 [9] 3GPP, "TS 24.237: Mobile radio interface Layer 3 specification;
242 Core network protocols; Stage 3 (Release 8)", 3GPP 24.237,
243 March 2009,
244 .
246 [10] 3GPP, "TS 24.292: IP Multimedia (IM) Core Network (CN)
247 subsystem Centralized Services (ICS); Stage 3 (Release 8)",
248 3GPP 24.292, March 2009,
249 .
251 [11] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0",
252 RFC 2246, January 1999.
254 Author's Address
256 Andrew Allen (editor)
257 Research in Motion (RIM)
258 2550 West Golf Road
259 Rolling Meadows, Illinois 60008
260 USA
262 Phone: unlisted
263 Fax: unlisted
264 Email: aallen@rim.com