idnits 2.17.1 draft-ietf-xcon-common-data-model-15.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 contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 10, 2010) is 5186 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: August 14, 2010 D. Morgan 6 Fidelity Investments 7 J. Urpalainen 8 Nokia 9 February 10, 2010 11 Conference Information Data Model for Centralized Conferencing (XCON) 12 draft-ietf-xcon-common-data-model-15.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 August 14, 2010. 47 Copyright Notice 48 Copyright (c) 2010 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 This document may contain material from IETF Documents or IETF 62 Contributions published or made publicly available before November 63 10, 2008. The person(s) controlling the copyright in some of this 64 material may not have granted the IETF Trust the right to allow 65 modifications of such material outside the IETF Standards Process. 66 Without obtaining an adequate license from the person(s) controlling 67 the copyright in such materials, this document may not be modified 68 outside the IETF Standards Process, and derivative works of it may 69 not be created outside the IETF Standards Process, except to format 70 it for publication as an RFC or to translate it into languages other 71 than English. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 76 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 78 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 79 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 80 3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 81 3.3.1. Conference Object URI Definition . . . . . . . . . . . 9 82 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 83 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 84 4.1. . . . . . . . . . . . . . . . . . . . . 13 85 4.2. . . . . . . . . . . . . . . . . . 14 86 4.2.1. . . . . . . . . . . . . . . . . . . . . . . 14 87 4.2.2. . . . . . . . . . . . . . . . . . . . . 14 88 4.2.3. . . . . . . . . . . . . . . . . . . . . . . 14 89 4.2.4. . . . . . . . . . . . . . . . . . . . . . 15 90 4.2.5. . . . . . . . . . . . . . . . . . . . . . . 15 91 4.2.6. . . . . . . . . . . . . . . . . . . . 15 92 4.2.7. . . . . . . . . . . . . . . . . . . . 15 93 4.2.8. . . . . . . . . . . . . . . . . . . . 15 94 4.2.9. . . . . . . . . . . . . . . . . . . 15 95 4.2.10. . . . . . . . . . . . . . . . . . . . . . 17 96 4.2.11. . . . . . . . . . . . . . . . . . . . . 17 97 4.2.12. . . . . . . . . . . . . . . . . . 17 98 4.2.13. . . . . . . . . . . . . . . . . . . 17 99 4.3. . . . . . . . . . . . . . . . . . . . . . . . 19 100 4.4. . . . . . . . . . . . . . . . . . . . . 20 101 4.4.1. . . . . . . . . 20 102 4.4.2. . . . . . . . . . . . . . . . . . . . . . 20 103 4.4.3. . . . . . . . . . . . . . . . . . . . . . . . 20 104 4.4.4. . . . . . . . . . . . . . . . . . . . . . . . 20 105 4.5. . . . . . . . . . . . . . . . . . . . 20 106 4.5.1. . . . . . . . . . . . . . . . . . . . 20 107 4.5.2. . . . . . . . . . . . . . . . . . 21 108 4.5.3. . . . . . . . . . . . . . . . 21 109 4.5.4. . . . . . . . . . . . . . . 21 110 4.6. . . . . . . . . . . . . . . . . . . . . . . . . . 22 111 4.6.1. . . . . . . . . . . . . . . . . . . . 22 112 4.6.2. . . . . . . . . . . . . . . . 23 113 4.6.3. . . . . . . . . . . . . . . . . . 23 114 4.6.4. . . . . . . . . . . . . . . . . . . 24 115 4.6.5. and Its Sub-elements . . . . . . . . . . 25 116 4.6.5.1. . . . . . . . . . . . . . . . . . . 26 117 4.6.5.2. . . . . . . . . . . . . . . . . 26 118 4.6.5.3. . . . . . . . . . . . . . . . 26 119 4.6.5.4. . . . . . . . . . . . . . . . . . . . . . 26 120 4.6.5.5. . . . . . . . . . . . . . . . . . . . 27 121 4.6.5.6. . . . . . . . . . . . . . . . . . 27 122 4.6.5.7. . . . . . . . . . 27 123 4.6.5.8. . . . . . . . . . 27 124 4.6.5.9. . . . . . . . . . 27 125 4.6.5.10. . . . . . . . . . . . . . . . . . . . . 28 126 4.7. . . . . . . . . . . . . . . . . . . . . 29 127 4.8. . . . . . . . . . . . . . . . . . . . . 29 128 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29 129 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 40 130 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40 131 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 132 8.1. Authentication, Access Control, and Integrity . . . . . . 50 133 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 50 134 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 135 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 51 136 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51 137 9.3. Conference Object Identifier Registration . . . . . . . . 52 138 9.4. Conference User Identifier Registration . . . . . . . . . 53 139 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 140 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 141 11.1. Normative References . . . . . . . . . . . . . . . . . . . 54 142 11.2. Informative References . . . . . . . . . . . . . . . . . . 54 143 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55 144 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 83 145 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 92 147 1. Introduction 149 There is a core data set of conference information that is utilized 150 in any conference, independent of the specific conference media. 151 This core data set called the 'conference information data model' is 152 defined in this document using an Extensible Markup Language (XML)- 153 based. The conference information data model defined in this 154 document is logically represented by the conference object. 156 Conference objects are a fundamental concept in Centralized 157 Conferencing, as described in the Centralized Conferencing Framework 158 [RFC5239]. A conference object contains data that represents a 159 conference during each of its various stages (e.g., created/creation, 160 reserved/reservation, active/activation, completed/completion). A 161 conference object can be manipulated using a conference control 162 protocol at a conference server. The conference object represents a 163 particular instantiation of a conference information data model. 164 Consequently, conference objects follow the XML format defined in 165 this document. 167 A conference object contains the core information of a conference 168 (i.e., capabilities, membership, call control signaling, media, etc.) 169 and specifies by whom, and in which way that information can be 170 manipulated. 172 Figure 1 shows the logical functional elements of a conference server 173 as defined by the Centralized Conferencing Framework [RFC5239]. They 174 are a Conference Control Server, a Floor Control Server, a number of 175 Foci, and a Notification Service. A conference control protocol 176 provides the interface between a conference control client and the 177 conference control server. A floor control protocol (e.g., BFCP 178 [RFC4582]) provides the interface between a floor control client and 179 the floor control server. A call signaling protocol (e.g., SIP, 180 H.323, Q.931, ISUP, etc.) provides the interface between a call 181 signaling client and a Focus. A notification protocol (e.g., SIP- 182 based event notifications [RFC3265]) provides the interface between 183 the conferencing client and the Notification Service. Within a 184 conference, the conference control server, floor control server, and 185 focus can modify the information in the conference object. 187 ............................................................... 188 . Conferencing Server . 189 . +---------------------------------------------------+ . 190 . | C o n f e r e n c e o b j e c t | . 191 . +-+--------------------------------------------------+| . 192 . | C o n f e r e n c e o b j e c t || . 193 . +-+---------------------------------------------------+|| . 194 . | C o n f e r e n c e o b j e c t ||| . 195 . | +--------------------------------------------------+||| . 196 . | | Conference Information Data Model |||| . 197 . | | +----------------------------------------------+ |||| . 198 . | | | Conference description (times, duration) | |||| . 199 . | | +----------------------------------------------+ |||| . 200 . | | +----------------------------------------------+ |||| . 201 . | | | Host information | |||| . 202 . | | +----------------------------------------------+ |||| . 203 . | | +----------------------------------------------+ |||| . 204 . | | | Conference state | |||| . 205 . | | +----------------------------------------------+ |||| . 206 . | | +----------------------------------------------+ |||| . 207 . | | | Floor information | |||| . 208 . | | +----------------------------------------------+ |||| . 209 . | | +----------------------------------------------+ |||| . 210 . | | | Membership (users, capacity) | |||| . 211 . | | +----------------------------------------------+ |||| . 212 . | | +----------------------------------------------+ |||| . 213 . | | | Sidebars, Etc. | |||| . 214 . | | +----------------------------------------------+ |||| . 215 . | | +----------------------------------------------+ |||| . 216 . | | | Etc. | |||| . 217 . | | +----------------------------------------------+ |||+ . 218 . | +--------------------------------------------------+|+ . 219 . +----^------------------^-------------^--------|------+ . 220 . | | | | . 221 . +------v-------+ +--------v-----+ +-----v-+ +----v-------+ . 222 . | Conference | | Floor | | | | | . 223 . | Control | | Control | |Foci | |Notification| . 224 . | Server | | Server | | | |Service | . 225 . +-----^--------+ +---^----------+ +-^-----+ +------------+ . 226 ........|..............|..............|..........|............. 227 |Conference |Floor |Call |Notification 228 |Control |Control |Signaling |Protocol 229 |Protocol |Protocol |Protocol | 230 ........v..............v..............v..........v............. 231 . C o n f e r e n c i n g C l i e n t . 232 ............................................................... 234 Figure 1: Conference Server Architecture 236 The Session Initiation Protocol (SIP) Event Package for Conference 237 State, specified in [RFC4575], already defines a data format for 238 conferences. However, that model is SIP specific and lacks elements 239 related to some of the functionality defined by the Centralized 240 Conferencing Framework [RFC5239] (e.g., floor control). The data 241 model defined in this document constitutes a superset of the data 242 format defined in [RFC4575]. The result is a data format that 243 supports more call signaling protocols besides SIP and that covers 244 all the functionality defined in the Centralized Conferencing 245 Framework [RFC5239]. 247 2. Terminology 249 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 250 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 251 document are to be interpreted as described in RFC 2119 [RFC2119]. 253 This document uses the terminology defined in the Centralized 254 Conferencing Framework [RFC5239], the SIPPING conferencing framework 255 [RFC4353] and the BFCP (Binary Floor Control Protocol) specification 256 [RFC4582]. Readers of this document should be familiar with the 257 terminology used in those documents. 259 3. Overview 261 The data model specified in this document is the result of extending 262 the data format defined in [RFC4575] with new elements. Examples of 263 such extensions include scheduling elements, media control elements, 264 floor control elements, non-SIP URIs, and addition of localization 265 extensions to text elements. This data model can be used by 266 conference servers providing different types of basic conferences. 267 It is expected that this data model can be further extended with new 268 elements in the future in order to implement additional advanced 269 features. 271 3.1. Data Model Format 273 A conference object document is an XML [W3C.REC-xml-20001006] 274 document that MUST be well formed and SHOULD be valid. Conference 275 object documents MUST be based on XML 1.0 and SHOULD be encoded using 276 UTF-8. 278 3.2. Data Model Namespace 280 This specification defines a new namespace specification for 281 identifying the elements defined in the data model. This namespace 282 is as follows: 284 urn:ietf:params:xml:ns:xcon-conference-info 286 3.3. The Conference Object Identifier 288 The conference object identifier (XCON-URI) can be viewed as a key to 289 accessing a specific conference object. It can be used, for 290 instance, by the conference control protocol to access, manipulate 291 and delete a conference object. A conference object identifier is 292 provided to the conferencing client by the conference notification 293 service or through out-of-band mechanisms (e.g. E-Mail). 295 A conferencing system may maintain a relationship between the 296 conference object identifiers and the identifiers associated with 297 each of the complementary centralized conferencing protocols (e.g., 298 call signaling protocols, BFCP, etc.). To facilitate the maintenance 299 of these relationships, the conference object identifier acts as a 300 top level identifier within the conferencing system for the purpose 301 of identifying the interfaces for these other protocols. This 302 implicit binding provides a structured mapping of the various 303 protocols with the associated conference object Identifier. Figure 2 304 illustrates the relationship between the identifiers used for the 305 protocols and the general conference object identifier (XCON-URI). 307 +--------------------------+ 308 | Conference | 309 | Object | 310 | Identifier | 311 +--------------------------+ 312 | xcon:Ji092i@example.com | 313 +------+-------------------+ 314 | 315 | 316 | 317 +-----------------+---------------+ 318 | | 319 +-----------+-----------+ +----------+---------+ 320 | CSP Conference IDs | |BFCP 'Conference ID'| 321 +-----------------------+ +--------------------+ 322 | h323:i092@example.com | | i092 | 323 | tel:+44(0)2920930033 | +----------+---------+ 324 | sip:i092@example.com | | 325 +-----------------------+ +-------+--------+ 326 | BFCP 'Floor ID'| 327 +----------------+ 328 | 543 | 329 | 236 | 330 +----------------+ 332 Figure 2: Conference Object Mapping 334 In Figure 2, the conference object identifier acts as the top level 335 key in the identification process. The call signaling protocols have 336 an associated conference user identifier, often represented in the 337 form of URIs. The binary floor control protocol, as defined in 338 [RFC4582], defines the 'conference ID' identifier which represents a 339 conference instance within floor control. When created within the 340 conferencing system, the 'conference ID' has a 1:1 mapping to the 341 unique conference object Identifier(XCON-URI). Operations associated 342 with the conference control protocols are directly associated with 343 the conference object, thus the primary identifier associated with 344 these protocols is the conference object identifier(XCON-URI). The 345 mappings between additional protocols/interface is not strictly 1:1 346 and does allow for multiple occurrences. For example, multiple call 347 signaling protocols will each have a representation that is 348 implicitly linked to the top level conference object identifier e.g. 349 H323 and SIP URIs that represent a conference instance. It should be 350 noted that a conferencing system is free to structure such 351 relationships as required and this information is just included as a 352 guideline that can be used. 354 Further elements can be added to the tree representation in Figure 2 355 to enable a complete representation of a conference instance within a 356 conferencing system. 358 3.3.1. Conference Object URI Definition 360 XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] 362 conf-object-id = 1*( unreserved / "+" / "=" / "/" ) 364 host, port, and unreserved are defined in RFC3986[RFC3986] 366 3.4. Data Model Structure 368 The information in this data model is structured in the following 369 manner. All the information related to a conference is contained in 370 a element. The element contains 371 the following child elements: 373 o The element describes the conference as a 374 whole. It has, for instance, information about the URI of the 375 conference, maximum users allowed in the conference, media 376 available in the conference, or the time the conference will 377 start. 378 o The element contains information about the entity 379 hosting the conference (e.g., its URI). 380 o The element informs the subscribers about the 381 changes in the overall conference information. 382 o The element contains information about the 383 status of the different floors in the conference. 384 o The element describes the membership information as a 385 whole. The element contains a set of child 386 elements, each describing a single participant in the conference. 387 o If a participant in the main conference joins a sidebar, a new 388 element is created in the conference referenced from the 389 element or under one of the 390 elements. 392 Note that some of the elements described above such , , , or are not defined in the data model but are defined in the data 395 format of [RFC4575]. We describe them here because they are part of 396 the basic structure of the data model. 398 4. Data Model Definition 400 The following non-normative diagram shows the structure of conference 401 object documents. The operator "!" preceding an element indicates 402 that the element is mandatory in the data model. The operator "*" 403 following an element indicates that the element is introduced and 404 defined in this document. That is, elements without a "*" have 405 already been defined in [RFC4575]. 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 | | | | |--