Debian Codegraph @

rfc8119.html

raw
1 <pre>Internet Engineering Task Force (IETF) M. Mohali
2 Request for Comments: 8119 Orange
3 Updates: <a href="./rfc4458">4458</a> M. Barnes
4 Category: Informational MLB@Realtime Communications
5 ISSN: 2070-1721 March 2017
6
7
8 <span class="h1">SIP "cause" URI Parameter for Service Number Translation</span>
9
10 Abstract
11
12 <a href="./rfc4458">RFC 4458</a> (regarding SIP URIs for applications) defines a "cause" URI
13 parameter, which may appear in the Request-URI of a SIP request, that
14 is used to indicate a reason why the request arrived to the User
15 Agent Server (UAS) receiving the message. This document updates <a href="./rfc4458">RFC</a>
16 <a href="./rfc4458">4458</a> by creating a new predefined value for the "cause" URI parameter
17 to cover service number translation for cases of retargeting due to
18 specific service action leading to the translation of a called
19 service access number. This document also provides guidance, which
20 was missing in <a href="./rfc4458">RFC 4458</a>, for using the "cause" URI parameter within
21 the History-Info header field, since this use is mandatory in some IP
22 networks' implementations.
23
24 Status of This Memo
25
26 This document is not an Internet Standards Track specification; it is
27 published for informational purposes.
28
29 This document is a product of the Internet Engineering Task Force
30 (IETF). It represents the consensus of the IETF community. It has
31 received public review and has been approved for publication by the
32 Internet Engineering Steering Group (IESG). Not all documents
33 approved by the IESG are a candidate for any level of Internet
34 Standard; see <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
35
36 Information about the current status of this document, any errata,
37 and how to provide feedback on it may be obtained at
38 <a href="http://www.rfc-editor.org/info/rfc8119">http://www.rfc-editor.org/info/rfc8119</a>.
39
40
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Mohali &amp; Barnes Informational [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2017 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction, Terminology, and Overview . . . . . . . . . . . <a href="#page-2">2</a>
75 <a href="#section-2">2</a>. Solution . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-3">3</a>. Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
77 <a href="#section-3.1">3.1</a>. Interaction with Request History Information . . . . . . <a href="#page-4">4</a>
78 3.2. Handling and Processing the Service Number Translation
79 "cause" URI Parameter Value . . . . . . . . . . . . . . . <a href="#page-5">5</a>
80 <a href="#section-4">4</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
81 <a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
82 <a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
83 <a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
84 <a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
85 <a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
86 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
88
89 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction, Terminology, and Overview</span>
90
91 [<a id="ref-RFC4458">RFC4458</a>] defines a mechanism to identify retargeting due to call
92 forwarding supplementary services. The "cause" URI parameter in the
93 target URI identifies the reason for retargeting and has defined
94 values equivalent to the TDM (Time Division Multiplexing) Redirecting
95 Reasons [<a href="#ref-ITU-T_Q.763">ITU-T_Q.763</a>]. The concept of "retargeting" is defined in
96 [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>].
97
98 In the Public Switched Telephone Network (PSTN ) / Integrated
99 Services Digital Network (ISDN), there is another kind of retargeting
100 introduced by the Intelligent Network (IN) services based on a
101 translation of the called number as mentioned in [<a href="#ref-ITU-T_Q.1214">ITU-T_Q.1214</a>].
102 Indeed, IN aims to ease the introduction of new services (i.e.,
103 Universal Personal Telecommunication (UPT), Virtual Private Network
104 (VPN), Freephone, etc.) based on greater flexibility and new
105
106
107
108 <span class="grey">Mohali &amp; Barnes Informational [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
111
112
113 capabilities as described in [<a href="#ref-ITU-T_I.312_Q.1201">ITU-T_I.312_Q.1201</a>]. For these IN
114 services, ISDN User Part (ISUP) introduced the "called IN number" and
115 the "original called IN number" parameters to capture the information
116 of the requested service access number prior its translation
117 [<a href="#ref-ITU-T_Q.763">ITU-T_Q.763</a>].
118
119 The term "service access number" is used in this specification to
120 refer to the dialable number by which a specific service is reached.
121 This special number is not a globally routable number; therefore, it
122 needs to be translated into a routable SIP or tel URI to process the
123 session establishment.
124
125 This specification proposes a solution to allow the identification of
126 well-known services, such as premium or toll-free services that
127 perform service access number translation, and to enable interworking
128 with SIP signaling with the ISUP called IN number and original called
129 IN number parameters.
130
131 The mechanism will allow a SIP network to insert and convey the
132 service access number requested before its translation to the final
133 destination.
134
135 In order to provide full call forwarding or access number translation
136 services, usage of the "cause" URI parameter is only relevant within
137 the History-Info header field defined in [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>]. Because this
138 relation has not been described in [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>], this document provides
139 guidance for using the "cause" URI parameter in conjunction with the
140 History-Info header field.
141
142 This document also answers a need expressed by the Third Generation
143 Partnership Project (3GPP) [<a href="#ref-TS.3GPP.24.229">TS.3GPP.24.229</a>] to identify the service
144 access number. The procedures it defines are intended for networks
145 that use 3GPP-defined services. Their use is undefined for other
146 networks.
147
148 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Solution</span>
149
150 A new value for the "cause" URI parameter of the 'sip:' or 'sips:'
151 URI schemes is defined for the "Service number translation" use case.
152 This value may be used in a 'sip:' or 'sips:' URI inserted in the
153 Request-URI and in the History-Info header field [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>] when the
154 URI is issued from a retargeting or a service access number
155 translation by a specific service similar to PSTN/ISDN IN services
156 that is not a call forwarding service.
157
158 As defined in [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>], the "cause" URI parameter must be encoded in
159 the new target URI when generated by the service.
160
161
162
163
164 <span class="grey">Mohali &amp; Barnes Informational [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
167
168
169 The ABNF grammar [<a href="./rfc5234" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">RFC5234</a>] for the cause-param and target-param
170 parameters from [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>] is summarized below (including updates
171 described in [<a href="#ref-Err1409" title="Erratum ID 1409">Err1409</a>]). The Status-Code is defined in [<a href="./rfc3261" title="&quot;SIP: Session Initiation Protocol&quot;">RFC3261</a>].
172
173 target-param = "target=" pvalue
174
175 cause-param = "cause=" Status-Code
176
177 The following value for this URI parameter is added to the existing
178 ones:
179
180 +---------------------------------+-------+
181 | Cause | Value |
182 +---------------------------------+-------+
183 | Service number translation | 380 |
184 +---------------------------------+-------+
185
186 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Guidelines</span>
187
188 In order to help implementation of this solution for conveyance of
189 the service access number, this document proposes guidance for usage
190 of the "cause" URI parameter: guidance for the usage of the "cause"
191 URI parameter in the request history information (in <a href="#section-3.1">Section 3.1</a>) and
192 guidance for processing a service number translation service using
193 the new "cause" URI parameter value (in <a href="#section-3.2">Section 3.2</a>).
194
195 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Interaction with Request History Information</span>
196
197 The History-Info header field defined in [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>] specifies a means
198 of providing the UAS and User Agent Client (UAC) with information
199 about the retargeting of a request. This information includes the
200 initial Request-URI and any retargeted URIs. This information is
201 placed in History-Info headers as the request is retargeted and, upon
202 reaching the UAS, is returned in certain responses. The History-Info
203 header field enables many enhanced services by providing the
204 information as to how and why a SIP request arrives at a specific
205 application or user and to keep this information throughout the
206 signaling path even when successive applications are involved.
207
208 When a proxy inserts a URI containing the "cause" URI parameter
209 defined in [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>] into the Request-URI of a forwarded request (per
210 [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>]), the proxy must also copy this new Request-URI within a
211 History-Info header field entry into the forwarded request; thus, the
212 URI in that entry includes the "cause" URI parameter. Therefore,
213 even if the Request-URI is replaced as a result of rerouting by a
214 downstream proxy, the History-Info header field will still contain
215 these parameters, which can be of use to the UAS. Note that if a
216 proxy does not support generation of the History-Info header field or
217
218
219
220 <span class="grey">Mohali &amp; Barnes Informational [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
223
224
225 if a downstream proxy removes the History-Info header fields, an
226 application will only have access to the "cause" URI parameter if the
227 request is not subsequently retargeted (i.e., it will be contained
228 only in the Request-URI in the incoming request). The implications
229 of the solution are further discussed in <a href="#section-3.2">Section 3.2</a>.
230
231 In order to be able to filter specific entries among the history
232 information, header field parameters have been defined in [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>].
233 In particular, the "mp" and "rc" header field parameters have the
234 following definitions:
235
236 o When the new target was determined based on a mapping to a user
237 other than the target user associated with the Request-URI being
238 retargeted, the "mp" header field parameter is added. This allows
239 the identification of retargets that are the result of an
240 application decision on a user's behalf and also retargets that
241 are the result of an internal decision made by an application.
242
243 o The "rc" header field parameter is added when the new target
244 represents a change in Request-URI, while the target user remains
245 the same.
246
247 These header field parameters can be used in conjunction with the new
248 "cause" URI parameter for certain applications, an example of which
249 is provided in <a href="#section-4">Section 4</a>.
250
251 When using the History-Info header field in conjunction with the
252 "cause" URI parameter in a Request-URI, it is important to consider
253 that the "cause" URI parameter is not the same parameter as the
254 "cause" header field parameter included in the Reason header
255 [<a href="./rfc3326" title="&quot;The Reason Header Field for the Session Initiation Protocol (SIP)&quot;">RFC3326</a>]. The "cause" header field parameter of the Reason header
256 field should be added to a History-Info entry only when the
257 retargeting is due to a received SIP response.
258
259 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Handling and Processing the Service Number Translation "cause" URI</span>
260 <span class="h3"> Parameter Value</span>
261
262 At the Application Server:
263
264 When an application receiving a request that is addressed to a
265 service access number changes the Request-URI into a routable
266 number, it should insert within this new Request-URI a "cause" URI
267 parameter value set to 380 "Service number translation".
268 Following the process described in [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>], the application
269 server adds a new History-Info header field entry including the
270 new Request-URI value including the "cause" URI parameter. It is
271
272
273
274
275
276 <span class="grey">Mohali &amp; Barnes Informational [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
279
280
281 also possible for an application server to add a "target" URI
282 parameter as defined in [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>] with the initial value of the
283 Request-URI received by the application server.
284
285 Note that if the new Request-URI is further replaced by a downstream
286 proxy for any reason and if the History-Info header field is not
287 supported, the information of the service access number initially
288 requested would be lost. Thus, it is strongly recommended to support
289 the History-Info header field all along the signaling path.
290
291 At the UAS:
292
293 When the UAS receiving the request wants to retrieve the service
294 access number by which it has been reached, first it should look
295 for the "cause" URI parameter value 380 in the History-Info header
296 field. This History-Info entry should also contain an "mp" or
297 "rc" header field parameter so that the UAS can find the requested
298 service number in the History-Info entry having an index parameter
299 value that matches this "mp" or "rc" header field parameter value.
300 If, for any reason, there is no "mp" or "rc" header field
301 parameter in the identified History-Info entry, the UAS can find
302 the requested service number in the preceding History-Info entry.
303
304 If the History-Info header is not supported or has been removed by a
305 proxy for any reason, the UAS might be able to find the requested
306 service access number before translation in either of the following
307 ways, but there is no guarantee:
308
309 o If the UAS is the direct target of the request coming from the
310 application, the UAS ought to be able to find the service access
311 number in the "target" URI parameter of the Request-URI if there
312 is also a "cause" URI parameter set to 380 in this Request-URI.
313
314 o If there is no "cause" URI parameter set to 380 in the Request-URI
315 and there is no History-Info header field, the UAS will not be
316 able to reliably retrieve the service access number before
317 translation. Some existing implementations are known to extract
318 the number from the To header field. While that approach may work
319 in some situations, it will not work in the general case because
320 the To header field value is sometimes changed by intermediaries,
321 and such a change is not always detectable.
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Mohali &amp; Barnes Informational [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
335
336
337 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Example</span>
338
339 In this section, an example is provided to illustrate the application
340 of the new cause-param value.
341
342 In this example, Alice calls her bank customer care. John is the
343 person at the call center that answers the call. John is in a call
344 center that manages several toll-free services, and he needs to know
345 for which service Alice is calling in order to provide the
346 appropriate welcome speech.
347
348 Alice Toll-Free Service Atlanta.com John
349 | | | |
350 | INVITE F1 | | |
351 |---------------&gt;| INVITE F2 | |
352 | |-------------&gt;| |
353 | | | INVITE F3 |
354 | | |------------------&gt;|
355
356 * Rest of flow not shown *
357
358 Figure 1: Service Access Number Translation Example
359
360 Message Details
361
362 F1 INVITE [2001:db8:9::2] -&gt; Toll-Free Service
363
364 In the initial request, the Request-URI contains the toll-free
365 number dialed by Alice.
366
367 INVITE sip:[email protected];user=phone SIP/2.0
368 Via: SIP/2.0/TCP [2001:db8:9::2]:5060;branch=z9hG4bK74bf
369 From: Alice &lt;sip:[email protected];user=phone&gt;;tag=9fxced76sl
370 To: &lt;sip:[email protected];user=phone&gt;
371 Call-ID: c3x842276298220188511
372 CSeq: 1 INVITE
373 Max-Forwards: 70
374 Contact: &lt;sip:alice@[2001:db8:9::2]&gt;
375 Content-Type: application/sdp
376 Content-Length: &lt;appropriate value&gt;
377
378 [SDP Not Shown]
379
380
381
382
383
384
385
386
387
388 <span class="grey">Mohali &amp; Barnes Informational [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
391
392
393 F2 INVITE Toll-Free Service -&gt; Atlanta.com
394
395 The toll-free application receives the request and translates
396 the service number into a routable number toward the call center.
397 The Request-URI is changed, and, in the new Request-URI, a
398 "cause" URI parameter set to 380 is added. As there was no
399 History-Info header field in the received request,
400 the application creates a History-Info header with two entries:
401 one for the received Request-URI and one for the new Request-URI.
402
403 INVITE sip:[email protected];cause=380;user=phone SIP/2.0
404 Via: SIP/2.0/TCP [2001:db8:a::2];branch=z9hG4bK-ik8
405 Via: SIP/2.0/TCP [2001:db8:9::2]:5060;branch=z9hG4bK74bf
406 From: Alice &lt;sip:[email protected];user=phone&gt;;tag=9fxced76sl
407 To: &lt;sip:[email protected];user=phone&gt;
408 Call-ID: c3x842276298220188511
409 CSeq: 1 INVITE
410 Max-Forwards: 69
411 Supported: histinfo
412 History-Info: &lt;sip:[email protected];user=phone&gt;;index=1
413 History-Info: &lt;sip:[email protected];cause=380;user=phone&gt;;
414 index=1.1;mp=1
415 Contact: &lt;sip:alice@[2001:db8:9::2]&gt;
416 Content-Type: application/sdp
417 Content-Length: &lt;appropriate value&gt;
418
419 [SDP Not Shown]
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 <span class="grey">Mohali &amp; Barnes Informational [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
447
448
449 F3 INVITE Atlanta.com -&gt; John
450
451 The call center proxy routes the received request to John's
452 IP address by changing the Request-URI. When changing the
453 Request-URI, the proxy adds a new entry in the History-Info
454 header field.
455
456 INVITE sip:john@[2001:db8:b::2] SIP/2.0
457 Via: SIP/2.0/TCP [2001:db8:b::3]:5060;branch=z9hG4bKpxk7g
458 Via: SIP/2.0/TCP [2001:db8:a::2];branch=z9hG4bK-ik8
459 Via: SIP/2.0/TCP [2001:db8:9::2]:5060;branch=z9hG4bK74bf
460 From: Alice &lt;sip:[email protected];user=phone&gt;;tag=9fxced76sl
461 To: &lt;sip:[email protected];user=phone&gt;
462 Call-ID: c3x842276298220188511
463 CSeq: 1 INVITE
464 Max-Forwards: 68
465 Supported: histinfo
466 History-Info: &lt;sip:[email protected];user=phone&gt;;index=1
467 History-Info: &lt;sip:[email protected];cause=380;user=phone&gt;;
468 index=1.1;mp=1
469 History-Info: &lt;sip:john@[2001:db8:b::2]&gt;;index=1.1.1;rc=1.1
470 Contact: &lt;sip:alice@[2001:db8:9::2]&gt;
471 Content-Type: application/sdp
472 Content-Length: &lt;appropriate value&gt;
473
474 [SDP Not Shown]
475
476 NOTE: Line breaks are for display purpose only
477
478 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
479
480 [<a id="ref-RFC4458">RFC4458</a>] defines a "cause" URI parameter specified as having
481 predefined values. This document defines a new value for the "cause"
482 URI parameter: 380.
483
484 IANA has modified the existing row for the "cause" URI parameter to
485 add a reference to this document under the "SIP/SIPS URI Parameters"
486 subregistry within the "Session Initiation Protocol (SIP) Parameters"
487 registry:
488
489 Parameter Name Predefined Values Reference
490 -------------- ----------------- ----------------------
491 cause Yes [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>][RFC8119]
492
493
494
495
496
497
498
499
500 <span class="grey">Mohali &amp; Barnes Informational [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
503
504
505 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
506
507 The security considerations in [<a href="./rfc4458" title="&quot;Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)&quot;">RFC4458</a>] apply.
508
509 If a privacy level of 'header' is requested in the Privacy header
510 field as described in [<a href="./rfc3323" title="&quot;A Privacy Mechanism for the Session Initiation Protocol (SIP)&quot;">RFC3323</a>], the "cause" URI parameter must be
511 removed from the Request-URI to maintain the network-provided privacy
512 requested. Privacy of the parameters, when they form part of a URI
513 within the History-Info header field, is covered in [<a href="./rfc7044" title="&quot;An Extension to the Session Initiation Protocol (SIP) for Request History Information&quot;">RFC7044</a>].
514
515 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
516
517 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
518
519 [<a id="ref-RFC3261">RFC3261</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
520 A., Peterson, J., Sparks, R., Handley, M., and E.
521 Schooler, "SIP: Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>,
522 DOI 10.17487/RFC3261, June 2002,
523 &lt;<a href="http://www.rfc-editor.org/info/rfc3261">http://www.rfc-editor.org/info/rfc3261</a>&gt;.
524
525 [<a id="ref-RFC3323">RFC3323</a>] Peterson, J., "A Privacy Mechanism for the Session
526 Initiation Protocol (SIP)", <a href="./rfc3323">RFC 3323</a>,
527 DOI 10.17487/RFC3323, November 2002,
528 &lt;<a href="http://www.rfc-editor.org/info/rfc3323">http://www.rfc-editor.org/info/rfc3323</a>&gt;.
529
530 [<a id="ref-RFC3326">RFC3326</a>] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason
531 Header Field for the Session Initiation Protocol (SIP)",
532 <a href="./rfc3326">RFC 3326</a>, DOI 10.17487/RFC3326, December 2002,
533 &lt;<a href="http://www.rfc-editor.org/info/rfc3326">http://www.rfc-editor.org/info/rfc3326</a>&gt;.
534
535 [<a id="ref-RFC7044">RFC7044</a>] Barnes, M., Audet, F., Schubert, S., van Elburg, J., and
536 C. Holmberg, "An Extension to the Session Initiation
537 Protocol (SIP) for Request History Information", <a href="./rfc7044">RFC 7044</a>,
538 DOI 10.17487/RFC7044, February 2014,
539 &lt;<a href="http://www.rfc-editor.org/info/rfc7044">http://www.rfc-editor.org/info/rfc7044</a>&gt;.
540
541 [<a id="ref-TS.3GPP.24.229">TS.3GPP.24.229</a>]
542 3GPP, "IP multimedia call control protocol based on
543 Session Initiation Protocol (SIP) and Session Description
544 Protocol (SDP); Stage 3", 3GPP TS 24.229 13.6.0.0, January
545 2015.
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Mohali &amp; Barnes Informational [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
559
560
561 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
562
563 [<a id="ref-Err1409">Err1409</a>] RFC Errata, Erratum ID 1409, <a href="./rfc4458">RFC 4458</a>.
564
565 [<a id="ref-ITU-T_I.312_Q.1201">ITU-T_I.312_Q.1201</a>]
566 ITU-T, "Principles of Intelligent Network Architecture",
567 ITU-T Recommendation I312/Q.1201, October 1992.
568
569 [<a id="ref-ITU-T_Q.1214">ITU-T_Q.1214</a>]
570 ITU-T, "Distributed Functional Plane For Intellignet
571 Network CS-1", ITU-T Recommendation Q.1214, October 1995.
572
573 [<a id="ref-ITU-T_Q.763">ITU-T_Q.763</a>]
574 ITU-T, "Signalling System No. 7 -- ISDN User Part formats
575 and codes", ITU-T Recommendation Q.763, December 1999.
576
577 [<a id="ref-RFC4458">RFC4458</a>] Jennings, C., Audet, F., and J. Elwell, "Session
578 Initiation Protocol (SIP) URIs for Applications such as
579 Voicemail and Interactive Voice Response (IVR)", <a href="./rfc4458">RFC 4458</a>,
580 DOI 10.17487/RFC4458, April 2006,
581 &lt;<a href="http://www.rfc-editor.org/info/rfc4458">http://www.rfc-editor.org/info/rfc4458</a>&gt;.
582
583 [<a id="ref-RFC5234">RFC5234</a>] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
584 Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>,
585 DOI 10.17487/RFC5234, January 2008,
586 &lt;<a href="http://www.rfc-editor.org/info/rfc5234">http://www.rfc-editor.org/info/rfc5234</a>&gt;.
587
588 Acknowledgements
589
590 The authors wish to thank the 3GPP community for providing guidance,
591 input, and comments on the document. Thanks also to Paul Kyzivat,
592 Dale Worley, Jean Mahoney, Robert Sparks, Joel Halpern, and Lionel
593 Morand for their detailed reviews of the document. Special thanks to
594 Ben Campbell for his help to make the work progress.
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Mohali &amp; Barnes Informational [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc8119">RFC 8119</a> Cause for Service Number Translation March 2017</span>
615
616
617 Authors' Addresses
618
619 Marianne Mohali
620 Orange
621 44 Avenue de la Republique
622 Chatillon 92320
623 France
624
625 Email: [email protected]
626
627
628 Mary Barnes
629 MLB@Realtime Communications
630 TX
631 United States of America
632
633 Email: [email protected]
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668 Mohali &amp; Barnes Informational [Page 12]
669 </pre>