draft-ietf-xcon-common-data-model-30.txt   draft-ietf-xcon-common-data-model-31.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 17, 2011 D. Morgan Expires: December 19, 2011 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
Jun 15, 2011 Jun 17, 2011
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-30.txt draft-ietf-xcon-common-data-model-31.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 17, 2011. This Internet-Draft will expire on December 19, 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 4, line 10 skipping to change at page 4, line 10
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 29 4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 29
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 29 4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 29
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 29 4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 29
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 29 4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 29
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 29 4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 29
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 29 4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 29
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 30 4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 30
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 30 4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 30
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 30 4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 30
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 30 4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 30
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 31 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 32
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 32 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 32
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 32 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 32
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 43 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 43
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 43 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 43
8. Security Considerations . . . . . . . . . . . . . . . . . . . 52 8. Security Considerations . . . . . . . . . . . . . . . . . . . 53
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 54 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 54
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 54 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 55
9.3. Conference Object Identifier Registration . . . . . . . . 55 9.3. Conference Object Identifier Registration . . . . . . . . 55
9.4. Conference User Identifier Registration . . . . . . . . . 56 9.4. Conference User Identifier Registration . . . . . . . . . 56
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57
11.1. Normative References . . . . . . . . . . . . . . . . . . . 57 11.1. Normative References . . . . . . . . . . . . . . . . . . . 57
11.2. Informative References . . . . . . . . . . . . . . . . . . 58 11.2. Informative References . . . . . . . . . . . . . . . . . . 58
Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 58 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 58
Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 86 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 86
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96
skipping to change at page 24, line 34 skipping to change at page 24, line 34
identifier MAY be used as the moderator-id. In the case of BFCP identifier MAY be used as the moderator-id. In the case of BFCP
as the floor control protocol, the <moderator-id> is defined in as the floor control protocol, the <moderator-id> is defined in
[RFC4582] section 3. Note that [RFC4582] refers to the moderator [RFC4582] section 3. Note that [RFC4582] refers to the moderator
role as a 'floor chair'. role as a 'floor chair'.
4.6. <users> 4.6. <users>
The <users> element is described in [RFC4575] and contains the <join- The <users> element is described in [RFC4575] and contains the <join-
handling>, <user-admission-policy>, <allowed-users-list> and <deny- handling>, <user-admission-policy>, <allowed-users-list> and <deny-
users-list> defined in this document and <user> child elements users-list> defined in this document and <user> child elements
defined in [RFC4575]. Note that the <users> element does not have defined in [RFC4575]. When the <users> element is used in the
the attribute 'state' defined in [RFC4575] for this element because context of the XCON Conference Information Model, the 'state' and
this attribute only applies to notification mechanisms. The 'version' attributes defined in [RFC4575] are not used, since they
following sections describe these elements in more detail. Other apply only to notification mechanisms. The following sections
child elements and attributes can be used to extend <users> in the describe these elements in more detail. Other child elements and
future. attributes can be used to extend <users> in the future.
4.6.1. <join-handling> 4.6.1. <join-handling>
The <join-handling> element defines the actions used by the The <join-handling> element defines the actions used by the
conference focus to control conference participation. This element conference focus to control conference participation. This element
defines the action that the focus is to take when processing a defines the action that the focus is to take when processing a
particular request to join a conference. This element defines values particular request to join a conference. This element defines values
of: of:
o "block": This action instructs the focus to deny access to the o "block": This action instructs the focus to deny access to the
conference. This action is the default action taken in the conference. This action is the default action taken in the
skipping to change at page 27, line 41 skipping to change at page 27, line 41
(e.g. SIP URI, xcon-userid defined in Section 4.6.5), roles (defined (e.g. SIP URI, xcon-userid defined in Section 4.6.5), roles (defined
in Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus in Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus
uses to determine who has been 'banned' from the conference. Such uses to determine who has been 'banned' from the conference. Such
banned users are prevented from re-joining the chatroom until they banned users are prevented from re-joining the chatroom until they
have been un-banned. have been un-banned.
4.6.5. <user> and Its <user> Sub-elements 4.6.5. <user> and Its <user> Sub-elements
The element <user> is described in [RFC4575] and describes a single The element <user> is described in [RFC4575] and describes a single
participant in the conference. The <user> element has an attribute participant in the conference. The <user> element has an attribute
'entity'. Note that the <user> element does not have the attribute 'entity'. However, when the <user> element is used in the context of
'state' defined in [RFC4575] for this element because this attribute the XCON Conference Information Model, the 'state' and 'version'
only applies to notifications mechanism. attributes defined in [RFC4575] are not used, since they apply only
to notification mechanisms.
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]
skipping to change at page 30, line 44 skipping to change at page 30, line 44
ruleset (in SIP terms, a participant is allowed to send a REFER ruleset (in SIP terms, a participant is allowed to send a REFER
request [RFC3515] to the focus which results in the focus sending an request [RFC3515] to the focus which results in the focus sending an
BYE request to the user the referrer wishes to leave the conference). BYE request to the user the referrer wishes to leave the conference).
If set to FALSE, the refer request is rejected. If this element is If set to FALSE, the refer request is rejected. If this element is
undefined it has a value of FALSE, causing the refer to be rejected. undefined it has a value of FALSE, causing the refer to be rejected.
4.6.5.10. <endpoint> 4.6.5.10. <endpoint>
The <endpoint> child element is identical to the element with the The <endpoint> child element is identical to the element with the
same name in [RFC4575] except that the 'state' attribute is not same name in [RFC4575] except that the 'state' attribute is not
included. The 'state' attribute only applies to notification included. When the <endpoint> element is used in the context of the
mechanisms. The <endpoint> element can provide the desired level of XCON Conference Information Model, the 'state' and 'version'
detail about the user's devices and their signaling sessions taking attributes defined in [RFC4575] are not used, since they apply only
part in the conference. to notification mechanisms. The <endpoint> element can provide the
desired level of detail about the user's devices and their signaling
sessions taking part in the conference.
The <endpoint> element has the following child elements: <display- The <endpoint> element has the following child elements: <display-
text>, <referred>, <status>, <joining-method>, <joining-info>, text>, <referred>, <status>, <joining-method>, <joining-info>,
<disconnection-method>, <disconnection-info>, <media>,and <call- <disconnection-method>, <disconnection-info>, <media>,and <call-
info>. All the <endpoint> child elements are defined in [RFC4575] info>. All the <endpoint> child elements are defined in [RFC4575]
with the exception of the <to-mixer> element, and the <from-mixer> with the exception of the <to-mixer> element, and the <from-mixer>
element. element.
The <endpoint>/<media> element has two other child elements defined The <endpoint>/<media> element has two other child elements defined
in this document, the <to-mixer>, and the <from-mixer>: in this document, the <to-mixer>, and the <from-mixer>:
skipping to change at page 31, line 49 skipping to change at page 32, line 8
child element: child element:
* Controls that apply to a specific user would appear under the * Controls that apply to a specific user would appear under the
<controls> element. <controls> element.
o More values can be defined in the future. o More values can be defined in the future.
4.7. <sidebars-by-ref> 4.7. <sidebars-by-ref>
The <sidebars-by-ref> element contains a set of <entry> child The <sidebars-by-ref> element contains a set of <entry> child
elements. This element is described in [RFC4575], 5.9.1. Note that elements. This element is described in [RFC4575], 5.9.1. When the
the <sidebars-by-ref> element does not have the attribute 'state' <sidebars-by-ref> element is used in the context of the XCON
defined in [RFC4575] for this element because this attribute only Conference Information Model, the 'state' and 'version' attributes
applies to notifications mechanism. defined in [RFC4575] are not used, since they apply only to
notification mechanisms.
4.8. <sidebars-by-val> 4.8. <sidebars-by-val>
The <sidebars-by-val> element contains a set of <entry> child The <sidebars-by-val> element contains a set of <entry> child
elements each containing information about a single sidebar. This elements each containing information about a single sidebar. This
element is described in [RFC4575], 5.9.2. Note that the <sidebars- element is described in [RFC4575], 5.9.2. When the <sidebars-by-val>
by-val> element does not have the attribute 'state' defined in element is used in the context of the XCON Conference Information
[RFC4575] for this element because this attribute only applies to Model, the 'state' and 'version' attributes defined in [RFC4575] are
notifications mechanism. not used, since they apply only to notification mechanisms.
5. RELAX NG Schema 5. RELAX NG Schema
In accordance with the Centralized Conferencing Framework document In accordance with the Centralized Conferencing Framework document
[RFC5239], the Conference Object is a logical representation of a [RFC5239], the Conference Object is a logical representation of a
conference instance. The conference information schema contains core conference instance. The conference information schema contains core
information that is utilized in any conference. It also contains the information that is utilized in any conference. It also contains the
variable information part of the Conference Object. variable information part of the Conference Object.
The normative schema is backwards compatible with [RFC5239], in other The normative schema is backwards compatible with [RFC5239], in other
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]
Sperberg-McQueen, C., Yergeau, F., Maler, E., Paoli, J., Maler, E., Yergeau, F., Sperberg-McQueen, C., 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. 
29 lines changed or deleted 33 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/