idnits 2.17.1 draft-ietf-xcon-common-data-model-14.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 10, 2009) is 5275 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2445 (Obsoleted by RFC 5545) ** Obsolete normative reference: RFC 4582 (Obsoleted by RFC 8855) ** Obsolete normative reference: RFC 4583 (Obsoleted by RFC 8856) -- Obsolete informational reference (is this intentional?): RFC 3265 (Obsoleted by RFC 6665) Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 XCON O. Novo 3 Internet-Draft G. Camarillo 4 Intended status: Standards Track Ericsson 5 Expires: May 14, 2010 D. Morgan 6 Fidelity Investments 7 J. Urpalainen 8 Nokia 9 November 10, 2009 11 Conference Information Data Model for Centralized Conferencing (XCON) 12 draft-ietf-xcon-common-data-model-14.txt 14 Abstract 16 This document defines an Extensible Markup Language (XML)-based 17 conference information data model for centralized conferencing 18 (XCON). A conference information data model is designed to convey 19 information about the conference and about participation in the 20 conference. The conference information data model defined in this 21 document constitutes an extension of the data format specified in the 22 Session Initiation Protocol (SIP) Event Package for Conference State. 24 Status of this Memo 26 This Internet-Draft is submitted to IETF in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF), its areas, and its working groups. Note that 31 other groups may also distribute working documents as Internet- 32 Drafts. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be accessed at 43 http://www.ietf.org/shadow.html. 45 This Internet-Draft will expire on May 14, 2010. 47 Copyright Notice 48 Copyright (c) 2009 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 66 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 67 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 68 3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 69 3.3.1. Conference Object URI Definition . . . . . . . . . . . 9 70 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 71 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 72 4.1. . . . . . . . . . . . . . . . . . . . . 13 73 4.2. . . . . . . . . . . . . . . . . . 14 74 4.2.1. . . . . . . . . . . . . . . . . . . . . . . 14 75 4.2.2. . . . . . . . . . . . . . . . . . . . . 14 76 4.2.3. . . . . . . . . . . . . . . . . . . . . . . 14 77 4.2.4. . . . . . . . . . . . . . . . . . . . . . 14 78 4.2.5. . . . . . . . . . . . . . . . . . . . . . . 15 79 4.2.6. . . . . . . . . . . . . . . . . . . . 15 80 4.2.7. . . . . . . . . . . . . . . . . . . . 15 81 4.2.8. . . . . . . . . . . . . . . . . . . . 15 82 4.2.9. . . . . . . . . . . . . . . . . . . 15 83 4.2.10. . . . . . . . . . . . . . . . . . . . . . 16 84 4.2.11. . . . . . . . . . . . . . . . . . . . . 17 85 4.2.12. . . . . . . . . . . . . . . . . . 17 86 4.2.13. . . . . . . . . . . . . . . . . . . 17 87 4.3. . . . . . . . . . . . . . . . . . . . . . . . 19 88 4.4. . . . . . . . . . . . . . . . . . . . . 19 89 4.4.1. . . . . . . . . 19 90 4.4.2. . . . . . . . . . . . . . . . . . . . . . 20 91 4.4.3. . . . . . . . . . . . . . . . . . . . . . . . 20 92 4.4.4. . . . . . . . . . . . . . . . . . . . . . . . 20 93 4.5. . . . . . . . . . . . . . . . . . . . 20 94 4.5.1. . . . . . . . . . . . . . . . . . . . 20 95 4.5.2. . . . . . . . . . . . . . . . . . 20 96 4.5.3. . . . . . . . . . . . . . . . 21 97 4.5.4. . . . . . . . . . . . . . . 21 98 4.6. . . . . . . . . . . . . . . . . . . . . . . . . . 22 99 4.6.1. . . . . . . . . . . . . . . . . . . . 22 100 4.6.2. . . . . . . . . . . . . . . . 23 101 4.6.3. . . . . . . . . . . . . . . . . . 23 102 4.6.4. . . . . . . . . . . . . . . . . . . 24 103 4.6.5. and Its Sub-elements . . . . . . . . . . 24 104 4.6.5.1. . . . . . . . . . . . . . . . . . . 25 105 4.6.5.2. . . . . . . . . . . . . . . . . 26 106 4.6.5.3. . . . . . . . . . . . . . . . 26 107 4.6.5.4. . . . . . . . . . . . . . . . . . . . . . 26 108 4.6.5.5. . . . . . . . . . . . . . . . . . . . 26 109 4.6.5.6. . . . . . . . . . . . . . . . . . 26 110 4.6.5.7. . . . . . . . . . 26 111 4.6.5.8. . . . . . . . . . 27 112 4.6.5.9. . . . . . . . . . 27 113 4.6.5.10. . . . . . . . . . . . . . . . . . . . . 27 114 4.7. . . . . . . . . . . . . . . . . . . . . 28 115 4.8. . . . . . . . . . . . . . . . . . . . . 28 116 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29 117 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 39 118 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40 119 8. Security Considerations . . . . . . . . . . . . . . . . . . . 49 120 8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 49 121 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 50 122 8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 50 123 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 124 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 50 125 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51 126 9.3. Conference Object Identifier Registration . . . . . . . . 52 127 9.4. Conference User Identifier Registration . . . . . . . . . 53 128 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 129 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 130 11.1. Normative References . . . . . . . . . . . . . . . . . . . 54 131 11.2. Informative References . . . . . . . . . . . . . . . . . . 54 132 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55 133 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 82 134 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 92 136 1. Introduction 138 There is a core data set of conference information that is utilized 139 in any conference, independent of the specific conference media. 140 This core data set called the 'conference information data model' is 141 defined in this document using an Extensible Markup Language (XML)- 142 based. The conference information data model defined in this 143 document is logically represented by the conference object. 145 Conference objects are a fundamental concept in Centralized 146 Conferencing, as described in the Centralized Conferencing Framework 147 [RFC5239]. A conference object contains data that represents a 148 conference during each of its various stages (e.g., created/creation, 149 reserved/reservation, active/activation, completed/completion). A 150 conference object can be manipulated using a conference control 151 protocol at a conference server. The conference object represents a 152 particular instantiation of a conference information data model. 153 Consequently, conference objects follow the XML format defined in 154 this document. 156 A conference object contains the core information of a conference 157 (i.e., capabilities, membership, call control signaling, media, etc.) 158 and specifies who, and in which way that information can be 159 manipulated. 161 Figure 1 shows the logical functional elements of a conference server 162 as defined by the Centralized Conferencing Framework [RFC5239]. They 163 are a Conference Control Server, a Floor Control Server, a number of 164 Foci, and a Notification Service. A conference control protocol 165 provides the interface between a conference control client and the 166 conference control server. A floor control protocol (e.g., BFCP 167 [RFC4582]) provides the interface between a floor control client and 168 the floor control server. A call signaling protocol (e.g., SIP, 169 H.323, Q.931, ISUP, etc.) provides the interface between a call 170 signaling client and a Focus. A notification protocol (e.g., SIP- 171 based event notifications [RFC3265]) provides the interface between 172 the conferencing client and the Notification Service. Within a 173 conference, the conference control server, floor control server, and 174 focus can modify the information in the conference object. 176 ............................................................... 177 . Conferencing Server . 178 . +---------------------------------------------------+ . 179 . | C o n f e r e n c e o b j e c t | . 180 . +-+--------------------------------------------------+| . 181 . | C o n f e r e n c e o b j e c t || . 182 . +-+---------------------------------------------------+|| . 183 . | C o n f e r e n c e o b j e c t ||| . 184 . | +--------------------------------------------------+||| . 185 . | | Conference Information Data Model |||| . 186 . | | +----------------------------------------------+ |||| . 187 . | | | Conference description (times, duration) | |||| . 188 . | | +----------------------------------------------+ |||| . 189 . | | +----------------------------------------------+ |||| . 190 . | | | Host information | |||| . 191 . | | +----------------------------------------------+ |||| . 192 . | | +----------------------------------------------+ |||| . 193 . | | | Conference state | |||| . 194 . | | +----------------------------------------------+ |||| . 195 . | | +----------------------------------------------+ |||| . 196 . | | | Floor information | |||| . 197 . | | +----------------------------------------------+ |||| . 198 . | | +----------------------------------------------+ |||| . 199 . | | | Membership (users, capacity) | |||| . 200 . | | +----------------------------------------------+ |||| . 201 . | | +----------------------------------------------+ |||| . 202 . | | | Sidebars, Etc. | |||| . 203 . | | +----------------------------------------------+ |||| . 204 . | | +----------------------------------------------+ |||| . 205 . | | | Etc. | |||| . 206 . | | +----------------------------------------------+ |||+ . 207 . | +--------------------------------------------------+|+ . 208 . +----^------------------^-------------^--------|------+ . 209 . | | | | . 210 . +------v-------+ +--------v-----+ +-----v-+ +----v-------+ . 211 . | Conference | | Floor | | | | | . 212 . | Control | | Control | |Foci | |Notification| . 213 . | Server | | Server | | | |Service | . 214 . +-----^--------+ +---^----------+ +-^-----+ +------------+ . 215 ........|..............|..............|..........|............. 216 |Conference |Floor |Call |Notification 217 |Control |Control |Signaling |Protocol 218 |Protocol |Protocol |Protocol | 219 ........v..............v..............v..........v............. 220 . C o n f e r e n c i n g C l i e n t . 221 ............................................................... 223 Figure 1: Conference Server Architecture 225 The Session Initiation Protocol (SIP) Event Package for Conference 226 State, specified in [RFC4575], already defines a data format for 227 conferences. However, that model is SIP specific and lacks elements 228 related to some of the functionality defined by the Centralized 229 Conferencing Framework [RFC5239] (e.g., floor control). The data 230 model defined in this document constitutes a superset of the data 231 format defined in [RFC4575]. The result is a data format that 232 supports more call signaling protocols besides SIP and that covers 233 all the functionality defined in the Centralized Conferencing 234 Framework [RFC5239]. 236 2. Terminology 238 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 239 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 240 document are to be interpreted as described in RFC 2119 [RFC2119]. 242 This document uses the terminology defined in the Centralized 243 Conferencing Framework [RFC5239], the SIPPING conferencing framework 244 [RFC4353] and the BFCP (Binary Floor Control Protocol) specification 245 [RFC4582]. Readers of this document should be familiar with the 246 terminology used in those documents. 248 3. Overview 250 The data model specified in this document is the result of extending 251 the data format defined in [RFC4575] with new elements. Examples of 252 such extensions include scheduling elements, media control elements, 253 floor control elements, non-SIP URIs, and addition of localization 254 extensions to text elements. This data model can be used by 255 conference servers providing different types of basic conferences. 256 It is expected that this data model can be further extended with new 257 elements in the future in order to implement additional advanced 258 features. 260 3.1. Data Model Format 262 A conference object document is an XML [W3C.REC-xml-20001006] 263 document that MUST be well formed and SHOULD be valid. Conference 264 object documents MUST be based on XML 1.0 and SHOULD be encoded using 265 UTF-8. 267 3.2. Data Model Namespace 269 This specification defines a new namespace specification for 270 identifying the elements defined in the data model. This namespace 271 is as follows: 273 urn:ietf:params:xml:ns:xcon-conference-info 275 3.3. The Conference Object Identifier 277 The conference object identifier (XCON-URI) can be viewed as a key to 278 accessing a specific conference object. It can be used, for 279 instance, by the conference control protocol to access, manipulate 280 and delete a conference object. A conference object identifier is 281 provided to the conferencing client by the conference notification 282 service or through out-of-band mechanisms (e.g. E-Mail). 284 A conferencing system may maintain a relationship between the 285 conference object identifiers and the identifiers associated with 286 each of the complementary centralized conferencing protocols (e.g., 287 call signaling protocols, BFCP, etc.). To facilitate the maintenance 288 of these relationships, the conference object identifier acts as a 289 top level identifier within the conferencing system for the purpose 290 of identifying the interfaces for these other protocols. This 291 implicit binding provides a structured mapping of the various 292 protocols with the associated conference object Identifier. Figure 2 293 illustrates the relationship between the identifiers used for the 294 protocols and the general conference object identifier (XCON-URI). 296 +--------------------------+ 297 | Conference | 298 | Object | 299 | Identifier | 300 +--------------------------+ 301 | xcon:Ji092i@example.com | 302 +------+-------------------+ 303 | 304 | 305 | 306 +-----------------+---------------+ 307 | | 308 +-----------+-----------+ +----------+---------+ 309 | CSP Conference IDs | |BFCP 'Conference ID'| 310 +-----------------------+ +--------------------+ 311 | h323:i092@example.com | | i092 | 312 | tel:+44(0)2920930033 | +----------+---------+ 313 | sip:i092@example.com | | 314 +-----------------------+ +-------+--------+ 315 | BFCP 'Floor ID'| 316 +----------------+ 317 | 543 | 318 | 236 | 319 +----------------+ 321 Figure 2: Conference Object Mapping 323 In Figure 2, the conference object identifier acts as the top level 324 key in the identification process. The call signaling protocols have 325 an associated conference user identifier, often represented in the 326 form of URIs. The binary floor control protocol, as defined in 327 [RFC4582], defines the 'conference ID' identifier which represents a 328 conference instance within floor control. When created within the 329 conferencing system, the 'conference ID' has a 1:1 mapping to the 330 unique conference object Identifier(XCON-URI). Operations associated 331 with the conference control protocols are directly associated with 332 the conference object, thus the primary identifier associated with 333 these protocols is the conference object identifier(XCON-URI). The 334 mappings between additional protocols/interface is not strictly 1:1 335 and does allow for multiple occurrences. For example, multiple call 336 signaling protocols will each have a representation that is 337 implicitly linked to the top level conference object identifier e.g. 338 H323 and SIP URIs that represent a conference instance. It should be 339 noted that a conferencing system is free to structure such 340 relationships as required and this information is just included as a 341 guideline that can be used. 343 Further elements can be added to the tree representation in Figure 2 344 to enable a complete representation of a conference instance within a 345 conferencing system. 347 3.3.1. Conference Object URI Definition 349 XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] 351 conf-object-id = 1*( unreserved / "+" / "=" / "/" ) 353 host, port, and unreserved are defined in RFC3986[RFC3986] 355 3.4. Data Model Structure 357 The information in this data model is structured in the following 358 manner. All the information related to a conference is contained in 359 a element. The element contains 360 the following child elements: 362 o The element describes the conference as a 363 whole. It has, for instance, information about the URI of the 364 conference, maximum users allowed in the conference, media 365 available in the conference, or the time the conference will 366 start. 367 o The element contains information about the entity 368 hosting the conference (e.g., its URI). 369 o The element informs the subscribers about the 370 changes in the overall conference information. 371 o The element contains information about the 372 status of the different floors in the conference. 373 o The element describes the membership information as a 374 whole. The element contains a set of child 375 elements, each describing a single participant in the conference. 376 o If a participant in the main conference joins a sidebar, a new 377 element is created in the conference referenced from the 378 element or under one of the 379 elements. 381 Note that some of the elements described above such , , , or are not defined in the data model but are defined in the data 384 format of [RFC4575]. We describe them here because they are part of 385 the basic structure of the data model. 387 4. Data Model Definition 389 The following non-normative diagram shows the structure of conference 390 object documents. The operator "!" preceding an element indicates 391 that the element is mandatory in the data model. The operator "*" 392 following an element indicates that the element is introduced and 393 defined in this document. That is, elements without a "*" have 394 already been defined in [RFC4575]. 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 | | | | |--