1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
|
<pre>Internet Engineering Task Force (IETF) A. Allen, Ed.
Request for Comments: 7255 Blackberry
Category: Informational May 2014
ISSN: 2070-1721
<span class="h1">Using the International Mobile station Equipment Identity (IMEI)</span>
<span class="h1">Uniform Resource Name (URN) as an Instance ID</span>
Abstract
This specification defines how the Uniform Resource Name (URN)
reserved for the Global System for Mobile Communications Association
(GSMA) identities and its sub-namespace for the International Mobile
station Equipment Identity (IMEI) 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 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 a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7255">http://www.rfc-editor.org/info/rfc7255</a>.
<span class="grey">Allen Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Background ......................................................<a href="#page-3">3</a>
<a href="#section-4">4</a>. 3GPP Use Cases ..................................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. User Agent Client Procedures ....................................<a href="#page-5">5</a>
<a href="#section-6">6</a>. User Agent Server Procedures ....................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. 3GPP SIP Registrar Procedures ...................................<a href="#page-6">6</a>
<a href="#section-8">8</a>. Security Considerations .........................................<a href="#page-7">7</a>
<a href="#section-9">9</a>. Acknowledgements ................................................<a href="#page-7">7</a>
<a href="#section-10">10</a>. References .....................................................<a href="#page-8">8</a>
<a href="#section-10.1">10.1</a>. Normative References ......................................<a href="#page-8">8</a>
<a href="#section-10.2">10.2</a>. Informative References ....................................<a href="#page-8">8</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This specification defines how the Uniform Resource Name (URN)
reserved for the Global System for Mobile Communications Association
(GSMA) identities and its sub-namespace for the International Mobile
station Equipment Identity (IMEI) as specified in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>] can be
used as an instance-id as specified in <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] and also as used
by <a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>].
<a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] specifies the '+sip.instance' Contact header field
parameter that contains a URN as specified in <a href="./rfc2141">RFC 2141</a> [<a href="#ref-4" title=""URN Syntax"">4</a>]. The
instance-id uniquely identifies a specific User Agent (UA) instance.
This instance-id is used as specified in <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] so that the
Session Initiation Protocol (SIP) registrar (as specified in <a href="./rfc3261">RFC 3261</a>
[<a href="#ref-9" title=""SIP: Session Initiation Protocol"">9</a>]) can recognize that the contacts from multiple registrations
correspond to the same UA. The instance-id is also used as specified
<span class="grey">Allen Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
by <a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>] 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).
<a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] requires that a UA SHOULD create a Universally Unique
Identifier (UUID) URN as specified in <a href="./rfc4122">RFC 4122</a> [<a href="#ref-6" title=""A Universally Unique IDentifier (UUID) URN Namespace"">6</a>] as its instance-id
but allows for the possibility to use other URN schemes. Per
<a href="./rfc5626">RFC 5626</a>, "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". This
specification meets this requirement by specifying how the GSMA IMEI
URN is used in the '+sip.instance' Contact header field parameter for
outbound behavior, and <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>] specifies how the GSMA IMEI URN
is constructed.
The GSMA IMEI is a URN for the IMEI -- a globally unique identifier
that identifies mobile devices used in the GSM, Universal Mobile
Telecommunications System (UMTS), and 3rd Generation Partnership
Project (3GPP) Long Term Evolution (LTE) networks. The IMEI
allocation is managed by the GSMA to ensure that the IMEI values are
globally unique. Details of the formatting of the IMEI as a URN are
specified in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>], and the definition of the IMEI is
contained in 3GPP TS 23.003 [<a href="#ref-10" title=""Numbering, addressing and identification"">10</a>]. Further details about the GSMA's
role in allocating the IMEI, and the IMEI allocation guidelines, can
be found in GSMA PRD TS.06 [<a href="#ref-11" title=""IMEI Allocation and Approval Guidelines"">11</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-7" title=""Key words for use in RFCs to Indicate Requirement Levels"">7</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Background</span>
GSM, UMTS, and LTE capable mobile devices represent 90% of the mobile
devices in use worldwide. Every manufactured GSM, UMTS, or LTE
mobile device has an allocated IMEI that uniquely identifies this
specific mobile device. Among other things, in some regulatory
jurisdictions the IMEI is used to identify that a stolen mobile
device is being used, to help to identify the subscription that is
using it, and to prevent use of the mobile device. While GSM was
originally a circuit switched system, enhancements such as the
General Packet Radio Service (GPRS) and UMTS have added IP data
capabilities that, along with the definition of the IP Multimedia
Subsystem (IMS), have made SIP-based calls and IP multimedia sessions
from mobile devices possible.
<span class="grey">Allen Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
The latest enhancement, known as LTE, introduces even higher data
rates and dispenses with the circuit switched infrastructure
completely. This means that with LTE networks, voice calls will need
to be conducted using IP and IMS. However, the transition to all IP
SIP-based IMS networks worldwide will take a great many years, and
mobile devices, being mobile, will need to operate in both IP/SIP/IMS
mode and circuit switched mode. This means that calls and sessions
will need to be handed over between IP/SIP/IMS mode and circuit
switched mode mid-call or mid-session. Also, since many existing GSM
and UMTS radio access networks are unable to support IP/SIP/IMS-based
voice services in a commercially acceptable manner, some sessions
could have some media types delivered via IP/IMS simultaneously with
voice media delivered via the circuit switched domain to the same
mobile device. To achieve this, the mobile device needs to be
simultaneously attached via both the IP/SIP/IMS domain and the
circuit switched domain.
To meet this need, the 3GPP has specified how to maintain session
continuity between the IP/SIP/IMS domain and the circuit switched
domain in 3GPP TS 24.237 [<a href="#ref-12" title=""Mobile radio interface Layer 3 specification; Core network protocols; Stage 3"">12</a>], and in 3GPP TS 24.292 [<a href="#ref-13" title=""IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3"">13</a>] has
specified how to access IMS hosted services via both the IP/SIP/IMS
domain and the circuit switched domain.
In order for the mobile device to access SIP/IMS services via the
circuit switched domain, the 3GPP has specified a Mobile Switching
Center (MSC) server enhanced for IMS Centralized Services (ICS) and a
MSC server enhanced for Single Radio Voice Call Continuity (SR-VCC)
that control mobile voice call setup over the circuit switched radio
access while establishing the corresponding voice session in the core
network using SIP/IMS. To enable this, the MSC server enhanced for
ICS or the MSC server enhanced for SR-VCC performs SIP registration
on behalf of the mobile device, which is also simultaneously directly
registered with the IP/SIP/IMS domain. The only mobile device
identifier that is transportable using GSM/UMTS/LTE signaling is the
IMEI; therefore, the instance-id included by the MSC server enhanced
for ICS or the MSC server enhanced for SR-VCC when acting on behalf
of the mobile device, and the instance-id directly included by the
mobile device, both need to be based on the IMEI.
Additionally, in order to meet the above requirements, the same IMEI
that is obtained from the circuit switched signaling by the MSC
server needs to be obtainable from SIP signaling so that it can be
determined that both the SIP signaling and circuit switched signaling
originate from the same mobile device.
For these reasons, 3GPP TS 24.237 [<a href="#ref-12" title=""Mobile radio interface Layer 3 specification; Core network protocols; Stage 3"">12</a>] and 3GPP TS 24.292 [<a href="#ref-13" title=""IP Multimedia (IM) Core Network (CN) subsystem Centralized Services (ICS); Stage 3"">13</a>]
already specify the use of the URN namespace for the GSMA IMEI URN as
specified in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>] as the instance-id used by GSM/UMTS/LTE
<span class="grey">Allen Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
mobile devices, the MSC server enhanced for SR-VCC, and the MSC
server enhanced for ICS, for SIP/IMS registrations and emergency-
related SIP requests.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. 3GPP Use Cases</span>
1. The mobile device includes its IMEI in the SIP REGISTER request
so that the SIP registrar can perform a check of the Equipment
Identity Register (EIR) to verify whether this mobile device is
allowed to access the network for non-emergency services or is
barred from doing so (e.g., because the device has been stolen).
If the mobile device is not allowed to access the network for
non-emergency services, the SIP registrar can reject the
registration and thus prevent a barred mobile device from
accessing the network for non-emergency services.
2. The mobile device includes its IMEI in SIP INVITE requests used
to establish emergency sessions. This is so that the Public
Safety Answering Point (PSAP) can obtain the IMEI of the mobile
device for identification purposes if required by regulations.
3. The IMEI that is included in SIP INVITE requests by the mobile
device and used to establish emergency sessions is also used in
cases of unauthenticated emergency sessions to enable the network
to identify the mobile device. This is especially important if
the unauthenticated emergency session is handed over from the
packet switched domain to the circuit switched domain. In this
scenario, the IMEI is the only identifier that is common to both
domains, so the Emergency Access Transfer Function (EATF) in the
network, which in such cases coordinates the transfer between
domains, can use the IMEI to determine that the circuit switched
call is from the same mobile device that was in the emergency
session in the packet switched domain.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. User Agent Client Procedures</span>
A User Agent Client (UAC) that has an IMEI as specified in 3GPP TS
23.003 [<a href="#ref-10" title=""Numbering, addressing and identification"">10</a>] and that is registering with a 3GPP IMS network MUST
include in the "sip.instance" media feature tag the GSMA IMEI URN
according to the syntax specified in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>] when performing the
registration procedures specified in <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] or <a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>], or
any other procedure requiring the inclusion of the "sip.instance"
media feature tag. The UAC SHOULD NOT include the optional 'svn'
parameter in the GSMA IMEI URN in the "sip.instance" media feature
tag, since the software version can change as a result of upgrades to
the device firmware that would create a new instance-id. Any future
non-zero values of the 'vers' parameter, or the future definition of
additional parameters for the GSMA IMEI URN that are intended to be
<span class="grey">Allen Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
used as part of an instance-id, will require that an update be made
to this RFC. The UAC MUST provide character-by-character identical
URNs in each registration according to <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>]. Hence, any
optional or variable components of the URN (e.g., the 'vers'
parameter) MUST be presented with the same values and in the same
order in every registration as in the first registration.
A UAC MUST NOT use the GSMA IMEI URN as an instance-id, except when
registering with a 3GPP IMS network. When a UAC is operating in IMS
mode, it will obtain from the Universal Integrated Circuit Card
(UICC) (commonly known as the SIM card) the domain of the network
with which to register. This is a carrier's IMS network domain. The
UAC will also obtain the address of the IMS edge proxy to send the
REGISTER request containing the IMEI using information elements in
the Attach response when it attempts to connect to the carrier's
packet data network. When registering with a non-3GPP IMS network, a
UAC SHOULD use a UUID as an instance-id as specified in <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>].
A UAC MUST NOT include the "sip.instance" media feature tag
containing the GSMA IMEI URN in the Contact header field of non-
REGISTER requests, except when the request is related to an emergency
session. Regulatory requirements can require that the IMEI be
provided to the PSAP. Any future exceptions to this prohibition will
require the publication of an RFC that addresses how privacy is not
violated by such usage.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. User Agent Server Procedures</span>
A User Agent Server (UAS) MUST NOT include its "sip.instance" media
feature tag containing the GSMA IMEI URN in the Contact header field
of responses, except when the response is related to an emergency
session. Regulatory requirements can require that the IMEI be
provided to the PSAP. Any future exceptions to this prohibition will
require the publication of an RFC that addresses how privacy is not
violated by such usage.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. 3GPP SIP Registrar Procedures</span>
In 3GPP IMS, when the SIP registrar receives in the Contact header
field a "sip.instance" media feature tag containing the GSMA IMEI URN
according to the syntax specified in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>] the SIP registrar
follows the procedures specified in <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>]. The IMEI URN MAY
be validated as described in <a href="./rfc7254">RFC 7254</a> [<a href="#ref-1" title=""A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)"">1</a>]. If the UA indicates that
it supports the extension in <a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>] and the SIP registrar
allocates a public GRUU according to the procedures specified in
<a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>], the instance-id MUST be obfuscated when creating the
'gr' parameter in order not to reveal the IMEI to other UAs when the
<span class="grey">Allen Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
public GRUU is included in non-REGISTER requests and responses. 3GPP
TS 24.229 [<a href="#ref-8" title=""IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3"">8</a>] subclause 5.4.7A.2 specifies the mechanism for
obfuscating the IMEI when creating the 'gr' parameter.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
Because IMEIs, like other formats of instance-ids, can be correlated
to a user, they are personally identifiable information and therefore
MUST be treated in the same way as any other personally identifiable
information. In particular, the "sip.instance" media feature tag
containing the GSMA IMEI URN MUST NOT be included in requests or
responses intended to convey any level of anonymity, as this could
violate the user's privacy. <a href="./rfc5626">RFC 5626</a> [<a href="#ref-2" title=""Managing Client- Initiated Connections in the Session Initiation Protocol (SIP)"">2</a>] states that "One case where
a UA could prefer to omit the "sip.instance" media feature tag is
when it is making an anonymous request or some other privacy concern
requires that the UA not reveal its identity". The same concerns
apply when using the GSMA IMEI URN as an instance-id. Publication of
the GSMA IMEI URN to networks to which the UA is not attached, or
with which the UA does not have a service relationship, is a security
breach, and the "sip.instance" media feature tag MUST NOT be
forwarded by the service provider's network elements when forwarding
requests or responses towards the destination UA. Additionally, an
instance-id containing the GSMA IMEI URN identifies a mobile device
and not a user. The instance-id containing the GSMA IMEI URN MUST
NOT be used alone as an address for a user or as an identification
credential for a user. The GRUU mechanism specified in <a href="./rfc5627">RFC 5627</a> [<a href="#ref-3" title=""Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)"">3</a>]
provides a means to create URIs that address the user at a specific
device or User Agent.
Entities that log the instance-id need to protect them as personally
identifiable information. Regulatory requirements can require that
carriers log SIP IMEIs.
In order to protect the "sip.instance" media feature tag containing
the GSMA IMEI URN from being tampered with, those REGISTER requests
containing the GSMA IMEI URN MUST be sent using a security mechanism
such as Transport Layer Security (TLS) (<a href="./rfc5246">RFC 5246</a> [<a href="#ref-5" title=""The Transport Layer Security (TLS) Protocol Version 1.2"">5</a>]) or another
security mechanism that provides equivalent levels of protection such
as hop-by-hop security based upon IPsec.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgements</span>
The author would like to thank Paul Kyzivat, Dale Worley, Cullen
Jennings, Adam Roach, Keith Drage, Mary Barnes, Peter Leis, James Yu,
S. Moonesamy, Roni Even, and Tim Bray for reviewing this document and
providing their comments.
<span class="grey">Allen Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. References</span>
<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Montemurro, M., Ed., Allen, A., McDonald, D., and P. Gosden, "A
Uniform Resource Name Namespace for the Global System for Mobile
Communications Association (GSMA) and the International Mobile
station Equipment Identity (IMEI)", <a href="./rfc7254">RFC 7254</a>, May 2014.
[<a id="ref-2">2</a>] Jennings, C., Mahy, R., and F. Audet, "Managing Client-
Initiated Connections in the Session Initiation Protocol (SIP)",
<a href="./rfc5626">RFC 5626</a>, October 2009.
[<a id="ref-3">3</a>] Rosenberg, J., "Obtaining and Using Globally Routable User Agent
URIs (GRUUs) in the Session Initiation Protocol (SIP)", <a href="./rfc5627">RFC</a>
<a href="./rfc5627">5627</a>, October 2009.
[<a id="ref-4">4</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, May 1997.
[<a id="ref-5">5</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS)
Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>, August 2008.
[<a id="ref-6">6</a>] Leach, P., Mealling, M., and R. Salz, "A Universally Unique
IDentifier (UUID) URN Namespace", <a href="./rfc4122">RFC 4122</a>, July 2005.
[<a id="ref-7">7</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-8">8</a>] 3GPP, "IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol
(SDP); Stage 3", 3GPP TS 24.229 (Release 8), March 2014,
<<a href="ftp://ftp.3gpp.org/Specs/archive/24_series/">ftp://ftp.3gpp.org/Specs/archive/24_series/</a> 24.229/>.
[<a id="ref-9">9</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-10">10</a>] 3GPP, "Numbering, addressing and identification", 3GPP TS 23.003
(Release 8), March 2014, <<a href="ftp://ftp.3gpp.org/Specs/archive/23_series/23.003/">ftp://ftp.3gpp.org/Specs/</a>
<a href="ftp://ftp.3gpp.org/Specs/archive/23_series/23.003/">archive/23_series/23.003/</a>>.
[<a id="ref-11">11</a>] GSM Association, "IMEI Allocation and Approval Guidelines", PRD
TS.06 (DG06) Version 6.0, July 2011,
<<a href="http://www.gsma.com/newsroom/wp-content/uploads/2012/06/ts0660tacallocationprocessapproved.pdf">http://www.gsma.com/newsroom/wp-content/uploads/2012/06/</a>
<a href="http://www.gsma.com/newsroom/wp-content/uploads/2012/06/ts0660tacallocationprocessapproved.pdf">ts0660tacallocationprocessapproved.pdf</a>>.
<span class="grey">Allen Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7255">RFC 7255</a> Using IMEI URN as an Instance ID May 2014</span>
[<a id="ref-12">12</a>] 3GPP, "Mobile radio interface Layer 3 specification; Core
network protocols; Stage 3", 3GPP TS 24.237 (Release 8),
September 2013, <<a href="ftp://ftp.3gpp.org/Specs/archive/24_series/24.237/">ftp://ftp.3gpp.org/Specs/archive/</a>
<a href="ftp://ftp.3gpp.org/Specs/archive/24_series/24.237/">24_series/24.237/</a>>.
[<a id="ref-13">13</a>] 3GPP, "IP Multimedia (IM) Core Network (CN) subsystem
Centralized Services (ICS); Stage 3", 3GPP TS 24.292 (Release
8), December 2013, <<a href="ftp://ftp.3gpp.org/Specs/archive/24_series/24.292/">ftp://ftp.3gpp.org/Specs/</a>
<a href="ftp://ftp.3gpp.org/Specs/archive/24_series/24.292/">archive/24_series/24.292/</a>>.
Author's Address
Andrew Allen (editor)
Blackberry
1200 Sawgrass Corporate Parkway
Sunrise, Florida 33323
USA
EMail: aallen@blackberry.com
Allen Informational [Page 9]
</pre>
|
