draft-ietf-xcon-common-data-model-14.txt   draft-ietf-xcon-common-data-model-15.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: May 14, 2010 D. Morgan Expires: August 14, 2010 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
November 10, 2009 February 10, 2010
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-14.txt draft-ietf-xcon-common-data-model-15.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 46 skipping to change at page 1, line 46
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 The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 14, 2010. This Internet-Draft will expire on August 14, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 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
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the BSD License. described in the BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6
3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 3.3. The Conference Object Identifier . . . . . . . . . . . . . 7
3.3.1. Conference Object URI Definition . . . . . . . . . . . 9 3.3.1. Conference Object URI Definition . . . . . . . . . . . 9
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13
4.2. <conference-description> . . . . . . . . . . . . . . . . . 14 4.2. <conference-description> . . . . . . . . . . . . . . . . . 14
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 14 4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 15
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 15 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 15
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15
4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 15 4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 15
4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 15 4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 15
4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 15 4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 15
4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 16 4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 17
4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 17 4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 17
4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 17 4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 17
4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 17 4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 17
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 19 4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 20
4.4.1. <allow-conference-event-subscription> . . . . . . . . 19 4.4.1. <allow-conference-event-subscription> . . . . . . . . 20
4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 20 4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 20
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 20 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 21
4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 21 4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 21
4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21 4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21
4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22 4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22
4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 23 4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 23
4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23 4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23
4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24 4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24
4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 24 4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 25
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 25 4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 26
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 26 4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 26
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 26 4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 26
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26 4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 26 4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 27
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 26 4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 27
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 26 4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 27
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 27 4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 27
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27 4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 27 4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 28
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 28 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 29
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 28 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 29
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 39 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 40
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40
8. Security Considerations . . . . . . . . . . . . . . . . . . . 49 8. Security Considerations . . . . . . . . . . . . . . . . . . . 50
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 49 8.1. Authentication, Access Control, and Integrity . . . . . . 50
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 50 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 50
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 50 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 51
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 50
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51
9.3. Conference Object Identifier Registration . . . . . . . . 52 9.3. Conference Object Identifier Registration . . . . . . . . 52
9.4. Conference User Identifier Registration . . . . . . . . . 53 9.4. Conference User Identifier Registration . . . . . . . . . 53
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54
11.1. Normative References . . . . . . . . . . . . . . . . . . . 54 11.1. Normative References . . . . . . . . . . . . . . . . . . . 54
11.2. Informative References . . . . . . . . . . . . . . . . . . 54 11.2. Informative References . . . . . . . . . . . . . . . . . . 54
Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55
Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 82 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 83
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 92
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 4, line 27 skipping to change at page 5, line 27
conference during each of its various stages (e.g., created/creation, conference during each of its various stages (e.g., created/creation,
reserved/reservation, active/activation, completed/completion). A reserved/reservation, active/activation, completed/completion). A
conference object can be manipulated using a conference control conference object can be manipulated using a conference control
protocol at a conference server. The conference object represents a protocol at a conference server. The conference object represents a
particular instantiation of a conference information data model. particular instantiation of a conference information data model.
Consequently, conference objects follow the XML format defined in Consequently, conference objects follow the XML format defined in
this document. this document.
A conference object contains the core information of a conference A conference object contains the core information of a conference
(i.e., capabilities, membership, call control signaling, media, etc.) (i.e., capabilities, membership, call control signaling, media, etc.)
and specifies who, and in which way that information can be and specifies by whom, and in which way that information can be
manipulated. manipulated.
Figure 1 shows the logical functional elements of a conference server Figure 1 shows the logical functional elements of a conference server
as defined by the Centralized Conferencing Framework [RFC5239]. They as defined by the Centralized Conferencing Framework [RFC5239]. They
are a Conference Control Server, a Floor Control Server, a number of are a Conference Control Server, a Floor Control Server, a number of
Foci, and a Notification Service. A conference control protocol Foci, and a Notification Service. A conference control protocol
provides the interface between a conference control client and the provides the interface between a conference control client and the
conference control server. A floor control protocol (e.g., BFCP conference control server. A floor control protocol (e.g., BFCP
[RFC4582]) provides the interface between a floor control client and [RFC4582]) provides the interface between a floor control client and
the floor control server. A call signaling protocol (e.g., SIP, the floor control server. A call signaling protocol (e.g., SIP,
skipping to change at page 14, line 34 skipping to change at page 15, line 34
<sidebar-parent>, <conference-time>, <conf-uris>, <service-uris>, <sidebar-parent>, <conference-time>, <conf-uris>, <service-uris>,
<maximum-user-count>, and <available-media>. <maximum-user-count>, and <available-media>.
The following sections describe these elements in more detail. Other The following sections describe these elements in more detail. Other
child elements MAY be defined in the future to extend the child elements MAY be defined in the future to extend the
<conference-description> element. <conference-description> element.
4.2.1. <language> 4.2.1. <language>
The <language> element indicates the predominant language that is The <language> element indicates the predominant language that is
expected to be employed within a conference. This element is not expected to be employed within a conference. The possible values of
enforcing the language of the conference, but only informs the this element are the values of the 'Subtag' column of the [RFC5646]
participants about the desirable language that they should use in the defined in IANA [IANA-Lan]. This element is not enforcing the
conference. Participants are free to switch to other languages if language of the conference, but only informs the participants about
they like. the desirable language that they should use in the conference.
Participants are free to switch to other languages if they like.
4.2.2. <display-text> 4.2.2. <display-text>
The <display-text> element is described in section 5.3 of [RFC4575]. The <display-text> element is described in section 5.3 of [RFC4575].
4.2.3. <subject> 4.2.3. <subject>
The <subject> element is described in section 5.3 of [RFC4575]. The <subject> element is described in section 5.3 of [RFC4575].
4.2.4. <free-text> 4.2.4. <free-text>
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 action. If set to The <allow-sidebars> element represents a boolean value. If set to
TRUE, the conference is allowed to create sidebar conferences. TRUE, the conference is allowed to create sidebar conferences. If
absent, or set to FALSE, the conference can 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>
When the <sidebar-parent> is present, it indicates that the When the <sidebar-parent> is present, it indicates that the
conference object represents a sidebar of another conference. The conference object represents a sidebar of another conference. The
<sidebar-parent> element contains the conference object Identifier <sidebar-parent> element contains the conference object Identifier
(XCON-URI) (different from the main XCON-URI) of the parent. (XCON-URI) (different from the main XCON-URI) of the parent.
4.2.9. <conference-time> 4.2.9. <conference-time>
The <conference-time> element contains the information related to The <conference-time> element contains the information related to
conference time and duration of a conference. The <conference-time> conference time, policy, and duration of a conference. The
element contains one or more <entry> elements each defining the time <conference-time> element contains one or more <entry> elements each
information specifying a single conference occurrence. defining the time and policy information specifying a single
conference occurrence. The <conference-time> element differs from
the iCalendar objects [RFC2445] in the possibility to defined
different policies (<can-join-after-offset>, <must-join-before-
offset>) for the same conference at different times.
Every <entry> element contains the following child elements: Every <entry> element contains the following child elements:
o <base>: The <base> child element specifies the iCalendar object of o <base>: The <base> child element specifies the iCalendar object of
the conference. The iCalendar object components are defined in the conference. The iCalendar object components are defined in
[RFC2445]. [RFC2445].
o <mixing-start-offset>: The <mixing-start-offset> child element o <mixing-start-offset>: The <mixing-start-offset> child element
specifies when the conference media mixing starts before the specifies when the conference media mixing starts before the
conference starts. If the <mixing-start-offset> element is not conference starts. If the <mixing-start-offset> element is not
present, it indicates that the conference media mixing starts present, it indicates that the conference media mixing starts
skipping to change at page 17, line 31 skipping to change at page 18, line 42
The <available-media> element consists of a sequence of <entry> child The <available-media> element consists of a sequence of <entry> child
elements. Each <entry> element contain the 'label' attribute that is elements. Each <entry> element contain the 'label' attribute that is
the media stream identifier assigned by the conferencing server. The the media stream identifier assigned by the conferencing server. The
attribute 'label' is described in [RFC4575], section 5.3.4. Each attribute 'label' is described in [RFC4575], section 5.3.4. Each
<entry> element contains the following child elements: <entry> element contains the following child elements:
o The <type> element is described in section 5.3.4 of [RFC4575]. o The <type> element is described in section 5.3.4 of [RFC4575].
o The <display-text> element is described in section 5.3.4 of o The <display-text> element is described in section 5.3.4 of
[RFC4575]. [RFC4575].
o The <status> element is described in section 5.3.4 of [RFC4575]. o The <status> element is described in section 5.3.4 of [RFC4575].
o The child element <mixing-mode> describes a default policy by o The child element <mixing-mode> describes a default scheduling
which the mixer will build the outgoing stream from the incoming policy by which the mixer will build the outgoing stream from the
streams. Note that this policy is different than the policy incoming streams. Note that this policy is different than the
describing the floors for each media. The <mixing-mode> child policy describing the floors for each media. The <mixing-mode>
element MUST contain one and only one of the "Moderator- child element MUST contain one and only one of the "Moderator-
controlled", "FCFS", and "Automatic" values indicating the default controlled", "FCFS", and "Automatic" values indicating the default
algorithm to use with every media stream. The "Moderator- algorithm to use with every media stream. The "Moderator-
controlled" value indicates that the moderator of the conference, controlled" value indicates that the moderator of the conference,
controls the media stream policy. The "FCFS" value indicates a controls the media stream policy. The "FCFS" value indicates a
'first-come-first-served' policy. 'first-come-first-served' policy. The "Automatic" value means the
mixer choose the best scheduling policy for the conference.
o The <codecs> element specifies the allowed codecs in the o The <codecs> element specifies the allowed codecs in the
conference. It has an attribute 'decision' that specifies if the conference. It has an attribute 'decision' that specifies if the
focus decides the common codec automatically or needs the approval focus decides the common codec automatically or needs the approval
of the moderator of the conference ("automatic", "moderator- of the moderator of the conference ("automatic", "moderator-
controlled"). The <codecs> element contains <codec> elements. A controlled"). The <codecs> element contains <codec> elements. A
<codec> element can have the attribute 'name' and 'policy'. The <codec> element can have the attribute 'name' and 'policy'. The
'name' attribute is a codec identifier assigned by the 'name' attribute is a codec identifier assigned by the
conferencing server. The 'policy' attribute contains the policy conferencing server. The 'policy' attribute contains the policy
for that codec (allowed, or disallowed). The <codec> element has for that codec (allowed, or disallowed). The <codec> element has
the child element <subtype> which stores the codec's name. The the child element <subtype> which stores the codec's name. The
skipping to change at page 19, line 45 skipping to change at page 21, line 7
The <host-info> element contains information about the entity hosting The <host-info> element contains information about the entity hosting
the conference. This information is set before conference the conference. This information is set before conference
activation, and is rarely changed during the conference lifetime. activation, and is rarely changed during the conference lifetime.
The <host-info> element and its child elements are described in The <host-info> element and its child elements are described in
[RFC4575], section 5.4. Future extensions to the <host-info> element [RFC4575], section 5.4. Future extensions to the <host-info> element
may define new values. may define new values.
4.4. <conference-state> 4.4. <conference-state>
The <conference-state> is introduced in RFC4575 [RFC4575]. The The <conference-state> is introduced in [RFC4575]. The <conference-
<conference-state> element contains the <allow-conference-event- state> element contains the <allow-conference-event-subscription>,
subscription>, <user-count>, <active>, and <locked> child elements. <user-count>, <active>, and <locked> child elements.
4.4.1. <allow-conference-event-subscription> 4.4.1. <allow-conference-event-subscription>
The <allow-conference-event-subscription> element represents a The <allow-conference-event-subscription> element represents a
boolean action. If set to TRUE, the focus is instructed to allow the boolean action. If set to TRUE, the focus is instructed to allow the
subscription to conference state events, such as RFC4575 'SIP Event subscription to conference state events, such as 'SIP Event Package
Package for Conference State' [RFC4575]. If set to FALSE, the for Conference State' [RFC4575]. If set to FALSE, the subscription
subscription to conference state events would be rejected. If this to conference state events would be rejected. If this element is
element is undefined it has a default value of TRUE, causing the undefined it has a default value of TRUE, causing the subscription to
subscription to conference state events to be accepted. conference state events to be accepted.
4.4.2. <user-count> 4.4.2. <user-count>
The <user-count> child element is explained in [RFC4575], section The <user-count> child element is explained in [RFC4575], section
5.5.1. 5.5.1.
4.4.3. <active> 4.4.3. <active>
The <active> child element is explained in [RFC4575], section 5.5.2. The <active> child element is explained in [RFC4575], section 5.5.2.
skipping to change at page 23, line 9 skipping to change at page 24, line 17
instructions specified in the transformations of this rule. instructions specified in the transformations of this rule.
o "authenticate": This action instructs the focus that the user has o "authenticate": This action instructs the focus that the user has
to provide a combination of username/password. to provide a combination of username/password.
o "directed-operator": This action instructs the focus to direct the o "directed-operator": This action instructs the focus to direct the
user to an operator. user to an operator.
4.6.2. <user-admission-policy> 4.6.2. <user-admission-policy>
The <user-admission-policy> is an element that lets an organizer (or The <user-admission-policy> is an element that lets an organizer (or
a participant with appropriate rights) choose a policy for the a participant with appropriate rights) choose a policy for the
conference that controls how users are allowed into the conference. conference that controls how users are authenticated into the
The list of possible values are: conference, using a mechanism of the conference's choosing. Since a
variety of signaling protocols are possible, a variety of
authentication mechanism - determined by every individual conference
servers - may need to be mapped from the different protocols. The
specific types of authentication mechanism are beyond the scope of
this document. The list of possible values are:
o "closedAuthenticated": A 'closedAuthenticated' policy requires o "closedAuthenticated": A 'closedAuthenticated' policy requires
each conference participant to be in the allowed users list each conference participant to be in the allowed users list
(listed under the <allowed-users-list> XML element) with each (listed under the <allowed-users-list> XML element) with each
participant being sufficiently (up to local policy) authenticated. participant being sufficiently (up to local policy) authenticated.
Conference join requests for users not in the allowed users list Conference join requests for users not in the allowed users list
or participants not authenticated should be rejected unless a or participants not authenticated should be rejected unless a
<join-handling> action of 'confirm' is selected in which case the <join-handling> action of 'confirm' is selected in which case the
user is placed on a pending list as indicated earlier. user is placed on a pending list as indicated earlier.
o "openAuthenticated": An 'openAuthenticated' policy requires each o "openAuthenticated": An 'openAuthenticated' policy requires each
skipping to change at page 24, line 48 skipping to change at page 26, line 14
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'. Note that the <user> element does not have the attribute
'state' defined in [RFC4575] for this element because this attribute 'state' defined in [RFC4575] for this element because this attribute
only applies to notifications mechanism. only applies to notifications mechanism.
The attribute 'entity' contains a unique conference user identifier The attribute 'entity' contains a unique conference user identifier
(XCON-USERID) within the scope of a conferencing system. The URI (XCON-USERID) within the scope of the conference. The URI format of
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]
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
skipping to change at page 26, line 12 skipping to change at page 27, line 24
The <display-text> child element is explained in [RFC4575], section The <display-text> child element is explained in [RFC4575], section
5.6.1. 5.6.1.
4.6.5.2. <associated-aors> 4.6.5.2. <associated-aors>
The <associated-aors> child element is explained in [RFC4575], The <associated-aors> child element is explained in [RFC4575],
section 5.6.2. section 5.6.2.
4.6.5.3. <provide-anonymity> 4.6.5.3. <provide-anonymity>
The <provide-anonymity> element provides anonymity to the user. In The <provide-anonymity> element specifies what level of anonymity the
this case, the focus provides to the rest of the participants an server should provide to the user. In this case, the focus provides
anonymous identity for that user, for example anonymousX, or it does to the rest of the participants an anonymous identity for that user,
not provide any information for that user such that other users can for example anonymousX, or it does not provide any information for
not see he is a participant in the conference. This element only that user such that other users can not see he is a participant in
affects the way the user information is provided to the other the conference. This element only affects the way the user
participants. The real information about the user is still stored in information is provided to the other participants. The real
the data model. This can be achieved by using the <provide- information about the user is still stored in the data model. This
anonymity> element. This element has three values: 'private', 'semi- can be achieved by using the <provide-anonymity> element. This
private' and 'hidden'. The 'private' value specifies that this user element has three values: 'private', 'semi-private' and 'hidden'.
is completely anonymous in the conference. 'semi-private' value The 'private' value specifies that this user is completely anonymous
specifies that this user is anonymous to all users with equal or in the conference. 'semi-private' value specifies that this user is
lesser permissions in the conference. 'hidden' value specifies that anonymous to all users with equal or lesser permissions in the
other users can not see this participant in the conference. conference. 'hidden' value specifies that other users can not see
this participant in the conference.
4.6.5.4. <roles> 4.6.5.4. <roles>
A role provides the context for the set of conference operations that A role provides the context for the set of conference operations that
a participant can perform. This element can contain one of the a participant can perform. This element can contain one of the
following values: "administrator", "moderator", "user", following values: "administrator", "moderator", "user",
"participant", "observer", and "none". The roles semantic definition "participant", "observer", and "none". The roles semantic definition
is out of the scope of this document and is subject to future policy is out of the scope of this document and is subject to future policy
documents. This element can be extended with new roles in future documents. This element can be extended with new roles in future
documents. documents.
skipping to change at page 26, line 50 skipping to change at page 28, line 18
5.6.4. 5.6.4.
4.6.5.6. <cascaded-focus> 4.6.5.6. <cascaded-focus>
The <cascaded-focus> child element is explained in [RFC4575], section The <cascaded-focus> child element is explained in [RFC4575], section
5.6.5. 5.6.5.
4.6.5.7. <allow-refer-users-dynamically> 4.6.5.7. <allow-refer-users-dynamically>
The <allow-refer-users-dynamically> element represents a boolean The <allow-refer-users-dynamically> element represents a boolean
action. If set to TRUE, a participant is allowed to instruct the value. If set to TRUE, a participant is allowed to instruct the
focus to refer a user to the conference without modifying the focus to refer a user to the conference without modifying the
<allowed-users-list> (in SIP terms, a participant is allowed to send <allowed-users-list> (in SIP terms, a participant is allowed to send
a REFER request to the focus which results in the focus sending a a REFER request to the focus which results in the focus sending a
REFER request to the user the referrer wishes to join the REFER request to the user the referrer wishes to join the
conference). If set to FALSE, the refer request is rejected. If conference). If set to FALSE, the refer request is rejected. If
this element is undefined it has a value of FALSE, causing the refer this element is undefined it has a value of FALSE, causing the refer
to be rejected. to be rejected.
4.6.5.8. <allow-invite-users-dynamically> 4.6.5.8. <allow-invite-users-dynamically>
skipping to change at page 27, line 48 skipping to change at page 29, line 20
element in this document does not defined the 'state' attribute element in this document does not defined the 'state' attribute
defined in [RFC4575] for the same element since the 'state' attribute defined in [RFC4575] for the same element since the 'state' attribute
only applies to notification mechanisms. only applies to notification mechanisms.
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>, <floor>,and
<call-info>. All the <endpoint> child elements are defined in <call-info>. All the <endpoint> child elements are defined in
[RFC4575] with the exception of the <floor> element. [RFC4575] with the exception of the <floor> element.
The <floor> element describes a floor that joins this participant in The <floor> element refers to the floor assigned to a certain
the conference. If a participant, for instance, needs to talk in the participant in the conference. If a participant, for instance, needs
conference, it first needs to get the floor from the chair of the to talk in the conference, it first needs to get the floor from the
conference. The <floor> element has an attribute 'id' which uniquely chair of the conference. The <floor> element has an attribute 'id'
identifies a floor or floors within a conference. The 'id' attribute which uniquely identifies a floor or floors within a conference. The
corresponds to the floor-id identifier defined in [RFC4582] section 'id' attribute corresponds to the floor-id identifier defined in
5.2.2. The <floor> element has a "Boolean" value. A value of FALSE [RFC4582] section 5.2.2. The <floor> element has a "Boolean" value.
indicates that this user does not hold the floor in this moment. If A value of FALSE indicates that this user does not hold the floor in
this control is not specified, this user SHOULD NOT specify the floor this moment. If this control is not specified, this user SHOULD NOT
option. specify the floor option.
Besides the <floor> element, the <endpoint>/<media> element has two Besides the <floor> element, the <endpoint>/<media> element has two
other child elements defined in this document, the <to-mixer>, and other child elements defined 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
skipping to change at page 30, line 4 skipping to change at page 31, line 25
& element free-text { text }? & element free-text { text }?
& element keywords { & element keywords {
list { xsd:string* } list { xsd:string* }
}? }?
& element conf-uris { uris-type }? & element conf-uris { uris-type }?
& element service-uris { uris-type }? & element service-uris { uris-type }?
& element maximum-user-count { xsd:int }? & element maximum-user-count { xsd:int }?
& element available-media { conference-media-type }? & element available-media { conference-media-type }?
& element xcon:language { xsd:language }? & element xcon:language { xsd:language }?
& element xcon:allow-sidebars { xsd:boolean }? & element xcon:allow-sidebars { xsd:boolean }?
& element xcon:cloning-parent { xsd:unsignedLong }? & element xcon:cloning-parent { xsd:anyURI }?
& element xcon:sidebar-parent { xsd:unsignedLong }? & element xcon:sidebar-parent { xsd:anyURI }?
& element xcon:conference-time { conferencetime-type }? & element xcon:conference-time { conferencetime-type }?
& anyElement* & anyElement*
} }
# HOST TYPE # HOST TYPE
host-type = host-type =
element display-text { text }? element display-text { text }?
& element web-page { xsd:anyURI }? & element web-page { xsd:anyURI }?
& element uris { uris-type }? & element uris { uris-type }?
& anyElement* & anyElement*
& anyAttribute & anyAttribute
skipping to change at page 30, line 51 skipping to change at page 32, line 24
uris-type = uris-type =
anyAttribute anyAttribute
& element entry { uri-type }* & element entry { uri-type }*
& anyElement* & anyElement*
# URI TYPE # URI TYPE
uri-type = uri-type =
element uri { xsd:anyURI } element uri { xsd:anyURI }
& element display-text { text }? & element display-text { text }?
& element purpose { text }? & element purpose { text }?
& element modified { execution-type }? & element modified { execution-type }?
& element xcon:conference-password { text }? & element xcon:conference-password { text }*
& anyElement* & anyElement*
& anyAttribute & anyAttribute
# USERS TYPE # USERS TYPE
users-type = users-type =
anyAttribute anyAttribute
& element user { user-type }* & element user { user-type }*
& element xcon:join-handling { join-handling-type }? & element xcon:join-handling { join-handling-type }?
& element xcon:user-admission-policy { user-admission-policy-type }? & element xcon:user-admission-policy { user-admission-policy-type }?
& element xcon:allowed-users-list { allowed-users-list-type }? & element xcon:allowed-users-list { allowed-users-list-type }?
& element xcon:deny-users-list { deny-user-list-type }? & element xcon:deny-users-list { deny-user-list-type }?
skipping to change at page 45, line 39 skipping to change at page 47, line 14
<xcon:video-layout <xcon:video-layout
>single-view</xcon:video-layout> >single-view</xcon:video-layout>
</xcon:controls> </xcon:controls>
</xcon:to-mixer> </xcon:to-mixer>
</media> </media>
<media id="2"> <media id="2">
<type>audio</type> <type>audio</type>
<label>10234</label> <label>10234</label>
<src-id>532535</src-id> <src-id>532535</src-id>
<status>sendrecv</status> <status>sendrecv</status>
<xcon:to-mixer name="VideoIn"> <xcon:to-mixer name="AudioIn">
<xcon:controls> <xcon:controls>
<xcon:gain>50</xcon:gain> <xcon:gain>50</xcon:gain>
</xcon:controls> </xcon:controls>
</xcon:to-mixer> </xcon:to-mixer>
<xcon:from-mixer name="VideoOut"> <xcon:from-mixer name="AudioOut">
<xcon:controls> <xcon:controls>
<xcon:gain>50</xcon:gain> <xcon:gain>50</xcon:gain>
</xcon:controls> </xcon:controls>
</xcon:from-mixer> </xcon:from-mixer>
</media> </media>
<!-- <!--
CALL INFO CALL INFO
--> -->
<call-info> <call-info>
<sip> <sip>
<display-text>full info</display-text> <display-text>full info</display-text>
<call-id>truy45469123478</call-id> <call-id>truy45469123478</call-id>
<from-tag>asd456cbgt</from-tag> <from-tag>asd456cbgt</from-tag>
<to-tag>3456jgjg1234</to-tag> <to-tag>3456jgjg1234</to-tag>
</sip> </sip>
</call-info> </call-info>
<xcon:floor id="345">true</xcon:floor> <xcon:floor id="345">true</xcon:floor>
skipping to change at page 47, line 23 skipping to change at page 48, line 46
<xcon:video-layout <xcon:video-layout
>single-view</xcon:video-layout> >single-view</xcon:video-layout>
</xcon:controls> </xcon:controls>
</xcon:to-mixer> </xcon:to-mixer>
</media> </media>
<media id="2"> <media id="2">
<type>audio</type> <type>audio</type>
<label>10234</label> <label>10234</label>
<src-id>532535</src-id> <src-id>532535</src-id>
<status>sendrecv</status> <status>sendrecv</status>
<xcon:to-mixer name="VideoIn"> <xcon:to-mixer name="AudioIn">
<xcon:controls> <xcon:controls>
<xcon:gain>50</xcon:gain> <xcon:gain>50</xcon:gain>
</xcon:controls> </xcon:controls>
</xcon:to-mixer> </xcon:to-mixer>
<xcon:from-mixer name="VideoOut"> <xcon:from-mixer name="AudioOut">
<xcon:controls> <xcon:controls>
<xcon:gain>50</xcon:gain> <xcon:gain>50</xcon:gain>
</xcon:controls> </xcon:controls>
</xcon:from-mixer> </xcon:from-mixer>
</media> </media>
<!-- <!--
CALL INFO CALL INFO
--> -->
<call-info> <call-info>
<sip> <sip>
skipping to change at page 49, line 40 skipping to change at page 51, line 15
Note that due to RFC formatting conventions, this documents splits Note that due to RFC formatting conventions, this documents splits
lines whose content would exceed 72 characters. Two backslash lines whose content would exceed 72 characters. Two backslash
characters mark where line folding has taken place. These characters mark where line folding has taken place. These
backslashes would not appear in the actual XML data model. backslashes would not appear in the actual XML data model.
8. Security Considerations 8. Security Considerations
There are numerous security considerations for this document. This There are numerous security considerations for this document. This
section considers them. section considers them.
8.1. Authentication 8.1. Authentication, Access Control, and Integrity
Different conferencing protocols will support different types of Different conferencing protocols will support different types of
authentication mechanisms. Since a variety of signaling protocols authentication mechanisms. Since a variety of signaling protocols
are possible, a variety of authentication mechanism may need to be are possible, a variety of authentication mechanism - determined by
mapped from the different protocols. every individual conference servers - may need to be mapped from the
different protocols. The specific types of authentication mechanism
are beyond the scope of this document.
Futhermore, users may use different namespaces to access to a Futhermore, users may use different namespaces to access to a
conference. So a mapping database has to specify the acceptable conference. So a mapping database has to specify the acceptable
range of namespace for a user. Doing so, a users will not access the range of namespace for a user. It is RECOMMENDED that the mapping
same conference twice using a different namespace. database has integrity when it is established, the integrity has to
be protected, and the database has to be maintained to ensure changes
in namespaces are accurately reflected. Doing so, users will not
access the same conference twice using a different namespace.
The security considerations for authentication (section 10.1) The security considerations for authentication (section 10.1)
described in the centralized conferencing framework [RFC4575] applies described in the centralized conferencing framework [RFC4575] applies
to this document. The focus must ensure that only authorized to this document. The focus must ensure that only authorized
entities are able to manipulate the data to access the information. entities are able to manipulate the data to access the information.
8.2. Confidentiality 8.2. Confidentiality
Participants of a conference may not want to reveal some private Participants of a conference may not want to reveal some private
information to other users. The Conference Information Data Model information to other users. The Conference Information Data Model
contains sensitive data which should not be analyzed or given to contains sensitive data which should not be analyzed or given to
anyone. Confidentiality is provided through encryption. Strong end- anyone. Examples of potential attacks include eavesdropping or
to-end authentication and encryption can be done using public keys, illegal copying of sensitive information. The protocols used for
and end-to-end encryption can be done using private keys. It is manipulation and retrieval of sensitive conference information MUST
RECOMMENDED that the protocols that manipulated the conference be able to provide confidentiality and integrity mechanism.
information data model use a strong encryption for conference Confidentiality is provided through encryption. Strong end-to-end
information protection. authentication and encryption can be done using public keys, and end-
to-end encryption can be done using private keys. It is RECOMMENDED
8.3. Integrity that all the protocols that manipulated the conference information
data model implement TLS.
A conferencing system may maintain a mapping database between the
conference object identifiers and the identifiers associated with
each of the complementary centralized conferencing protocols, as well
as, a mapping between the conference user identifiers and the
identifiers associated with each user in a conference. This mapping
database contains sensitive data. It is RECOMMENDED that the mapping
database has integrity when it is established, the integrity has to
be protected, and the database has to be maintained to ensure changes
in namespaces are accurately reflected.
9. IANA Considerations 9. IANA Considerations
9.1. Relax NG Schema Registration 9.1. Relax NG Schema Registration
This specification registers a schema. The schema can be found This specification registers a schema. The schema can be found
as the sole content of Section 5. as the sole content of Section 5.
URI: urn:ietf:params:xml:ns:xcon-conference-info URI: urn:ietf:params:xml:ns:xcon-conference-info
Registrant Contact: IETF XCON working group, Registrant Contact: IETF XCON working group,
<xcon@ietf.org>, Oscar Novo <xcon@ietf.org>, Oscar Novo
<Oscar.Novo@ericsson.com> <Oscar.Novo@ericsson.com>
Relax NG Schema: The Relax NG schema to be registered is contained Relax NG Schema: The Relax NG schema to be registered is contained
skipping to change at page 53, line 41 skipping to change at page 54, line 41
Comments: Comments:
Identifies the User in the conference Identifies the User in the conference
10. Acknowledgements 10. Acknowledgements
This document is really a distillation of many ideas discussed over a This document is really a distillation of many ideas discussed over a
long period of time. These ideas were contributed by many different long period of time. These ideas were contributed by many different
drafts in the XCON working group and the SIPPING working group. We drafts in the XCON working group and the SIPPING working group. We
would like to thank Orit Levin, Roni Even, Adam Roach, Mary Barnes, would like to thank Orit Levin, Roni Even, Adam Roach, Mary Barnes,
Chris Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Chris Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen,
Aki Niemi, Rohan Mahy, Jonathan Lennox, and Henning Schulzrinne for Aki Niemi, Rohan Mahy, Jonathan Lennox, Sean Duddy, Richard Barnes,
their comments. Also, we would like to thank Mary Barnes, and Chris and Henning Schulzrinne for their comments. Also, we would like to
Boulton for letting us use the conference and user identifier thank Mary Barnes, and Chris Boulton for letting us use the
information of their xcon drafts. Last but not least, we would like conference and user identifier information of their xcon drafts.
to express our gratitude to all those reviewers for their invaluable Last but not least, we would like to express our gratitude to all
contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi, those reviewers for their invaluable contribution: Simon Pietro
Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, Romano, Lorenzo Miniero, Tobia Castaldi, Miguel Garcia, Mary Barnes,
Pierre Tane, and Ben Campbell. Srivatsa Srinivasan, Avshalom Houri, Pierre Tane, and Ben Campbell.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and [RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
skipping to change at page 54, line 38 skipping to change at page 55, line 38
RFC 4583, November 2006. RFC 4583, November 2006.
[RFC5239] Barnes, M., Boulton, C., and O. Levin, "A Framework for [RFC5239] Barnes, M., Boulton, C., and O. Levin, "A Framework for
Centralized Conferencing", RFC 5239, June 2008. Centralized Conferencing", RFC 5239, June 2008.
11.2. Informative References 11.2. Informative References
[IANA] "IANA registry for RTP Payload Types" [IANA] "IANA registry for RTP Payload Types"
"http://www.iana.org/assignments/rtp-parameters". "http://www.iana.org/assignments/rtp-parameters".
[IANA-Lan]
"IANA Language Subtag Registry"
"http://www.iana.org/assignments/
language-subtag-registry".
[RELAX] "RELAX NG Home Page" "http://relaxng.org/". [RELAX] "RELAX NG Home Page" "http://relaxng.org/".
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
June 2002. June 2002.
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
Event Notification", RFC 3265, June 2002. Event Notification", RFC 3265, June 2002.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
skipping to change at page 55, line 15 skipping to change at page 56, line 19
[RFC4353] Rosenberg, J., "A Framework for Conferencing with the [RFC4353] Rosenberg, J., "A Framework for Conferencing with the
Session Initiation Protocol (SIP)", RFC 4353, Session Initiation Protocol (SIP)", RFC 4353,
February 2006. February 2006.
[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
Languages", BCP 47, RFC 5646, September 2009.
[W3C.REC-xml-20001006] [W3C.REC-xml-20001006]
Sperberg-McQueen, C., Paoli, J., Maler, E., 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"
skipping to change at page 57, line 45 skipping to change at page 59, line 4
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="available-media"> <element name="available-media">
<ref name="conference-media-type"/> <ref name="conference-media-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="xcon:language"> <element name="xcon:language">
<data type="language"/> <data type="language"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="xcon:allow-sidebars"> <element name="xcon:allow-sidebars">
<data type="boolean"/> <data type="boolean"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="xcon:cloning-parent"> <element name="xcon:cloning-parent">
<data type="unsignedLong"/> <data type="anyURI"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="xcon:sidebar-parent"> <element name="xcon:sidebar-parent">
<data type="unsignedLong"/> <data type="anyURI"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="xcon:conference-time"> <element name="xcon:conference-time">
<ref name="conferencetime-type"/> <ref name="conferencetime-type"/>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
skipping to change at page 61, line 37 skipping to change at page 62, line 45
<optional> <optional>
<element name="purpose"> <element name="purpose">
<text/> <text/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="modified"> <element name="modified">
<ref name="execution-type"/> <ref name="execution-type"/>
</element> </element>
</optional> </optional>
<optional> <zeroOrMore>
<element name="xcon:conference-password"> <element name="xcon:conference-password">
<text/> <text/>
</element> </element>
</optional> </zeroOrMore>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
</interleave> </interleave>
</define> </define>
<!-- <!--
USERS TYPE USERS TYPE
--> -->
skipping to change at page 83, line 23 skipping to change at page 84, line 31
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
attributeFormDefault="unqualified" elementFormDefault="qualified" attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="urn:ietf:params:xml:ns:xcon-conference-info"> targetNamespace="urn:ietf:params:xml:ns:xcon-conference-info">
<xs:import namespace="urn:ietf:params:xml:ns:conference-info" <xs:import namespace="urn:ietf:params:xml:ns:conference-info"
schemaLocation="rfc4575.xsd"/> schemaLocation="rfc4575.xsd"/>
<xs:import namespace="http://www.w3.org/XML/1998/namespace" <xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/03/xml.xsd"/> schemaLocation="http://www.w3.org/2001/03/xml.xsd"/>
<xs:element name="conference-password" type="xs:string"/> <xs:simpleType name="conference-password">
<xs:list itemType="xs:string"/>
</xs:simpleType>
<xs:element name="mixing-mode" type="mixing-mode-type"/> <xs:element name="mixing-mode" type="mixing-mode-type"/>
<xs:element name="codecs" type="codecs-type"/> <xs:element name="codecs" type="codecs-type"/>
<xs:element name="controls" type="controls-type"/> <xs:element name="controls" type="controls-type"/>
<xs:element name="language" type="xs:language"/> <xs:element name="language" type="xs:language"/>
<xs:element name="allow-sidebars" type="xs:boolean"/> <xs:element name="allow-sidebars" type="xs:boolean"/>
<xs:element name="cloning-parent" type="xs:unsignedLong"/> <xs:element name="cloning-parent" type="xs:anyURI"/>
<xs:element name="sidebar-parent" type="xs:unsignedLong"/> <xs:element name="sidebar-parent" type="xs:anyURI"/>
<xs:element name="conference-time" type="conference-time-type"/> <xs:element name="conference-time" type="conference-time-type"/>
<xs:element name="allow-conference-event-subscription" <xs:element name="allow-conference-event-subscription"
type="xs:boolean"/> type="xs:boolean"/>
<xs:element name="to-mixer" type="mixer-type"/> <xs:element name="to-mixer" type="mixer-type"/>
<xs:element name="provide-anonymity" <xs:element name="provide-anonymity"
type="provide-anonymity-type"/> type="provide-anonymity-type"/>
<xs:element name="allow-refer-users-dynamically" <xs:element name="allow-refer-users-dynamically"
type="xs:boolean"/> type="xs:boolean"/>
<xs:element name="allow-invite-users-dynamically" <xs:element name="allow-invite-users-dynamically"
type="xs:boolean"/> type="xs:boolean"/>
 End of changes. 53 change blocks. 
126 lines changed or deleted 159 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/