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
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
|
<pre>Internet Engineering Task Force (IETF) G. Camarillo
Request for Comments: 6502 Ericsson
Category: Standards Track S. Srinivasan
ISSN: 2070-1721
R. Even
Gesher Erove Ltd
J. Urpalainen
Nokia
March 2012
<span class="h1">Conference Event Package Data Format Extension</span>
<span class="h1">for Centralized Conferencing (XCON)</span>
Abstract
This document specifies the notification mechanism for XCON
(centralized conferencing). This mechanism reuses the SIP (Session
Initiation Protocol) event package for conference state.
Additionally, the notification mechanism includes support for the
XCON data model and for partial notifications.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6502">http://www.rfc-editor.org/info/rfc6502</a>.
<span class="grey">Camarillo, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
<span class="grey">Camarillo, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Notification Formats ............................................<a href="#page-5">5</a>
<a href="#section-4">4</a>. Full Notifications ..............................................<a href="#page-5">5</a>
<a href="#section-4.1">4.1</a>. Backwards Compatibility ....................................<a href="#page-5">5</a>
<a href="#section-5">5</a>. Partial Notifications ...........................................<a href="#page-6">6</a>
<a href="#section-5.1">5.1</a>. Generation of Partial Notifications ........................<a href="#page-6">6</a>
<a href="#section-5.2">5.2</a>. Processing of Partial Notifications ........................<a href="#page-7">7</a>
<a href="#section-5.3">5.3</a>. Partial Notification Format ................................<a href="#page-8">8</a>
<a href="#section-5.4">5.4</a>. XML Schema for Partial Notifications .......................<a href="#page-8">8</a>
<a href="#section-5.5">5.5</a>. Examples ...................................................<a href="#page-9">9</a>
<a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-10">10</a>
6.1. MIME type Registration:
application/xcon-conference-info+xml ......................<a href="#page-10">10</a>
6.2. MIME type Registration:
application/xcon-conference-info-diff+xml .................<a href="#page-11">11</a>
6.3. URN Sub-Namespace Registration:
xcon-conference-info-diff .................................<a href="#page-12">12</a>
<a href="#section-6.4">6.4</a>. XML Schema Registration ...................................<a href="#page-12">12</a>
<a href="#section-7">7</a>. Security Considerations ........................................<a href="#page-12">12</a>
<a href="#section-8">8</a>. References .....................................................<a href="#page-13">13</a>
<a href="#section-8.1">8.1</a>. Normative References ......................................<a href="#page-13">13</a>
<a href="#section-8.2">8.2</a>. Informative References ....................................<a href="#page-13">13</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The XCON (Centralized Conferencing) framework [<a href="./rfc5239" title=""A Framework for Centralized Conferencing"">RFC5239</a>] defines a
notification service that provides updates about a conference
instance's state to authorized parties using a notification protocol,
as shown in Figure 1. This document specifies how to use the SIP
(Session Initiation Protocol [<a href="./rfc3261" title=""SIP: Session Initiation Protocol"">RFC3261</a>]) event package for conference
state defined in [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>] as a notification protocol between a
client and a conference's notification server.
<span class="grey">Camarillo, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
...........................
. Conferencing System .
. .
. +--------------+ .
. | Conf. object | .
. | | .
. +--------------+ .
. | .
. v .
. +------------+ .
. |Notification| .
. |Service | .
. +------------+ .
. ^ .
..........|................
|
| Notification
| Protocol
|(notifications following the
| XCON data model)
|
..........|............
. v .
. +------------+ .
. |Notification| .
. | Client | .
. +------------+ .
. .
. Conferencing Client .
.......................
Figure 1: Notification service and protocol in the XCON architecture
In addition to specifying the SIP event package for conference state,
[<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>] specifies a data format to be used with the event package.
The XCON data model [<a href="./rfc6501" title=""Conference Information Data Model for Centralized Conferencing (XCON)"">RFC6501</a>] extends that format with new elements
and attributes so that the extended format supports more
functionality (e.g., floor control). The notification protocol
specified in this document supports all the data defined in the XCON
data model (i.e., the data originally defined in [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>] plus all
the extensions defined in [<a href="./rfc6501" title=""Conference Information Data Model for Centralized Conferencing (XCON)"">RFC6501</a>]) plus a partial notification
mechanism based on XML patch operations [<a href="./rfc5261" title=""An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors"">RFC5261</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="grey">Camarillo, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Notification Formats</span>
In order to obtain notifications from a conference server's
notification service, a client subscribes to the 'conference' event
package at the server as specified in [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>]. Per [<a href="./rfc4575" title=""A Session Initiation Protocol (SIP) Event Package for Conference State"">RFC4575</a>],
NOTIFY requests within this event package can carry an XML document
in the "application/conference-info+xml" format. Additionally, per
this specification, NOTIFY requests can also carry XML documents in
the "application/xcon-conference-info+xml" and the "application/
xcon-conference-info-diff+xml" formats.
A document in the "application/xcon-conference-info+xml" format
provides the user agent with the whole state of a conference
instance. A document in the "application/
xcon-conference-info-diff+xml" format provides the user agent with
the changes the state of the conference instance has experienced
since the last notification sent to the user agent.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Full Notifications</span>
Subscribers signal support for full notifications by including the
"application/xcon-conference-info+xml" format in the Accept header
field of the SUBSCRIBE requests they generate. If a client
subscribing to the 'conference' event package generates an Accept
header field that includes the MIME type "application/
xcon-conference-info+xml", the server has the option of returning
documents that follow the XML format specified in [<a href="./rfc6501" title=""Conference Information Data Model for Centralized Conferencing (XCON)"">RFC6501</a>] and are
carried in "application/xcon-conference-info+xml" message bodies.
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Backwards Compatibility</span>
Conference servers that implement the SIP event package for
conference state and support the "application/
xcon-conference-info+xml" MIME type MUST also support the
"application/conference-info+xml" MIME type. This way, legacy
clients, which only support "application/conference-info+xml", are
able to receive notifications in a format they understand.
Clients that implement the SIP event package for conference state and
support the "application/xcon-conference-info+xml" MIME type SHOULD
also support the "application/conference-info+xml" MIME type. This
way, these clients are able to receive notifications from legacy
servers, which only support "application/conference-info+xml", in a
format they understand.
<span class="grey">Camarillo, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Partial Notifications</span>
The conference state reported by this event package may contain many
elements. When the "xcon-conference-info+xml" format is used and
there is a change in the state of an element, the server generates a
notification with the whole conference state. Generating large
notifications to report small changes does not meet the efficiency
requirements of some bandwidth-constrained environments. The partial
notifications mechanism specified in this section is a more efficient
way to report changes in the conference state.
The SIP event package for conference state defined a partial
notification mechanism based on <state> elements. Servers compliant
with this specification MUST NOT use that partial notification
mechanism. Instead, they MUST use the mechanism specified in this
section.
Subscribers signal support for partial notifications by including the
"application/xcon-conference-info-diff+xml" format in the Accept
header field of the SUBSCRIBE requests they generate. If a client
subscribing to the 'conference' event package generates an Accept
header field that includes the MIME type "application/
xcon-conference-info-diff+xml", the server has the option of
returning documents that follow the XML format specified in
<a href="#section-5.4">Section 5.4</a> and are carried in "application/
xcon-conference-diff-info+xml" message bodies.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Generation of Partial Notifications</span>
Once a subscription is accepted and installed, the server MUST
deliver full state in its first notification. To report full state,
the server MUST set the Content-Type header field to the value
"application/xcon-conference-info+xml".
In order to deliver a partial notification, the server MUST set the
Content-Type header field to the value "application/
xcon-conference-info-diff+xml". When the server generates a partial
notification, the server SHOULD only include the information that has
changed compared to the previous notification. It is up to the
server's local policy to determine what is considered as a change to
the previous state.
The server MUST construct partial notifications according to the
following logic: all the information that has been added to the
document is listed inside <add> elements. All information that has
been removed from the document is listed inside <remove> elements,
and all information that has been changed is listed under <replace>
elements.
<span class="grey">Camarillo, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
The server MUST NOT send a new NOTIFY request with a partial
notification until it has received a final response from the
subscriber for the previous one or the previous NOTIFY request has
timed out.
When the server receives a SUBSCRIBE request (refresh or termination)
within the associated subscription, it SHOULD send a NOTIFY request
containing the full document using the 'application/
xcon-conference-info+xml' content type.
If the server has used a content type other than 'application/
xcon-conference-info+xml' in notifications within the existing
subscription and changes to deliver partial notifications, the server
MUST deliver full state using the 'application/
xcon-conference-info+xml' content type before generating its first
partial notification.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Processing of Partial Notifications</span>
When a subscriber receives the first notification containing full
state in a 'application/xcon-conference-info+xml' MIME body, the
subscriber MUST store the received full document as its local copy.
When the subscriber receives a subsequent notification, the
subscriber MUST modify its locally stored information according to
the following logic:
o If the notification carries an 'application/
xcon-conference-info+xml' document, the subscriber MUST replace
its local copy of the document with the document received in the
notification.
o If the notification carries an 'application/
xcon-conference-info-diff+xml' document, the subscriber MUST apply
the changes indicated in the received 'application/
xcon-conference-info-diff+xml' document to its local copy of the
full document.
If the subscriber encounters a processing error while processing an
'application/xcon-conference-info-diff+xml' encoded document, the
subscriber SHOULD renew its subscription. A subscriber can fall back
to normal operations by not including the "application/
xcon-conference-info-diff+xml" format in a new SUBSCRIBE request.
If the server changes the content type used in notifications within
the existing subscription, the subscriber MUST discard all the
previously received information and process the new content as
specified for that content type.
<span class="grey">Camarillo, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Partial Notification Format</span>
An xcon-conference-info-diff document is an XML
[<a href="#ref-W3C.REC-xml-20081126">W3C.REC-xml-20081126</a>] document that MUST be well-formed and SHOULD
be valid. The namespace URI for the <conference-info-diff> root
document element is defined in [<a href="./rfc6501" title=""Conference Information Data Model for Centralized Conferencing (XCON)"">RFC6501</a>]:
urn:ietf:params:xml:ns:xcon-conference-info
The root document element <conference-info-diff> has a single
mandatory attribute, "entity". The value of this attribute is the
conference object identifier (XCON-URI) that identifies the
conference being described in the document.
The content of the <conference-info-diff> element is an unordered
sequence of <add>, <replace>, and <remove> elements followed by
elements from other namespaces for the purposes of extensibility.
Any such unknown elements MUST be ignored by the client. The <add>,
<replace>, and <remove> elements can contain other extension
attributes than what are defined in the corresponding base types of
[<a href="./rfc5261" title=""An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors"">RFC5261</a>].
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. XML Schema for Partial Notifications</span>
This is the XML schema for the "application/
xcon-conference-info-diff+xml" data format. The
"urn:ietf:params:xml:schema:xml-patch-ops" schema is defined in
[<a href="./rfc5261" title=""An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors"">RFC5261</a>].
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
targetNamespace="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<!-- include patch-ops type definitions -->
<xs:include
schemaLocation="urn:ietf:params:xml:schema:patch-ops"/>
<!-- partial updates -->
<xs:element name="conference-info-diff">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:choice>
<!-- add some content -->
<xs:element name="add">
<xs:complexType mixed="true">
<xs:complexContent>
<span class="grey">Camarillo, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
<xs:extension base="add">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- remove some content -->
<xs:element name="remove">
<xs:complexType>
<xs:complexContent>
<xs:extension base="remove">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- replace some content -->
<xs:element name="replace">
<xs:complexType mixed="true">
<xs:complexContent>
<xs:extension base="replace">
<xs:anyAttribute processContents="lax"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<!-- allow extension elements from other namespaces -->
<xs:any namespace="##other" processContents="lax"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="entity" type="xs:anyURI" use="required"/>
<xs:anyAttribute processContents="lax"/>
</xs:complexType>
</xs:element>
</xs:schema>
<span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a>. Examples</span>
The following is an 'application/xcon-conference-info-diff+xml'
partial update document:
<?xml version="1.0" encoding="UTF-8"?>
<conference-info-diff
xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
entity="conference123@example.com">
<span class="grey">Camarillo, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
<add
sel="*/users/allowed-users-list"> <target
uri="sip:john@example.com" method="refer"/>
</add>
<replace sel="*/conference-state/user-count/text()">5</replace>
</conference-info-diff>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
There are four IANA considerations associated with this
specification.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. MIME type Registration: application/xcon-conference-info+xml</span>
This section registers the 'application/xcon-conference-info+xml'
MIME type.
MIME media type name: application
MIME subtype name: xcon-conference-info+xml
Mandatory parameters: none
Optional Parameters: Same as charset parameter application/xml as
specified in [<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Encoding considerations: Same as encoding considerations of
application/xml as specified in [<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Security considerations: Security considerations: See <a href="./rfc3023#section-10">Section 10 of
[RFC3023]</a>.
Interoperability considerations: none
Published specification: <a href="./rfc6502">RFC 6502</a>
Applications that use this media type: This document type has been
defined to support centralized conferencing applications.
Additional Information:
Magic Number: none
File extension: .xml
Macintosh file type code: "TEXT"
<span class="grey">Camarillo, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Intended usage: COMMON
Author/Change controller: The IETF.
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. MIME type Registration: application/xcon-conference-info-diff+xml</span>
This section registers the 'application/
xcon-conference-info-diff+xml' MIME type.
MIME media type name: application
MIME subtype name: xcon-conference-info-diff+xml
Mandatory parameters: none
Optional Parameters: Same as charset parameter application/xml as
specified in [<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Encoding considerations: Same as encoding considerations of
application/xml as specified in [<a href="./rfc3023" title=""XML Media Types"">RFC3023</a>].
Security considerations: Security considerations: See <a href="./rfc3023#section-10">Section 10 of
[RFC3023]</a>.
Interoperability considerations: none
Published specification: <a href="./rfc6502">RFC 6502</a>
Applications that use this media type: This document type has been
defined to support partial notifications in centralized
conferencing applications.
Additional Information:
Magic Number: none
File extension: .xml
Macintosh file type code: "TEXT"
Personal and email address for further information: IETF XCON
Working Group <xcon@ietf.org>
Intended usage: COMMON
<span class="grey">Camarillo, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
Author/Change controller: The IETF.
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. URN Sub-Namespace Registration: xcon-conference-info-diff</span>
This section registers a new XML namespace per the procedures in
[<a href="./rfc3688" title=""The IETF XML Registry"">RFC3688</a>].
URI: urn:ietf:params:xml:ns:xcon-conference-info-diff
Registrant Contact: IETF SIPPING working group <sipping@ietf.org>,
Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
XML:
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"<a href="http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd</a>">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/>
<title>Partial Notifications in Centralized Conferencing</title>
</head>
<body>
<h1>Namespace for Partial Notifications in</h1>
<h1>Centralized Conferencing</h1>
<h2>urn:ietf:params:xml:ns:xcon-conference-info-diff</h2>
<p>See <a href="http://www.rfc-editor.org/rfc/rfc6502.txt">
<a href="./rfc6502">RFC 6502</a></a>.</p>
</body>
</html>
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. XML Schema Registration</span>
This section registers an XML schema per the procedures in [<a href="./rfc3688" title=""The IETF XML Registry"">RFC3688</a>].
URI: urn:ietf:params:xml:schema:xcon-conference-info-diff
Registrant Contact: IETF XCON working group, <xcon@ietf.org>, Gonzalo
Camarillo <Gonzalo.Camarillo@ericsson.com>
The XML for this schema can be found in <a href="#section-5.4">Section 5.4</a>.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
This document specifies how to deliver notifications using the SIP
event package for conference state in two new formats. The fact that
notifications are encoded in a different format does not have
<span class="grey">Camarillo, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
security implications. <a href="./rfc4575#section-8">Section 8 of [RFC4575]</a> contains security
considerations related to the use of the event package. Implementers
of the event package need to follow those considerations regardless
of the format used to encode their notifications.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.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-RFC3023">RFC3023</a>] Murata, M., St. Laurent, S., and D. Kohn, "XML Media
Types", <a href="./rfc3023">RFC 3023</a>, January 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-RFC4575">RFC4575</a>] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Initiation Protocol (SIP) Event Package for Conference
State", <a href="./rfc4575">RFC 4575</a>, August 2006.
[<a id="ref-RFC5261">RFC5261</a>] Urpalainen, J., "An Extensible Markup Language (XML) Patch
Operations Framework Utilizing XML Path Language (XPath)
Selectors", <a href="./rfc5261">RFC 5261</a>, September 2008.
[<a id="ref-RFC6501">RFC6501</a>] Novo, O., Camarillo, G., Morgan, D., and J. Urpalainen,
"Conference Information Data Model for Centralized
Conferencing (XCON)", <a href="./rfc6501">RFC 6501</a>, March 2012.
[<a id="ref-W3C.REC-xml-20081126">W3C.REC-xml-20081126</a>]
Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008,
<<a href="http://www.w3.org/TR/2008/REC-xml-20081126">http://www.w3.org/TR/2008/REC-xml-20081126</a>>.
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Informative References</span>
[<a id="ref-RFC3688">RFC3688</a>] Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
January 2004.
[<a id="ref-RFC5239">RFC5239</a>] Barnes, M., Boulton, C., and O. Levin, "A Framework for
Centralized Conferencing", <a href="./rfc5239">RFC 5239</a>, June 2008.
<span class="grey">Camarillo, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6502">RFC 6502</a> XCON Event Package March 2012</span>
Authors' Addresses
Gonzalo Camarillo
Ericsson
Hirsalantie 11
Jorvas 02420
Finland
EMail: Gonzalo.Camarillo@ericsson.com
Srivatsa Srinivasan
EMail: srivatsa.srinivasan@gmail.com
Roni Even
Gesher Erove Ltd
14 David Hamelech
Tel Aviv 64953
Israel
EMail: ron.even.tlv@gmail.com
Jari Urpalainen
Nokia
Itamerenkatu 11-13
Helsinki 00180
Finland
EMail: jari.urpalainen@nokia.com
Camarillo, et al. Standards Track [Page 14]
</pre>
|
