idnits 2.17.1 draft-ietf-xcon-common-data-model-28.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. 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 (May 27, 2011) is 4711 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 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: 2 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: November 28, 2011 D. Morgan 6 Fidelity Investments 7 J. Urpalainen 8 Nokia 9 May 27, 2011 11 Conference Information Data Model for Centralized Conferencing (XCON) 12 draft-ietf-xcon-common-data-model-28.txt 14 Abstract 16 RFC5239 defines the idea of a centralized conferencing (XCON) as an 17 association of participants with a central focus. The state of a 18 conference is represented by a conference object. This document 19 defines an Extensible Markup Language (XML)-based conference 20 information data model to be used for conference objects. A 21 conference information data model is designed to convey information 22 about the conference and about participation in the conference. The 23 conference information data model defined in this document 24 constitutes an extension of the data format specified in the Session 25 Initiation Protocol (SIP) Event Package for Conference State. 27 Status of this Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at http://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on November 28, 2011. 44 Copyright Notice 46 Copyright (c) 2011 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (http://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 This document may contain material from IETF Documents or IETF 60 Contributions published or made publicly available before November 61 10, 2008. The person(s) controlling the copyright in some of this 62 material may not have granted the IETF Trust the right to allow 63 modifications of such material outside the IETF Standards Process. 64 Without obtaining an adequate license from the person(s) controlling 65 the copyright in such materials, this document may not be modified 66 outside the IETF Standards Process, and derivative works of it may 67 not be created outside the IETF Standards Process, except to format 68 it for publication as an RFC or to translate it into languages other 69 than English. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 74 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 75 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 76 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7 77 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 8 78 3.3. The Conference Object Identifier . . . . . . . . . . . . . 8 79 3.3.1. Conference Object URI Definition . . . . . . . . . . . 10 80 3.3.2. Normalization and Conference Object URI Comparison . . 10 81 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10 82 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11 83 4.1. . . . . . . . . . . . . . . . . . . . . 15 84 4.2. . . . . . . . . . . . . . . . . . 15 85 4.2.1. . . . . . . . . . . . . . . . . . . . . . . 16 86 4.2.2. . . . . . . . . . . . . . . . . . . . . 16 87 4.2.3. . . . . . . . . . . . . . . . . . . . . . . 16 88 4.2.4. . . . . . . . . . . . . . . . . . . . . . 16 89 4.2.5. . . . . . . . . . . . . . . . . . . . . . . 16 90 4.2.6. . . . . . . . . . . . . . . . . . . . 16 91 4.2.7. . . . . . . . . . . . . . . . . . . . 16 92 4.2.8. . . . . . . . . . . . . . . . . . . . 16 93 4.2.9. . . . . . . . . . . . . . . . . . . 17 94 4.2.10. . . . . . . . . . . . . . . . . . . . . . 18 95 4.2.11. . . . . . . . . . . . . . . . . . . . . 18 96 4.2.12. . . . . . . . . . . . . . . . . . 19 97 4.2.13. . . . . . . . . . . . . . . . . . . 19 98 4.3. . . . . . . . . . . . . . . . . . . . . . . . 21 99 4.4. . . . . . . . . . . . . . . . . . . . . 22 100 4.4.1. . . . . . . . . 22 101 4.4.2. . . . . . . . . . . . . . . . . . . . . . 22 102 4.4.3. . . . . . . . . . . . . . . . . . . . . . . . 22 103 4.4.4. . . . . . . . . . . . . . . . . . . . . . . . 22 104 4.5. . . . . . . . . . . . . . . . . . . . 22 105 4.5.1. . . . . . . . . . . . . . . . . . . . 22 106 4.5.2. . . . . . . . . . . . . . . . . . 23 107 4.5.3. . . . . . . . . . . . . . . . 23 108 4.5.4. . . . . . . . . . . . . . . 23 109 4.6. . . . . . . . . . . . . . . . . . . . . . . . . . 24 110 4.6.1. . . . . . . . . . . . . . . . . . . . 24 111 4.6.2. . . . . . . . . . . . . . . . 25 112 4.6.3. . . . . . . . . . . . . . . . . . 26 113 4.6.4. . . . . . . . . . . . . . . . . . . 27 114 4.6.5. and Its Sub-elements . . . . . . . . . . 27 115 4.6.5.1. . . . . . . . . . . . . . . . . . . 29 116 4.6.5.2. . . . . . . . . . . . . . . . . 29 117 4.6.5.3. . . . . . . . . . . . . . . . 29 118 4.6.5.4. . . . . . . . . . . . . . . . . . . . . . 29 119 4.6.5.5. . . . . . . . . . . . . . . . . . . . 29 120 4.6.5.6. . . . . . . . . . . . . . . . . . 29 121 4.6.5.7. . . . . . . . . . 30 122 4.6.5.8. . . . . . . . . . 30 123 4.6.5.9. . . . . . . . . . 30 124 4.6.5.10. . . . . . . . . . . . . . . . . . . . . 30 125 4.7. . . . . . . . . . . . . . . . . . . . . 31 126 4.8. . . . . . . . . . . . . . . . . . . . . 32 127 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 32 128 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 43 129 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 43 130 8. Security Considerations . . . . . . . . . . . . . . . . . . . 52 131 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 132 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 54 133 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 54 134 9.3. Conference Object Identifier Registration . . . . . . . . 55 135 9.4. Conference User Identifier Registration . . . . . . . . . 56 136 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57 137 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 138 11.1. Normative References . . . . . . . . . . . . . . . . . . . 57 139 11.2. Informative References . . . . . . . . . . . . . . . . . . 58 140 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 58 141 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 86 142 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96 144 1. Introduction 146 There is a core data set of conference information that is utilized 147 in any conference, independent of the specific conference media. 148 This core data set called the 'conference information data model' is 149 defined in this document using an Extensible Markup Language (XML)- 150 based format. The conference information data model defined in this 151 document is logically represented by the conference object. 153 Conference objects are a fundamental concept in Centralized 154 Conferencing, as described in the Centralized Conferencing Framework 155 [RFC5239]. A conference object contains data that represents a 156 conference during each of its various stages (e.g., created/creation, 157 reserved/reservation, active/activation, completed/completion). A 158 conference object can be manipulated using a conference control 159 protocol at a conference server. The conference object represents a 160 particular instantiation of a conference information data model. 161 Consequently, conference objects use the XML format defined in this 162 document. 164 A conference object contains the core information of a conference 165 (i.e., capabilities, membership, call control signaling, media, etc.) 166 and specifies by whom, and in which way, that information can be 167 manipulated. 169 Figure 1 shows the logical functional elements of a conference server 170 as defined by the Centralized Conferencing Framework [RFC5239]. They 171 are a Conference Control Server, a Floor Control Server, a number of 172 Foci, and a Notification Service. A conference control protocol 173 provides the interface between a conference control client and the 174 conference control server. A floor control protocol (e.g., BFCP 175 [RFC4582]) provides the interface between a floor control client and 176 the floor control server. A call signaling protocol (e.g., SIP, 177 H.323, Q.931, ISUP, etc.) provides the interface between a call 178 signaling client and a Focus. A notification protocol (e.g., SIP- 179 based event notifications [RFC3265]) provides the interface between 180 the conferencing client and the Notification Service. Within a 181 conference, the conference control server, floor control server, and 182 focus can modify the information in the conference object. 184 ............................................................... 185 . Conferencing Server . 186 . +---------------------------------------------------+ . 187 . | C o n f e r e n c e o b j e c t | . 188 . +-+--------------------------------------------------+| . 189 . | C o n f e r e n c e o b j e c t || . 190 . +-+---------------------------------------------------+|| . 191 . | C o n f e r e n c e o b j e c t ||| . 192 . | +--------------------------------------------------+||| . 193 . | | Conference Information Data Model |||| . 194 . | | +----------------------------------------------+ |||| . 195 . | | | Conference description (times, duration) | |||| . 196 . | | +----------------------------------------------+ |||| . 197 . | | +----------------------------------------------+ |||| . 198 . | | | Host information | |||| . 199 . | | +----------------------------------------------+ |||| . 200 . | | +----------------------------------------------+ |||| . 201 . | | | Conference state | |||| . 202 . | | +----------------------------------------------+ |||| . 203 . | | +----------------------------------------------+ |||| . 204 . | | | Floor information | |||| . 205 . | | +----------------------------------------------+ |||| . 206 . | | +----------------------------------------------+ |||| . 207 . | | | Membership (users, capacity) | |||| . 208 . | | +----------------------------------------------+ |||| . 209 . | | +----------------------------------------------+ |||| . 210 . | | | Sidebars, Etc. | |||| . 211 . | | +----------------------------------------------+ |||| . 212 . | | +----------------------------------------------+ |||| . 213 . | | | Etc. | |||| . 214 . | | +----------------------------------------------+ |||+ . 215 . | +--------------------------------------------------+|+ . 216 . +----^------------------^-------------^--------|------+ . 217 . | | | | . 218 . +------v-------+ +--------v-----+ +-----v-+ +----v-------+ . 219 . | Conference | | Floor | | | | | . 220 . | Control | | Control | |Foci | |Notification| . 221 . | Server | | Server | | | |Service | . 222 . +-----^--------+ +---^----------+ +-^-----+ +------------+ . 223 ........|..............|..............|..........|............. 224 |Conference |Floor |Call |Notification 225 |Control |Control |Signaling |Protocol 226 |Protocol |Protocol |Protocol | 227 ........v..............v..............v..........v............. 228 . C o n f e r e n c i n g C l i e n t . 229 ............................................................... 231 Figure 1: Conference Server Architecture 233 The Session Initiation Protocol (SIP) Event Package for Conference 234 State, specified in [RFC4575], already defines a data format for 235 conferences. However, that model is SIP specific and lacks elements 236 related to some of the functionality defined by the Centralized 237 Conferencing Framework [RFC5239] (e.g., floor control). The data 238 model defined in this document constitutes a superset of the data 239 format defined in [RFC4575]. The result is a data format that 240 supports more call signaling protocols besides SIP and that covers 241 all the functionality defined in the Centralized Conferencing 242 Framework [RFC5239]. 244 2. Terminology 246 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 247 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 248 document are to be interpreted as described in RFC 2119 [RFC2119]. 250 This document uses the terminology defined in the Centralized 251 Conferencing Framework [RFC5239], the SIPPING conferencing framework 252 [RFC4353] and the BFCP (Binary Floor Control Protocol) specification 253 [RFC4582]. Readers of this document should be familiar with the 254 terminology used in those documents. 256 3. Overview 258 The data model specified in this document is the result of extending 259 the data format defined in [RFC4575] with new elements. Examples of 260 such extensions include scheduling elements, media control elements, 261 floor control elements, non-SIP URIs, and addition of localization 262 extensions to text elements. This data model can be used by 263 conference servers providing different types of basic conferences. 264 It is expected that this data model can be further extended with new 265 elements in the future in order to implement additional advanced 266 features. 268 3.1. Data Model Format 270 A conference object document is an XML [W3C.REC-xml-20081126] 271 document. Conference object documents MUST be based on Extensible 272 Markup Language (XML) 1.0 and SHOULD be encoded using UTF-8. 274 The normative description of the syntax of the conference object 275 document, for use by implementors of parsers and generators, is found 276 in the RelaxNG schema provided in Section 5. Compliant messages MUST 277 meet the requirements of that schema. 279 3.2. Data Model Namespace 281 This specification defines a new namespace specification for 282 identifying the elements defined in the data model. This namespace 283 is as follows: 285 urn:ietf:params:xml:ns:xcon-conference-info 287 3.3. The Conference Object Identifier 289 The conference object identifier (XCON-URI) can be viewed as a key to 290 accessing a specific conference object. It can be used, for 291 instance, by the conference control protocol to access, manipulate 292 and delete a conference object. A conference object identifier is 293 provided to the conferencing client by the conference notification 294 service or through out-of-band mechanisms (e.g. E-Mail). 296 A conferencing system may maintain a relationship between the 297 conference object identifiers and the identifiers associated with 298 each of the complementary centralized conferencing protocols (e.g., 299 call signaling protocols, BFCP, etc.). To facilitate the maintenance 300 of these relationships, the conference object identifier acts as a 301 top level identifier within the conferencing system for the purpose 302 of identifying the interfaces for these other protocols. This 303 implicit binding provides a structured mapping of the various 304 protocols with the associated conference object Identifier. Figure 2 305 illustrates the relationship between the identifiers used for the 306 protocols and the general conference object identifier (XCON-URI). 308 +--------------------------+ 309 | Conference | 310 | Object | 311 | Identifier | 312 +--------------------------+ 313 | xcon:Ji092i@example.com | 314 +------+-------------------+ 315 | 316 | 317 | 318 +-----------------+---------------+ 319 | | 320 +-----------+-----------+ +----------+---------+ 321 | CSP Conference IDs | |BFCP 'Conference ID'| 322 +-----------------------+ +--------------------+ 323 | h323:i092@example.com | | i092 | 324 | tel:+44(0)2920930033 | +----------+---------+ 325 | sip:i092@example.com | | 326 +-----------------------+ +-------+--------+ 327 | BFCP 'Floor ID'| 328 +----------------+ 329 | 543 | 330 | 236 | 331 +----------------+ 333 Figure 2: Conference Object Mapping 335 In Figure 2, the conference object identifier acts as the top level 336 key in the identification process. The call signaling protocols have 337 an associated conference user identifier, often represented in the 338 form of URIs. The binary floor control protocol, as defined in 339 [RFC4582], defines the 'conference ID' identifier which represents a 340 conference instance within floor control. When created within the 341 conferencing system, the 'conference ID' has a 1:1 mapping to the 342 unique conference object Identifier(XCON-URI). Operations associated 343 with the conference control protocols are directly associated with 344 the conference object, thus the primary identifier associated with 345 these protocols is the conference object identifier(XCON-URI). The 346 mappings between additional protocols/interface is not strictly 1:1 347 and does allow for multiple occurrences. For example, multiple call 348 signaling protocols will each have a representation that is 349 implicitly linked to the top level conference object identifier e.g. 350 H323 and SIP URIs that represent a conference instance. It should be 351 noted that a conferencing system is free to structure such 352 relationships as required and this information is just included as a 353 guideline that can be used. 355 Further elements can be added to the tree representation in Figure 2 356 to enable a complete representation of a conference instance within a 357 conferencing system. 359 3.3.1. Conference Object URI Definition 361 XCON-URI = "xcon" ":" [conf-object-id "@"] host 363 conf-object-id = 1*( unreserved / "+" / "=" / "/" ) 365 host and unreserved are defined in RFC3986[RFC3986] 367 XCON-URI is a URI conference identifier and even though its 368 construction is similar to a URL, in this case, the XCON-URI can not 369 be resolved to addresses and/or ports. 371 3.3.2. Normalization and Conference Object URI Comparison 373 In order to facilitate the comparison of the XCON-URI identifiers, 374 all the components of the identifiers MUST be converted to lowercase. 375 After normalizing the URI strings, the URIs comparison MUST applied a 376 character-by-character basis as prescribed by RFC3986, Section 6.2.1. 378 The host construction, as defined in RFC3986 can take the form of an 379 IP address, which is not conventionally compared on a character-by- 380 character basis. The host part of an XCON-URI serves only as an 381 identifier; that is, it is never used as an address. The character- 382 by-character comparison still applies. 384 3.4. Data Model Structure 386 The information in this data model is structured in the following 387 manner. All the information related to a conference is contained in 388 a element. The element contains 389 the following child elements: 391 o The element describes the conference as a 392 whole. It has, for instance, information about the URI of the 393 conference, maximum users allowed in the conference, media 394 available in the conference, or the time the conference will 395 start. 397 o The element contains information about the entity 398 hosting the conference (e.g., its URI). 400 o The element informs the subscribers about the 401 changes in the overall conference information. 403 o The element contains information about the 404 status of the different floors in the conference. 406 o The element describes the membership information as a 407 whole. The element contains a set of child 408 elements, each describing a single participant in the conference. 410 o If a participant in the main conference joins a sidebar, a new 411 element is created in the conference referenced from the 412 element or under one of the 413 elements. 415 Note that some of the elements described above such , , , or are not defined in the data model in this specification but are 418 defined in the data format of [RFC4575]. We describe them here 419 because they are part of the basic structure of the data model. 421 4. Data Model Definition 423 The following non-normative diagram shows the structure of conference 424 object documents. The symbol "!" preceding an element indicates that 425 the element is REQUIRED in the data model. The symbol "*" following 426 an element indicates that the element is introduced and defined in 427 this document. That is, elements without a "*" have already been 428 defined in [RFC4575]. 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 | | | | |--