idnits 2.17.1 draft-ietf-xcon-common-data-model-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 20. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2664. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2641. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2648. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2654. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 40 instances of too long lines in the document, the longest one being 65 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1870 has weird spacing: '...:choice minOc...' == Line 1894 has weird spacing: '...:choice minOc...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 4, 2006) is 6595 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '11' is defined on line 2593, but no explicit reference was found in the text -- Possible downref: Normative reference to a draft: ref. '1' ** Downref: Normative reference to an Informational draft: draft-ietf-sipping-conferencing-framework (ref. '4') -- Possible downref: Non-RFC (?) normative reference: ref. '5' ** Obsolete normative reference: RFC 2445 (ref. '6') (Obsoleted by RFC 5545) == Outdated reference: A later version (-11) exists of draft-ietf-geopriv-common-policy-08 Summary: 6 errors (**), 0 flaws (~~), 7 warnings (==), 9 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 Expires: October 6, 2006 Ericsson 5 D. Morgan 6 Fidelity Investments 7 R. Even 8 Polycom 9 April 4, 2006 11 A Common Conference Information Data Model for Centralized Conferencing 12 (XCON) 13 draft-ietf-xcon-common-data-model-00.txt 15 Status of this Memo 17 By submitting this Internet-Draft, each author represents that any 18 applicable patent or other IPR claims of which he or she is aware 19 have been or will be disclosed, and any of which he or she becomes 20 aware will be disclosed, in accordance with Section 6 of BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on October 6, 2006. 40 Copyright Notice 42 Copyright (C) The Internet Society (2006). 44 Abstract 46 This document collects, organizes, and describes the conference 47 variables that have been introduced in various protocol drafts of the 48 XCON and SIPPING working groups. The goal of this document is to 49 allow the conference control protocols to use a unified common 50 conference information data model for XCON. This document formally 51 defines an Extensible Markup Language (XML) Schema that represents 52 the common conference information in a conferencing server. The 53 information is modeled as a series of elements, each of which 54 contains a set of children and attributes. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 3. Common Conference Data . . . . . . . . . . . . . . . . . . . . 4 61 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 3.2. . . . . . . . . . . . . . . . . . 10 63 3.2.1. . . . . . . . . . . . . . . . . . . 11 64 3.2.2. . . . . . . . . . . . . . . . . . . . . . 13 65 3.2.3. . . . . . . . . . . . . . . . . . . . . 13 66 3.2.4. . . . . . . . . . . . . . . . . . 13 67 3.2.5. . . . . . . . . . . . . . . . . . . 13 68 3.3. . . . . . . . . . . . . . . . . . . . . . . . 14 69 3.4. . . . . . . . . . . . . . . . . . . . . 14 70 3.5. . . . . . . . . . . . . . . . . . . . 14 71 3.5.1. . . . . . . . . . . . . . . . . . . . . . . 15 72 3.5.2. . . . . . . . . . . . . . . . . . . . . 15 73 3.5.3. . . . . . . . . . . . . . . . . . . . . 15 74 3.5.4. . . . . . . . . . . . . . . . . . . . . . . . 15 75 3.6. . . . . . . . . . . . . . . . . . . . 16 76 3.7. . . . . . . . . . . . . . . . . . . . . . . . . . 17 77 3.7.1. . . . . . . . . . . . . . . . . . . . . 18 78 3.7.1.1. . . . . . . . . . . . . . . . . . . . . 18 79 3.7.2. . . . . . . . . . . . . . . . . . . . 19 80 3.7.3. . . . . . . . . . . . . . . . . . . . . . 19 81 3.7.4. . . . . . . . . . . . . . . 19 82 3.7.4.1. . . . . . . . . . . . . . . . 19 83 3.7.4.2. . . . . . . . . . . . . . . . . 20 84 3.7.4.2.1. . . . . . . . . . . . . . . . . . 20 85 3.7.4.2.1.1. . . . . . . . . . . . . . 21 86 3.7.4.2.1.2. . . . . . . . . . . . . . . 21 87 3.7.4.2.1.3. . . . . . . . . . . . 21 88 3.7.4.2.1.4. . . . . . . . . . . . . 21 89 3.7.4.2.1.5. . . . . . . . . . 21 90 3.7.4.2.1.6. . . . . . . . . . . . . 21 91 3.7.4.2.1.7. . . . . . . . . . . . . . 21 92 3.7.4.2.1.8. . . . . . . . . . . . 22 93 3.7.4.2.1.9. . . . . . . . . . . . . 22 94 3.7.4.2.1.10. . . . . . . . . . . 22 95 3.7.4.2.1.11. . . . . . . . . 22 97 3.7.4.2.2. . . . . . . . . . . . . . . . . . . 23 98 3.7.5. . . . . . . . . . . . . . . . . . . . . . . . . 24 99 3.8. . . . . . . . . . . . . . . . . . . . . 25 100 3.9. . . . . . . . . . . . . . . . . . . . . 25 101 3.10. Template . . . . . . . . . . . . . . . . . . . . . . . . . 25 102 3.10.1. . . . . . . . . . . . . . . . . . . 26 103 3.10.2. . . . . . . . . . . . . . . . . . . 26 104 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 26 105 5. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 43 106 6. XML example . . . . . . . . . . . . . . . . . . . . . . . . . 44 107 7. Security Considerations . . . . . . . . . . . . . . . . . . . 54 108 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 109 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54 110 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 111 10.1. Normative References . . . . . . . . . . . . . . . . . . . 54 112 10.2. Informative References . . . . . . . . . . . . . . . . . . 55 113 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 56 114 Intellectual Property and Copyright Statements . . . . . . . . . . 57 116 1. Introduction 118 This document defines an Extensible Markup Language (XML) Schema that 119 represents the common conference information in a conferencing 120 server. The information is modeled as a series of elements, each of 121 which contains children and attributes. 123 The common conference information is a part of the Conference Object. 124 The Conference Object contains two components: the "Common Conference 125 Information" component and the "Conference Template" component. The 126 common conference information component contains the XML schema, 127 which is used to represent the core information that is utilized in 128 any conference (capabilities,membership, roles, call control 129 signalling, media, etc...) and specifies the set of rights, 130 permissions and limitations pertaining to operations being performed 131 on a certain Conference Object. 133 This document gives an overview of the conference variables that have 134 been introduced in various protocol drafts of the XCON working group 135 to date and proposes to create a unified common conference 136 information data model for XCON. 138 This document has been constructed in compliance with the XCON 139 Framework [1] and the Session Initiation Protocol (SIP) Event Package 140 for Conference State [2]. It also incorporates data elements 141 proposed in several XCON WG and SIPPING WG drafts. 143 [Editors Note: This document is still in early stages of development 144 and is intended to trigger discussions.] 146 2. Terminology 148 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 149 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 150 this document are to be interpreted as described in RFC-2119 [3]. 152 This document uses the terminology defined in the XCON Conferencing 153 Framework [1] and the SIPPING Conferencing Framework [4]. In 154 addition, it uses definitions from The Binary Floor Control Protocol 155 [7]. 157 3. Common Conference Data 159 3.1. General 161 The conference object data model document is an XML [5] document that 162 MUST be well formed and SHOULD be valid. Conference object data 163 model documents MUST be based on XML 1.0 and SHOULD be encoded using 164 UTF-8. 166 A Common Conference information document begins with the root element 167 tag of conference-type. The has 168 the attribute 'entity' that contains the conference unique identifier 169 that identifies the conference being described in the document. 171 The element is comprised of , , , , 173 , , , , 174 , and child elements. A common 175 conference document must at least include the , , , , and 177 child elements. Some of this information can be represented 178 using the conference-info-type schema as defined in [2]. 180 Changes in the state of the conference should be communicated to the 181 subscribers using a conference package subscribers (ex. A Session 182 Initiation Protocol (SIP) Event Package for Conference State). 183 Critical changes should be communicated to specific subscribers, 184 perhaps those with unique roles. The conference policy control 185 protocol msy be used to retrieve the conference state at any time. 187 The following non-normative diagram gives an example of the overall 188 hierarchy used in this format. The operator "!" preceding an element 189 indicates that this element is MANDATORY in the data model. The 190 operator "*" preceding an element indicates that this element is 191 introduced/proposed in this draft. 193 [Editors Note: The non-normative diagram will be remove in the 194 following versions of the draft. Its uses is only to make easier the 195 reader to see the hierarchical position of the elements.] 197 ! 198 | 199 |--! 200 | |-- 201 | |-- 202 | |-- 203 | |-- 204 | |-- 205 | |-- 206 | |-- 207 | |--* 208 | |-- 209 | | |-- 210 | | | |-- 211 | | | |-- 212 | | | |-- 213 | | | |-- 214 | | | |-- 215 | | | |-- 216 | | | |-- 217 | | | |-- 218 | | ... 219 | |-- 220 | | |-- 221 | | | |-- 222 | | | |-- 223 | | | |-- 224 | | | |-- 225 | | |-- 226 | | | |-- 227 | | | |-- 228 | | |-- 229 | | | |-- 230 | | | |--* 231 | | |-- 232 | | | |-- 233 | | ... 234 | |-- 235 | | |-- 236 | | | |-- 237 | | | |-- 238 | | | |-- 239 | | |-- 240 | | | |-- 241 | | | |-- 242 | | |-- 243 | | | |-- 244 | | ... 245 | |-- 246 | | |-- 247 | | |-- 248 | | ... 249 | |--! 250 | | |--! 251 | | | |-- 252 | | | |-- 253 | | | |-- 254 | | | |-- 255 | | | |-- 256 | | | |-- 257 | | | | |-- 258 | | | | |-- 259 | | | | ... 260 | | |-- 261 | | | |-- 262 | | | |-- 263 | | | |-- 264 | | | |-- 265 | | | |-- 266 | | | |-- 267 | | | | |-- 268 | | | | |-- 269 | | | | ... 270 | | ... 271 | 272 |--! 273 | |-- 274 | |-- 275 | |--! 276 | | |--! 277 | | | |--! 278 | | | |-- 279 | | | |-- 280 | | |-- 281 | | | |-- 282 | | | |-- 283 | | |-- 284 | | | |-- 285 | ... 286 |--! 287 | |-- 288 | |-- 289 | |--! 290 | |-- 291 | 292 |-- 293 | |-- 294 | | |-- 295 | | | |-- 296 | | | ... 297 | | |-- 298 | | | |-- 299 | | | ... 300 | | |-- 301 | | | |-- 302 | | | ... 303 | | |-- 304 | | | |-- 305 | | | | |-- 306 | | | ... 307 | |--* 308 | | |--* 309 | |--* 310 | | |--* 311 | ... 312 | 313 |-- 314 | |-- 315 | |-- 316 | |-- 317 | | |-- 318 | | | |-- 319 | | | |-- 320 | | | |-- 321 | | | |-- 322 | | | |-- 323 | | | ... 324 | | ... 325 | 326 |--! 327 | |-- 328 | |-- 329 | |-- 330 | | |-- 331 | | |-- ... 332 | | 333 | |-- 334 | | |-- 335 | | |-- ... 336 | | |-- 337 | | |-- ... 338 | | 339 | |-- 340 | | |-- 341 | | |-- ... 342 | | |-- 343 | | |-- ... 344 | | 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 | | | | |--