draft-ietf-xcon-common-data-model-24.txt   draft-ietf-xcon-common-data-model-25.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: October 16, 2011 D. Morgan Expires: October 17, 2011 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
April 14, 2011 April 15, 2011
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-24.txt draft-ietf-xcon-common-data-model-25.txt
Abstract Abstract
[RFC5239] defines the idea of a centralized conferencing (XCON) as an [RFC5239] defines the idea of a centralized conferencing (XCON) as an
association of participants with a central focus. The state of a association of participants with a central focus. The state of a
conference is represented by a conference object. This document conference is represented by a conference object. This document
defines an Extensible Markup Language (XML)-based conference defines an Extensible Markup Language (XML)-based conference
information data model to be used for conference objects. A information data model to be used for conference objects. A
conference information data model is designed to convey information conference information data model is designed to convey information
about the conference and about participation in the conference. The about the conference and about participation in the conference. The
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. 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."
This Internet-Draft will expire on October 16, 2011. This Internet-Draft will expire on October 17, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 3, line 19 skipping to change at page 3, line 19
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 7 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 7
3.3. The Conference Object Identifier . . . . . . . . . . . . . 8 3.3. The Conference Object Identifier . . . . . . . . . . . . . 8
3.3.1. Conference Object URI Definition . . . . . . . . . . . 10 3.3.1. Conference Object URI Definition . . . . . . . . . . . 10
3.3.2. Normalization and Conference Object URI Comparison . . 10 3.3.2. Normalization and Conference Object URI Comparison . . 10
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15
4.2. <conference-description> . . . . . . . . . . . . . . . . . 15 4.2. <conference-description> . . . . . . . . . . . . . . . . . 15
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 15 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 16 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 16
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 16 4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 16
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 16
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 16 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 16
4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 16 4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 16
4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 16 4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 16
4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 16 4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 17
4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 18 4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 18
4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 18 4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 18
4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 18 4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 19
4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 19 4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 19
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 21 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 21
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 22 4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 22
4.4.1. <allow-conference-event-subscription> . . . . . . . . 22 4.4.1. <allow-conference-event-subscription> . . . . . . . . 22
4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 22 4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 22
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 22 4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 22
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 22 4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 22
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 22 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 22
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 22 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 22
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 23 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 23
skipping to change at page 10, line 26 skipping to change at page 10, line 26
construction is similar to a URL, in this case, the XCON-URI can not construction is similar to a URL, in this case, the XCON-URI can not
be resolved to addresses and/or ports. be resolved to addresses and/or ports.
3.3.2. Normalization and Conference Object URI Comparison 3.3.2. Normalization and Conference Object URI Comparison
In order to facilitate the comparison of the XCON-URI identifiers, In order to facilitate the comparison of the XCON-URI identifiers,
all the components of the identifiers MUST be converted to lowercase. all the components of the identifiers MUST be converted to lowercase.
After normalizing the URI strings, the URIs comparison MUST applied a After normalizing the URI strings, the URIs comparison MUST applied a
character-by-character basis as prescribed by RFC3986, Section 6.2.1. character-by-character basis as prescribed by RFC3986, Section 6.2.1.
The host construction, as defined in RFC3986 can take the form of an
IP address, which is not conventionally compared on a character-by-
character basis. The host part of an XCON-URI serves only as an
identifier; that is, it is never used as an address. The character-
by-character comparison still applies.
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 58, line 41 skipping to change at page 58, line 41
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[RFC5018] Camarillo, G., "Connection Establishment in the Binary [RFC5018] Camarillo, G., "Connection Establishment in the Binary
Floor Control Protocol (BFCP)", RFC 5018, September 2007. Floor Control Protocol (BFCP)", RFC 5018, September 2007.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[W3C.REC-xml-20001006] [W3C.REC-xml-20001006]
Sperberg-McQueen, C., Maler, E., Paoli, J., and T. Bray, Bray, T., Sperberg-McQueen, C., Paoli, J., and E. Maler,
"Extensible Markup Language (XML) 1.0 (Second Edition)", "Extensible Markup Language (XML) 1.0 (Second Edition)",
World Wide Web Consortium FirstEdition REC-xml-20001006, World Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000, October 2000,
<http://www.w3.org/TR/2000/REC-xml-20001006>. <http://www.w3.org/TR/2000/REC-xml-20001006>.
Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. Non-Normative RELAX NG Schema in XML Syntax
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<grammar <grammar
ns="urn:ietf:params:xml:ns:conference-info" ns="urn:ietf:params:xml:ns:conference-info"
 End of changes. 9 change blocks. 
8 lines changed or deleted 14 lines changed or added

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