draft-ietf-xcon-common-data-model-18.txt   draft-ietf-xcon-common-data-model-19.txt 
XCON O. Novo XCON O. Novo
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: August 28, 2010 D. Morgan Expires: November 20, 2010 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
February 24, 2010 May 19, 2010
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-18.txt draft-ietf-xcon-common-data-model-19.txt
Abstract Abstract
This document defines an Extensible Markup Language (XML)-based This document defines an Extensible Markup Language (XML)-based
conference information data model for centralized conferencing conference information data model for centralized conferencing
(XCON). A conference information data model is designed to convey (XCON). A conference information data model is designed to convey
information about the conference and about participation in the information about the conference and about participation in the
conference. The conference information data model defined in this conference. The conference information data model defined in this
document constitutes an extension of the data format specified in the document constitutes an extension of the data format specified in the
Session Initiation Protocol (SIP) Event Package for Conference State. Session Initiation Protocol (SIP) Event Package for Conference State.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 20, 2010.
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 August 28, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 3, line 7 skipping to change at page 3, line 7
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 7
3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 3.3. The Conference Object Identifier . . . . . . . . . . . . . 8
3.3.1. Conference Object URI Definition . . . . . . . . . . . 9 3.3.1. Conference Object URI Definition . . . . . . . . . . . 10
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 3.3.2. Normalization and Conference Object URI Comparison . . 10
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11
4.2. <conference-description> . . . . . . . . . . . . . . . . . 14 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14 4.2. <conference-description> . . . . . . . . . . . . . . . . . 15
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 15
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 15
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 15 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 15 4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 16
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 15 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 16
4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 15 4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 16
4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 15 4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 16
4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 17 4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 16
4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 17 4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 18
4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 17 4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 18
4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 17 4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 18
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19 4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 18
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 20 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 21
4.4.1. <allow-conference-event-subscription> . . . . . . . . 20 4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 21
4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 20 4.4.1. <allow-conference-event-subscription> . . . . . . . . 21
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 21
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 21
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20 4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 21
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 21
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 21 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 22
4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 21 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 22
4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21 4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 22
4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 23
4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22 4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 23 4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 24
4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23 4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 24
4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24 4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 25
4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 25 4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 26
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 26 4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 26
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 26 4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 27
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 26 4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 27
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26 4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 27
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 27 4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 28
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 27 4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 28
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 27 4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 28
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 27 4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 28
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27 4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 28
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 28 4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 29
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 29 4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 29
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 29 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 30
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 30
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 40 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 30
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 41
8. Security Considerations . . . . . . . . . . . . . . . . . . . 50 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 41
8.1. Authentication, Access Control, and Integrity . . . . . . 50 8. Security Considerations . . . . . . . . . . . . . . . . . . . 51
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 50 8.1. Authentication, Access Control, and Integrity . . . . . . 51
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 52
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 51 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 52
9.3. Conference Object Identifier Registration . . . . . . . . 52 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 52
9.4. Conference User Identifier Registration . . . . . . . . . 53 9.3. Conference Object Identifier Registration . . . . . . . . 53
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 9.4. Conference User Identifier Registration . . . . . . . . . 54
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54
11.1. Normative References . . . . . . . . . . . . . . . . . . . 54 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 55
11.2. Informative References . . . . . . . . . . . . . . . . . . 54 11.1. Normative References . . . . . . . . . . . . . . . . . . . 55
Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55 11.2. Informative References . . . . . . . . . . . . . . . . . . 55
Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 83 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 92 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 84
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 93
1. Introduction 1. Introduction
There is a core data set of conference information that is utilized There is a core data set of conference information that is utilized
in any conference, independent of the specific conference media. in any conference, independent of the specific conference media.
This core data set called the 'conference information data model' is This core data set called the 'conference information data model' is
defined in this document using an Extensible Markup Language (XML)- defined in this document using an Extensible Markup Language (XML)-
based. The conference information data model defined in this based. The conference information data model defined in this
document is logically represented by the conference object. document is logically represented by the conference object.
skipping to change at page 10, line 15 skipping to change at page 10, line 15
conferencing system. conferencing system.
3.3.1. Conference Object URI Definition 3.3.1. Conference Object URI Definition
XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host, port, and unreserved are defined in RFC3986[RFC3986] host, port, and unreserved are defined in RFC3986[RFC3986]
3.3.2. Normalization and Conference Object URI Comparison
In order to facilitate the comparison of the XCON-URI identifiers,
all the components of the identifiers SHOULD be converted to
lowercase. After normalizing the URI strings, the URIs comparison
SHOULD applied a character-by-character basis as prescribed by
RFC3986, Section 6.2.1.
3.4. Data Model Structure 3.4. Data Model Structure
The information in this data model is structured in the following The information in this data model is structured in the following
manner. All the information related to a conference is contained in manner. All the information related to a conference is contained in
a <conference-info> element. The <conference-info> element contains a <conference-info> element. The <conference-info> element contains
the following child elements: the following child elements:
o The <conference-description> element describes the conference as a o The <conference-description> element describes the conference as a
whole. It has, for instance, information about the URI of the whole. It has, for instance, information about the URI of the
conference, maximum users allowed in the conference, media conference, maximum users allowed in the conference, media
skipping to change at page 26, line 23 skipping to change at page 26, line 36
The attribute 'entity' contains a unique conference user identifier The attribute 'entity' contains a unique conference user identifier
(XCON-USERID) within the scope of the conference. The URI format of (XCON-USERID) within the scope of the conference. The URI format of
this identifier is as follow: this identifier is as follow:
XCON-USERID = "xcon-userid" ":" conf-user-id XCON-USERID = "xcon-userid" ":" conf-user-id
conf-user-id = 1*(unreserved) conf-user-id = 1*(unreserved)
[unreserved is defined in RFC3986] [unreserved is defined in RFC3986]
In order to facilitate the comparison of the XCON-USERID identifiers,
all the components of the identifiers SHOULD be converted to
lowercase. After normalizing the URI strings, the URIs comparison
SHOULD applied a character-by-character basis as prescribed by
RFC3986, Section 6.2.1.
Other user identifiers can be associated with this conference user Other user identifiers can be associated with this conference user
identifier and enable the conferencing system to correlate and map identifier and enable the conferencing system to correlate and map
these multiple authenticated user identities to a single global user these multiple authenticated user identities to a single global user
identifier. Figure 4 illustrates an example using the conference identifier. Figure 4 illustrates an example using the conference
user identifier in association with the user identity defined for user identifier in association with the user identity defined for
BFCP, SIP, and H323 user identity. It should be noted that a BFCP, SIP, and H323 user identity. It should be noted that a
conferencing system is free to structure such relationships as conferencing system is free to structure such relationships as
required and this information is just included as a guideline that required and this information is just included as a guideline that
can be used. can be used.
 End of changes. 10 change blocks. 
85 lines changed or deleted 95 lines changed or added

This html diff was produced by rfcdiff 1.38. The latest version is available from http://tools.ietf.org/tools/rfcdiff/