XCON O. Novo Internet-Draft G. Camarillo Intended status: Informational Ericsson Expires: April 13, 2007 D. Morgan Fidelity Investments R. Even Polycom October 10, 2006 A Common Conference Information Data Model for Centralized Conferencing (XCON) draft-ietf-xcon-common-data-model-03.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 April 13, 2007. Copyright Notice Copyright (C) The Internet Society (2006). 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 Novo, et al. Expires April 13, 2007 [Page 1] Internet-Draft Common Conference Schema October 2006 allow the conference control protocols to use a unified common conference information data model for XCON. This document formally 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Common Conference Data . . . . . . . . . . . . . . . . . . . . 4 3.1. General . . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2. Common Conference Policies . . . . . . . . . . . . . . . . 9 3.3. . . . . . . . . . . . . . . . . . 10 3.3.1. . . . . . . . . . . . . . . . . . . 11 3.3.2. . . . . . . . . . . . . . . . . . . . . . 13 3.3.3. . . . . . . . . . . . . . . . . . . . . 13 3.3.4. . . . . . . . . . . . . . . . . . 13 3.3.5. . . . . . . . . . . . . . . . . . . 13 3.3.6. . . . . . . . . . . . . . . . . . . 13 3.3.7. . . . . . . . . . . . . . . . . . . . . . . 14 3.3.7.1. mute . . . . . . . . . . . . . . . . . . . . . . . 14 3.3.7.2. pause-video . . . . . . . . . . . . . . . . . . . 14 3.3.7.3. gain . . . . . . . . . . . . . . . . . . . . . . . 15 3.4. . . . . . . . . . . . . . . . . . . . . . . . 15 3.5. . . . . . . . . . . . . . . . . . . . . 15 3.6. . . . . . . . . . . . . . . . . . . . 15 3.7. . . . . . . . . . . . . . . . . . . . . . . . . . 16 3.7.1. . . . . . . . . . . . . . . . . . 17 3.7.2. . . . . . . . . . . . . . . 18 3.7.2.1. . . . . . . . . . . . . . . . . 18 3.7.2.1.1. . . . . . . . . . . . . . . . . . 18 3.7.2.1.2. . . . . . . . . . . . . . . . . 19 3.7.2.1.3. . . . . . . . . . . . . . 19 3.7.2.1.4. . . . . . . . . . . . . . . 19 3.7.2.1.5. . . . . . . . . . . . 19 3.7.2.1.6. . . . . . . . . . . . . . . 19 3.7.2.1.7. . . . . . . . . . . . . . . . 19 3.7.2.1.8. . . . . . 20 3.7.2.1.9. . . . . . . . 20 3.7.2.1.10. . . . . . . . . . . . . 20 3.7.2.1.11. . . . . . . . . . . 20 3.7.2.2. . . . . . . . . . . . . . . . . . . . . 21 3.8. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.8.1. from-mixer, to-mixer . . . . . . . . . . . . . . . . . 23 3.8.1.1. . . . . . . . . . . . . . . . . . . . . . 23 Novo, et al. Expires April 13, 2007 [Page 2] Internet-Draft Common Conference Schema October 2006 3.9. . . . . . . . . . . . . . . . . . . . . 24 3.10. . . . . . . . . . . . . . . . . . . . . 24 4. RELAX NG schema . . . . . . . . . . . . . . . . . . . . . . . 24 5. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 48 6. XML example . . . . . . . . . . . . . . . . . . . . . . . . . 49 7. Security Considerations . . . . . . . . . . . . . . . . . . . 58 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 58 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 58 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58 10.1. Normative References . . . . . . . . . . . . . . . . . . . 58 10.2. Informative References . . . . . . . . . . . . . . . . . . 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 59 Intellectual Property and Copyright Statements . . . . . . . . . . 61 Novo, et al. Expires April 13, 2007 [Page 3] Internet-Draft Common Conference Schema October 2006 1. Introduction This document defines an Extensible Markup Language (XML) Schema that represents the conference object in a conferencing server. The information is modeled as a series of elements, each of which contains children and attributes. The Conference Object 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. This document has been constructed in compliance with the XCON Framework [1] and the Session Initiation Protocol (SIP) Event Package for Conference State [2]. 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 [3]. This document uses the terminology defined in the XCON Conferencing Framework [1] and the SIPPING Conferencing Framework [4]. In addition, it uses definitions from The Binary Floor Control Protocol [7]. 3. Common Conference Data 3.1. General The conference object data model document is an XML [5] 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 Novo, et al. Expires April 13, 2007 [Page 4] Internet-Draft Common Conference Schema October 2006 the attribute 'entity' that contains the conference unique identifier that identifies the conference being described in the document. The element is comprised of , , , , , , , 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 [2]. 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 conference policy control protocol msy be used to retrieve the conference state at any time. 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 April 13, 2007 [Page 5] Internet-Draft Common Conference Schema October 2006 | | | |-- | | | |-- | | | |-- | | |-- | | | |-- | | | |-- | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | ... | |-- | | |-- | | | |-- | | | |-- | | | |-- | | |-- | | | |-- | | | |-- | | |-- | | | |-- | | |-- | | | |-- | | ... | |-- | | |-- | | |-- | | ... | |-- | | |-- | | |-- | | ... | |--! | | |--! | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | | |-- | | | | |-- | | | | ... | | | |-- | | | | |-- | | | | |-- | | | | ... Novo, et al. Expires April 13, 2007 [Page 6] Internet-Draft Common Conference Schema October 2006 | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | | |-- | | | | |-- | | | | ... | | | |-- | | | | |-- | | | | ... | | ... | |--! | |-- | |-- | |--! | | |--! | | | |--! | | | |-- | | | |-- | | |-- | | | |-- | | | |-- | | |-- | | | |-- | ... |--! | |-- | |-- | |--! | |-- | |-- | |-- | |-- | |-- | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | ... | | ... | Novo, et al. Expires April 13, 2007 [Page 7] Internet-Draft Common Conference Schema October 2006 |--! | |-- | |-- | |-- | | |-- | | |-- ... | | | |-- | | |-- | | | |-- | | | | |-- | | | | | |-- | | | | | | | | | | | | | ... | | | | | | | | | | | |-- | | | | | | |-- | | | | | | |-- | | | | | | | | | |-- | | | | | | | | | | | ... | | | ... | | | |--! | | |-- | | |-- | | |-- | | |-- | | | | | | | ... | | |-- | | |-- | | |-- | | |-- | | |-- | | |-- | | |--! | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |-- | | | |--! | | | | |-- | | | | |-- Novo, et al. Expires April 13, 2007 [Page 8] Internet-Draft Common Conference Schema October 2006 | | | | |--