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