idnits 2.17.1 draft-novo-xcon-common-data-model-01.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 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2300. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2277. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2284. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2290. ** 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 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. 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). -- 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 (March 06, 2006) is 6620 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: '14' is defined on line 2219, but no explicit reference was found in the text == Unused Reference: '15' is defined on line 2223, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 2228, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 2232, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 2237, 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-07 Summary: 5 errors (**), 0 flaws (~~), 10 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: September 7, 2006 Ericsson 5 D. Morgan 6 Fidelity Investments 7 March 06, 2006 9 A Common Conference Information Data Model for Centralized Conferencing 10 (XCON) 11 draft-novo-xcon-common-data-model-01.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on September 7, 2006. 38 Copyright Notice 40 Copyright (C) The Internet Society (2006). 42 Abstract 44 This document collects, organizes, and describes the conference 45 variables that have been introduced in various protocol drafts of the 46 XCON and SIPPING working groups. The goal of this document is to 47 allow the conference control protocols to use a unified common 48 conference information data model for XCON. This document formally 49 defines an Extensible Markup Language (XML) Schema that represents 50 the common conference information in a conferencing server. The 51 information is modeled as a series of elements, each of which 52 contains a set of children and attributes. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 3. Common Conference Data . . . . . . . . . . . . . . . . . . . . 3 59 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3.2. . . . . . . . . . . . . . . . . . 9 61 3.2.1. . . . . . . . . . . . . . . . . . . 10 62 3.2.2. . . . . . . . . . . . . . . . . . . . . . 11 63 3.2.3. . . . . . . . . . . . . . . . . . . . . 11 64 3.2.4. . . . . . . . . . . . . . . . . . 12 65 3.2.5. . . . . . . . . . . . . . . . . . . 12 66 3.3. . . . . . . . . . . . . . . . . . . . . . . . 12 67 3.4. . . . . . . . . . . . . . . . . . . . . 12 68 3.5. . . . . . . . . . . . . . . . . . . . 13 69 3.6. . . . . . . . . . . . . . . . . . . . 13 70 3.7. . . . . . . . . . . . . . . . . . . . . . . . . . 13 71 3.7.1. . . . . . . . . . . . . . . . . . . . . 14 72 3.7.2. . . . . . . . . . . . . . . . . . . . 14 73 3.7.3. . . . . . . . . . . . . . . . . . . . . . 14 74 3.7.4. . . . . . . . . . . . . . . 14 75 3.7.4.1. . . . . . . . . . . . . . . . 15 76 3.7.4.2. . . . . . . . . . . . . . . . . 15 77 3.7.4.2.1. . . . . . . . . . . . . . . . . . 15 78 3.7.4.2.2. . . . . . . . . . . . . . . . . . . 16 79 3.7.5. . . . . . . . . . . . . . . . . . . . . . . . . 17 80 3.8. . . . . . . . . . . . . . . . . . . . . 17 81 3.9. . . . . . . . . . . . . . . . . . . . . 18 82 3.10. Template . . . . . . . . . . . . . . . . . . . . . . . . . 18 83 3.10.1. . . . . . . . . . . . . . . . . . . 18 84 3.10.2. . . . . . . . . . . . . . . . . . . 18 85 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 18 86 5. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 35 87 6. XML example . . . . . . . . . . . . . . . . . . . . . . . . . 35 88 7. Security Considerations . . . . . . . . . . . . . . . . . . . 45 89 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 90 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 45 91 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 92 10.1. Normative References . . . . . . . . . . . . . . . . . . . 46 93 10.2. Informative References . . . . . . . . . . . . . . . . . . 46 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 48 95 Intellectual Property and Copyright Statements . . . . . . . . . . 49 97 1. Introduction 99 This document defines an Extensible Markup Language (XML) Schema that 100 represents the common conference information in a conferencing 101 server. The information is modeled as a series of elements, each of 102 which contains children and attributes. 104 The common conference information is a part of the Conference Object. 105 The Conference Object contains two components: the "Common Conference 106 Information" component and the "Conference Template" component. The 107 common conference information component contains the XML schema, 108 which is used to represent the core information that is utilized in 109 any conference (capabilities,membership, roles, call control 110 signalling, media, etc...) and specifies the set of rights, 111 permissions and limitations pertaining to operations being performed 112 on a certain Conference Object. 114 This document gives an overview of the conference variables that have 115 been introduced in various protocol drafts of the XCON working group 116 to date and proposes to create a unified common conference 117 information data model for XCON. 119 This document has been constructed in compliance with the XCON 120 Framework [1] and the Session Initiation Protocol (SIP) Event Package 121 for Conference State [2]. It also incorporates data elements 122 proposed in several XCON WG and SIPPING WG drafts. 124 [Editors Note: This document is still in early stages of development 125 and is intended to trigger discussions.] 127 2. Terminology 129 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 130 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 131 this document are to be interpreted as described in RFC-2119 [3]. 133 This document uses the terminology defined in the XCON Conferencing 134 Framework [1] and the SIPPING Conferencing Framework [4]. In 135 addition, it uses definitions from The Binary Floor Control Protocol 136 [7]. 138 3. Common Conference Data 140 3.1. General 142 The conference object data model document is an XML [5] document that 143 MUST be well formed and SHOULD be valid. Conference object data 144 model documents MUST be based on XML 1.0 and SHOULD be encoded using 145 UTF-8. 147 A Common Conference information document begins with the root element 148 tag of conference-type. The has 149 the attribute 'entity' that contains the conference URI that 150 identifies the conference being described in the document. 152 The element is comprised of , , , , 154 , , , , 155 , and child elements. A common 156 conference document must at least include the , , , , and 158 child elements. Some of this information can be represented 159 using the conference-info-type schema as defined in [2]. 161 Changes in the state of the conference should be communicated to the 162 subscribers using a conference package subscribers (ex. A Session 163 Initiation Protocol (SIP) Event Package for Conference State). 164 Critical changes should be communicated to specific subscribers, 165 perhaps those with unique roles. 167 The following non-normative diagram gives an example of the overall 168 hierarchy used in this format. The operator "!" preceding an element 169 indicates that this element is MANDATORY in the data model. The 170 operator "*" preceding an element indicates that this element is 171 introduced/proposed in this draft. 173 [Editors Note: The non-normative diagram will be remove in the 174 following versions of the draft. Its uses is only to make easier the 175 reader to see the hierarchical position of the elements.] 177 ! 178 | 179 |--! 180 | |-- 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 | | |--! 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 | | | | |-- 2112 2115 2116 2117 sips:conference@example.com;grid=40 2118 private with Bob 2119 2120 2121 2124 2125 2126 2127 2128 2129 2130 2131 2132 2134 Note that due to RFC formatting conventions, this documents splits 2135 lines whose content would exceed 72 characters. Two backslash 2136 characters mark where the lines folding has taken place. These 2137 backslash would not appear in the actual XML data model. 2139 7. Security Considerations 2141 A malicious user can manipulate parts of the Conference Information 2142 Data Model privileges document giving themselves and others 2143 privileges to manipulate the data model. It is very important that 2144 only authorized clients are able to manipulate the Conference 2145 Information Data Model document. Any conference control protocol 2146 MUST provide authentication, confidentiality and integrity. 2148 8. IANA Considerations 2150 9. Acknowledgements 2152 This document is really a distillation of many ideas discussed over a 2153 long period of time. These ideas were contributed by many different 2154 drafts in the XCON working group and the SIPPING working group. Roni 2155 Even, and Orit Levin contributed with many good concepts that are 2156 described here. Also I would like to thanks Adam Roach, Mary Barnes, 2157 Chris Boulton, Umesh Chandra, Orit Levin, and Jari Urpilainen for 2158 their comments. 2160 10. References 2162 10.1. Normative References 2164 [1] Barnes, M. and C. Boulton, "A Framework and Data Model for 2165 Centralized Conferencing", draft-barnes-xcon-framework-02 (work 2166 in progress), February 2005. 2168 [2] Rosenberg, J., "A Session Initiation Protocol (SIP) Event 2169 Package for Conference State", 2170 draft-ietf-sipping-conference-package-12 (work in progress), 2171 July 2005. 2173 [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2174 Levels", BCP 14, RFC 2119, March 1997. 2176 [4] Rosenberg, J., "A Framework for Conferencing with the Session 2177 Initiation Protocol", 2178 draft-ietf-sipping-conferencing-framework-05 (work in progress), 2179 May 2005. 2181 [5] Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, 2182 "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C 2183 FirstEdition REC-xml-20001006, October 2000. 2185 [6] Dawson, F. and Stenerson, D., "Internet Calendaring and 2186 Scheduling Core Object Specification (iCalendar)", RFC 2445, 2187 November 1998. 2189 10.2. Informative References 2191 [7] Camarillo, G., "The Binary Floor Control Protocol (BFCP)", 2192 draft-ietf-xcon-bfcp-06 (work in progress), December 2005. 2194 [8] Khartabil, H., "The Conference Policy Control Protocol (CPCP)", 2195 draft-ietf-xcon-cpcp-01 (work in progress), October 2004. 2197 [9] Levin, O., "Centralized Conference Control Protocol", 2198 draft-levin-xcon-cccp-04 (work in progress), January 2006. 2200 [10] Camarillo, G., "A Session Initiation Protocol (SIP) Event 2201 Package for Media Policy", 2202 draft-camarillo-sipping-policy-package-00 (work in progress), 2203 October 2003. 2205 [11] Koskelainen, P. and H. Khartabil, "An Extensible Markup 2206 Language (XML) Configuration Access Protocol (XCAP) Usage for 2207 Conference Policy Manipulation", 2208 draft-koskelainen-xcon-xcap-cpcp-usage-02 (work in progress), 2209 February 2004. 2211 [12] Schulzrinne, H., "A Document Format for Expressing Privacy 2212 Preferences", draft-ietf-geopriv-common-policy-07 (work in 2213 progress), February 2006. 2215 [13] Boulton, C. and U. Chandra, "Media Policy Templates for XCON", 2216 draft-boulton-xcon-media-template-02 (work in progress), 2217 October 2005. 2219 [14] Even, R., "Conferencing media policy requirements", 2220 draft-even-sipping-media-policy-requirements-00 (work in 2221 progress), February 2003. 2223 [15] Mahy, R. and N. Ismail, "Media Policy Manipulation in the 2224 Conference Policy Control Protocol", 2225 draft-mahy-sipping-media-policy-control-00 (work in progress), 2226 February 2003. 2228 [16] Levin, O., "Conference Policy Control Protocol for Centralized 2229 Conferencing", draft-levin-xcon-cpcp-00 (work in progress), 2230 June 2003. 2232 [17] Camarillo, G., "Session Description Protocol (SDP) Format for 2233 Binary Floor Control Protocol (BFCP) Streams", 2234 draft-ietf-mmusic-sdp-bfcp-03 (work in progress), 2235 December 2005. 2237 [18] Khartabil, H. and A. Niemi, "Privileges for Manipulating a 2238 Conference Policy", 2239 draft-ietf-xcon-conference-policy-privileges-01 (work in 2240 progress), October 2004. 2242 Authors' Addresses 2244 Oscar Novo 2245 Ericsson 2246 Hirsalantie 11 2247 Jorvas 02420 2248 Finland 2250 Email: Oscar.Novo@ericsson.com 2252 Gonzalo Camarillo 2253 Ericsson 2254 Hirsalantie 11 2255 Jorvas 02420 2256 Finland 2258 Email: Gonzalo.Camarillo@ericsson.com 2260 David P. Morgan 2261 Fidelity Investments 2262 82 Devonshire St, MZ V8C 2263 Boston, MA 02109-3614 2264 USA 2266 Email: Dave.Morgan@fmr.com 2268 Intellectual Property Statement 2270 The IETF takes no position regarding the validity or scope of any 2271 Intellectual Property Rights or other rights that might be claimed to 2272 pertain to the implementation or use of the technology described in 2273 this document or the extent to which any license under such rights 2274 might or might not be available; nor does it represent that it has 2275 made any independent effort to identify any such rights. Information 2276 on the procedures with respect to rights in RFC documents can be 2277 found in BCP 78 and BCP 79. 2279 Copies of IPR disclosures made to the IETF Secretariat and any 2280 assurances of licenses to be made available, or the result of an 2281 attempt made to obtain a general license or permission for the use of 2282 such proprietary rights by implementers or users of this 2283 specification can be obtained from the IETF on-line IPR repository at 2284 http://www.ietf.org/ipr. 2286 The IETF invites any interested party to bring to its attention any 2287 copyrights, patents or patent applications, or other proprietary 2288 rights that may cover technology that may be required to implement 2289 this standard. Please address the information to the IETF at 2290 ietf-ipr@ietf.org. 2292 Disclaimer of Validity 2294 This document and the information contained herein are provided on an 2295 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2296 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2297 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2298 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2299 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2300 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2302 Copyright Statement 2304 Copyright (C) The Internet Society (2006). This document is subject 2305 to the rights, licenses and restrictions contained in BCP 78, and 2306 except as set forth therein, the authors retain all their rights. 2308 Acknowledgment 2310 Funding for the RFC Editor function is currently provided by the 2311 Internet Society.