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
502
503
504
505
506
507
508
509
510
511
512
513
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
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
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
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
|
<pre>Network Working Group G. Camarillo
Request for Comments: 5366 Ericsson
Category: Standards Track A. Johnston
Avaya
October 2008
<span class="h1">Conference Establishment Using Request-Contained Lists</span>
<span class="h1">in the Session Initiation Protocol (SIP)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
This document describes how to create a conference using SIP URI-list
services. In particular, it describes a mechanism that allows a User
Agent Client to provide a conference server with the initial list of
participants using an INVITE-contained URI list.
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-2">2</a>
<a href="#section-3">3</a>. User Agent Client Procedures ....................................<a href="#page-2">2</a>
<a href="#section-3.1">3.1</a>. Response Handling ..........................................<a href="#page-2">2</a>
<a href="#section-3.2">3.2</a>. Re-INVITE Request Generation ...............................<a href="#page-3">3</a>
<a href="#section-4">4</a>. URI-List Document Format ........................................<a href="#page-3">3</a>
<a href="#section-5">5</a>. Conference Server Procedures ....................................<a href="#page-5">5</a>
<a href="#section-5.1">5.1</a>. Re-INVITE Request Handling .................................<a href="#page-6">6</a>
<a href="#section-6">6</a>. Example .........................................................<a href="#page-6">6</a>
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-10">10</a>
<a href="#section-8">8</a>. IANA Considerations ............................................<a href="#page-10">10</a>
<a href="#section-9">9</a>. Acknowledgments ................................................<a href="#page-11">11</a>
<a href="#section-10">10</a>. References ....................................................<a href="#page-11">11</a>
<a href="#section-10.1">10.1</a>. Normative References .....................................<a href="#page-11">11</a>
<a href="#section-10.2">10.2</a>. Informative References ...................................<a href="#page-12">12</a>
<span class="grey">Camarillo & Johnston Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
<a href="./rfc4579#section-5.4">Section 5.4 of [RFC4579]</a> describes how to create a conference using
ad hoc SIP [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>] methods. The client sends an INVITE request to
a conference factory URI and receives the actual conference URI,
which contains the "isfocus" feature tag, in the Contact header field
of a response -- typically a 200 (OK) response.
Once the UAC (User Agent Client) obtains the conference URI, it can
add participants to the newly created conference in several ways,
which are described in [<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>].
Some environments have tough requirements regarding conference
establishment time. They require the UAC to be able to request the
creation of an ad hoc conference and to provide the conference server
with the initial set of participants in a single operation. This
document describes how to meet this requirement using the mechanism
to transport URI lists in SIP messages described in [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</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" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. User Agent Client Procedures</span>
A UAC that wants to include the set of initial participants in its
initial INVITE request to create an ad hoc conference adds a body
whose disposition type is 'recipient-list', as defined in [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</a>],
with a URI list that contains the participants that the UAC wants the
conference server to invite. Additionally, the UAC MUST include the
'recipient-list-invite' option-tag (which is registered with the IANA
in <a href="#section-8">Section 8</a>) in a Require header field. The UAC sends this INVITE
request to the conference factory URI.
The INVITE transaction is also part of an offer/answer exchange that
will establish a session between the UAC and the conference server,
as specified in [<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>]. Therefore, the INVITE request may need to
carry a multipart body: a session description and a URI list.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Response Handling</span>
The status code in the response to the INVITE request does not
provide any information about whether or not the conference server
was able to bring the users in the URI list into the conference.
That is, a 200 (OK) response means that the conference was created
successfully, that the UAC that generated the INVITE request is in
<span class="grey">Camarillo & Johnston Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
the conference, and that the server understood the URI list. If the
UAC wishes to obtain information about the status of other users in
the conference, it SHOULD use general conference mechanisms, such as
the conference package, which is defined in [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>].
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Re-INVITE Request Generation</span>
The previous sections have specified how to include a URI list in an
initial INVITE request to a conference server. Once the INVITE-
initiated dialog between the UAC and the conference server has been
established, the UAC can send subsequent INVITE requests (typically
referred to as re-INVITE requests) to the conference server to, for
example, modify the characteristics of the media exchanged with the
server.
At this point, there are no semantics associated with 'recipient-
list' bodies in re-INVITE requests (although future extensions may
define them). Therefore, UACs SHOULD NOT include 'recipient-list'
bodies in re-INVITE requests sent to a conference server.
Note that a difference between an initial INVITE request and a
re-INVITE request is that while the initial INVITE request is sent
to the conference factory URI, the re-INVITE request is sent to
the URI provided by the server in a Contact header field when the
dialog was established. Therefore, from the UAC's point of view,
the resource identified by the former URI supports 'recipient-
list' bodies, while the resource identified by the latter does not
support them.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. URI-List Document Format</span>
As described in [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</a>], specifications of individual URI-list
services, like the conferencing service described here, need to
specify a default format for 'recipient-list' bodies used within the
particular service.
The default format for 'recipient-list' bodies for conferencing UAs
(User Agents) is the XML resource list format (which is specified in
[<a href="./rfc4826" title=""Extensible Markup Language (XML) Formats for Representing Resource Lists"">RFC4826</a>]) extended with the "Extensible Markup Language (XML) Format
Extension for Representing Copy Control Attributes in Resource Lists"
[<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>]. Consequently, conferencing UACs generating 'recipient-
list' bodies MUST support both of these formats and MAY support other
formats. Conferencing servers able to handle 'recipient-list' bodies
MUST support both of these formats and MAY support other formats.
As described in "Extensible Markup Language (XML) Format Extension
for Representing Copy Control Attributes in Resource Lists"
[<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>], each URI can be tagged with a 'copyControl' attribute set
<span class="grey">Camarillo & Johnston Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
to either "to", "cc", or "bcc", indicating the role in which the
recipient will get the INVITE request. Additionally, URIs can be
tagged with the 'anonymize' attribute to prevent the conference
server from disclosing the target URI in a URI list.
In addition, "Extensible Markup Language (XML) Format Extension for
Representing Copy Control Attributes in Resource Lists" [<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>]
defines a 'recipient-list-history' body that contains the list of
recipients. The default format for 'recipient-list-history' bodies
for conferencing UAs is also the XML resource list document format
specified in [<a href="./rfc4826" title=""Extensible Markup Language (XML) Formats for Representing Resource Lists"">RFC4826</a>] extended with "Extensible Markup Language
(XML) Format Extension for Representing Copy Control Attributes in
Resource Lists" [<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>]. Consequently, conferencing UACs able to
generate 'recipient-list-history' bodies MUST support these formats
and MAY support others. Conferencing UAs able to understand
'recipient-list-history' MUST support these formats and MAY support
others. Conferencing servers able to handle 'recipient-list-history'
bodies MUST support these formats and MAY support others.
Nevertheless, the XML resource list document specified in [<a href="./rfc4826" title=""Extensible Markup Language (XML) Formats for Representing Resource Lists"">RFC4826</a>]
provides features, such as hierarchical lists and the ability to
include entries by reference relative to the XML Configuration Access
Protocol (XCAP) root URI, that are not needed by the conferencing
service defined in this document, which only needs to transfer a flat
list of URIs between a UA (User Agent) and the conference server.
Therefore, when using the default resource list document,
conferencing UAs SHOULD use flat lists (i.e., no hierarchical lists)
and SHOULD NOT use <entry-ref> elements. A conference factory
application receiving a URI list with more information than what has
just been described MAY discard all the extra information.
Figure 1 shows an example of a flat list that follows the XML
resource list document (specified in [<a href="./rfc4826" title=""Extensible Markup Language (XML) Formats for Representing Resource Lists"">RFC4826</a>]) extended with
"Extensible Markup Language (XML) Format Extension for Representing
Copy Control Attributes in Resource Lists" [<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>].
<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"
xmlns:cp="urn:ietf:params:xml:ns:copycontrol">
<list>
<entry uri="sip:bill@example.com" cp:copyControl="to" />
<entry uri="sip:joe@example.org" cp:copyControl="cc" />
<entry uri="sip:ted@example.net" cp:copyControl="bcc" />
</list>
</resource-lists>
Figure 1: URI list
<span class="grey">Camarillo & Johnston Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Conference Server Procedures</span>
Conference servers that are able to receive and process INVITE
requests with a 'recipient-list' body SHOULD include a 'recipient-
list-invite' option-tag in a Supported header field when responding
to OPTIONS requests.
On reception of an INVITE request containing a 'recipient-list' body
as described in <a href="#section-3">Section 3</a>, a conference server MUST follow the rules
described in [<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>] to create ad hoc conferences. Once the ad hoc
conference is created, the conference server SHOULD attempt to add
the participants in the URI list to the conference as if their
addition had been requested using any of the methods described in
[<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>].
The INVITE transaction is also part of an offer/answer exchange that
will establish a session between the UAC and the conference server,
as specified in [<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>]. Therefore, the INVITE request may carry a
multipart body: a session description and a URI list.
Once the conference server has created the ad hoc conference and has
attempted to add the initial set of participants, the conference
server behaves as a regular conference server and MUST follow the
rules in [<a href="./rfc4579" title=""Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents"">RFC4579</a>].
The incoming INVITE request will contain a URI-list body or reference
(as specified in [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</a>]) with the actual list of recipients. If
this URI list includes resources tagged with the 'copyControl'
attribute set to a value of "to" or "cc", the conference server
SHOULD include a URI list in each of the outgoing INVITE requests.
This list SHOULD be formatted according to the XML format for
representing resource lists (specified in [<a href="./rfc4826" title=""Extensible Markup Language (XML) Formats for Representing Resource Lists"">RFC4826</a>]) and the
copyControl extension specified in [<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>].
The URI-list service MUST follow the procedures specified in
[<a href="./rfc5364" title=""Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists"">RFC5364</a>] with respect to the handling of the 'anonymize', 'count',
and 'copyControl' attributes.
If the conference server includes a URI list in an outgoing INVITE
request, it MUST include a Content-Disposition header field (which is
specified in [<a href="./rfc2183" title=""Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field"">RFC2183</a>]) with the value set to 'recipient-list-
history' and a 'handling' parameter (as specified in [<a href="./rfc3204" title=""MIME media types for ISUP and QSIG Objects"">RFC3204</a>]) set
to "optional".
<span class="grey">Camarillo & Johnston Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Re-INVITE Request Handling</span>
At this point, there are no semantics associated with 'recipient-
list' bodies in re-INVITE requests (although future extensions may
define them). Therefore, a conference server receiving a re-INVITE
request with a 'recipient-list' body and, consequently, a
'recipient-list-invite' option-tag, following standard SIP
procedures, rejects it with a 420 (Bad Extension), which carries an
Unsupported header field listing the 'recipient-list-invite' option-
tag.
This is because the resource identified by the conference URI does
not actually support this extension. On the other hand, the
resource identified by the conference factory URI does support
this extension and, consequently, would include the 'recipient-
list-invite' option-tag in, for example, responses to OPTIONS
requests.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Example</span>
Figure 2 shows an example of operation. A UAC sends an INVITE
request (F1) that contains an SDP body and a URI list to the
conference server. The conference server answers with a 200 (OK)
response and generates an INVITE request to each of the UASs (User
Agent Servers) identified by the URIs included in the URI list. The
conference server includes SDP and a manipulated URI list in each of
the outgoing INVITE requests.
<span class="grey">Camarillo & Johnston Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
+--------+ +---------+ +--------+ +--------+ +--------+
|SIP UAC | | confer. | |SIP UAS | |SIP UAS | |SIP UAS |
| | | server | | 1 | | 2 | | n |
+--------+ +---------+ +--------+ +--------+ +--------+
| | | | |
| F1 INVITE | | | |
| ---------------->| | | |
| F2 200 OK | | | |
|<---------------- | F3 INVITE | | |
| | ------------->| | |
| | F4 INVITE | | |
| | ------------------------>| |
| | F5 INVITE | | |
| | ----------------------------------->|
| | F6 200 OK | | |
| |<------------- | | |
| | F7 200 OK | | |
| |<------------------------ | |
| | F8 200 OK | | |
| |<----------------------------------- |
| | | | |
| | | | |
| | | | |
Figure 2: Example of operation
Figure 3 shows an example of the INVITE request F1, which carries a
multipart/mixed body composed of two other bodies: an application/sdp
body that describes the session and an application/resource-lists+xml
body that contains the list of target URIs.
INVITE sip:conf-fact@example.com SIP/2.0
Via: SIP/2.0/TCP atlanta.example.com
;branch=z9hG4bKhjhs8ass83
Max-Forwards: 70
To: "Conf Factory" <sip:conf-fact@example.com>
From: Alice <sip:alice@example.com>;tag=32331
Call-ID: d432fa84b4c76e66710
CSeq: 1 INVITE
Contact: <sip:alice@atlanta.example.com>
Allow: INVITE, ACK, CANCEL, BYE, REFER
Allow-Events: dialog
Accept: application/sdp, message/sipfrag
Require: recipient-list-invite
Content-Type: multipart/mixed;boundary="boundary1"
Content-Length: 690
<span class="grey">Camarillo & Johnston Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
--boundary1
Content-Type: application/sdp
v=0
o=alice 2890844526 2890842807 IN IP4 atlanta.example.com
s=-
c=IN IP4 192.0.2.1
t=0 0
m=audio 20000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
m=video 20002 RTP/AVP 31
a=rtpmap:31 H261/90000
--boundary1
Content-Type: application/resource-lists+xml
Content-Disposition: recipient-list
<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"
xmlns:cp="urn:ietf:params:xml:ns:copyControl">
<list>
<entry uri="sip:bill@example.com" cp:copyControl="to" />
<entry uri="sip:randy@example.net" cp:copyControl="to"
cp:anonymize="true"/>
<entry uri="sip:eddy@example.com" cp:copyControl="to"
cp:anonymize="true"/>
<entry uri="sip:joe@example.org" cp:copyControl="cc" />
<entry uri="sip:carol@example.net" cp:copyControl="cc"
cp:anonymize="true"/>
<entry uri="sip:ted@example.net" cp:copyControl="bcc" />
<entry uri="sip:andy@example.com" cp:copyControl="bcc" />
</list>
</resource-lists>
--boundary1--
Figure 3: INVITE request received at the conference server
The INVITE requests F3, F4, and F5 are similar in nature. All those
INVITE requests contain a multipart/mixed body that is composed of
two other bodies: an application/sdp body describing the session and
an application/resource-lists+xml containing the list of recipients.
The application/resource-lists+xml bodies are not equal to the
application/resource-lists+xml included in the received INVITE
request F1, because the conference server has anonymized those URIs
tagged with the 'anonymize' attribute and has removed those URIs
tagged with a "bcc" 'copyControl' attribute. Figure 4 shows an
example of the message F3.
<span class="grey">Camarillo & Johnston Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
INVITE sip:bill@example.com SIP/2.0
Via: SIP/2.0/TCP conference.example.com
;branch=z9hG4bKhjhs8as454
Max-Forwards: 70
To: <sip:bill@example.com>
From: Conference Server <sip:conf34@example.com>;tag=234332
Call-ID: 389sn189dasdf
CSeq: 1 INVITE
Contact: <sip:conf34@conference.example.com>;isfocus
Allow: INVITE, ACK, CANCEL, BYE, REFER
Allow-Events: dialog, conference
Accept: application/sdp, message/sipfrag
Content-Type: multipart/mixed;boundary="boundary1"
Content-Length: 690
--boundary1
Content-Type: application/sdp
v=0
o=conf 2890844343 2890844343 IN IP4 conference.example.com
s=-
c=IN IP4 192.0.2.5
t=0 0
m=audio 40000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
m=video 40002 RTP/AVP 31
a=rtpmap:31 H261/90000
--boundary1
Content-Type: application/resource-lists+xml
Content-Disposition: recipient-list-history; handling=optional
<?xml version="1.0" encoding="UTF-8"?>
<resource-lists xmlns="urn:ietf:params:xml:ns:resource-lists"
xmlns:cp="urn:ietf:params:xml:ns:copycontrol">
<list>
<entry uri="sip:bill@example.com" cp:copyControl="to" />
<entry uri="sip:anonymous@anonymous.invalid" cp:copyControl="to"
cp:count="2"/>
<entry uri="sip:joe@example.org" cp:copyControl="cc" />
<entry uri="sip:anonymous@anonymous.invalid" cp:copyControl="cc"
cp:count="1"/>
</list>
</resource-lists>
--boundary1--
Figure 4: INVITE request sent by the conference server
<span class="grey">Camarillo & Johnston Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
This document discusses setup of SIP conferences using a request-
contained URI list. Both conferencing and URI-list services have
specific security requirements, which are summarized here.
Conferences generally have authorization rules about who can or
cannot join a conference, what type of media can or cannot be used,
etc. This information is used by the focus to admit or deny
participation in a conference. It is RECOMMENDED that these types of
authorization rules be used to provide security for a SIP conference.
For this authorization information to be used, the focus needs to be
able to authenticate potential participants. Normal SIP mechanisms,
including Digest authentication and certificates, can be used. These
conference-specific security requirements are discussed further in
the requirements and framework documents -- [<a href="./rfc4245" title=""High-Level Requirements for Tightly Coupled SIP Conferencing"">RFC4245</a>] and [<a href="./rfc4353" title=""A Framework for Conferencing with the Session Initiation Protocol (SIP)"">RFC4353</a>].
For conference creation using a list, there are some additional
security considerations. "Framework and Security Considerations for
Session Initiation Protocol (SIP) URI-List Services" [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</a>]
discusses issues related to SIP URI-list services. Given that a
conference server sending INVITE requests to a set of users acts as a
URI-list service, implementations of conference servers that handle
lists MUST follow the security-related rules in [<a href="./rfc5363" title=""Framework and Security Considerations for Session Initiation Protocol (SIP) URI- List Services"">RFC5363</a>]. These
rules include opt-in lists and mandatory authentication and
authorization of clients.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span>
This document defines the 'recipient-list-invite' SIP option-tag. It
has been registered in the Option Tags subregistry under the SIP
parameter registry. The following is the description used in the
registration:
+------------------------+------------------------------+-----------+
| Name | Description | Reference |
+------------------------+------------------------------+-----------+
| recipient-list-invite | The body contains a list of | [<a href="./rfc5366">RFC5366</a>] |
| | URIs that indicates the | |
| | recipients of the SIP INVITE | |
| | request | |
+------------------------+------------------------------+-----------+
Table 1: Registration of the 'recipient-list-invite' option-tag
in SIP
<span class="grey">Camarillo & Johnston Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Acknowledgments</span>
Cullen Jennings, Hisham Khartabil, Jonathan Rosenberg, and Keith
Drage provided useful comments on this document. Miguel Garcia-
Martin assembled the dependencies to the 'copyControl' attribute
extension.
<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-RFC2119">RFC2119</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-RFC2183">RFC2183</a>] Troost, R., Dorner, S., and K. Moore, Ed., "Communicating
Presentation Information in Internet Messages: The
Content-Disposition Header Field", <a href="./rfc2183">RFC 2183</a>, August 1997.
[<a id="ref-RFC3204">RFC3204</a>] Zimmerer, E., Peterson, J., Vemuri, A., Ong, L., Audet,
F., Watson, M., and M. Zonoun, "MIME media types for ISUP
and QSIG Objects", <a href="./rfc3204">RFC 3204</a>, December 2001.
[<a id="ref-RFC3261">RFC3261</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.
[<a id="ref-RFC4579">RFC4579</a>] Johnston, A. and O. Levin, "Session Initiation Protocol
(SIP) Call Control - Conferencing for User Agents", <a href="https://www.rfc-editor.org/bcp/bcp119">BCP</a>
<a href="https://www.rfc-editor.org/bcp/bcp119">119</a>, <a href="./rfc4579">RFC 4579</a>, August 2006.
[<a id="ref-RFC4826">RFC4826</a>] Rosenberg, J., "Extensible Markup Language (XML) Formats
for Representing Resource Lists", <a href="./rfc4826">RFC 4826</a>, May 2007.
[<a id="ref-RFC5363">RFC5363</a>] Camarillo, G. and A.B. Roach, "Framework and Security
Considerations for Session Initiation Protocol (SIP) URI-
List Services", <a href="./rfc5363">RFC 5363</a>, October 2008.
[<a id="ref-RFC5364">RFC5364</a>] Garcia-Martin, M. and G. Camarillo, "Extensible Markup
Language (XML) Format Extension for Representing Copy
Control Attributes in Resource Lists", <a href="./rfc5364">RFC 5364</a>, October
2008.
<span class="grey">Camarillo & Johnston Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>. Informative References</span>
[<a id="ref-RFC4245">RFC4245</a>] Levin, O. and R. Even, "High-Level Requirements for
Tightly Coupled SIP Conferencing", <a href="./rfc4245">RFC 4245</a>, November
2005.
[<a id="ref-RFC4353">RFC4353</a>] Rosenberg, J., "A Framework for Conferencing with the
Session Initiation Protocol (SIP)", <a href="./rfc4353">RFC 4353</a>, February
2006.
[<a id="ref-RFC4575">RFC4575</a>] Rosenberg, J., Schulzrinne, H., and O. Levin, Ed., "A
Session Initiation Protocol (SIP) Event Package for
Conference State", <a href="./rfc4575">RFC 4575</a>, August 2006.
Authors' Addresses
Gonzalo Camarillo
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
EMail: Gonzalo.Camarillo@ericsson.com
Alan Johnston
Avaya
St. Louis, MO 63124
USA
EMail: alan@sipstation.com
<span class="grey">Camarillo & Johnston Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc5366">RFC 5366</a> INVITE-Contained Lists October 2008</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can 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>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Camarillo & Johnston Standards Track [Page 13]
</pre>
|
