idnits 2.17.1 draft-ietf-xcon-common-data-model-03.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 2809. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2820. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2827. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2833. ** 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 issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 2 instances of too long lines in the document, the longest one being 16 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 == 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). == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: The 'mute' control is used in conjunction with a audio stream to cease transmission of associated media. It has a 'Boolean' value. If this control is not specify, the access to the control is not available to the client and media SHOULD not be transported for the associated media stream. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: If this control is not specify, the access to the control is not available to the client and media SHOULD not be transported for the associated media stream. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: The element has a 'Boolen' value. A value of 'false' indicates that this user does not hold the floor in this moment. If this control is not specify, this user SHOULD not specify the floor option. -- 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 (October 10, 2006) is 6380 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '9' is defined on line 2758, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-ietf-xcon-framework-05 ** Obsolete normative reference: RFC 2445 (ref. '6') (Obsoleted by RFC 5545) Summary: 5 errors (**), 0 flaws (~~), 7 warnings (==), 7 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: Informational Ericsson 5 Expires: April 13, 2007 D. Morgan 6 Fidelity Investments 7 R. Even 8 Polycom 9 October 10, 2006 11 A Common Conference Information Data Model for Centralized Conferencing 12 (XCON) 13 draft-ietf-xcon-common-data-model-03.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 April 13, 2007. 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. Common Conference Policies . . . . . . . . . . . . . . . . 9 63 3.3. . . . . . . . . . . . . . . . . . 10 64 3.3.1. . . . . . . . . . . . . . . . . . . 11 65 3.3.2. . . . . . . . . . . . . . . . . . . . . . 13 66 3.3.3. . . . . . . . . . . . . . . . . . . . . 13 67 3.3.4. . . . . . . . . . . . . . . . . . 13 68 3.3.5. . . . . . . . . . . . . . . . . . . 13 69 3.3.6. . . . . . . . . . . . . . . . . . . 13 70 3.3.7. . . . . . . . . . . . . . . . . . . . . . . 14 71 3.3.7.1. mute . . . . . . . . . . . . . . . . . . . . . . . 14 72 3.3.7.2. pause-video . . . . . . . . . . . . . . . . . . . 14 73 3.3.7.3. gain . . . . . . . . . . . . . . . . . . . . . . . 15 74 3.4. . . . . . . . . . . . . . . . . . . . . . . . 15 75 3.5. . . . . . . . . . . . . . . . . . . . . 15 76 3.6. . . . . . . . . . . . . . . . . . . . 15 77 3.7. . . . . . . . . . . . . . . . . . . . . . . . . . 16 78 3.7.1. . . . . . . . . . . . . . . . . . 17 79 3.7.2. . . . . . . . . . . . . . . 18 80 3.7.2.1. . . . . . . . . . . . . . . . . 18 81 3.7.2.1.1. . . . . . . . . . . . . . . . . . 18 82 3.7.2.1.2. . . . . . . . . . . . . . . . . 19 83 3.7.2.1.3. . . . . . . . . . . . . . 19 84 3.7.2.1.4. . . . . . . . . . . . . . . 19 85 3.7.2.1.5. . . . . . . . . . . . 19 86 3.7.2.1.6. . . . . . . . . . . . . . . 19 87 3.7.2.1.7. . . . . . . . . . . . . . . . 19 88 3.7.2.1.8. . . . . . 20 89 3.7.2.1.9. . . . . . . . 20 90 3.7.2.1.10. . . . . . . . . . . . . 20 91 3.7.2.1.11. . . . . . . . . . . 20 92 3.7.2.2. . . . . . . . . . . . . . . . . . . . . 21 93 3.8. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 94 3.8.1. from-mixer, to-mixer . . . . . . . . . . . . . . . . . 23 95 3.8.1.1. . . . . . . . . . . . . . . . . . . . . . 23 97 3.9. . . . . . . . . . . . . . . . . . . . . 24 98 3.10. . . . . . . . . . . . . . . . . . . . . 24 99 4. RELAX NG schema . . . . . . . . . . . . . . . . . . . . . . . 24 100 5. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 48 101 6. XML example . . . . . . . . . . . . . . . . . . . . . . . . . 49 102 7. Security Considerations . . . . . . . . . . . . . . . . . . . 58 103 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 104 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 58 105 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58 106 10.1. Normative References . . . . . . . . . . . . . . . . . . . 58 107 10.2. Informative References . . . . . . . . . . . . . . . . . . 59 108 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 59 109 Intellectual Property and Copyright Statements . . . . . . . . . . 61 111 1. Introduction 113 This document defines an Extensible Markup Language (XML) Schema that 114 represents the conference object in a conferencing server. The 115 information is modeled as a series of elements, each of which 116 contains children and attributes. 118 The Conference Object contains the XML schema, which is used to 119 represent the core information that is utilized in any conference 120 (capabilities, membership, roles, call control signalling, media, 121 etc...) and specifies the set of rights, permissions and limitations 122 pertaining to operations being performed on a certain Conference 123 Object. 125 This document gives an overview of the conference variables that have 126 been introduced in various protocol drafts of the XCON working group 127 to date and proposes to create a unified common conference 128 information data model for XCON. 130 This document has been constructed in compliance with the XCON 131 Framework [1] and the Session Initiation Protocol (SIP) Event Package 132 for Conference State [2]. It also incorporates data elements 133 proposed in several XCON WG and SIPPING WG drafts. 135 2. Terminology 137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 138 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 139 this document are to be interpreted as described in RFC-2119 [3]. 141 This document uses the terminology defined in the XCON Conferencing 142 Framework [1] and the SIPPING Conferencing Framework [4]. In 143 addition, it uses definitions from The Binary Floor Control Protocol 144 [7]. 146 3. Common Conference Data 148 3.1. General 150 The conference object data model document is an XML [5] document that 151 MUST be well formed and SHOULD be valid. Conference object data 152 model documents MUST be based on XML 1.0 and SHOULD be encoded using 153 UTF-8. 155 A Common Conference information document begins with the root element 156 tag of conference-type. The has 157 the attribute 'entity' that contains the conference unique identifier 158 that identifies the conference being described in the document. 160 The element is comprised of , , , , 162 , , , child elements. A 163 common conference document must at least include the , , , and child 165 elements. Some of this information can be represented using the 166 conference-info-type schema as defined in [2]. 168 Changes in the state of the conference should be communicated to the 169 subscribers using a conference package subscribers (ex. A Session 170 Initiation Protocol (SIP) Event Package for Conference State). 171 Critical changes should be communicated to specific subscribers, 172 perhaps those with unique roles. The conference policy control 173 protocol msy be used to retrieve the conference state at any time. 175 The following non-normative diagram gives an example of the overall 176 hierarchy used in this format. The operator "!" preceding an element 177 indicates that this element is MANDATORY in the data model. The 178 operator "*" preceding an element indicates that this element is 179 introduced/proposed in this draft. 181 ! 182 | 183 |--! 184 | |-- 185 | |-- 186 | |-- 187 | |-- 188 | |-- 189 | |-- 190 | |-- 191 | |-- 192 | |-- 193 | | |-- 194 | | | |-- 195 | | | |-- 196 | | | |-- 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 | | | | ... 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 | | | | |--