Debian Codegraph @

rfc3959.html

raw
1 <pre>Network Working Group G. Camarillo
2 Request for Comments: 3959 Ericsson
3 Category: Standards Track December 2004
4
5
6 <span class="h1">The Early Session Disposition Type for</span>
7 <span class="h1">the Session Initiation Protocol (SIP)</span>
8
9 Status of This Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Copyright Notice
18
19 Copyright (C) The Internet Society (2004).
20
21 Abstract
22
23 This document defines a new disposition type (early-session) for the
24 Content-Disposition header field in the Session Initiation Protocol
25 (SIP). The treatment of "early-session" bodies is similar to the
26 treatment of "session" bodies. That is, they follow the offer/answer
27 model. Their only difference is that session descriptions whose
28 disposition type is "early-session" are used to establish early media
29 sessions within early dialogs, as opposed to regular sessions within
30 regular dialogs.
31
32 Table of Contents
33
34 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
35 <a href="#section-2">2</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
36 <a href="#section-3">3</a>. Issues Related to Early Media Session Establishment . . . . . <a href="#page-2">2</a>
37 <a href="#section-4">4</a>. The Early Session Disposition Type . . . . . . . . . . . . . . <a href="#page-4">4</a>
38 <a href="#section-5">5</a>. Preconditions . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
39 <a href="#section-6">6</a>. Option tag . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
40 <a href="#section-7">7</a>. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
41 <a href="#section-8">8</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
42 <a href="#section-9">9</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
43 <a href="#section-10">10</a>. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
44 <a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
45 <a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
46 <a href="#section-11.2">11.2</a>. Informational References . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
47 Author's Address . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
48 Full Copyright Statement . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
49
50
51
52 <span class="grey">Camarillo Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
55
56
57 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
58
59 Early media refers to media (e.g., audio and video) that is exchanged
60 before a particular session is accepted by the called user. Within a
61 dialog, early media occurs from the moment the initial INVITE is sent
62 until the User Agent Server (UAS) generates a final response. It may
63 be unidirectional or bidirectional, and can be generated by the
64 caller, the callee, or both. Typical examples of early media
65 generated by the callee are ringing tone and announcements (e.g.,
66 queuing status). Early media generated by the caller typically
67 consists of voice commands or dual tone multi-frequency (DTMF) tones
68 to drive interactive voice response (IVR) systems.
69
70 The basic SIP specification (<a href="./rfc3261">RFC 3261</a> [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>]) only supports very simple
71 early media mechanisms. These simple mechanisms have a number of
72 problems related to forking and security, and do not satisfy the
73 requirements of most applications. <a href="./rfc3960">RFC 3960</a> [<a href="#ref-8" title="&quot;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)&quot;">8</a>] goes beyond the
74 mechanisms defined in <a href="./rfc3261">RFC 3261</a> [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>] and describes two models of early
75 media using SIP: the gateway model and the application server model.
76
77 Although both early media models described in <a href="./rfc3960">RFC 3960</a> [<a href="#ref-8" title="&quot;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)&quot;">8</a>] are
78 superior to the one specified in <a href="./rfc3261">RFC 3261</a> [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>], the gateway model
79 still presents a set of issues. In particular, the gateway model
80 does not work well with forking. Nevertheless, the gateway model is
81 needed because some SIP entities (in particular, some gateways)
82 cannot implement the application server model.
83
84 The application server model addresses some of the issues present in
85 the gateway model. This model uses the early-session disposition
86 type specified in this document.
87
88 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span>
89
90 In this document, the key words "MUST", "MUST NOT", "REQUIRED",
91 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
92 RECOMMENDED", "MAY", and "OPTIONAL" are to be interpreted as
93 described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a> [<a href="#ref-1" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">1</a>] and indicate requirement levels for
94 compliant implementations.
95
96 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Issues Related to Early Media Session Establishment</span>
97
98 Traditionally, early media sessions have been established in the same
99 way as regular sessions. That is, using an offer/answer exchange
100 where the disposition type of the session descriptions is "session".
101 Application servers perform an offer/answer exchange with the User
102 Agent Client (UAC) to exchange early media exclusively, while UASs
103 use the same offer/answer exchange, first to exchange early media,
104 and once the regular dialog is established, to exchange regular
105
106
107
108 <span class="grey">Camarillo Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
111
112
113 media. This way of establishing early media sessions is known as the
114 gateway model [<a href="#ref-8" title="&quot;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)&quot;">8</a>], which presents some issues related to forking and
115 security. These issues exist when this model is used by either an
116 application server or by a UAS.
117
118 Application servers may not be able to generate an answer for an
119 offer received in the INVITE. The UAC created the offer for the UAS,
120 and so, it may have applied end-to-end encryption or have included
121 information (e.g., related to key management) that the application
122 server is not supposed to use. Therefore, application servers need a
123 means to perform an offer/answer exchange with the UAC that is
124 independent from the offer/answer exchange between both UAs.
125
126 UASs using the offer/answer exchange that will carry regular media
127 for sending and receiving early media can cause media clipping, as
128 described in Section 2.1.1 of [<a href="#ref-8" title="&quot;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)&quot;">8</a>]. Some UACs cannot receive early
129 media from different UASs at the same time. So, when an INVITE forks
130 and several UASs start sending early media, the UAC mutes all the
131 UASs but one (which is usually chosen at random). If the UAS that
132 accepts the INVITE (i.e., sends a 200 OK) was muted, a new
133 offer/answer exchange is needed to unmute it. This usually causes
134 media clipping. Therefore, UASs need a means of performing an
135 offer/answer exchange with the UAC to exchange early media that is
136 independent from the offer/answer exchanged used to exchange regular
137 media.
138
139 A potential solution to this need would be to establish a different
140 dialog using a globally routable URI to perform an independent
141 offer/answer exchange. This dialog would be labelled as a dialog for
142 early media and would be somehow related to the original dialog at
143 the UAC. However, performing all the offer/answer exchanges within
144 the original dialog has many advantages:
145
146 o It is simpler.
147
148 o It does not have synchronization problems, because all the early
149 dialogs are terminated when the session is accepted.
150
151 o It does not require globally routable URIs.
152
153 o It does not introduce service interaction issues related to
154 services that may be wrongly applied to the new dialog.
155
156 o It makes firewall management easier.
157
158 This way of performing offer/answer exchanges for early media is
159 referred to as the application server model [<a href="#ref-8" title="&quot;Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)&quot;">8</a>]. This model uses the
160 early-session disposition type defined in the following section.
161
162
163
164 <span class="grey">Camarillo Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
167
168
169 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. The Early Session Disposition Type</span>
170
171 We define a new disposition type for the Content-Disposition header
172 field: early-session. User agents MUST use early-session bodies to
173 establish early media sessions in the same way as they use session
174 bodies to establish regular sessions, as described in RFCs 3261 [<a href="#ref-2" title="&quot;SIP: Session Initiation Protocol&quot;">2</a>]
175 and 3264 [<a href="#ref-3" title="&quot;An Offer/Answer Model with Session Description Protocol (SDP)&quot;">3</a>]. Particularly, early-session bodies MUST follow the
176 offer/answer model and MAY appear in the same messages as session
177 bodies do with the exceptions of 2xx responses for an INVITE and
178 ACKs. Nevertheless, it is NOT RECOMMENDED that early offers in
179 INVITEs be included because they can fork, and the UAC could receive
180 multiple early answers establishing early media streams at roughly
181 the same time. Also, the use of the same transport address (IP
182 address plus port) in a session body and in an early-session body is
183 NOT RECOMMENDED. Using different transport addresses (e.g.,
184 different ports) to receive early and regular media makes it easy to
185 detect the start of the regular media.
186
187 If a User Agent (UA) needs to refuse an early-session offer, it MUST
188 do so by refusing all the media streams in it. When SDP [<a href="#ref-7" title="&quot;SDP: Session Description Protocol&quot;">7</a>] is used,
189 this is done by setting the port number of all the media streams to
190 zero.
191
192 This is the same mechanism that UACs use to refuse regular offers
193 that arrive in a response to an empty INVITE.
194
195 An early media session established using early-session bodies MUST be
196 terminated when its corresponding early dialog is terminated or it
197 transitions to a regular dialog.
198
199 It is RECOMMENDED that UAs generating regular and early session
200 descriptions use, as long as it is possible, the same codecs in both.
201 This way, the remote UA does not need to change codecs when the early
202 session transitions to a regular session.
203
204 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Preconditions</span>
205
206 <a href="./rfc3312">RFC 3312</a> [<a href="#ref-4" title="&quot;Integration of Resource Management and Session Initiation Protocol (SIP)&quot;">4</a>] defines a framework for preconditions for SDP. Early-
207 sessions MAY contain preconditions, which are treated in the same way
208 as preconditions in regular sessions. That is, the UAs do not
209 exchange media, and the called user is not alerted until the
210 preconditions are met.
211
212
213
214
215
216
217
218
219
220 <span class="grey">Camarillo Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
223
224
225 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Option Tag</span>
226
227 We define an option tag to be used in Require and Supported header
228 fields: early-session. A UA adding the early-session option tag to a
229 message indicates that it understands the early-session disposition
230 type.
231
232 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Example</span>
233
234 Figure 1 shows the message flow between two UAs. INVITE (1) has an
235 early-session option tag in its Supported header field and the body
236 shown in Figure 2. The UAS sends back a response with two body
237 parts, as shown in Figure 3: one of disposition type session and the
238 other early-session. The session body part is the answer to the
239 offer in the INVITE. The early-session body part is an offer to
240 establish an early media session. When the UAC receives the 183
241 (Session Progress) response, it sends the answer to the early-session
242 offer in a PRACK, as shown in Figure 4. This early media session is
243 terminated when the early dialog transitions to a regular dialog.
244 That is, when the UAS sends the (5) 200 (OK) response for the INVITE.
245
246 A B
247 | |
248 |--------(1) INVITE--------&gt;|
249 | offer |
250 | |
251 |&lt;--(2) Session Progress----|
252 | early-offer |
253 | answer |
254 | |
255 |---------(3) PRACK--------&gt;|
256 | early-answer |
257 | |
258 |&lt;--------(4) 200 OK--------|
259 | |
260 | * * |
261 | ************************* |
262 |* Early Media *|
263 | ************************* |
264 | * * |
265 | |
266 |&lt;--------(5) 200 OK--------|
267 | |
268 |----------(6) ACK---------&gt;|
269 | |
270
271 Figure 1: Message flow
272
273
274
275
276 <span class="grey">Camarillo Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
279
280
281 Content-Type: application/sdp
282 Content-Disposition: session
283
284 v=0
285 o=alice 2890844730 2890844731 IN IP4 host.example.com
286 s=
287 c=IN IP4 192.0.2.1
288 t=0 0
289 m=audio 20000 RTP/AVP 0
290
291 Figure 2: Offer
292
293
294 Content-Type: multipart/mixed; boundary="boundary1"
295 Content-Length: 401
296
297 --boundary1
298 Content-Type: application/sdp
299 Content-Disposition: session
300
301 v=0
302 o=Bob 2890844725 2890844725 IN IP4 host.example.org
303 s=
304 c=IN IP4 192.0.2.2
305 t=0 0
306 m=audio 30000 RTP/AVP 0
307
308 --boundary1
309 Content-Type: application/sdp
310 Content-Disposition: early-session
311
312 v=0
313 o=Bob 2890844714 2890844714 IN IP4 host.example.org
314 s=
315 c=IN IP4 192.0.2.2
316 t=0 0
317 m=audio 30002 RTP/AVP 0
318
319 --boundary1--
320
321 Figure 3: Early offer and answer
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Camarillo Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
335
336
337 Content-Type: application/sdp
338 Content-Disposition: early-session
339
340 v=0
341 o=alice 2890844717 2890844717 IN IP4 host.example.com
342 s=
343 c=IN IP4 192.0.2.1
344 t=0 0
345 m=audio 20002 RTP/AVP 0
346
347 Figure 4: Early answer
348
349 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
350
351 The security implications of using early-session bodies in SIP are
352 the same as when using session bodies; they are part of the
353 offer/answer model.
354
355 SIP uses the offer/answer model [<a href="#ref-3" title="&quot;An Offer/Answer Model with Session Description Protocol (SDP)&quot;">3</a>] to establish early sessions in
356 both the gateway and the application server models. User Agents
357 (UAs) generate a session description, which contains the transport
358 address (i.e., IP address plus port) where they want to receive
359 media, and send it to their peer in a SIP message. When media
360 packets arrive at this transport address, the UA assumes that they
361 come from the receiver of the SIP message carrying the session
362 description. Nevertheless, attackers may attempt to gain access to
363 the contents of the SIP message and send packets to the transport
364 address contained in the session description. To prevent this
365 situation, UAs SHOULD encrypt their session descriptions (e.g., using
366 S/MIME).
367
368 Still, even if a UA encrypts its session descriptions, an attacker
369 may try to guess the transport address used by the UA and send media
370 packets to that address. Guessing such a transport address is
371 sometimes easier than it may seem because many UAs always pick up the
372 same initial media port. To prevent this situation, UAs SHOULD use
373 media-level authentication mechanisms (e.g., Secure Realtime
374 Transport Protocol (SRTP)[<a href="#ref-6" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">6</a>]). In addition, UAs that wish to keep
375 their communications confidential SHOULD use media-level encryption
376 mechanisms (e.g, SRTP [<a href="#ref-6" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">6</a>]).
377
378 Attackers may attempt to make a UA send media to a victim as part of
379 a DoS attack. This can be done by sending a session description with
380 the victim's transport address to the UA. To prevent this attack,
381 the UA SHOULD engage in a handshake with the owner of the transport
382 address received in a session description (just verifying willingness
383 to receive media) before sending a large amount of data to the
384 transport address. This check can be performed by using a connection
385
386
387
388 <span class="grey">Camarillo Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
391
392
393 oriented transport protocol, by using Simple Traversal of the UDP
394 Protocol through NAT (STUN)[<a href="#ref-5" title="&quot;STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)&quot;">5</a>] in an end-to-end fashion, or by the
395 key exchange in SRTP [<a href="#ref-6" title="&quot;The Secure Real-time Transport Protocol (SRTP)&quot;">6</a>].
396
397 In any event, note that the previous security considerations are not
398 early media specific, but apply to the usage of the offer/answer
399 model in SIP to establish sessions in general.
400
401 Additionally, an early media-specific risk (roughly speaking, an
402 equivalent to forms of "toll fraud" in the Public Switched Telephone
403 Network (PSTN)) attempts to exploit the different charging policies
404 some operators apply to early and to regular media. When UAs are
405 allowed to exchange early media for free, but are required to pay for
406 regular media sessions, rogue UAs may try to establish a
407 bidirectional early media session and never send a 2xx response for
408 the INVITE.
409
410 On the other hand, some application servers (e.g., Interactive Voice
411 Response systems) use bidirectional early media to obtain information
412 from the callers (e.g., the Personal Identification Number (PIN) code
413 of a calling card). So, we do not recommend that operators disallow
414 bidirectional early media. Instead, operators should consider a
415 remedy of charging early media exchanges that last too long, or
416 stopping them at the media level (according to the operator's
417 policy).
418
419 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
420
421 This document defines a new Content-Disposition header field
422 disposition type (early-session) in <a href="#section-4">Section 4</a>. This value has been
423 registered in the IANA registry for Content-Dispositions with the
424 following description:
425
426 early-session The body describes an early communications
427 session, for example, an <a href="./rfc2327">RFC 2327</a> SDP body
428
429 This document defines a SIP option tag (early-session) in <a href="#section-6">Section 6</a>.
430 It has been registered in the SIP parameters registry
431 (<a href="http://www.iana.org/assignments/sip-parameters">http://www.iana.org/assignments/sip-parameters</a>) under "Option Tags",
432 with the following description.
433
434 early-session A UA adding the early-session option tag to a
435 message indicates that it understands the early-
436 session content disposition.
437
438
439
440
441
442
443
444 <span class="grey">Camarillo Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
447
448
449 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgements</span>
450
451 Francois Audet, Christer Holmberg, and Allison Mankin provided useful
452 comments on this document.
453
454 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
455
456 <span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
457
458 [<a id="ref-1">1</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
459 Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
460
461 [<a id="ref-2">2</a>] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
462 Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
463 Session Initiation Protocol", <a href="./rfc3261">RFC 3261</a>, June 2002.
464
465 [<a id="ref-3">3</a>] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
466 Session Description Protocol (SDP)", <a href="./rfc3264">RFC 3264</a>, June 2002.
467
468 [<a id="ref-4">4</a>] Camarillo, G., Marshall, W., and J. Rosenberg, "Integration of
469 Resource Management and Session Initiation Protocol (SIP)", <a href="./rfc3312">RFC</a>
470 <a href="./rfc3312">3312</a>, October 2002.
471
472 [<a id="ref-5">5</a>] Rosenberg, J., Weinberger, J., Huitema, C., and R. Mahy,
473 "STUN - Simple Traversal of User Datagram Protocol (UDP) Through
474 Network Address Translators (NATs)", <a href="./rfc3489">RFC 3489</a>, March 2003.
475
476 [<a id="ref-6">6</a>] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
477 Norrman, "The Secure Real-time Transport Protocol (SRTP)", <a href="./rfc3711">RFC</a>
478 <a href="./rfc3711">3711</a>, March 2004.
479
480 <span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informational References</span>
481
482 [<a id="ref-7">7</a>] Handley, M. and V. Jacobson, "SDP: Session Description
483 Protocol", <a href="./rfc2327">RFC 2327</a>, April 1998.
484
485 [<a id="ref-8">8</a>] Camarillo, G. and H. Schulzrinne, "Early Media and Ringing Tone
486 Generation in the Session Initiation Protocol (SIP)", <a href="./rfc3960">RFC 3960</a>,
487 December 2004.
488
489
490
491
492
493
494
495
496
497
498
499
500 <span class="grey">Camarillo Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
503
504
505 Author's Address
506
507 Gonzalo Camarillo
508 Ericsson
509 Hirsalantie 11
510 Jorvas 02420
511 Finland
512
513 EMail: [email protected]
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Camarillo Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc3959">RFC 3959</a> Early Session Disposition Type December 2004</span>
559
560
561 Full Copyright Statement
562
563 Copyright (C) The Internet Society (2004).
564
565 This document is subject to the rights, licenses and restrictions
566 contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
567 retain all their rights.
568
569 This document and the information contained herein are provided on an
570 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
571 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
572 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
573 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
574 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
575 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
576
577 Intellectual Property
578
579 The IETF takes no position regarding the validity or scope of any
580 Intellectual Property Rights or other rights that might be claimed to
581 pertain to the implementation or use of the technology described in
582 this document or the extent to which any license under such rights
583 might or might not be available; nor does it represent that it has
584 made any independent effort to identify any such rights. Information
585 on the IETF's procedures with respect to rights in IETF Documents can
586 be found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
587
588 Copies of IPR disclosures made to the IETF Secretariat and any
589 assurances of licenses to be made available, or the result of an
590 attempt made to obtain a general license or permission for the use of
591 such proprietary rights by implementers or users of this
592 specification can be obtained from the IETF on-line IPR repository at
593 <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
594
595 The IETF invites any interested party to bring to its attention any
596 copyrights, patents or patent applications, or other proprietary
597 rights that may cover technology that may be required to implement
598 this standard. Please address the information to the IETF at ietf-
599 [email protected].
600
601 Acknowledgement
602
603 Funding for the RFC Editor function is currently provided by the
604 Internet Society.
605
606
607
608
609
610
611
612 Camarillo Standards Track [Page 11]
613 </pre>