draft-ietf-xcon-common-data-model-20.txt   draft-ietf-xcon-common-data-model-21.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: April 18, 2011 D. Morgan Expires: May 14, 2011 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
Oct 15, 2010 Nov 10, 2010
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-20.txt draft-ietf-xcon-common-data-model-21.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.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 April 18, 2011. This Internet-Draft will expire on May 14, 2011.
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
skipping to change at page 29, line 29 skipping to change at page 29, line 29
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. The 'state' attribute only applies to notification
mechanisms. The <endpoint> element can provide the desired level of mechanisms. The <endpoint> element can provide the desired level of
detail about the user's devices and their signaling sessions taking detail about the user's devices and their signaling sessions taking
part in the conference. 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>, <floor>,and <disconnection-method>, <disconnection-info>, <media>,and <call-
<call-info>. All the <endpoint> child elements are defined in info>. All the <endpoint> child elements are defined in [RFC4575]
[RFC4575] with the exception of the <floor> element, <to-mixer>, and with the exception of the <to-mixer> element, and the <from-mixer>
the <from-mixer> element. element.
The <floor> element refers to the floor assigned to a certain
participant in the conference. If a participant, for instance, needs
to talk in the conference, it first needs to get the floor from the
chair of the conference. The <floor> element has an attribute 'id'
which uniquely identifies a floor within a conference. The 'id'
attribute corresponds to the floor-id identifier defined in [RFC4582]
section 5.2.2. The <floor> element has a "Boolean" value. A value
of FALSE indicates that this user does not hold the floor in this
moment. If this control is not specified, this user SHOULD NOT
specify the floor option.
Besides the <floor> element, the <endpoint>/<media> element has two The <endpoint>/<media> element has two other child elements defined
other child elements defined in this document, the <to-mixer>, and in this document, the <to-mixer>, and the <from-mixer>:
the <from-mixer>:
o <from-mixer>, <to-mixer>: These are controls that apply to a o <from-mixer>, <to-mixer>: These are controls that apply to a
user's media stream being sent from the mixer to the participants user's media stream being sent from the mixer to the participants
endpoint or to the mixer from the participants endpoint. The <to- endpoint or to the mixer from the participants endpoint. The <to-
mixer> element details properties associated with the incoming mixer> element details properties associated with the incoming
streams to the mixer (streams sent to the mixer from the streams to the mixer (streams sent to the mixer from the
participant). The <from-mixer> element details properties participant). The <from-mixer> element details properties
associated with the outgoing streams from the mixer (sent from the associated with the outgoing streams from the mixer (sent from the
mixer to the participant). Both of these elements have the mixer to the participant). Both of these elements have the
attribute 'name'. The 'name' attribute has the values "VideoIn", attribute 'name'. The 'name' attribute has the values "VideoIn",
"VideoOut", "AudioOut", and "AudioIn". The "VideoOut" and "VideoOut", "AudioOut", and "AudioIn". The "VideoOut" and
"AudioOut" media streams detail properties associated with the "AudioOut" media streams detail properties associated with the
outgoing video and audio from the mixer. The "VideoIn" and outgoing video and audio from the mixer. The "VideoIn" and
"AudioIn" media stream details properties associated with the "AudioIn" media stream details properties associated with the
incoming video and audio to the mixer. More values can be defined incoming video and audio to the mixer. Both of these elements can
in the future. The <to-mixer> and <from-mixer> elements have the have the <floor> child element defined:
<controls> child element:
* The <floor> element refers to the floor assigned to a certain
participant in the conference. If a participant, for instance,
needs to talk in the conference, it first needs to get the
floor from the chair of the conference. The <floor> element
has an attribute 'id' which uniquely identifies a floor within
a conference. The 'id' attribute corresponds to the floor-id
identifier defined in [RFC4582] section 5.2.2. The <floor>
element has a "Boolean" value. A value of FALSE indicates that
this user does not hold the floor in this moment. If this
control is not specified, this user SHOULD NOT specify the
floor option.
The <to-mixer> and <from-mixer> elements can have the <controls>
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.
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. Note that
the <sidebars-by-ref> element does not have the attribute 'state' the <sidebars-by-ref> element does not have the attribute 'state'
defined in [RFC4575] for this element because this attribute only defined in [RFC4575] for this element because this attribute only
applies to notifications mechanism. applies to notifications mechanism.
4.8. <sidebars-by-val> 4.8. <sidebars-by-val>
skipping to change at page 33, line 32 skipping to change at page 33, line 34
& anyAttribute & anyAttribute
& element display-text { text }? & element display-text { text }?
& element referred { execution-type }? & element referred { execution-type }?
& element status { endpoint-status-type }? & element status { endpoint-status-type }?
& element joining-method { joining-type }? & element joining-method { joining-type }?
& element joining-info { execution-type }? & element joining-info { execution-type }?
& element disconnection-method { disconnection-type }? & element disconnection-method { disconnection-type }?
& element disconnection-info { execution-type }? & element disconnection-info { execution-type }?
& element media { media-type }* & element media { media-type }*
& element call-info { call-type }? & element call-info { call-type }?
& element xcon:floor {
attribute id { text },
anyAttribute,
xsd:boolean
}*
& anyElement* & anyElement*
# ENDPOINT STATUS TYPE # ENDPOINT STATUS TYPE
endpoint-status-type = endpoint-status-type =
"pending" "pending"
| "dialing-out" | "dialing-out"
| "dialing-in" | "dialing-in"
| "alerting" | "alerting"
| "on-hold" | "on-hold"
| "connected" | "connected"
| "muted-via-focus" | "muted-via-focus"
skipping to change at page 38, line 29 skipping to change at page 38, line 26
| xsd:string "refer" | xsd:string "refer"
| free-text-extension | free-text-extension
# ANONYMITY TYPE # ANONYMITY TYPE
provide-anonymity-type = provide-anonymity-type =
"private" | "semi-private" | "hidden" | free-text-extension "private" | "semi-private" | "hidden" | free-text-extension
# MIXER TYPE # MIXER TYPE
mixer-type = mixer-type =
attribute name { mixer-name-type } attribute name { mixer-name-type }
& anyAttribute & anyAttribute
& element xcon:controls { control-type }* & element xcon:controls { control-type }*
& element xcon:floor {
attribute id { text },
anyAttribute,
xsd:boolean
}*
& anyElement* & anyElement*
# MIXER NAME TYPE # MIXER NAME TYPE
mixer-name-type = mixer-name-type =
"VideoIn" | "VideoOut" | "AudioOut" | "AudioIn" | free-text-extension "VideoIn" | "VideoOut" | "AudioOut" | "AudioIn" | free-text-extension
# FREE TEXT EXTENSION # FREE TEXT EXTENSION
# (re-define this as <notAllowed/>, # (re-define this as <notAllowed/>,
# if extensions beyond this spec are not used) # if extensions beyond this spec are not used)
free-text-extension = text free-text-extension = text
skipping to change at page 56, line 31 skipping to change at page 56, line 31
[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., Bray, T., Paoli, J., and E. Maler, Maler, E., Sperberg-McQueen, C., Paoli, J., and T. Bray,
"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"
skipping to change at page 66, line 34 skipping to change at page 66, line 34
<element name="media"> <element name="media">
<ref name="media-type"/> <ref name="media-type"/>
</element> </element>
</zeroOrMore> </zeroOrMore>
<optional> <optional>
<element name="call-info"> <element name="call-info">
<ref name="call-type"/> <ref name="call-type"/>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<element name="xcon:floor">
<attribute name="id">
<text/>
</attribute>
<ref name="anyAttribute"/>
<data type="boolean"/>
</element>
</zeroOrMore>
<zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</interleave> </interleave>
</define> </define>
<!-- <!--
ENDPOINT STATUS TYPE ENDPOINT STATUS TYPE
--> -->
<define name="endpoint-status-type"> <define name="endpoint-status-type">
<choice> <choice>
<value>pending</value> <value>pending</value>
skipping to change at page 79, line 51 skipping to change at page 79, line 41
<!-- <!--
MIXER TYPE MIXER TYPE
--> -->
<define name="mixer-type"> <define name="mixer-type">
<interleave> <interleave>
<attribute name="name"> <attribute name="name">
<ref name="mixer-name-type"/> <ref name="mixer-name-type"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<zeroOrMore> <zeroOrMore>
<element name="xcon:floor">
<attribute name="id">
<text/>
</attribute>
<ref name="anyAttribute"/>
<data type="boolean"/>
</element>
</zeroOrMore>
<zeroOrMore>
<element name="xcon:controls"> <element name="xcon:controls">
<ref name="control-type"/> <ref name="control-type"/>
</element> </element>
</zeroOrMore> </zeroOrMore>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</interleave> </interleave>
</define> </define>
skipping to change at page 92, line 50 skipping to change at page 92, line 50
<xs:pattern value="semi-private"/> <xs:pattern value="semi-private"/>
<xs:pattern value="hidden"/> <xs:pattern value="hidden"/>
<xs:pattern value=".+"/> <xs:pattern value=".+"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<!-- MIXER TYPE --> <!-- MIXER TYPE -->
<xs:complexType name="mixer-type"> <xs:complexType name="mixer-type">
<xs:sequence> <xs:sequence>
<xs:element name="floor">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:boolean">
<xs:attribute name="id" type="xs:string"
use="required"/>
<xs:anyAttribute namespace="##any"
processContents="lax"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:element name="controls" type="controls-type" <xs:element name="controls" type="controls-type"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" <xs:any namespace="##other" processContents="lax"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="name" type="mixer-name-type" <xs:attribute name="name" type="mixer-name-type"
use="required"/> use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
 End of changes. 14 change blocks. 
40 lines changed or deleted 54 lines changed or added

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