XCON O. Novo Internet-Draft G. Camarillo Expires: March 29, 2006 Ericsson D. Morgan Fidelity Investments September 25, 2005 A Common Conference Information Data Model for Centralized Conferencing (XCON) draft-novo-xcon-common-data-model-00.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on March 29, 2006. Copyright Notice Copyright (C) The Internet Society (2005). Abstract This document collects, organizes, and describes the conference variables that have been introduced in various protocol drafts of the XCON and SIPPING working groups. The goal of this document is to allow the conference control protocols to use a unified common conference information data model for XCON. This document formally Novo, et al. Expires March 29, 2006 [Page 1] Internet-Draft Common Conference Schema September 2005 defines an Extensible Markup Language (XML) Schema that represents the common conference information in a conferencing server. The information is modeled as a series of elements, each of which contains a set of children and attributes. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Common Conference Data . . . . . . . . . . . . . . . . . . . . 3 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. . . . . . . . . . . . . . . . . . 9 3.2.1. . . . . . . . . . . . . . . . . . . 10 3.2.2. . . . . . . . . . . . . . . . . . . . . . 10 3.2.3. . . . . . . . . . . . . . . . . . . . . 10 3.2.4. . . . . . . . . . . . . . . . . . 10 3.2.5. . . . . . . . . . . . . . . . . . . 10 3.3. . . . . . . . . . . . . . . . . . . . . . . . 11 3.4. . . . . . . . . . . . . . . . . . . . . 11 3.5. . . . . . . . . . . . . . . . . . . . 11 3.6. . . . . . . . . . . . . . . . . . . . 11 3.7. . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.7.1. . . . . . . . . . . . . . . . . . . . 12 3.7.2. . . . . . . . . . . . . . . . . . . . . . 12 3.7.3. . . . . . . . . . . . . . . 12 3.7.3.1. . . . . . . . . . . . . . . . 12 3.7.3.2. . . . . . . . . . . . . . . . . 13 3.7.3.2.1. . . . . . . . . . . . . . . . . . 13 3.7.3.2.2. . . . . . . . . . . . . . . . . . . 14 3.7.4. . . . . . . . . . . . . . . . . . . . . . . . . 14 3.8. . . . . . . . . . . . . . . . . . . . . 15 3.9. . . . . . . . . . . . . . . . . . . . . 15 4. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 16 5. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 16 6. XML example . . . . . . . . . . . . . . . . . . . . . . . . . 17 7. Security Considerations . . . . . . . . . . . . . . . . . . . 26 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 27 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 10.1. Normative References . . . . . . . . . . . . . . . . . . . 27 10.2. Informative References . . . . . . . . . . . . . . . . . . 27 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 29 Intellectual Property and Copyright Statements . . . . . . . . . . 30 Novo, et al. Expires March 29, 2006 [Page 2] Internet-Draft Common Conference Schema September 2005 1. Introduction This document defines an Extensible Markup Language (XML) Schema that represents the common conference information in a conferencing server. The information is modeled as a series of elements, each of which contains children and attributes. The common conference information is a part of the Conference Object. The Conference Object contains two sections: the "Common Conference Information" section and the "Conference Template" section. The common conference information section contains the XML schema, which is used to represent the core information that is utilized in any conference (capabilities, membership, roles, call control signalling, media, etc...) and specifies the set of rights, permissions and limitations pertaining to operations being performed on a certain Conference Object. This document gives an overview of the conference variables that have been introduced in various protocol drafts of the XCON working group to date and proposes to create a unified common conference information data model for XCON. [Editors Note: This document is still in early stages of development and is intended to trigger discussions. It is not intended to provide a complete schema description at this stage, but rather explore a potential schema to accommodate the proposals made so far.] This document has been constructed in compliance with the XCON Framework [1] and the Session Initiation Protocol (SIP) Event Package for Conference State [5]. It also incorporates data elements proposed in several XCON WG and SIPPING WG drafts. 2. Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. This document uses the terminology defined in the XCON Conferencing Framework [1] and the SIPPING Conferencing Framework [3]. In addition, it uses definitions from The Binary Floor Control Protocol [6]. 3. Common Conference Data Novo, et al. Expires March 29, 2006 [Page 3] Internet-Draft Common Conference Schema September 2005 3.1. General The conference object data model document is an XML [4] document that MUST be well formed and SHOULD be valid. Conference object data model documents MUST be based on XML 1.0 and SHOULD be encoded using UTF-8. A Common Conference information document begins with the root element tag of conference-type. The has the attribute 'entity' that contains the conference URI that identifies the conference being described in the document. The element has the element. This attribute is explained in section 5 of this draft. The element is comprised of , , , , , , and child elements. A common conference document must at least include the , , and child elements. Some of this information can be represented using the conference-info-type schema as defined in [5]. Changes in the state of the conference should be communicated to the subscribers using a conference package subscribers (ex. A Session Initiation Protocol (SIP) Event Package for Conference State). Critical changes should be communicated to specific subscribers, perhaps those with unique roles. The following non-normative diagram gives an example of the overall hierarchy used in this format. The operator "!" preceding an element indicates that this element is MANDATORY in the data model. The operator "*" preceding an element indicates that this element is introduced/proposed in this draft. ! |--!* | |--! | |-- | |-- | |-- | |-- | |-- | |-- | |-- | |-- | | |-- | | | |--* Novo, et al. Expires March 29, 2006 [Page 4] Internet-Draft Common Conference Schema September 2005 | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | ... | |-- | | |-- | | | |-- | | | |-- | | | |-- | | |-- | | | |-- | | | |-- | | | |-- | | ... | |-- | | |-- | | | |-- | | | |-- | | | |-- | | ... | |-- | | |-- | | | |-- | | |-- | | | |-- | | ... | |--! | | |--! | | | |-- | | | |-- | | | |-- | | | |-- | | | | |-- | | | | |-- | | | | ... | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | | |-- | | | | |-- | | | | ... | | ... | |--! Novo, et al. Expires March 29, 2006 [Page 5] Internet-Draft Common Conference Schema September 2005 | |-- | |-- | |--! | | |--! | | | |--! | | | |-- | | |-- | | | |-- | | | |-- | ... |--! | |-- | |-- | |--! | |-- | |-- | |-- | | |-- | | | |-- | | | ... | | |-- | | | |-- | | | ... | | |-- | | | |-- | | | ... | | |-- | | | |-- | | | | |-- | | | ... | ... | |-- | |-- | |-- | |-- | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | ... | |--! | |-- | |-- | | |-- Novo, et al. Expires March 29, 2006 [Page 6] Internet-Draft Common Conference Schema September 2005 | | |-- ... | | |-- | | |-- ... | | | |-- | | |-- | | |-- ... | | |-- | | |-- ... | | | |-- | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | ... | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | | | |-- | | | |-- | | | | |-- | | | | | |-- | | | | | | | | | | | | | ... | | | | | | | | | | | |-- | | | | | | |-- | | | | | | |-- | | | | | | | | | |-- | | | | | | | | | | | ... | | | ... | | | |--! | | |-- | | |-- | | |-- | | | |-- | | | ... | | |-- | | |-- | | |-- Novo, et al. Expires March 29, 2006 [Page 7] Internet-Draft Common Conference Schema September 2005 | | |-- | | |-- | | |-- | | |-- | | |-- | | | |-- | | | | |-- | | | | |-- | | | ... | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | | | |-- Note that due to RFC formatting conventions, this documents splits lines whose content would exceed 72 characters. Two backslash character marks where this lines folding has taken place. These backslash would not appear in the actual XML data model. 7. Security Considerations A malicious user can manipulate parts of the Conference Information Data Model privileges document giving themselves and others privileges to manipulate the data model. It is very important that only authorized clients are able to manipulate the Conference Information Data Model document. Any conference control protocol MUST provide authentication, confidentiality and integrity. Novo, et al. Expires March 29, 2006 [Page 26] Internet-Draft Common Conference Schema September 2005 8. IANA Considerations 9. Acknowledgements This document is really a distillation of many ideas discussed over a long period of time. These ideas were contributed by many different drafts in the XCON working group and the SIPPING working group. 10. References 10.1. Normative References [1] Barnes, M. and C. Boulton, "A Framework and Data Model for Centralized Conferencing", draft-barnes-xcon-framework-02 (work in progress), February 2005. [2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [3] Rosenberg, J., "A Framework for Conferencing with the Session Initiation Protocol", draft-ietf-sipping-conferencing-framework-05 (work in progress), May 2005. [4] Paoli, J., Sperberg-McQueen, C., Bray, T., and E. Maler, "Extensible Markup Language (XML) 1.0 (Second Edition)", W3C FirstEdition REC-xml-20001006, October 2000. 10.2. Informative References [5] Rosenberg, J., "A Session Initiation Protocol (SIP) Event Package for Conference State", draft-ietf-sipping-conference-package-12 (work in progress), July 2005. [6] Camarillo, G., "The Binary Floor Control Protocol (BFCP)", draft-camarillo-xcon-bfcp-00 (work in progress), May 2004. [7] Khartabil, H., "The Conference Policy Control Protocol (CPCP)", draft-ietf-xcon-cpcp-01 (work in progress), October 2004. [8] Camarillo, G., "A Session Initiation Protocol (SIP) Event Package for Media Policy", draft-camarillo-sipping-policy-package-00 (work in progress), October 2003. Novo, et al. Expires March 29, 2006 [Page 27] Internet-Draft Common Conference Schema September 2005 [9] Koskelainen, P. and H. Khartabil, "An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Conference Policy Manipulation", draft-koskelainen-xcon-xcap-cpcp-usage-02 (work in progress), February 2004. [10] Schulzrinne, H., "A Document Format for Expressing Privacy Preferences", draft-ietf-geopriv-common-policy-05 (work in progress), July 2005. [11] Boulton, C. and U. Chandra, "Media Policy Templates for XCON", draft-boulton-xcon-media-template-01 (work in progress), April 2005. [12] Even, R., "Conferencing media policy requirements", draft-even-sipping-media-policy-requirements-00 (work in progress), February 2003. [13] Mahy, R. and N. Ismail, "Media Policy Manipulation in the Conference Policy Control Protocol", draft-mahy-sipping-media-policy-control-00 (work in progress), February 2003. [14] Levin, O., "Conference Policy Control Protocol for Centralized Conferencing", draft-levin-xcon-cpcp-00 (work in progress), June 2003. [15] Camarillo, G., "Session Description Protocol (SDP) Format for Binary Floor Control Protocol (BFCP) Streams", draft-ietf-mmusic-sdp-bfcp-02 (work in progress), July 2005. [16] Khartabil, H. and A. Niemi, "Privileges for Manipulating a Conference Policy", draft-ietf-xcon-conference-policy-privileges-01 (work in progress), October 2004. Novo, et al. Expires March 29, 2006 [Page 28] Internet-Draft Common Conference Schema September 2005 Authors' Addresses Oscar Novo Ericsson Hirsalantie 11 Jorvas 02420 Finland Email: Oscar.Novo@ericsson.com Gonzalo Camarillo Ericsson Hirsalantie 11 Jorvas 02420 Finland Email: Gonzalo.Camarillo@ericsson.com David P. Morgan Fidelity Investments 82 Devonshire St, MZ V8C Boston, MA 02109-3614 USA Email: Dave.Morgan@fmr.com Novo, et al. Expires March 29, 2006 [Page 29] Internet-Draft Common Conference Schema September 2005 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Disclaimer of Validity This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Copyright Statement Copyright (C) The Internet Society (2005). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Novo, et al. Expires March 29, 2006 [Page 30]