draft-ietf-xcon-common-data-model-29.txt   draft-ietf-xcon-common-data-model-30.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: December 3, 2011 D. Morgan Expires: December 17, 2011 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
Jun 01, 2011 Jun 15, 2011
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-29.txt draft-ietf-xcon-common-data-model-30.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 43 skipping to change at page 1, line 43
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 December 3, 2011. This Internet-Draft will expire on December 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 7, line 44 skipping to change at page 7, line 44
extensions to text elements. This data model can be used by extensions to text elements. This data model can be used by
conference servers providing different types of basic conferences. conference servers providing different types of basic conferences.
It is expected that this data model can be further extended with new It is expected that this data model can be further extended with new
elements in the future in order to implement additional advanced elements in the future in order to implement additional advanced
features. features.
3.1. Data Model Format 3.1. Data Model Format
A conference object document is an XML [W3C.REC-xml-20081126] A conference object document is an XML [W3C.REC-xml-20081126]
document. Conference object documents MUST be based on Extensible document. Conference object documents MUST be based on Extensible
Markup Language (XML) 1.0 and SHOULD be encoded using UTF-8. Markup Language (XML) 1.0 and MUST be encoded using UTF-8.
The normative description of the syntax of the conference object The normative description of the syntax of the conference object
document, for use by implementors of parsers and generators, is found document, for use by implementors of parsers and generators, is found
in the RelaxNG schema provided in Section 5. Compliant messages MUST in the RelaxNG schema provided in Section 5. Compliant messages MUST
meet the requirements of that schema. meet the requirements of that schema.
3.2. Data Model Namespace 3.2. Data Model Namespace
This specification defines a new namespace specification for This specification defines a new namespace specification for
identifying the elements defined in the data model. This namespace identifying the elements defined in the data model. This namespace
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 XCON-URI = "xcon" ":" [conf-object-id "@"] host
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host and unreserved are defined in RFC3986[RFC3986] host and unreserved are defined in RFC3986[RFC3986]
XCON-URI is a URI conference identifier and even though its An XCON-URI is not designed to be resolved, and an application MUST
construction is similar to a URL, in this case, the XCON-URI can not NOT attempt to perform a standard DNS lookup on the host portion of
be resolved to addresses and/or ports. such a URI in an attempt to discover an IP address or port at which
to connect.
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 The host construction, as defined in RFC3986 can take the form of an
IP address, which is not conventionally compared on a character-by- IP address, which is not conventionally compared on a character-by-
skipping to change at page 11, line 37 skipping to change at page 11, line 37
The following non-normative diagram shows the structure of conference The following non-normative diagram shows the structure of conference
object documents. The symbol "!" preceding an element indicates that object documents. The symbol "!" preceding an element indicates that
the element is REQUIRED in the data model. The symbol "*" following the element is REQUIRED in the data model. The symbol "*" following
an element indicates that the element is introduced and defined in an element indicates that the element is introduced and defined in
this document. That is, elements without a "*" have already been this document. That is, elements without a "*" have already been
defined in [RFC4575]. defined in [RFC4575].
!<conference-info> !<conference-info>
| |
|--!<conference-description> |--<conference-description>
| |--<language>* | |--<language>*
| |--<display-text> | |--<display-text>
| |--<subject> | |--<subject>
| |--<free-text> | |--<free-text>
| |--<keywords> | |--<keywords>
| |--<allow-sidebars>* | |--<allow-sidebars>*
| |--<cloning-parent>* | |--<cloning-parent>*
| |--<sidebar-parent>* | |--<sidebar-parent>*
| |--<conference-time>* | |--<conference-time>*
| | |--<entry>* | | |--<entry>*
skipping to change at page 12, line 25 skipping to change at page 12, line 25
| | ... | | ...
| |--<service-uris> | |--<service-uris>
| | |--<entry> | | |--<entry>
| | | |--<uri> | | | |--<uri>
| | | |--<display-text> | | | |--<display-text>
| | | |--<purpose> | | | |--<purpose>
| | ... | | ...
| |--<maximum-user-count> | |--<maximum-user-count>
| | ... | | ...
| |--<available-media> | |--<available-media>
| | |--!<entry> | | |--<entry>
| | | |--<display-text> | | | |--<display-text>
| | | |--<type> | | | |--<type>
| | | |--<status> | | | |--<status>
| | | |--<mixing-mode>* | | | |--<mixing-mode>*
| | | |--<codecs>* | | | |--<codecs>*
| | | | |--<codec>* | | | | |--<codec>*
| | | | | |--<subtype>* | | | | | |--<subtype>*
| | | | |--<codec>* | | | | |--<codec>*
| | | | | |--<subtype>* | | | | | |--<subtype>*
| | | | ... | | | | ...
skipping to change at page 13, line 30 skipping to change at page 13, line 30
| |--<active> | |--<active>
| |--<locked> | |--<locked>
| |
|--<floor-information>* |--<floor-information>*
| |--<conference-ID>* | |--<conference-ID>*
| |--<allow-floor-events>* | |--<allow-floor-events>*
| |--<floor-request-handling>* | |--<floor-request-handling>*
| |--<conference-floor-policy>* | |--<conference-floor-policy>*
| | |--<floor>* | | |--<floor>*
| | | |--!<media-label>* | | | |--!<media-label>*
| | | |--!<algorithm>* | | | |--<algorithm>*
| | | |--<max-floor-users>* | | | |--<max-floor-users>*
| | | |--<moderator-id>* | | | |--<moderator-id>*
| | | ... | | | ...
| | ... | | ...
| |
|--!<users> |--<users>
| |--<join-handling>* | |--<join-handling>*
| |--<user-admission-policy>* | |--<user-admission-policy>*
| |--<allowed-users-list>* | |--<allowed-users-list>*
| | |--<target>* | | |--<target>*
| | | | | |
| | |--<persistent-list>* | | |--<persistent-list>*
| | | |--<user>* | | | |--<user>*
| | | | |-- <email>* | | | | |-- <email>*
| | | |
| |--<deny-users-list>* | |--<deny-users-list>*
skipping to change at page 15, line 19 skipping to change at page 15, line 19
| |--<entry> | |--<entry>
| | | | | |
| ... ... | ... ...
The following sections describe these elements in detail. The full The following sections describe these elements in detail. The full
Relax NG schema is provided in Section 5. Relax NG schema is provided in Section 5.
4.1. <conference-info> 4.1. <conference-info>
A conference object document begins with the root element A conference object document begins with the root element
<conference-info>, which is defined in [RFC4575]. The <conference- <conference-info>, which is defined in [RFC4575]. The attributes of
info> attributes are described in [RFC4575]. Note that the the <conference-info> element are also defined in [RFC4575].
<conference-info> element does not have the attributes 'state' and However, when the <conference-info> element is used in the context of
'version' defined in [RFC4575] for this element because these the XCON Conference Information Model, the 'state' and 'version'
attributes only apply to notification mechanisms. attributes defined in [RFC4575] are not used, since they apply only
to notification mechanisms.
In addition, [RFC4575] defines an 'entity' attribute that contains In addition, [RFC4575] defines an 'entity' attribute that contains
the conference object identifier (XCON-URI) that identifies the the conference object identifier (XCON-URI) that identifies the
conference being described in the document. conference being described in the document.
The <conference-info> element contains the <conference-description>, The <conference-info> element contains the <conference-description>,
<host-info>, <conference-state>, <floor-information>, <users>, <host-info>, <conference-state>, <floor-information>, <users>,
<sidebars-by-ref>, and <sidebars-by-val> child elements. All these <sidebars-by-ref>, and <sidebars-by-val> child elements. All these
elements, except <floor-information>, are defined in [RFC4575]. A elements, except <floor-information>, are defined in [RFC4575]. A
conference document MUST at least include the <conference- conference document MUST at least include the <conference-
skipping to change at page 16, line 35 skipping to change at page 16, line 35
The <free-text> element is described in section 5.3 of [RFC4575]. The <free-text> element is described in section 5.3 of [RFC4575].
4.2.5. <keywords> 4.2.5. <keywords>
The <keywords> element is described in section 5.3 of [RFC4575]. The <keywords> element is described in section 5.3 of [RFC4575].
4.2.6. <allow-sidebars> 4.2.6. <allow-sidebars>
The <allow-sidebars> element represents a boolean value. If set to The <allow-sidebars> element represents a boolean value. If set to
TRUE, the conference is allowed to create sidebar conferences. If "true" or "1", the conference is allowed to create sidebar
absent, or set to FALSE, the conference can not create sidebar conferences. If absent, or set to "false" or "0", the conference can
conferences. not create sidebar conferences.
4.2.7. <cloning-parent> 4.2.7. <cloning-parent>
When the <cloning-parent> is present, it indicates that the When the <cloning-parent> is present, it indicates that the
conference object is a child of a parent conference. The <cloning- conference object is a child of a parent conference. The <cloning-
parent> element contains the conference object Identifier (XCON-URI) parent> element contains the conference object Identifier (XCON-URI)
(different from the main XCON-URI) of the parent. (different from the main XCON-URI) of the parent.
4.2.8. <sidebar-parent> 4.2.8. <sidebar-parent>
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-20081126] [W3C.REC-xml-20081126]
Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J., Sperberg-McQueen, C., Yergeau, F., Maler, E., Paoli, J.,
and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008, xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
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. 13 change blocks. 
21 lines changed or deleted 23 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/