idnits 2.17.1 draft-ietf-xcon-common-data-model-32.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 (Sep 20, 2011) is 4596 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) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 3 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: March 23, 2012 D. Morgan 6 Fidelity Investments 7 J. Urpalainen 8 Nokia 9 Sep 20, 2011 11 Conference Information Data Model for Centralized Conferencing (XCON) 12 draft-ietf-xcon-common-data-model-32.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 March 23, 2012. 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 . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 76 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 77 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 78 3.3. The Conference Object Identifier . . . . . . . . . . . . . 6 79 3.3.1. Conference Object URI Definition . . . . . . . . . . . 8 80 3.3.2. Normalization and Conference Object URI Comparison . . 8 81 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 8 82 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 9 83 4.1. . . . . . . . . . . . . . . . . . . . . 13 84 4.2. . . . . . . . . . . . . . . . . . 13 85 4.2.1. . . . . . . . . . . . . . . . . . . . . . . 14 86 4.2.2. . . . . . . . . . . . . . . . . . . . 14 87 4.2.3. . . . . . . . . . . . . . . . . . . . 14 88 4.2.4. . . . . . . . . . . . . . . . . . . . 14 89 4.2.5. . . . . . . . . . . . . . . . . . . 14 90 4.2.6. . . . . . . . . . . . . . . . . . . . . . 16 91 4.2.7. . . . . . . . . . . . . . . . . . . 16 92 4.3. . . . . . . . . . . . . . . . . . . . . . . . 19 93 4.4. . . . . . . . . . . . . . . . . . . . . 19 94 4.4.1. . . . . . . . . 19 95 4.5. . . . . . . . . . . . . . . . . . . . 19 96 4.5.1. . . . . . . . . . . . . . . . . . . . 19 97 4.5.2. . . . . . . . . . . . . . . . . . 20 98 4.5.3. . . . . . . . . . . . . . . . 20 99 4.5.4. . . . . . . . . . . . . . . 20 100 4.6. . . . . . . . . . . . . . . . . . . . . . . . . . 21 101 4.6.1. . . . . . . . . . . . . . . . . . . . 21 102 4.6.2. . . . . . . . . . . . . . . . 22 103 4.6.3. . . . . . . . . . . . . . . . . . 23 104 4.6.4. . . . . . . . . . . . . . . . . . . 24 105 4.6.5. and Its Sub-elements . . . . . . . . . . 24 106 4.6.5.1. . . . . . . . . . . . . . . . 26 107 4.6.5.2. . . . . . . . . . . . . . . . . . . . . . 26 108 4.6.5.3. . . . . . . . . . 26 109 4.6.5.4. . . . . . . . . . 26 110 4.6.5.5. . . . . . . . . . 27 111 4.6.5.6. . . . . . . . . . . . . . . . . . . . . 27 112 4.7. . . . . . . . . . . . . . . . . . . . . 28 113 4.8. . . . . . . . . . . . . . . . . . . . . 28 114 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29 115 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 39 116 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40 117 8. Security Considerations . . . . . . . . . . . . . . . . . . . 49 118 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 119 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 51 120 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51 121 9.3. Conference Object Identifier Registration . . . . . . . . 52 122 9.4. Conference User Identifier Registration . . . . . . . . . 53 123 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54 124 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 125 11.1. Normative References . . . . . . . . . . . . . . . . . . . 54 126 11.2. Informative References . . . . . . . . . . . . . . . . . . 55 127 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55 128 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 83 129 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 93 131 1. Introduction 133 There is a core data set of conference information that is utilized 134 in any conference, independent of the specific conference media. 135 This core data set called the 'conference information data model' is 136 defined in this document using an Extensible Markup Language (XML)- 137 based format. The conference information data model defined in this 138 document is logically represented by the conference object. 140 Conference objects are a fundamental concept in Centralized 141 Conferencing, as described in the Centralized Conferencing Framework 142 [RFC5239]. The conference object represents a particular 143 instantiation of a conference information data model. Consequently, 144 conference objects use the XML format defined in this document. 146 The Session Initiation Protocol (SIP) Event Package for Conference 147 State, specified in [RFC4575], already defines a data format for 148 conferences. However, that model is SIP specific and lacks elements 149 related to some of the functionality defined by the Centralized 150 Conferencing Framework [RFC5239] (e.g., floor control). The data 151 model defined in this document constitutes a superset of the data 152 format defined in [RFC4575]. The result is a data format that 153 supports more call signaling protocols besides SIP and that covers 154 all the functionality defined in the Centralized Conferencing 155 Framework [RFC5239]. 157 2. Terminology 159 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 160 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 161 document are to be interpreted as described in RFC 2119 [RFC2119]. 163 This document uses the terminology defined in the Centralized 164 Conferencing Framework [RFC5239], the SIPPING conferencing framework 165 [RFC4353] and the BFCP (Binary Floor Control Protocol) specification 166 [RFC4582]. Readers of this document should be familiar with the 167 terminology used in those documents. 169 3. Overview 171 The data model specified in this document is the result of extending 172 the data format defined in [RFC4575] with new elements. Examples of 173 such extensions include scheduling elements, media control elements, 174 floor control elements, non-SIP URIs, and addition of localization 175 extensions to text elements. This data model can be used by 176 conference servers providing different types of basic conferences. 178 It is expected that this data model can be further extended with new 179 elements in the future in order to implement additional advanced 180 features. 182 3.1. Data Model Format 184 A conference object document is an XML [W3C.REC-xml-20081126] 185 document. Conference object documents MUST be based on Extensible 186 Markup Language (XML) 1.0 and MUST be encoded using UTF-8. 188 The normative description of the syntax of the conference object 189 document, for use by implementors of parsers and generators, is found 190 in the RelaxNG schema provided in Section 5. Compliant messages MUST 191 meet the requirements of that schema. 193 3.2. Data Model Namespace 195 This specification defines a new namespace specification for 196 identifying the elements defined in the data model. This namespace 197 is as follows: 199 urn:ietf:params:xml:ns:xcon-conference-info 201 3.3. The Conference Object Identifier 203 The conference object identifier (XCON-URI) can be viewed as a key to 204 accessing a specific conference object. It can be used, for 205 instance, by the conference control protocol to access, manipulate 206 and delete a conference object. A conference object identifier is 207 provided to the conferencing client by the conference notification 208 service or through out-of-band mechanisms (e.g. E-Mail). 210 A conferencing system may maintain a relationship between the 211 conference object identifiers and the identifiers associated with 212 each of the complementary centralized conferencing protocols (e.g., 213 call signaling protocols, BFCP, etc.). To facilitate the maintenance 214 of these relationships, the conference object identifier acts as a 215 top level identifier within the conferencing system for the purpose 216 of identifying the interfaces for these other protocols. This 217 implicit binding provides a structured mapping of the various 218 protocols with the associated conference object Identifier. Figure 1 219 illustrates the relationship between the identifiers used for the 220 protocols and the general conference object identifier (XCON-URI). 222 +--------------------------+ 223 | Conference | 224 | Object | 225 | Identifier | 226 +--------------------------+ 227 | xcon:Ji092i@example.com | 228 +------+-------------------+ 229 | 230 | 231 | 232 +-----------------+---------------+ 233 | | 234 +-----------+-----------+ +----------+---------+ 235 | CSP Conference IDs | |BFCP 'Conference ID'| 236 +-----------------------+ +--------------------+ 237 | h323:i092@example.com | | i092 | 238 | tel:+44(0)2920930033 | +----------+---------+ 239 | sip:i092@example.com | | 240 +-----------------------+ +-------+--------+ 241 | BFCP 'Floor ID'| 242 +----------------+ 243 | 543 | 244 | 236 | 245 +----------------+ 247 Figure 1: Conference Object Mapping 249 In Figure 1, the conference object identifier acts as the top level 250 key in the identification process. The call signaling protocols have 251 an associated conference user identifier, often represented in the 252 form of URIs. The binary floor control protocol, as defined in 253 [RFC4582], defines the 'conference ID' identifier which represents a 254 conference instance within floor control. When created within the 255 conferencing system, the 'conference ID' has a 1:1 mapping to the 256 unique conference object Identifier(XCON-URI). Operations associated 257 with the conference control protocols are directly associated with 258 the conference object, thus the primary identifier associated with 259 these protocols is the conference object identifier(XCON-URI). The 260 mappings between additional protocols/interface is not strictly 1:1 261 and does allow for multiple occurrences. For example, multiple call 262 signaling protocols will each have a representation that is 263 implicitly linked to the top level conference object identifier e.g. 264 H323 and SIP URIs that represent a conference instance. It should be 265 noted that a conferencing system is free to structure such 266 relationships as required and this information is just included as a 267 guideline that can be used. 269 Further elements can be added to the tree representation in Figure 1 270 to enable a complete representation of a conference instance within a 271 conferencing system. 273 3.3.1. Conference Object URI Definition 275 XCON-URI = "xcon" ":" [conf-object-id "@"] host 277 conf-object-id = 1*( unreserved / "+" / "=" / "/" ) 279 host and unreserved are defined in RFC3986[RFC3986] 281 An XCON-URI is not designed to be resolved, and an application MUST 282 NOT attempt to perform a standard DNS lookup on the host portion of 283 such a URI in an attempt to discover an IP address or port at which 284 to connect. 286 3.3.2. Normalization and Conference Object URI Comparison 288 In order to facilitate the comparison of the XCON-URI identifiers, 289 all the components of the identifiers MUST be converted to lowercase. 290 After normalizing the URI strings, the URIs comparison MUST applied a 291 character-by-character basis as prescribed by RFC3986, Section 6.2.1. 293 The host construction, as defined in RFC3986 can take the form of an 294 IP address, which is not conventionally compared on a character-by- 295 character basis. The host part of an XCON-URI serves only as an 296 identifier; that is, it is never used as an address. The character- 297 by-character comparison still applies. 299 3.4. Data Model Structure 301 The information in this data model is structured in the following 302 manner. All the information related to a conference is contained in 303 a element. The element contains 304 the following child elements: 306 o The element describes the conference as a 307 whole. It has, for instance, information about the URI of the 308 conference, maximum users allowed in the conference, media 309 available in the conference, or the time the conference will 310 start. 312 o The element contains information about the entity 313 hosting the conference (e.g., its URI). 315 o The element informs the subscribers about the 316 changes in the overall conference information. 318 o The element contains information about the 319 status of the different floors in the conference. 321 o The element describes the membership information as a 322 whole. The element contains a set of child 323 elements, each describing a single participant in the conference. 325 o If a participant in the main conference joins a sidebar, a new 326 element is created in the conference referenced from the 327 element or under one of the 328 elements. 330 Note that some of the elements described above such , , , or are not defined in the data model in this specification but are 333 defined in the data format of [RFC4575]. We describe them here 334 because they are part of the basic structure of the data model. 336 4. Data Model Definition 338 The following non-normative diagram shows the structure of conference 339 object documents. The symbol "!" preceding an element indicates that 340 the element is REQUIRED in the data model. The symbol "*" following 341 an element indicates that the element is introduced and defined in 342 this document. That is, elements without a "*" have already been 343 defined in [RFC4575]. 345 ! 346 | 347 |-- 348 | |--* 349 | |-- 350 | |-- 351 | |-- 352 | |-- 353 | |--* 354 | |--* 355 | |--* 356 | |--* 357 | | |--* 358 | | | |--* 359 | | | |--* 360 | | | |--* 361 | | | |--* 362 | | | |--* 363 | | | |--* 364 | | | |--* 365 | | | |--* 366 | | ... 367 | |-- 368 | | |-- 369 | | | |-- 370 | | | |-- 371 | | | |-- 372 | | | |--* 373 | | ... 374 | |-- 375 | | |-- 376 | | | |-- 377 | | | |-- 378 | | | |-- 379 | | ... 380 | |-- 381 | | ... 382 | |-- 383 | | |-- 384 | | | |-- 385 | | | |-- 386 | | | |-- 387 | | | |--* 388 | | | |--* 389 | | | | |--* 390 | | | | | |--* 391 | | | | |--* 392 | | | | | |--* 393 | | | | ... 394 | | | |--* 395 | | | | |--* 396 | | | | |--* 397 | | | | ... 398 | | |-- 399 | | | |-- 400 | | | |-- 401 | | | |-- 402 | | | |--* 403 | | | |--* 404 | | | | |--* 405 | | | | | |--* 406 | | | | |--* 407 | | | | | |--* 408 | | | | ... 409 | | | |--* 410 | | | | |--* 411 | | | | |--* 412 | | | | ... 413 | | ... 414 | 415 |-- 416 | |-- 417 | |-- 418 | |-- 419 | | |-- 420 | | | |-- 421 | | | |-- 422 | ... 423 |-- 424 | |--* 425 | |-- 426 | |-- 427 | |-- 428 | 429 |--* 430 | |--* 431 | |--* 432 | |--* 433 | |--* 434 | | |--* 435 | | | |--!* 436 | | | |--* 437 | | | |--* 438 | | | |--* 439 | | | ... 440 | | ... 441 | 442 |-- 443 | |--* 444 | |--* 445 | |--* 446 | | |--* 447 | | | 448 | | |--* 449 | | | |--* 450 | | | | |-- * 451 | | 452 | |--* 453 | | 454 | |-- 455 | | |-- 456 | | |-- 457 | | |--* 458 | | |-- 459 | | | | 460 | | | ... 461 | | |-- 462 | | |-- 463 | | |--* 464 | | |--* 465 | | |--* 466 | | |-- 467 | | | |-- 468 | | | |-- 469 | | | |-- 470 | | | |-- 471 | | | |-- 472 | | | |-- 473 | | | |-- 474 | | | |-- 475 | | | | |-- 476 | | | | |-- 477 | | | | |--