draft-ietf-xcon-common-data-model-07.txt   draft-ietf-xcon-common-data-model-08.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 22, 2008 D. Morgan Expires: June 18, 2008 D. Morgan
Fidelity Investments Fidelity Investments
R. Even R. Even
Polycom Polycom
November 19, 2007 December 16, 2007
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-07.txt draft-ietf-xcon-common-data-model-08.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 22, 2008. This Internet-Draft will expire on June 18, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
Session Initiation Protocol (SIP) Event Package for Conference State. Session Initiation Protocol (SIP) Event Package for Conference State.
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 URI Definition . . . . . . . . . . . . . . 8 3.3.1. Conference URI Definition . . . . . . . . . . . . . . 9
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 8 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 9 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13
4.2. <conference-description> . . . . . . . . . . . . . . . . . 13 4.2. <conference-description> . . . . . . . . . . . . . . . . . 14
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 13 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> . . . . . . . . . . . . . . . . . . . . . 14
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 14 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15
4.2.7. <conference-time> . . . . . . . . . . . . . . . . . . 14 4.2.7. <conference-time> . . . . . . . . . . . . . . . . . . 15
4.2.8. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 15 4.2.8. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 16
4.2.9. <service-uris> . . . . . . . . . . . . . . . . . . . . 16 4.2.9. <service-uris> . . . . . . . . . . . . . . . . . . . . 16
4.2.10. <maximum-user-count> . . . . . . . . . . . . . . . . . 16 4.2.10. <maximum-user-count> . . . . . . . . . . . . . . . . . 17
4.2.11. <available-media> . . . . . . . . . . . . . . . . . . 16 4.2.11. <available-media> . . . . . . . . . . . . . . . . . . 17
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 18 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 18 4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 19
4.4.1. <allow-conference-event-subscription> . . . . . . . . 19 4.4.1. <allow-conference-event-subscription> . . . . . . . . 19
4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 19 4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 19
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 19 4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 19 4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 19 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 19 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 19 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 20
4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 20 4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 20
4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 20 4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21
4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 21 4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 21 4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22
4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 22 4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 22
4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 22 4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23
4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 23 4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24
4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 23 4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 24
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 24 4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 25
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 24 4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 25
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 25 4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 25
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 25 4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 25 4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 26
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 25 4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 26
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 25 4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 26
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 25 4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 26
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 26 4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 26 4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 27
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 27 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 28
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 27 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 28
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 27 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 28
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 34 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 36
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 35 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 36
8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 8. Security Considerations . . . . . . . . . . . . . . . . . . . 45
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 43 8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 45
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 43 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 46
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 43 8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 46
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 43 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 46
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 44 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 47
9.3. Conference Object Identifier Registration . . . . . . . . 45 9.3. Conference Object Identifier Registration . . . . . . . . 47
9.4. Conference User Identifier Registration . . . . . . . . . 46 9.4. Conference User Identifier Registration . . . . . . . . . 48
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 46 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
11.1. Normative References . . . . . . . . . . . . . . . . . . . 46 11.1. Normative References . . . . . . . . . . . . . . . . . . . 48
11.2. Informative References . . . . . . . . . . . . . . . . . . 47 11.2. Informative References . . . . . . . . . . . . . . . . . . 49
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML
Syntax . . . . . . . . . . . . . . . . . . . . . . . 47 Syntax . . . . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 70
Intellectual Property and Copyright Statements . . . . . . . . . . 69 Intellectual Property and Copyright Statements . . . . . . . . . . 72
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.
Conference objects are a fundamental concept in Centralized Conference objects are a fundamental concept in Centralized
Conferencing, as described in the Centralized Conferencing Framework Conferencing, as described in the Centralized Conferencing Framework
[4]. A conference object contains data that represents a conference [I-D.ietf-xcon-framework]. A conference object contains data that
during each of its various stages (e.g., created/creation, reserved/ represents a conference during each of its various stages (e.g.,
reservation, active/activation, completed/completion). A conference created/creation, reserved/reservation, active/activation, completed/
object can be manipulated using a conference control protocol at a completion). A conference object can be manipulated using a
conference server. The conference object represents a particular conference control protocol at a conference server. The conference
instantiation of a conference information data model. Consequently, object represents a particular instantiation of a conference
conference objects follow the XML format defined in this document. information data model. Consequently, conference objects follow the
XML format defined in 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 who, 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 [4]. They are a as defined by the Centralized Conferencing Framework
Conference Control Server, a Floor Control Server, a number of Foci, [I-D.ietf-xcon-framework]. They are a Conference Control Server, a
and a Notification Service. A conference control protocol provides Floor Control Server, a number of Foci, and a Notification Service.
the interface between a conference control client and the conference A conference control protocol provides the interface between a
control server. A floor control protocol (e.g., BFCP [5]) provides conference control client and the conference control server. A floor
the interface between a floor control client and the floor control control protocol (e.g., BFCP [RFC4582]) provides the interface
server. A call signaling protocol (e.g., SIP, H.323, Q.931, ISUP, between a floor control client and the floor control server. A call
etc.) provides the interface between a call signaling client and a signaling protocol (e.g., SIP, H.323, Q.931, ISUP, etc.) provides the
Focus. A notification protocol (e.g., SIP-based event notifications interface between a call signaling client and a Focus. A
[6]) provides the interface between the conferencing client and the notification protocol (e.g., SIP-based event notifications [RFC3265])
provides the interface between the conferencing client and the
Notification Service. Within a conference, the conference control Notification Service. Within a conference, the conference control
server, floor control server, and focus can modify the information in server, floor control server, and focus can modify the information in
the conference object. the conference object.
............................................................... ...............................................................
. Conferencing Server . . Conferencing Server .
. +---------------------------------------------------+ . . +---------------------------------------------------+ .
. | C o n f e r e n c e o b j e c t | . . | C o n f e r e n c e o b j e c t | .
. +-+--------------------------------------------------+| . . +-+--------------------------------------------------+| .
. | C o n f e r e n c e o b j e c t || . . | C o n f e r e n c e o b j e c t || .
skipping to change at page 6, line 5 skipping to change at page 6, line 5
........|..............|..............|..........|............. ........|..............|..............|..........|.............
|Conference |Binary Floor |Call |Notification |Conference |Binary Floor |Call |Notification
|Control |Control |Signaling |Protocol |Control |Control |Signaling |Protocol
|Protocol |Protocol |Protocol | |Protocol |Protocol |Protocol |
........v..............v..............v..........v............. ........v..............v..............v..........v.............
. C o n f e r e n c i n g C l i e n t . . C o n f e r e n c i n g C l i e n t .
............................................................... ...............................................................
Figure 1: Conference Server Architecture Figure 1: Conference Server Architecture
The Session Initiation Protocol (SIP) Event Package for Conference The Session Initiation Protocol (SIP) Event Package for Conference
State, specified in RFC4575 [1], already defines a data format for State, specified in [RFC4575], already defines a data format for
conferences. However, that model is SIP specific and lacks elements conferences. However, that model is SIP specific and lacks elements
related to some of the functionality defined by the Centralized related to some of the functionality defined by the Centralized
Conferencing Framework [4] (e.g., floor control). The data model Conferencing Framework [I-D.ietf-xcon-framework] (e.g., floor
defined in this document constitutes a superset of the data format control). The data model defined in this document constitutes a
defined in RFC4575 [1]. The result is a data format that supports superset of the data format defined in [RFC4575]. The result is a
more call signaling protocols besides SIP and that covers all the data format that supports more call signaling protocols besides SIP
functionality defined in the Centralized Conferencing Framework [4]. and that covers all the functionality defined in the Centralized
Conferencing Framework [I-D.ietf-xcon-framework].
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [2]. document are to be interpreted as described in RFC 2119 [RFC2119].
This document uses the terminology defined in the Centralized This document uses the terminology defined in the Centralized
Conferencing Framework [4], the SIPPING conferencing framework [7] Conferencing Framework [I-D.ietf-xcon-framework], the SIPPING
and the BFCP (Binary Floor Control Protocol) specification [5]. conferencing framework [RFC4353] and the BFCP (Binary Floor Control
Readers of this document should be familiar with the terminology used Protocol) specification [RFC4582]. Readers of this document should
in those documents. be familiar with the terminology used in those documents.
3. Overview 3. Overview
The data model specified in this document is the result of extending The data model specified in this document is the result of extending
the data format defined in RFC4575 [1] with new elements. Examples the data format defined in [RFC4575] with new elements. Examples of
of such extensions include scheduling elements, media control such extensions include scheduling elements, media control elements,
elements, floor control elements, non-SIP URIs, and addition of floor control elements, non-SIP URIs, and addition of localization
localization extensions to text elements. This data model can be extensions to text elements. This data model can be used by
used by conference servers providing different types of basic conference servers providing different types of basic conferences.
conferences. It is expected that this data model can be further It is expected that this data model can be further extended with new
extended with new elements in the future in order to implement elements in the future in order to implement additional advanced
additional advanced features. features.
3.1. Data Model Format 3.1. Data Model Format
A conference object document is an XML [8] document that MUST be well A conference object document is an XML [W3C.REC-xml-20001006]
formed and SHOULD be valid. Conference object documents MUST be document that MUST be well formed and SHOULD be valid. Conference
based on XML 1.0 and SHOULD be encoded using UTF-8. object documents MUST be based on XML 1.0 and SHOULD be encoded using
UTF-8.
3.2. Data Model Namespace 3.2. Data Model Namespace
This specification defines a new namespace specification for This specification defines a new namespace specification for
identifying the elements defined in the data model. This namespace identifying the elements defined in the data model. This namespace
is as follows: is as follows:
urn:ietf:params:xml:ns:xcon-conference-info urn:ietf:params:xml:ns:xcon-conference-info
3.3. The Conference Object Identifier 3.3. The Conference Object Identifier
skipping to change at page 7, line 43 skipping to change at page 8, line 20
| xcon:Ji092i@example.com | | xcon:Ji092i@example.com |
+------+-------------------+ +------+-------------------+
| |
| |
| |
+-----------------+---------------+ +-----------------+---------------+
| | | |
+-----------+-----------+ +----------+---------+ +-----------+-----------+ +----------+---------+
| CSP Conference IDs | |BFCP 'Conference ID'| | CSP Conference IDs | |BFCP 'Conference ID'|
+-----------------------+ +--------------------+ +-----------------------+ +--------------------+
|h323:Ji092i@example.com| | Ji092i | | h323:i092@example.com | | i092 |
|tel:+44(0)2920930033 | +----------+---------+ |tel:+44(0)2920930033 | +----------+---------+
|sip:Ji092i@example.com | | | sip:i092@example.com | |
+-----------------------+ +-------+--------+ +-----------------------+ +-------+--------+
| BFCP 'Floor ID'| | BFCP 'Floor ID'|
+----------------+ +----------------+
| 543 | | 543 |
| 09cnJk | | 236 |
+----------------+ +----------------+
Figure 2: Conference Object Mapping Figure 2: Conference Object Mapping
In Figure 2, the conference object identifier acts as the top level In Figure 2, the conference object identifier acts as the top level
key in the identification process. The call signaling protocols have key in the identification process. The call signaling protocols have
an associated conference user identifier, often represented in the an associated conference user identifier, often represented in the
form of URIs. The binary floor control protocol, as defined in [5], form of URIs. The binary floor control protocol, as defined in
defines the 'conference ID' identifier which represents a conference [RFC4582], defines the 'conference ID' identifier which represents a
instance within floor control. When created within the conferencing conference instance within floor control. When created within the
system, the 'conference ID' has a 1:1 mapping to the unique conferencing system, the 'conference ID' has a 1:1 mapping to the
conference object Identifier(XCON-URI). Operations associated with unique conference object Identifier(XCON-URI). Operations associated
the conference control protocols are directly associated with the with the conference control protocols are directly associated with
conference object, thus the primary identifier associated with these the conference object, thus the primary identifier associated with
protocols is the conference object identifier(XCON-URI). The these protocols is the conference object identifier(XCON-URI). The
mappings between additional protocols/interface is not strictly 1:1 mappings between additional protocols/interface is not strictly 1:1
and does allow for multiple occurrences. For example, multiple call and does allow for multiple occurrences. For example, multiple call
signaling protocols will each have a representation that is signaling protocols will each have a representation that is
implicitly linked to the top level conference object identifier e.g. implicitly linked to the top level conference object identifier e.g.
H323 and SIP URIs that represent a conference instance. It should be H323 and SIP URIs that represent a conference instance. It should be
noted that a conferencing system is free to structure such noted that a conferencing system is free to structure such
relationships as required and this information is just included as a relationships as required and this information is just included as a
guideline that can be used. guideline that can be used.
Further elements can be added to the tree representation in Figure 2 Further elements can be added to the tree representation in Figure 2
to enable a complete representation of a conference instance within a to enable a complete representation of a conference instance within a
conferencing system. conferencing system.
3.3.1. Conference URI Definition 3.3.1. Conference URI Definition
XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host, port, and unreserved are defined in RFC3986[9] host, port, and unreserved are defined in RFC3986[RFC3986]
3.4. Data Model Structure 3.4. Data Model Structure
The information in this data model is structured in the following The information in this data model is structured in the following
manner. All the information related to a conference is contained in manner. All the information related to a conference is contained in
a <conference-info> element. The <conference-info> element contains a <conference-info> element. The <conference-info> element contains
the following child elements: the following child elements:
o The <conference-description> element describes the conference as a o The <conference-description> element describes the conference as a
whole. It has, for instance, information about the URI of the whole. It has, for instance, information about the URI of the
skipping to change at page 9, line 22 skipping to change at page 9, line 44
whole. The <users> element contains a set of <user> child whole. The <users> element contains a set of <user> child
elements, each describing a single participant in the conference. elements, each describing a single participant in the conference.
o If a participant in the main conference joins a sidebar, a new o If a participant in the main conference joins a sidebar, a new
element is created in the conference referenced from the element is created in the conference referenced from the
<sidebars-by-ref> element or under one of the <sidebars-by-val> <sidebars-by-ref> element or under one of the <sidebars-by-val>
elements. elements.
Note that some of the elements described above such <conference- Note that some of the elements described above such <conference-
info>, <conference-description>, <sidebars-by-ref>, or <sidebars-by- info>, <conference-description>, <sidebars-by-ref>, or <sidebars-by-
val> are not defined in the data model but are defined in the data val> are not defined in the data model but are defined in the data
format of RFC 4575 [1]. We describe them here because they are part format of [RFC4575]. We describe them here because they are part of
of the basic structure of the data model. the basic structure of the data model.
4. Data Model Definition 4. Data Model Definition
The following non-normative diagram shows the structure of conference The following non-normative diagram shows the structure of conference
object documents. The operator "!" preceding an element indicates object documents. The operator "!" preceding an element indicates
that the element is mandatory in the data model. The operator "*" that the element is mandatory in the data model. The operator "*"
following an element indicates that the element is introduced and following an element indicates that the element is introduced and
defined in this document. That is, elements without a "*" have defined in this document. That is, elements without a "*" have
already been defined in RFC 4575 [1]. already been defined in [RFC4575].
!<conference-info> !<conference-info>
| |
|--!<conference-description> |--!<conference-description>
| |--<language>* | |--<language>*
| |--<display-text> | |--<display-text>
| |--<subject> | |--<subject>
| |--<free-text> | |--<free-text>
| |--<keywords> | |--<keywords>
| |--<allow-sidebars>* | |--<allow-sidebars>*
skipping to change at page 10, line 23 skipping to change at page 10, line 51
| |--<service-uris> | |--<service-uris>
| | |--<entry> | | |--<entry>
| | | |--<uri> | | | |--<uri>
| | | |--<display-text> | | | |--<display-text>
| | | |--<purpose> | | | |--<purpose>
| | ... | | ...
| |--<maximum-user-count> | |--<maximum-user-count>
| | ... | | ...
| |--<available-media> | |--<available-media>
| | |--!<entry> | | |--!<entry>
| | | |--<type>
| | | |--<display-text> | | | |--<display-text>
| | | |--<type>
| | | |--<status> | | | |--<status>
| | | |--<mixing-mode>* | | | |--<mixing-mode>*
| | | |--<codecs>* | | | |--<codecs>*
| | | | |--<entry>* | | | | |--<entry>*
| | | | |--<entry>* | | | | |--<entry>*
| | | | ... | | | | ...
| | | |--<controls>* | | | |--<controls>*
| | | | |--<mute>* | | | | |--<mute>*
| | | | |--<gain>* | | | | |--<gain>*
| | | | ... | | | | ...
| | |--<entry> | | |--<entry>
| | | |--<type>
| | | |--<display-text> | | | |--<display-text>
| | | |--<type>
| | | |--<status> | | | |--<status>
| | | |--<mixing-mode>* | | | |--<mixing-mode>*
| | | |--<codecs>* | | | |--<codecs>*
| | | | |--<entry>* | | | | |--<entry>*
| | | | |--<entry>* | | | | |--<entry>*
| | | | ... | | | | ...
| | | |--<controls>* | | | |--<controls>*
| | | | |--<pause-video>* | | | | |--<pause-video>*
| | | | |--<video-layout>* | | | | |--<video-layout>*
| | | | ... | | | | ...
skipping to change at page 11, line 36 skipping to change at page 12, line 15
| | | ... | | | ...
| | ... | | ...
| |
|--!<users> |--!<users>
| |--<join-handling>* | |--<join-handling>*
| |--<user-admission-policy>* | |--<user-admission-policy>*
| |--<allowed-users-list>* | |--<allowed-users-list>*
| | |--<target>* | | |--<target>*
| | | | | |
| | |--<persistent-list>* | | |--<persistent-list>*
| | | |--<target>* | | | |--<user>*
| | | | |-- <email>* | | | | |-- <email>*
| | | |
| |--<deny-users-list>* | |--<deny-users-list>*
| | | |
| |--<user> | |--<user>
| | |--<display-text> | | |--<display-text>
| | |--<associated-aors> | | |--<associated-aors>
| | |--<provide-anonymity>* | | |--<provide-anonymity>*
| | |--<roles> | | |--<roles>
| | | | | | | |
skipping to change at page 13, line 14 skipping to change at page 13, line 42
| ... ... | ... ...
Figure 4: Non-normative diagram Figure 4: Non-normative diagram
The following sections describe these elements in detail. The full The following sections describe these elements in detail. The full
Relax NG schema is provided Section 5. Relax NG schema is provided Section 5.
4.1. <conference-info> 4.1. <conference-info>
A conference object document begins with the root element tag A conference object document begins with the root element tag
<conference-info>, which is defined in RFC4575 [1]. The <conference- <conference-info>, which is defined in [RFC4575]. The <conference-
info> attributes are described in RFC4575 [1]. Notice that the info> attributes are described in [RFC4575]. Note that the
<conference-info> element does not have the attributes 'state' and <conference-info> element does not have the attributes 'state' and
'version' defined in RFC4575[1] for this element because this 'version' defined in [RFC4575] for this element because this
attribute only applies to notifications mechanism. RFC4575 [1] attribute only applies to notifications mechanism.
defines as well an 'entity' attribute that contains the conference
object identifier (XCON-URI) that identifies the conference being In addition, [RFC4575] defines an 'entity' attribute that contains
described in the document. the conference object identifier (XCON-URI) that identifies the
conference being described in the document.
The <conference-info> element contains the <conference-description>, The <conference-info> element contains the <conference-description>,
<host-info>, <conference-state>, <floor-information>, <users>, <host-info>, <conference-state>, <floor-information>, <users>,
<sidebars-by-ref>, and <sidebars-by-val> child elements. All these <sidebars-by-ref>, and <sidebars-by-val> child elements. All these
elements, except <floor-information>, are defined in [1]. A elements, except <floor-information>, are defined in [RFC4575]. A
conference document MUST at least include the <conference- conference document MUST at least include the <conference-
description> and <users> child elements. description> and <users> child elements.
4.2. <conference-description> 4.2. <conference-description>
The <conference-description> element, which is defined in RFC4575 The <conference-description> element, which is defined in [RFC4575],
[1], describes the conference as a whole. It should have an extra describes the conference as a whole. It should have an extra
attribute 'lang' to specify the language used in the contents of this attribute 'lang' to specify the language used in the contents of this
element. It is comprised of <language> <display-text>, <subject>, element. It is comprised of <language> <display-text>, <subject>,
<free-text>, <keywords>, <allow-sidebars>, <conference-time>, <conf- <free-text>, <keywords>, <allow-sidebars>, <conference-time>, <conf-
uris>, <service-uris>, <maximum-user-count>, and <available-media>. uris>, <service-uris>, <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. expected to be employed within a conference. This element is not
enforcing the language of the conference, only informs to the
participants about the desirable language that they should used 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 RFC 4575 The <display-text> element is described in section 5.3 of [RFC4575].
[1].
4.2.3. <subject> 4.2.3. <subject>
The <subject> element is described in section 5.3 of RFC 4575 [1]. 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 RFC 4575 [1]. 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 RFC 4575 [1]. 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 action. If set to
TRUE, the conference is allowed to create sidebar conferences. TRUE, the conference is allowed to create sidebar conferences.
4.2.7. <conference-time> 4.2.7. <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 and duration of a conference. The <conference-time>
element contains one or more <entry> elements each defining the time element contains one or more <entry> elements each defining the time
information specifying a single conference occurrence. information specifying a single conference occurrence.
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
RFC 2445 [3]. [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. The <mixing-start-offset> child element conference starts. The <mixing-start-offset> child element
expresses the offset as signed integers representing seconds expresses the offset as signed integers representing seconds
before/after the iCalendar DTSTART field [3]. If the <mixing- before/after the iCalendar DTSTART field [RFC2445]. If the
start-offset> element is not present, it indicates that the <mixing-start-offset> element is not present, it indicates that
conference media mixing starts immediately. The <mixing-start- the conference media mixing starts immediately. The <mixing-
offset> has the mandatory 'required-participant' attribute. This start-offset> has the mandatory 'required-participant' attribute.
attribute has one of 4 values: "none", "administrator", This attribute contains one of the following values: "none",
"moderator", and "participant". This attribute allows a "administrator", "moderator", "user", "observer", and
privileged user to define when media mixing starts based on the "participant". More values can be specified in the future. The
latter of the mixing start time, and the time the first 'required-participant' attribute allows a privileged user to
participant, administrator, or moderator arrives. If the value is define when media mixing starts based on the latter of the mixing
set to "none'", mixing starts according to the mixing start time. start time, and the time the first participant arrives. If the
value is set to "none'", mixing starts according to the mixing
start time.
o <mixing-end-offset>: The <mixing-end-offset> child element that o <mixing-end-offset>: The <mixing-end-offset> child element that
specifies the time a conference media mixing stops after the specifies the time a conference media mixing stops after the
conference stops. The <mixing-end-offset> child element expresses conference stops. The <mixing-end-offset> child element expresses
the offset as signed integers representing seconds before/after the offset as signed integers representing seconds before/after
the iCalendar DTEND field [3]. If the <mixing-end-offset> element the iCalendar DTEND field [RFC2445]. If the <mixing-end-offset>
is not present, it indicates that the conference occurrence is not element is not present, it indicates that the conference
bounded. The <mixing-end-offset> elements both have the mandatory occurrence is not bounded. The <mixing-end-offset> elements both
'required-participant' attribute. This attribute has one of 4 have the mandatory 'required-participant' attribute. This
values: "none", "administrator", "moderator", and "participant". attribute contains one of the following values: "none",
This attribute allows a privileged user to define when media "administrator", "moderator", "observer", "user", and
mixing ends based on the earlier of the <mixing-end-offset>, and "participant". More values can be specified in the future. The
the time the last participant, or moderator leaves. If the value 'required-participant' attribute allows a privileged user to
is set to "none", mixing stops according to the <mixing-end- define when media mixing ends based on the earlier of the <mixing-
end-offset>, and the time the last participant leaves. If the
value is set to "none", mixing stops according to the <mixing-end-
offset>. If the conference policy was modified so that last offset>. If the conference policy was modified so that last
privileged user is now a normal conference participant, and the privileged user is now a normal conference participant, and the
conference requires a privileged user to continue; that conference conference requires a privileged user to continue; that conference
MUST terminate. MUST terminate.
o <can-join-after-offset>: An administrator can indicate the time o <can-join-after-offset>: An administrator can indicate the time
when users can join a conference by populating the <can-join- when users can join a conference by populating the <can-join-
after-offset> element. after-offset> element.
o <must-join-before-offset>: An administrator can define the time o <must-join-before-offset>: An administrator can define the time
after which new users are not allowed to join the conference after which new users are not allowed to join the conference
anymore. This is done by populating the <must-join-before-offset> anymore. This is done by populating the <must-join-before-offset>
skipping to change at page 16, line 5 skipping to change at page 16, line 40
end-offset> refers to the possibility to extend the conference. end-offset> refers to the possibility to extend the conference.
It has a boolean value. It has a boolean value.
4.2.8. <conf-uris> 4.2.8. <conf-uris>
The <conf-uris> contains the identifiers to be used in order to The <conf-uris> contains the identifiers to be used in order to
access the conference by different signaling means. This document access the conference by different signaling means. This document
describes a new element, <conference-password>. This element describes a new element, <conference-password>. This element
contains the password of the conference, for instance, PSTN contains the password of the conference, for instance, PSTN
conference will store the 'PIN code' in this element. All the other conference will store the 'PIN code' in this element. All the other
<conf-uris> child element are described in section 5.3.1 of RFC <conf-uris> child element are described in section 5.3.1 of
4575[1]. Future extensions to this schema may define new values and [RFC4575]. Future extensions to this schema may define new values
register them with IANA. and register them with IANA.
4.2.9. <service-uris> 4.2.9. <service-uris>
The <service-uris> describes auxiliary services available for the The <service-uris> describes auxiliary services available for the
conference. The <service-uris> element is described in section 5.3.2 conference. The <service-uris> element is described in section 5.3.2
of RFC4575[1]. Future extensions to this schema may define new of [RFC4575]. Future extensions to this schema may define new values
values and register them with IANA. and register them with IANA.
4.2.10. <maximum-user-count> 4.2.10. <maximum-user-count>
The <maximum-user-count> contains the overall number of users allowed The <maximum-user-count> contains the overall number of users allowed
to join the conference. Note that this value is set by an to join the conference. Note that this value is set by an
administrator and can reflect any local policies such as network administrator and can reflect any local policies such as network
consumption, CPU processing power, and licensing rules. consumption, CPU processing power, and licensing rules.
4.2.11. <available-media> 4.2.11. <available-media>
The <available-media> has the 'label' attribute that is the media The <available-media> has the 'label' attribute that is the media
stream identifier assigned by the conferencing server. The attribute stream identifier assigned by the conferencing server. The attribute
'label' is described in RFC 4575 [1], section 5.3.4. The <available- 'label' is described in [RFC4575], section 5.3.4. The <available-
media> element contains a sequence of <entry> child elements. Each media> element contains a sequence of <entry> child elements. 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 RFC 4575 [1]. 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 RFC o The <display-text> element is described in section 5.3.4 of
4575 [1]. [RFC4575].
o The <status> element is described in section 5.3.4 of RFC 4575 o The <status> element is described in section 5.3.4 of [RFC4575].
[1].
o The child element <mixing-mode> describes a default policy by o The child element <mixing-mode> describes a default policy by
which the mixer will build the outgoing stream from the incoming which the mixer will build the outgoing stream from the incoming
streams. Notice that this policy is different than the policy streams. Note that this policy is different than the policy
describing the floors for each media. The <mixing-mode> child describing the floors for each media. The <mixing-mode> child
element MUST contain one and only one of the "Moderator- 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.
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 <entry> elements. A controlled"). The <codecs> element contains <codec> elements. A
<entry> element can have the attribute 'name' and 'policy'. The <codec> element can have the attribute 'name' and 'policy'. The
'name' attribute identifies a codec. The list of possible codecs 'name' attribute identifies a codec. The list of possible codecs
accepted as a 'name' attribute is defined by the IANA registry for accepted as a 'name' attribute is defined by the IANA registry for
RTP Payload Types. The possible values of the attribute 'name' RTP Payload Types. The possible values of the attribute 'name'
are the values of the 'subtype' column of the RTP Payload Format are the values of the 'subtype' column of the RTP Payload Format
media types per RFC4855[10] defined in IANA [11]. The 'policy' media types per [RFC4855] defined in IANA [IANA]. The 'policy'
attribute contains the policy for that codec (allowed, or attribute contains the policy for that codec (allowed, or
disallowed). disallowed).
o The <controls> element contains the basic audio and video global o The <controls> element contains the basic audio and video global
control elements for a conference. It is expected that for the control elements for a conference. It is expected that for the
majority of the basic conferences, these controls are sufficient. majority of the basic conferences, these controls are sufficient.
If the conference server wants to support more advanced controls, If the conference server wants to support more advanced controls,
then it is recommended that an extension to the data model be then it is recommended that an extension to the data model be
used. In the <controls> element the schema is extensible, hence used. In the <controls> element the schema is extensible, hence
new control types can be added in the future. So moderator new control types can be added in the future. So moderator
controls that affect all media output would go under the controls that affect all media output would go under the
skipping to change at page 18, line 41 skipping to change at page 19, line 28
aspect ratio of the streams is preserved. aspect ratio of the streams is preserved.
+ automatic: This option allows the focus to add panels as + automatic: This option allows the focus to add panels as
streams are added. streams are added.
4.3. <host-info> 4.3. <host-info>
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[1], section 5.4. Future extensions to the <host-info> [RFC4575], section 5.4. Future extensions to the <host-info> element
element may define new values. may define new values.
4.4. <conference-state> 4.4. <conference-state>
The <conference-state> is introduced in RFC4575 [1]. The The <conference-state> is introduced in RFC4575 [RFC4575]. The
<conference-state> element contains the <allow-conference-event- <conference-state> element contains the <allow-conference-event-
subscription>, <user-count>, <active>, and <locked> child elements. subscription>, <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 RFC4575 'SIP Event
Package for Conference State' [1]. If set to FALSE, the subscription Package for Conference State' [RFC4575]. If set to FALSE, the
to conference state events would be rejected. If this element is subscription to conference state events would be rejected. If this
undefined it has a default value of TRUE, causing the subscription to element is undefined it has a default value of TRUE, causing the
conference state events to be accepted. subscription to conference state events to be accepted.
4.4.2. <user-count> 4.4.2. <user-count>
The <user-count> child element is explained in RFC 4575 [1], 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 RFC 4575 [1], section The <active> child element is explained in [RFC4575], section 5.5.2.
5.5.2.
4.4.4. <locked> 4.4.4. <locked>
The <locked> child element is explained in RFC 4575 [1], section The <locked> child element is explained in [RFC4575], section 5.5.3.
5.5.3.
4.5. <floor-information> 4.5. <floor-information>
The <floor-information> element contains the <conference-ID>, <allow- The <floor-information> element contains the <conference-ID>, <allow-
floor-events>, <floor-request-handling>, and <conference-floor- floor-events>, <floor-request-handling>, and <conference-floor-
policy> child elements. Other elements from different namespaces MAY policy> child elements. Other elements from different namespaces MAY
be present for the purposes of extensibility. The absence of this be present for the purposes of extensibility. The absence of this
element from an XML document indicates that the conference does not element from an XML document indicates that the conference does not
have a floor. have a floor.
4.5.1. <conference-ID> 4.5.1. <conference-ID>
The <conference-ID> is a 32-bit BFCP conference identifier defined in The <conference-ID> is a 32-bit BFCP conference identifier defined in
RFC4582 [5] section 5.1. that identifies the BFCP conference the [RFC4582] section 5.1. that identifies the BFCP conference the
message belongs to. This identifier represents a conference instance message belongs to. This identifier represents a conference instance
within floor control. When created within the conferencing system, within floor control. When created within the conferencing system,
the 'conference-ID' has a 1:1 mapping to the unique conference object the 'conference-ID' has a 1:1 mapping to the unique conference object
Identifier (XCON-URI). Identifier (XCON-URI).
4.5.2. <allow-floor-events> 4.5.2. <allow-floor-events>
The <allow-floor-events> element represents a boolean action. If set The <allow-floor-events> element represents a boolean action. If set
to TRUE, the focus is instructed to accept the subscription to floor to TRUE, the focus is instructed to accept the subscription to floor
control events. If set to FALSE, the focus is instructed to reject control events. If set to FALSE, the focus is instructed to reject
the subscription. If this element is undefined, it has a default the subscription. If this element is undefined, it has a default
value of FALSE, causing the subscription to floor control events to value of FALSE, causing the subscription to floor control events to
be rejected. be rejected.
There are two methods which a conference participant subscribes There are two methods which a conference participant subscribes
himself to a floor control event. One method is using an offer/ himself to a floor control event. One method is using an offer/
answer exchange mechanism (RFC3264 [12]) using SIP INVITE and BFCP answer exchange mechanism ([RFC3264]) using SIP INVITE and BFCP
parameters in the SDP (RFC4583 [13]). The other method is a general parameters in the SDP ([RFC4583]). The other method is a general
authorization mechanism described in section 9 of RFC4582 [5] and in authorization mechanism described in section 9 of [RFC4582] and in
RFC5018 [14]. Future documentation may define additional connection [RFC5018]. Future documentation may define additional connection
mechanisms. mechanisms.
4.5.3. <floor-request-handling> 4.5.3. <floor-request-handling>
The <floor-request-handling> element defines the actions used by the The <floor-request-handling> element defines the actions used by the
conference focus to control floor requests. This element defines the conference focus to control floor requests. This element defines the
action that the focus is to take when processing a particular request action that the focus is to take when processing a particular request
to a floor within a conference. This element defines values of: to a floor within a conference. This element defines values of:
o "block": This action instructs the focus to deny the floor o "block": This action instructs the focus to deny the floor
skipping to change at page 20, line 39 skipping to change at page 21, line 22
this document. this document.
Note that this section discusses floor control information, Note that this section discusses floor control information,
therefore, the value "block" in a <floor-request-handling> element is therefore, the value "block" in a <floor-request-handling> element is
not related with the "block" value in the <join-handling> element not related with the "block" value in the <join-handling> element
(see Section 4.6). (see Section 4.6).
4.5.4. <conference-floor-policy> 4.5.4. <conference-floor-policy>
The <conference-floor-policy> element has one or more <floor> child The <conference-floor-policy> element has one or more <floor> child
elements. Each <floor> element has the following child elements: elements. Every <floor> child elements has an attribute 'id' which
uniquely identifies a floor or floors within a conference. The 'id'
attribute corresponds to the floor-id identifier defined in [RFC4582]
section 5.2.2. Each <floor> element has the following child
elements:
o <media-label>: Every floor is identified for one or more mandatory o <media-label>: Every floor is identified for one or more mandatory
<media-label> element. If the <available-media> information is <media-label> element. If the <available-media> information is
included in the conference document, the value of this element included in the conference document, the value of this element
MUST be equal to the 'label' value of the corresponding media MUST be equal to the 'label' value of the corresponding media
stream <entry> in the <available-media> container. The number of stream <entry> in the <available-media> container. The number of
those elements indicates how many floors the conference can have. those elements indicates how many floors the conference can have.
A floor can be used for one or more media types; A floor can be used for one or more media types;
o <algorithm>: A floor can be controlled using many algorithms; the o <algorithm>: A floor can be controlled using many algorithms; the
mandatory <algorithm> element MUST be set to any of the mandatory <algorithm> element MUST be set to any of the
"moderator-controlled", "FCFS" or "random" values indicating the "moderator-controlled", "FCFS" or "random" values indicating the
algorithm. The "Moderator-controlled" value indicates that the algorithm. The "Moderator-controlled" value indicates that the
moderator of the conference controls the floor. The "FCFS" value moderator of the conference controls the floor. The "FCFS" value
states for 'first-come-first-served' floor control. states for 'first-come-first-served' floor control.
o <max-floor-users>: The <max-floor-users> child element in the o <max-floor-users>: The <max-floor-users> child element in the
<floor> element is optional and, if present, dictates the maximum <floor> element is optional and, if present, dictates the maximum
number of users who can have the floor at one time. number of users who can have the floor at one time.
o <moderator-id>: The optional <moderator-id> indicates the 'User o <moderator-id>: The optional <moderator-id> indicates the 'User
ID' of the moderator. The 'User ID' is a BFCP identifier defined ID' of the moderator. The 'User ID' is a BFCP identifier defined
in RFC4582 [5] section 5.1. It MUST be set if the element in [RFC4582] section 5.1. It MUST be set if the element
<algorithm> is set to "Moderator-controlled" value. Note that <algorithm> is set to "Moderator-controlled" value. Note that
RFC4582 [5] refers to the moderator role as a 'floor chair'. [RFC4582] refers to the moderator role as a 'floor chair'.
4.6. <users> 4.6. <users>
The <users> element is described in RFC4575 [1] and contains the The <users> element is described in [RFC4575] and contains the <join-
<join-handling>, <user-admission-policy>, <allowed-users-list> and handling>, <user-admission-policy>, <allowed-users-list> and <deny-
<deny-users-list> defined in this document and <user> child elements users-list> defined in this document and <user> child elements
defined in RFC4575[1]. Notice that the <users> element does not have defined in [RFC4575]. Note that the <users> element does not have
the attribute 'state' defined in RFC4575[1] for this element because the attribute 'state' defined in [RFC4575] for this element because
this attribute only applies to notifications mechanism. The this attribute only applies to notifications mechanism. The
following sections describe these elements in more detail. Other following sections describe these elements in more detail. Other
child elements and attributes can be used to extend <users> in the child elements and attributes can be used to extend <users> in the
future. 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
skipping to change at page 23, line 19 skipping to change at page 24, line 5
and therefore a separation between the two is needed. and therefore a separation between the two is needed.
The <allowed-users-list> element has a <persistent-list> child The <allowed-users-list> element has a <persistent-list> child
element as well. Some chatroom systems allow -- and some require -- element as well. Some chatroom systems allow -- and some require --
registration of detailed information about a user before they are registration of detailed information about a user before they are
allowed to join a chatroom. The <persistent-list> child element allowed to join a chatroom. The <persistent-list> child element
stores persistent information about users who are not actively part stores persistent information about users who are not actively part
of an ongoing chatroom session. The <persistent-list> element stores of an ongoing chatroom session. The <persistent-list> element stores
the following information: the following information:
o target: The <target> element stores the name, nickname and email o user: The <user> element stores the name, nickname, the conference
address of a user. It has two attrbutes: 'name' and 'nickname' user identifier (XCON_USERID) and email address of a user. It has
and an <email> element. three attributes: 'name', 'nickname' and 'id' and an <email>
element. Future extensions to this schema may define new elements
for the <user> element.
Future extensions to this schema may define new elements for the Future extensions to this schema may define new elements for the
<target> element. <target> element.
4.6.4. <deny-users-list> 4.6.4. <deny-users-list>
The <deny-users-list> child element contains a list of user URIs, The <deny-users-list> child element contains a list of user URIs,
roles, or domains (*@example.com) that the focus uses to determine roles, or domains (*@example.com) that the focus uses to determine
who has been 'banned' from the conference. Such banned users are who has been 'banned' from the conference. Such banned users are
prevented from re-joining the chatroom until they have been un- prevented from re-joining the chatroom until they have been un-
banned. 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 RFC5475[1] and describes a single The element <user> is described in RFC4575[RFC4575] and describes a
participant in the conference. The <user> element has an attribute single participant in the conference. The <user> element has an
'entity'. Notice that the <user> element does not have the attribute attribute 'entity'. Note that the <user> element does not have the
'state' defined in RFC4575[1] for this element because this attribute attribute 'state' defined in [RFC4575] for this element because this
only applies to notifications mechanism. attribute 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). The URI format of this identifier is as follow: (XCON_USERID). The URI format of this identifier is as follow:
XCON_USERID = "xcon_userid" ":" conf-object-id XCON_USERID = "xcon_userid" ":" conf-object-id
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
[unreserved is defined in RFC3986] [unreserved is defined in RFC3986]
skipping to change at page 24, line 23 skipping to change at page 25, line 15
+--------------+ +--------------+
| Conference | | Conference |
| User | | User |
| Identifier | | Identifier |
+--------------+ +--------------+
| John | | John |
+------+-------+ +------+-------+
| |
| |
| |
+---------------------+---------------------+ +----------------------+-------------------------+
| | | | | |
+-------+--------+ +-------+-------+ +--------+-------+ +-------+--------+ +-----------+-----------+ +-----------+-----------+
| BFCP User ID | | SIP User ID | | H323 User ID | | BFCP User ID | | SIP User URI | | H323 User URI |
+----------------+ +---------------+ +----------------+ +----------------+ +-----------------------+ +-----------------------+
| HK37ihdaj | | 123674 | | 928373 | | 543 | |sip:851221@example.com | |h323:taeduk@example.com|
+----------------+ +---------------+ +----------------+ +----------------+ +-----------------------+ +-----------------------+
Figure 6: Conference Object Mapping Figure 6: Conference Object Mapping
The element <user> element contains the <display-text>, <associated- The element <user> element contains the <display-text>, <associated-
aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>, aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>,
<allow-refer-users-dynamically>, <allow-invite-users-dynamically>, <allow-refer-users-dynamically>, <allow-invite-users-dynamically>,
<allow-remove-users-dynamically>, and <endpoint>. The following <allow-remove-users-dynamically>, and <endpoint>. The following
sections describe these elements in more detail. sections describe these elements in more detail.
4.6.5.1. <display-text> 4.6.5.1. <display-text>
The <display-text> child element is explained in RFC 4575 [1], The <display-text> child element is explained in [RFC4575], section
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 RFC 4575 [1], 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 provides anonymity to the user. In
this case, the focus provides to the rest of the participants an this case, the focus provides to the rest of the participants an
anonymous identity for that user, for example anonymousX. This anonymous identity for that user, for example anonymousX. This
element only affects the way the user information is provided to the element only affects the way the user information is provided to the
other participants. The real information about the user is still other participants. The real information about the user is still
stored in the data model. This can be achieved by using the stored in the data model. This can be achieved by using the
<provide-anonymity> element. This element has two values: 'private' <provide-anonymity> element. This element has two values: 'private'
and 'semi-private'. The 'private' value specifies that this user is and 'semi-private'. The 'private' value specifies that this user is
completely anonymous in the conference. 'semi-private' value completely anonymous in the conference. 'semi-private' value
specifies that this user is anonymous to all users with equal or specifies that this user is anonymous to all users with equal or
lesser permissions in the conference. lesser permissions in the conference.
4.6.5.4. <roles> 4.6.5.4. <roles>
The <roles> child element is explained in RFC 4575 [1], section A role provides the context for the set of conference operations that
5.6.3. a participant can perform. This element can contain one of the
following values: "administrator", "moderator", "user",
"participant", "observer", and "none". The roles semantic definition
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.
4.6.5.5. <languages> 4.6.5.5. <languages>
The <languages> child element is explained in RFC 4575 [1], section The <languages> child element is explained in [RFC4575], section
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 RFC 4575 [1], The <cascaded-focus> child element is explained in [RFC4575], section
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 action. 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
skipping to change at page 26, line 22 skipping to change at page 27, line 18
action. If set to TRUE, a participant is allowed to instruct the action. If set to TRUE, a participant is allowed to instruct the
focus to remove a user from the conference without modifying the focus to remove a user from the conference without modifying the
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 to the focus which results in the focus sending an BYE request to the focus which results in the focus sending an BYE
request to the user the referrer wishes to leave the conference). If request to the user the referrer wishes to leave the conference). If
set to FALSE, the refer request is rejected. If this element is 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 defined in RFC4575[1]. It can The <endpoint> child element is defined in [RFC4575]. It can provide
provide the desired level of detail about the user's devices and the desired level of detail about the user's devices and their
their signaling sessions taking part in the conference and has the signaling sessions taking part in the conference. The <endpoint>
following child elements defined in RFC4575 [1]: <display-text>, element in this document does not defined the 'state' attribute
<referred>, <status>, <joining-method>, <joining-info>, defined in [RFC4575] for the same element since the 'state' attribute
<disconnection-method>, <disconnection-info>, <media>, and <call- only applies to notification mechanisms.
info>. Notice that the <endpoint> element does not have the
attribute 'state' defined in RFC4575[1] for this element because this
attribute only applies to notifications mechanism.
Besides the <endpoint>/<media> child elements defined in RFC 4575[1], The <endpoint> element has the following child elements: <display-
the <endpoint>/<media> element has two other child elements: <to- text>, <referred>, <status>, <joining-method>, <joining-info>,
mixer>, and <from-mixer> described in the following list: <disconnection-method>, <disconnection-info>, <media>, <floor>,and
<call-info>. All the <endpoint> child elements are defined in
[RFC4575] with the exception of the <floor> element.
The <floor> element describes a floor that joins this 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 or floors 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
other child elements defined in this document, the <to-mixer>, and
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. More values can be defined
in the future. Each of these elements have the <floor> and in the future. The <to-mixer> and <from-mixer> elements have the
<controls> child elements: <controls> child element:
* The <floor> element describes a floor that joins this
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 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.
* 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.
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 [1], 5.9.1. Notice elements. This element is described in [RFC4575], 5.9.1. Note that
that the <sidebars-by-ref> element does not have the attribute the <sidebars-by-ref> element does not have the attribute 'state'
'state' defined in RFC4575[1] for this element because this attribute defined in [RFC4575] for this element because this attribute only
only applies to notifications mechanism. applies to notifications mechanism.
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 [1], 5.9.2. Notice that the element is described in [RFC4575], 5.9.2. Note that the <sidebars-
<sidebars-by-val> element does not have the attribute 'state' defined by-val> element does not have the attribute 'state' defined in
in RFC4575[1] for this element because this attribute only applies to [RFC4575] for this element because this attribute only applies to
notifications mechanism. notifications mechanism.
5. RELAX NG Schema 5. RELAX NG Schema
In accordance with the Centralized Conferencing Framework document In accordance with the Centralized Conferencing Framework document
[4], the Conference Object is a logical representation of a [I-D.ietf-xcon-framework], the Conference Object is a logical
conference instance. The conference information schema contains core representation of a conference instance. The conference information
information that is utilized in any conference. It also contains the schema contains core information that is utilized in any conference.
variable information part of the Conference Object. It also contains the variable information part of the Conference
Object.
This specification defines some document fragments in RELAX NG format This specification defines some document fragments in RELAX NG format
[15]. [RELAX].
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0" namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
namespace local = "" namespace local = ""
default namespace ns1 = "urn:ietf:params:xml:ns:xcon-conference-info" default namespace ns1 = "urn:ietf:params:xml:ns:xcon-conference-info"
namespace ns2 = "urn:ietf:params:xml:ns:conference-info" namespace ns2 = "urn:ietf:params:xml:ns:conference-info"
start = element conference-info { conference-type } start = element conference-info { conference-type }
# CONFERENCE TYPE # CONFERENCE TYPE
conference-type = conference-type =
attribute entity { text }, attribute entity { text },
skipping to change at page 28, line 44 skipping to change at page 29, line 46
element available-media { conference-media-type }?, element available-media { conference-media-type }?,
anyElement* anyElement*
} }
# CONFERENCE TIME # CONFERENCE TIME
conferencetime-type = conferencetime-type =
anyAttribute, anyAttribute,
element entry { element entry {
element base { text }?, element base { text }?,
element mixing-start-offset { element mixing-start-offset {
xsd:dateTime { pattern = ".+T.+Z.*" }, xsd:dateTime { pattern = ".+T.+Z.*" },
attribute required-participant { text }, attribute required-participant { single-role-type },
anyAttribute anyAttribute
}?, }?,
element mixing-end-offset { element mixing-end-offset {
xsd:dateTime { pattern = ".+T.+Z.*" }, xsd:dateTime { pattern = ".+T.+Z.*" },
attribute required-participant { text }, attribute required-participant { single-role-type },
anyAttribute anyAttribute
}?, }?,
element can-join-after-offset { element can-join-after-offset {
xsd:dateTime { pattern = ".+T.+Z.*" } xsd:dateTime { pattern = ".+T.+Z.*" }
}?, }?,
element must-join-before-offset { element must-join-before-offset {
xsd:dateTime { pattern = ".+T.+Z.*" } xsd:dateTime { pattern = ".+T.+Z.*" }
}?, }?,
element notify-end-of-conference { xsd:int }?, element notify-end-of-conference { xsd:int }?,
element allowed-extend-mixing-end-offset { xsd:boolean }?, element allowed-extend-mixing-end-offset { xsd:boolean }?,
skipping to change at page 29, line 29 skipping to change at page 30, line 31
anyElement* anyElement*
# CONFERENCE MEDIUM TYPE # CONFERENCE MEDIUM TYPE
conference-medium-type = conference-medium-type =
attribute label { text }, attribute label { text },
anyAttribute, anyAttribute,
element display-text { text }?, element display-text { text }?,
element type { text }?, element type { text }?,
element status { media-status-type }?, element status { media-status-type }?,
element mixing-mode { mix-mode-type }?, element mixing-mode { mix-mode-type }?,
element codecs { codecs-type }?, element codecs { codecs-type }?,
element controls { controls-type }?, element controls { control-type }?,
anyElement*
# CONTROLS TYPE
controls-type =
anyAttribute,
element control { control-type }*,
anyElement* anyElement*
# MIX MODE TYPE # MIX MODE TYPE
mix-mode-type = mix-mode-type =
xsd:string "moderator-controlled" xsd:string "moderator-controlled"
| xsd:string "FCFS" | xsd:string "FCFS"
| xsd:string "automatic" | xsd:string "automatic"
| text
# CODECS TYPE # CODECS TYPE
codecs-type = codecs-type =
attribute decision { decision-type }, attribute decision { decision-type },
anyAttribute, anyAttribute,
element codec { codec-type }*, element codec { codec-type }*,
anyElement* anyElement*
# CODEC TYPE # CODEC TYPE
codec-type = codec-type =
attribute name { text }, attribute name { text },
attribute policy { policy-type }, attribute policy { policy-type },
anyAttribute anyAttribute
# DECISION TYPE # DECISION TYPE
decision-type = decision-type =
xsd:string "automatic" | xsd:string "moderator-controlled" xsd:string "automatic" | xsd:string "moderator-controlled" | text
# POLICY TYPE # POLICY TYPE
policy-type = xsd:string "allowed" | xsd:string "disallowed" policy-type = xsd:string "allowed" | xsd:string "disallowed" | text
# CONTROL TYPE # CONTROL TYPE
control-type = control-type =
anyAttribute, anyAttribute,
(element mute { xsd:boolean } (element mute { xsd:boolean },
| element pause-video { xsd:boolean } element pause-video { xsd:boolean },
| element gain { element gain {
xsd:int { minInclusive = "-127" maxInclusive = "127" } xsd:int { minInclusive = "-127" maxInclusive = "127" }
} },
| element video-layout { element video-layout {
xsd:string "single-view" xsd:string "single-view"
| xsd:string "dual-view" | xsd:string "dual-view"
| xsd:string "dual-view-crop" | xsd:string "dual-view-crop"
| xsd:string "dual-view-2x1" | xsd:string "dual-view-2x1"
| xsd:string "dual-view-2x1-crop" | xsd:string "dual-view-2x1-crop"
| xsd:string "quad-view" | xsd:string "quad-view"
| xsd:string "multiple-3x3" | xsd:string "multiple-3x3"
| xsd:string "multiple-4x4" | xsd:string "multiple-4x4"
| xsd:string "multiple-5x1" | xsd:string "multiple-5x1"
| xsd:string "automatic" | xsd:string "automatic"
} | text
| anyElement*) },
anyElement*)*
# CONFERENCE STATE TYPE # CONFERENCE STATE TYPE
conference-state-type = conference-state-type =
anyAttribute, anyAttribute,
element allow-conference-event-subscription { xsd:boolean }?, element allow-conference-event-subscription { xsd:boolean }?,
element user-count { xsd:unsignedInt }?, element user-count { xsd:unsignedInt }?,
element active { xsd:boolean }?, element active { xsd:boolean }?,
element locked { xsd:boolean }?, element locked { xsd:boolean }?,
anyElement* anyElement*
# FLOOR INFORMATION TYPE # FLOOR INFORMATION TYPE
floor-information-type = floor-information-type =
anyAttribute, anyAttribute,
(element conference-ID { xsd:unsignedInt }, (element conference-ID { xsd:unsignedInt },
element allow-floor-events { xsd:boolean }, element allow-floor-events { xsd:boolean },
element floor-request-handling { floor-request-type }, element floor-request-handling { floor-request-type },
element conference-floor-policy { Conference-floor-policy }, element conference-floor-policy { Conference-floor-policy },
anyElement*)* anyElement*)*
# FLOOR REQUEST TYPE # FLOOR REQUEST TYPE
floor-request-type = xsd:string "block" | xsd:string "confirm" floor-request-type =xsd:string "block" | xsd:string "confirm" | text
# CONFERENCE FLOOR POLICY # CONFERENCE FLOOR POLICY
Conference-floor-policy = Conference-floor-policy =
anyAttribute, anyAttribute,
element floor { element floor {
attribute id { text },
anyAttribute, anyAttribute,
element media-label { xsd:nonNegativeInteger }+, element media-label { xsd:nonNegativeInteger }+,
(element algorithm { (element algorithm {
xsd:string "moderator-controlled" xsd:string "moderator-controlled"
| xsd:string "FCFS" | xsd:string "FCFS"
| xsd:string "random" | xsd:string "random"
| text
}, },
element max-floor-users { xsd:nonNegativeInteger }, element max-floor-users { xsd:nonNegativeInteger },
element moderator-id { text }, element moderator-id { text },
anyElement*)* anyElement*)*
}+ }+
# USERS TYPE # USERS TYPE
users-type = users-type =
anyAttribute, anyAttribute,
element join-handling { join-handling-type }?, element join-handling { join-handling-type }?,
element user-admission-policy { user-admission-policy-type }?, element user-admission-policy { user-admission-policy-type }?,
element allowed-users-list { UserList }?, element allowed-users-list { UserList }?,
element denied-users-list { deny-user-list }?, element deny-users-list { deny-user-list }?,
element user { user-type }*, element user { user-type }*,
anyElement* anyElement*
# USERS ADMISSION POLICY # USERS ADMISSION POLICY
user-admission-policy-type = user-admission-policy-type =
xsd:string "closedAuthenticated" xsd:string "closedAuthenticated"
| xsd:string "openAuthenticated" | xsd:string "openAuthenticated"
| xsd:string "anonymous" | xsd:string "anonymous"
| text
# JOIN HANDLING TYPE # JOIN HANDLING TYPE
join-handling-type = join-handling-type =
xsd:string "block" xsd:string "block"
| xsd:string "confirm" | xsd:string "confirm"
| xsd:string "allow" | xsd:string "allow"
| xsd:string "authenticate" | xsd:string "authenticate"
| xsd:string "directed-operator" | xsd:string "directed-operator"
| text
# DENYUSERLIST # DENYUSERLIST
deny-user-list = deny-user-list =
anyAttribute, anyAttribute,
element target { element target {
attribute uri { xsd:anyURI }, attribute uri { xsd:anyURI },
anyAttribute anyAttribute
}*, }*,
anyElement* anyElement*
# USERLIST # USERLIST
UserList = UserList =
anyAttribute, anyAttribute,
element target { target-type }*, element target { target-type }*,
anyElement*, anyElement*,
element persistent-list { element persistent-list {
element user { element user {
attribute name { text }, attribute name { text },
attribute nickname { text }, attribute nickname { text },
element e-mail { text } attribute id { text },
anyAttribute,
element e-mail { text }*
}*, }*,
anyElement anyElement
}? }?
# TARGET TYPE # TARGET TYPE
target-type = target-type =
attribute uri { xsd:anyURI }, attribute uri { xsd:anyURI },
attribute method { method-type }, attribute method { method-type },
anyAttribute anyAttribute
# METHOD TYPE # METHOD TYPE
method-type = method-type =
xsd:string "dial-in" | xsd:string "dial-out" | xsd:string "refer" xsd:string "dial-in"
| xsd:string "dial-out"
| xsd:string "refer"
| text
# USER TYPE # USER TYPE
user-type = user-type =
attribute entity { xsd:anyURI }, attribute entity { xsd:anyURI },
anyAttribute, anyAttribute,
element display-text { text }?, element display-text { text }?,
element associated-aors { conference-info-urn* }?, element associated-aors { conference-info-urn* }?,
element provide-anonymity { "private" | "semi-private" }?, element provide-anonymity { "private" | "semi-private" | text }?,
element roles { text }?, element roles { single-role-type }?,
element languages { element languages {
list { xsd:language } list { xsd:language }
}?, }?,
element cascaded-focus { xsd:anyURI }?, element cascaded-focus { xsd:anyURI }?,
element allow-refer-users-dynamically { xsd:boolean }?, element allow-refer-users-dynamically { xsd:boolean }?,
element allow-invite-users-dynamically { xsd:boolean }?, element allow-invite-users-dynamically { xsd:boolean }?,
element allow-remove-users-dynamically { xsd:boolean }?, element allow-remove-users-dynamically { xsd:boolean }?,
element endpoint { endpoint-type }*, element endpoint { endpoint-type }*,
anyElement* anyElement*
# ENDPOINT TYPE # ENDPOINT TYPE
skipping to change at page 32, line 46 skipping to change at page 34, line 6
attribute entity { text }, attribute entity { text },
anyAttribute, anyAttribute,
element display-text { text }?, element display-text { text }?,
element referred { conference-info-urn* }?, element referred { conference-info-urn* }?,
element status { endpoint-status-type }?, element status { endpoint-status-type }?,
element joining-method { joining-type }?, element joining-method { joining-type }?,
element joining-info { conference-info-urn* }?, element joining-info { conference-info-urn* }?,
element disconnection-method { disconnection-type }?, element disconnection-method { disconnection-type }?,
element disconnection-info { conference-info-urn* }?, element disconnection-info { conference-info-urn* }?,
element media { media-type }*, element media { media-type }*,
element floor {
attribute id { text },
anyAttribute,
xsd:boolean
}*,
element call-info { conference-info-urn* }?, element call-info { conference-info-urn* }?,
anyElement* anyElement*
# MEDIA TYPE # MEDIA TYPE
media-type = media-type =
attribute id { xsd:int }, attribute id { xsd:int },
anyAttribute, anyAttribute,
element display-text { text }?, element display-text { text }?,
element type { text }?, element type { text }?,
element label { text }?, element label { text }?,
element src-id { text }?, element src-id { text }?,
element status { media-status-type }?, element status { media-status-type }?,
element to-mixer { mixer-type }?, element to-mixer { mixer-type }?,
element from-mixer { mixer-type }?, element from-mixer { mixer-type }?,
anyElement* anyElement*
# MIXER TYPE # MIXER TYPE
mixer-type = mixer-type =
anyAttribute, anyAttribute,
(element floor { xsd:boolean }, element controls { control-type }?,
element controls { controls-type })?,
anyElement* anyElement*
# SIDEBARS-BY-REF TYPE # SIDEBARS-BY-REF TYPE
sidebars-by-ref-type = sidebars-by-ref-type =
anyAttribute, anyAttribute,
element entry { conference-info-urn* }*, element entry { conference-info-urn* }*,
anyElement* anyElement*
# SIDEBARS-BY-VAL TYPE # SIDEBARS-BY-VAL TYPE
sidebars-by-val-type = sidebars-by-val-type =
anyAttribute, anyAttribute,
element entry { conference-type }*, element entry { conference-type }*,
anyElement* anyElement*
# SINGLE ROLE TYPE
single-role-type =
xsd:string "administrator"
| xsd:string "moderator"
| xsd:string "user"
| xsd:string "participant"
| xsd:string "observer"
| xsd:string "none"
| text
# ********************************* # *********************************
# EXTENSIBILITY OF THE SCHEMA # EXTENSIBILITY OF THE SCHEMA
# ********************************* # *********************************
# EXTENSIBILITY ELEMENTS # EXTENSIBILITY ELEMENTS
anyElement = anyElement =
element * { element * {
(attribute * { text } (attribute * { text }
| text | text
| anyElement)* | anyElement)*
} }
# EXTENSIBILITY ATTRIBUTES # EXTENSIBILITY ATTRIBUTES
anyAttribute = anyAttribute =
attribute * - (entity attribute * - (entity
skipping to change at page 34, line 19 skipping to change at page 35, line 39
# WILDCARD FOR EVENT-PACKAGE NAMESPACE # WILDCARD FOR EVENT-PACKAGE NAMESPACE
conference-info-urn = conference-info-urn =
element * - (ns2:* | local:*) { element * - (ns2:* | local:*) {
mixed { mixed {
(attribute * { text } (attribute * { text }
| conference-info-urn)* | conference-info-urn)*
} }
} }
# DEFINITION OF ENDPOINT STATUS TYPE # DEFINITION OF ENDPOINT STATUS TYPE
media-status-type = "recvonly" | "sendonly" | "sendrecv" | "inactive" media-status-type =
"recvonly" | "sendonly" | "sendrecv" | "inactive" | text
# 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"
| "disconnecting" | "disconnecting"
| "disconnected" | "disconnected"
| text
# JOINING TYPE # JOINING TYPE
joining-type = "dialed-in" | "dialed-out" | "focus-owner" joining-type = "dialed-in" | "dialed-out" | "focus-owner" | text
# DISCONNECTION TYPE # DISCONNECTION TYPE
disconnection-type = "departed" | "booted" | "failed" | "busy" disconnection-type = "departed" | "booted" | "failed" | "busy" | text
6. XML Schema Extensibility 6. XML Schema Extensibility
The Conference Information Data Model defined in this document is The Conference Information Data Model defined in this document is
meant to be extensible toward specific application domains. Such meant to be extensible toward specific application domains. Such
extensions are accomplished by defining elements, child elements and extensions are accomplished by defining elements, child elements and
attributes that are specific to the desired application domain. The attributes that are specific to the desired application domain. The
IETF MAY extend the data model schema with extension elements from IETF MAY extend the data model schema with extension elements from
the same namespace in future. Other instances are free to define the same namespace in future. Other instances are free to define
extension elements under any namespace other than extension elements under any namespace other than
urn:ietf:params:xml:ns:xcon-conference-info. urn:ietf:params:xml:ns:xcon-conference-info.
Elements or attributes from unknown namespaces MUST be ignored. Elements or attributes from unknown namespaces MUST be ignored.
7. XML Example 7. XML Example
The following is an example of a conference information document. The following is an example of a conference information document.
The conference starts on October 17, 2007, at 10:30 AM in New York The conference starts on October 17, 2007, at 10:30 AM in New York
City and finishes the same day at 12:30 PM every week. In this City and finishes the same day at 12:30 PM every week. In this
example, there are currently 3 participants in a conference, one example, there are currently 3 participants in a conference, one
administrator, one moderator, and one participant. Note that administrator, one moderator, and one participant. Sidebars are
sidebars are allowed in this conference and there is one sidebar in allowed in this conference and ,consequently, there is one sidebar in
the conference. Also note that there is one floor moderator for the the conference. In addition, Alice and Carol are using a floor in
audio and a different floor moderator for the video. the main conference to manage the audio and video resources. At the
moment, Alice is assigned to use the floor.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<conference-info xmlns="urn:ietf:params:xml:ns:xcon-conference-info" <conference-info xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
entity="conference123@example.com"> entity="conference123@example.com">
<!-- <!--
CONFERENCE DESCRIPTION CONFERENCE DESCRIPTION
--> -->
<conference-description lang="en-us"> <conference-description lang="en-us">
<language>en-us</language> <language>En-us</language>
<display-text>Discussion of Formula-1 racing</display-text> <display-text>Discussion of Formula-1 racing</display-text>
<subject> Sports:Formula-1</subject> <subject> Sports:Formula-1</subject>
<free-text>This is a conference example</free-text> <free-text>This is a conference example</free-text>
<keywords>Formula-1, cars</keywords> <keywords>Formula-1, cars</keywords>
<webpage>http://www.example.com/users/formula-1</webpage>
<allow-sidebars>true</allow-sidebars> <allow-sidebars>true</allow-sidebars>
<!-- <!--
CONFERENCE TIME CONFERENCE TIME
--> -->
<conference-time> <conference-time>
<entry> <entry>
<base>BEGIN:VCALENDAR <base>BEGIN:VCALENDAR
PRODID:-//LlamaSpinner Inc.//NONSGML CamelCall//EN PRODID:-//LlamaSpinner Inc.//NONSGML CamelCall//EN
VERSION:2.0 VERSION:2.0
BEGIN:VEVENT BEGIN:VEVENT
DTSTAMP:20061103T140728Z DTSTAMP:20071003T140728Z
UID:20061103T140728Z-345FDA-carol@example.com UID:20071003T140728Z-345FDA-carol@example.com
ORGANIZER:MAILTO:carol@example.com ORGANIZER:MAILTO:carol@example.com
DTSTART:20071017T143000Z DTSTART:20071017T143000Z
RRULE:FREQ=WEEKLY RRULE:FREQ=WEEKLY
DTEND:20071217T163000Z DTEND:20071217T163000Z
END:VEVENT END:VEVENT
END:VCALENDAR</base> END:VCALENDAR</base>
<mixing-start-offset required-participant="moderator" <mixing-start-offset required-participant="moderator"
> 2007-10-17T14:29:00Z</mixing-start-offset> > 2007-10-17T14:29:00Z</mixing-start-offset>
<mixing-end-offset required-participant="participant" <mixing-end-offset required-participant="participant"
> 2007-10-17T16:31:00Z</mixing-end-offset> > 2007-10-17T16:31:00Z</mixing-end-offset>
skipping to change at page 36, line 15 skipping to change at page 37, line 36
</entry> </entry>
</conference-time> </conference-time>
<!-- <!--
CONFERENCE UNIQUE IDENTIFIERS CONFERENCE UNIQUE IDENTIFIERS
--> -->
<conf-uris> <conf-uris>
<entry> <entry>
<uri>tel:+3585671234</uri> <uri>tel:+3585671234</uri>
<display-text>Conference Bridge</display-text> <display-text>Conference Bridge</display-text>
<purpose>participation</purpose> <purpose>participation</purpose>
<conference-password>5678</conference-password>
</entry> </entry>
<entry> <entry>
<uri>http://www.example.com/live.ram</uri> <uri>http://www.example.com/live.ram</uri>
<purpose>streaming</purpose> <purpose>streaming</purpose>
</entry> </entry>
</conf-uris> </conf-uris>
<!-- <!--
SERVICE URIS SERVICE URIS
--> -->
<service-uris> <service-uris>
<entry> <entry>
<uri>http://www.example.com/formula1/</uri> <uri>http://www.example.com/formula1/</uri>
<purpose>web-page</purpose> <purpose>web-page</purpose>
</entry> </entry>
</service-uris> </service-uris>
<!-- <!--
MAXIMUM USER COUNT MAXIMUM USER COUNT
--> -->
<maximum-user-count> <maximum-user-count>50</maximum-user-count>
<entry role="administrator">2</entry>
<entry role="moderator">5</entry>
<entry role="participant">150</entry>
</maximum-user-count>
<!-- <!--
AVAILABLE MEDIA AVAILABLE MEDIA
--> -->
<available-media> <available-media>
<entry label="10234"> <entry label="10234">
<display-text>main audio</display-text> <display-text>main audio</display-text>
<type>audio</type> <type>audio</type>
<status>sendrecv</status> <status>sendrecv</status>
<mixing-mode>automatic</mixing-mode> <mixing-mode>automatic</mixing-mode>
<mix-level>3</mix-level>
<codecs decision="automatic"> <codecs decision="automatic">
<codec name="PCMU" policy="allowed"/> <codec name="PCMU" policy="allowed"/>
</codecs> </codecs>
<controls>
<mute>true</mute>
<gain>50</gain>
</controls>
</entry> </entry>
<entry label="10235"> <entry label="10235">
<display-text>main video</display-text> <display-text>main video</display-text>
<type>video</type> <type>video</type>
<status>sendrecv</status> <status>sendrecv</status>
<mixing-mode>automatic</mixing-mode> <mixing-mode>automatic</mixing-mode>
<mix-level>4</mix-level>
<codecs decision="automatic"> <codecs decision="automatic">
<codec name="H.263" policy="allowed"/> <codec name="H.263" policy="allowed"/>
</codecs> </codecs>
<controls>
<video-layout>single-view</video-layout>
</controls>
</entry> </entry>
</available-media> </available-media>
</conference-description> </conference-description>
<!-- <!--
HOST INFO HOST INFO
--> -->
<host-info> <host-info>
<display-text>Formula1</display-text> <display-text>Formula1</display-text>
<web-page>http://www.example.com/formula1/</web-page> <web-page>http://www.example.com/formula1/</web-page>
<uris> <uris>
skipping to change at page 37, line 35 skipping to change at page 39, line 10
</entry> </entry>
<entry> <entry>
<uri>sip:carol@example.com</uri> <uri>sip:carol@example.com</uri>
</entry> </entry>
</uris> </uris>
</host-info> </host-info>
<!-- <!--
CONFERENCE STATE CONFERENCE STATE
--> -->
<conference-state> <conference-state>
<allow-conference-state>true</allow-conference-state> <allow-conference-event-subscription
>true</allow-conference-event-subscription>
<user-count>3</user-count> <user-count>3</user-count>
<active>true</active> <active>true</active>
<locked>false</locked> <locked>false</locked>
</conference-state> </conference-state>
<!-- <!--
FLOOR INFORMATION FLOOR INFORMATION
--> -->
<floor-information> <floor-information>
<conference-ID>567</conference-ID> <conference-ID>567</conference-ID>
<allow-floor-events>true</allow-floor-events> <allow-floor-events>true</allow-floor-events>
<floor-request-handling>confirm</floor-request-handling> <floor-request-handling>confirm</floor-request-handling>
<conference-floor-policy> <conference-floor-policy>
<floor> <floor id="345">
<media-label>10234</media-label> <media-label>10234</media-label>
<media-label>10235</media-label> <media-label>10235</media-label>
<algorithm>moderator-controlled</algorithm> <algorithm>moderator-controlled</algorithm>
<max-floor-users>1</max-floor-users> <max-floor-users>1</max-floor-users>
<moderator-id>234</moderator-id> <moderator-id>234</moderator-id>
</floor> </floor>
</conference-floor-policy> </conference-floor-policy>
</floor-information> </floor-information>
<!-- <!--
USERS USERS
skipping to change at page 38, line 26 skipping to change at page 39, line 50
<!-- <!--
ALLOWED USERS LIST ALLOWED USERS LIST
--> -->
<allowed-users-list> <allowed-users-list>
<target uri="sip:bob@example.com" method="dial-out"/> <target uri="sip:bob@example.com" method="dial-out"/>
<target uri="sip:alice@example.com" method="dial-out"/> <target uri="sip:alice@example.com" method="dial-out"/>
<target uri="sip:carol@example.com" method="dial-out"/> <target uri="sip:carol@example.com" method="dial-out"/>
<target uri="sip:john@example.com" method="refer"/> <target uri="sip:john@example.com" method="refer"/>
</allowed-users-list> </allowed-users-list>
<!-- <!--
DENY USERS LIST
-->
<deny-users-list>
<target uri="sip:charlie@example.com"/>
</deny-users-list>
<!--
USER BOB USER BOB
--> -->
<user entity="bob534"> <user entity="bob534">
<display-text>Bob Hoskins</display-text> <display-text>Bob Hoskins</display-text>
<associated-aors> <associated-aors>
<SIP> <entry>
<uri>mailto:bob@example.com</uri> <uri>mailto:bob@example.com</uri>
<display-text>email</display-text> <display-text>email</display-text>
</SIP> </entry>
</associated-aors> </associated-aors>
<provide-anonymity>private</provide-anonymity> <provide-anonymity>semi-private</provide-anonymity>
<roles> <roles>
<entry>participant</entry> <entry>participant</entry>
</roles> </roles>
<languages>en</languages> <languages>en-us</languages>
<allow-refer-users-dynamically <allow-refer-users-dynamically
>false</allow-refer-users-dynamically> >false</allow-refer-users-dynamically>
<allow-invite-users-dynamically <allow-invite-users-dynamically
>false</allow-invite-users-dynamically> >false</allow-invite-users-dynamically>
<allow-remove-users-dynamically <allow-remove-users-dynamically
>false</allow-remove-users-dynamically> >false</allow-remove-users-dynamically>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:bob@example.com"> <endpoint entity="sip:bob@example.com">
<display-text>Bob's Laptop</display-text> <display-text>Bob's Laptop</display-text>
<referred> <referred>
<when>2006-10-17T14:00:00Z</when> <when>2007-10-17T14:00:00Z</when>
<reason>expert required</reason> <reason>expert required</reason>
<by>sip:alice@example.com</by> <by>sip:alice@example.com</by>
</referred> </referred>
<status>connected</status> <status>connected</status>
<joining-method>dialed-out</joining-method> <joining-method>dialed-out</joining-method>
<joining-info> <joining-info>
<when>2006-10-17T14:00:00Z</when> <when>2007-10-17T14:00:00Z</when>
<reason>invitation</reason> <reason>invitation</reason>
<by>sip:alice@example.com</by> <by>sip:alice@example.com</by>
</joining-info> </joining-info>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1"> <media id="1">
<type>video</type>
<label>10235</label> <label>10235</label>
<src-id>432424</src-id> <src-id>432424</src-id>
<status>sendrecv</status>
<to-mixer name="VideoIn">
<controls>
<video-layout
>single-view</video-layout>
</controls>
</to-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>hsjh8980vhsb78</call-id> <call-id>hsjh8980vhsb78</call-id>
<from-tag>vav738dvbs</from-tag> <from-tag>vav738dvbs</from-tag>
<to-tag>8954jgjg8432</to-tag> <to-tag>8954jgjg8432</to-tag>
skipping to change at page 39, line 45 skipping to change at page 41, line 37
</endpoint> </endpoint>
</user> </user>
<!-- <!--
USER ALICE USER ALICE
--> -->
<user entity="alice334"> <user entity="alice334">
<display-text>Alice Kay</display-text> <display-text>Alice Kay</display-text>
<associated-aors> <associated-aors>
<SIP> <entry>
<uri>mailto:alice@example.com</uri> <uri>mailto:alice@example.com</uri>
<display-text>email</display-text> <display-text>email</display-text>
</SIP> </entry>
</associated-aors> </associated-aors>
<provide-anonymity>private</provide-anonymity> <provide-anonymity>private</provide-anonymity>
<roles> <roles>
<entry>moderator</entry> <entry>moderator</entry>
</roles> </roles>
<languages>en</languages> <languages>en-us</languages>
<allow-refer-users-dynamically <allow-refer-users-dynamically
>true</allow-refer-users-dynamically> >true</allow-refer-users-dynamically>
<allow-invite-users-dynamically <allow-invite-users-dynamically
>true</allow-invite-users-dynamically> >true</allow-invite-users-dynamically>
<allow-remove-users-dynamically <allow-remove-users-dynamically
>true</allow-remove-users-dynamically> >true</allow-remove-users-dynamically>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:alice@example.com"> <endpoint entity="sip:alice@example.com">
<display-text>Alice's Desktop</display-text> <display-text>Alice's Desktop</display-text>
<status>connected</status> <status>connected</status>
<joining-method>dialed-in</joining-method> <joining-method>dialed-in</joining-method>
<joining-info> <joining-info>
<when>2006-10-17T13:35:08Z</when> <when>2007-10-17T13:35:08Z</when>
<reason>invitation</reason> <reason>invitation</reason>
<by>sip:conference@example.com</by> <by>sip:conference@example.com</by>
</joining-info> </joining-info>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1"> <media id="1">
<type>video</type>
<label>10235</label> <label>10235</label>
<src-id>432424</src-id> <src-id>432424</src-id>
<status>sendrecv</status> <status>sendrecv</status>
<to-mixer name="VideoIn">
<controls>
<video-layout
>single-view</video-layout>
</controls>
</to-mixer>
</media> </media>
<media id="2"> <media id="2">
<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>
<to-mixer name="VideoIn">
<controls>
<gain>50</gain>
</controls>
</to-mixer>
<from-mixer name="VideoOut">
<controls>
<gain>50</gain>
</controls>
</from-mixer>
</media> </media>
<floor id="345">true</floor>
<!-- <!--
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>
skipping to change at page 41, line 4 skipping to change at page 43, line 15
<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>
</endpoint> </endpoint>
</user> </user>
<!-- <!--
USER CAROL USER CAROL
--> -->
<user entity="carol233"> <user entity="carol233">
<display-text>Carol More</display-text> <display-text>Carol More</display-text>
<associated-aors> <associated-aors>
<SIP> <entry>
<uri>mailto:carol@example.com</uri> <uri>mailto:carol@example.com</uri>
<display-text>email</display-text> <display-text>email</display-text>
</SIP> </entry>
</associated-aors> </associated-aors>
<provide-anonymity>private</provide-anonymity> <provide-anonymity>private</provide-anonymity>
<roles> <roles>
<entry>administrator</entry> <entry>administrator</entry>
</roles> </roles>
<languages>en</languages> <languages>en-us</languages>
<allow-refer-users-dynamically <allow-refer-users-dynamically
>true</allow-refer-users-dynamically> >true</allow-refer-users-dynamically>
<allow-invite-users-dynamically <allow-invite-users-dynamically
>true</allow-invite-users-dynamically> >true</allow-invite-users-dynamically>
<allow-remove-users-dynamically <allow-remove-users-dynamically
>true</allow-remove-users-dynamically> >true</allow-remove-users-dynamically>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:carol@example.com"> <endpoint entity="sip:carol@example.com">
<display-text>Carol's Computer</display-text> <display-text>Carol's Computer</display-text>
<status>connected</status> <status>connected</status>
<joining-method>dialed-in</joining-method> <joining-method>dialed-in</joining-method>
<joining-info> <joining-info>
<when>2006-10-17T13:30:05Z</when> <when>2007-10-17T13:30:05Z</when>
<reason>invitation</reason> <reason>invitation</reason>
<by>sip:conference@example.com</by> <by>sip:conference@example.com</by>
</joining-info> </joining-info>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1"> <media id="1">
<type>video</type>
<label>10235</label> <label>10235</label>
<src-id>432424</src-id> <src-id>432424</src-id>
<status>sendrecv</status> <status>sendrecv</status>
<to-mixer name="VideoIn">
<controls>
<video-layout
>single-view</video-layout>
</controls>
</to-mixer>
</media> </media>
<media id="2"> <media id="2">
<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>
<to-mixer name="VideoIn">
<controls>
<gain>50</gain>
</controls>
</to-mixer>
<from-mixer name="VideoOut">
<controls>
<gain>50</gain>
</controls>
</from-mixer>
</media> </media>
<floor id="345">false</floor>
<!-- <!--
CALL INFO CALL INFO
--> -->
<call-info> <call-info>
<sip> <sip>
<display-text>full info</display-text> <display-text>full info</display-text>
<call-id>wevb12562321894</call-id> <call-id>wevb12562321894</call-id>
<from-tag>asw456wedf</from-tag> <from-tag>asw456wedf</from-tag>
<to-tag>2365dfrt3497</to-tag> <to-tag>2365dfrt3497</to-tag>
</sip> </sip>
skipping to change at page 43, line 7 skipping to change at page 45, line 36
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
A malicious user can manipulate parts of the Conference Information Different conferencing protocols will support different types of
Data Model privileges document giving themselves and others authentication mechanisms. Since a variety of signaling protocols
privileges to manipulate the document. It is very important that are possible, a variety of authentication mechanism may need to be
only authorized clients are able to manipulate the Conference mapped from the different protocols.
Information Data Model document.
Futhermore, users may use different namespaces to access to a
conference. So a mapping database has to specify the acceptable
range of namespace for a user. Doing so, a 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 [1] applies to described in the centralized conferencing framework [RFC4575] applies
this document. The focus must ensure that only authorized entities to this document. The focus must ensure that only authorized
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. Confidentiality is provided through encryption. Strong end-
to-end authentication and encryption can be done using public keys, to-end authentication and encryption can be done using public keys,
and end-to-end encryption can be done using private keys. It is and end-to-end encryption can be done using private keys. It is
RECOMMENDED that the protocols that manipulated the conference RECOMMENDED that the protocols that manipulated the conference
information data model use a strong encryption for conference information data model use a strong encryption for conference
information protection. information protection.
8.3. Integrity 8.3. Integrity
It is important that the Conference Information Data Model can only A conferencing system may maintain a mapping database between the
be accessed or modified by those authorized users. Without conference object identifiers and the identifiers associated with
integrity, the Conference Information Data Model could be modified, each of the complementary centralized conferencing protocols, as well
fooling the user into believing incorrect information. Measures as, a mapping between the conference user identifiers and the
taken to ensure integrity include maintaining rigorous authentication identifiers associated with each user in a conference. This mapping
practices. 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 45, line 44 skipping to change at page 47, line 47
9.3. Conference Object Identifier Registration 9.3. Conference Object Identifier Registration
The IANA is requested to register the following URI scheme The IANA is requested to register the following URI scheme
under the Permanent URI Schemes register. under the Permanent URI Schemes register.
XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx] XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host, port, and unreserved are defined in RFC3986[9] host, port, and unreserved are defined in RFC3986[RFC3986]
[Note to the RFC Editor: replace xxxx with the number this RFC gets [Note to the RFC Editor: replace xxxx with the number this RFC gets
assigned.] assigned.]
9.4. Conference User Identifier Registration 9.4. Conference User Identifier Registration
The IANA is requested to register the following URI scheme The IANA is requested to register the following URI scheme
under the Permanent URI Schemes register. under the Permanent URI Schemes register.
XCON_USERID = "xcon_userid" ":" conf-object-id [ RFC xxxx ] XCON_USERID = "xcon_userid" ":" conf-object-id [ RFC xxxx ]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
unreserved is defined in RFC3986[9] unreserved is defined in RFC3986[RFC3986]
[Note to the RFC Editor: replace xxxx with the number this RFC gets [Note to the RFC Editor: replace xxxx with the number this RFC gets
assigned.] assigned.]
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, Adam Roach, Mary Barnes, Chris would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris
skipping to change at page 46, line 39 skipping to change at page 48, line 41
information of their xcon drafts. Last but not least, I would like information of their xcon drafts. Last but not least, I would like
to express my gratitude to all those reviewers for their invaluable to express my gratitude to all those reviewers for their invaluable
contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi, contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi,
Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, and Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, and
Ben Campbell. Ben Campbell.
11. References 11. References
11.1. Normative References 11.1. Normative References
[1] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Initiation Protocol (SIP) Event Package for Conference State", Requirement Levels", BCP 14, RFC 2119, March 1997.
RFC 4575, August 2006.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement [RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and
Levels", BCP 14, RFC 2119, March 1997. Scheduling Core Object Specification (iCalendar)",
RFC 2445, November 1998.
[3] Dawson, F. and Stenerson, D., "Internet Calendaring and [RFC4575] Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
Scheduling Core Object Specification (iCalendar)", RFC 2445, Initiation Protocol (SIP) Event Package for Conference
November 1998. State", RFC 4575, August 2006.
11.2. Informative References 11.2. Informative References
[4] Barnes, M., Boulton, C., and O. Levin, "A Framework for [I-D.ietf-xcon-framework]
Centralized Conferencing", draft-ietf-xcon-framework-10 (work Barnes, M., Boulton, C., and O. Levin, "A Framework for
in progress), November 2007. Centralized Conferencing", draft-ietf-xcon-framework-10
(work in progress), November 2007.
[5] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor Control [IANA] "IANA registry for RTP Payload Types"
Protocol (BFCP)", RFC 4582, November 2006. "http://www.iana.org/assignments/rtp-parameters".
[6] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [RELAX] "RELAX NG Home Page" "http://relaxng.org/".
Notification", RFC 3265, June 2002.
[7] Rosenberg, J., "A Framework for Conferencing with the Session [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
Initiation Protocol (SIP)", RFC 4353, February 2006. with Session Description Protocol (SDP)", RFC 3264,
June 2002.
[8] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, [RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
"Extensible Markup Language (XML) 1.0 (Second Edition)", World Event Notification", RFC 3265, June 2002.
Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>.
[9] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, Resource Identifier (URI): Generic Syntax", STD 66,
January 2005. RFC 3986, January 2005.
[10] Casner, S., "Media Type Registration of RTP Payload Formats", [RFC4353] Rosenberg, J., "A Framework for Conferencing with the
RFC 4855, February 2007. Session Initiation Protocol (SIP)", RFC 4353,
February 2006.
[11] "IANA registry for RTP Payload Types" [RFC4582] Camarillo, G., Ott, J., and K. Drage, "The Binary Floor
"http://www.iana.org/assignments/rtp-parameters". Control Protocol (BFCP)", RFC 4582, November 2006.
[12] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with [RFC4583] Camarillo, G., "Session Description Protocol (SDP) Format
Session Description Protocol (SDP)", RFC 3264, June 2002. for Binary Floor Control Protocol (BFCP) Streams",
RFC 4583, November 2006.
[13] Camarillo, G., "Session Description Protocol (SDP) Format for [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Binary Floor Control Protocol (BFCP) Streams", RFC 4583, Formats", RFC 4855, February 2007.
November 2006.
[14] Camarillo, G., "Connection Establishment in the Binary Floor [RFC5018] Camarillo, G., "Connection Establishment in the Binary
Control Protocol (BFCP)", RFC 5018, September 2007. Floor Control Protocol (BFCP)", RFC 5018, September 2007.
[15] "RELAX NG Home Page" "http://relaxng.org/". [W3C.REC-xml-20001006]
Paoli, J., Maler, E., Sperberg-McQueen, C., and T. Bray,
"Extensible Markup Language (XML) 1.0 (Second Edition)",
World Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000,
<http://www.w3.org/TR/2000/REC-xml-20001006>.
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. 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 ns="urn:ietf:params:xml:ns:xcon-conference-info" <grammar ns="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns="http://relaxng.org/ns/structure/1.0" xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
<start> <start>
<element name="conference-info"> <element name="conference-info">
skipping to change at page 51, line 14 skipping to change at page 53, line 21
<element name="base"> <element name="base">
<text/> <text/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="mixing-start-offset"> <element name="mixing-start-offset">
<data type="dateTime"> <data type="dateTime">
<param name="pattern">.+T.+Z.*</param> <param name="pattern">.+T.+Z.*</param>
</data> </data>
<attribute name="required-participant"> <attribute name="required-participant">
<text/> <ref name="single-role-type"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="mixing-end-offset"> <element name="mixing-end-offset">
<data type="dateTime"> <data type="dateTime">
<param name="pattern">.+T.+Z.*</param> <param name="pattern">.+T.+Z.*</param>
</data> </data>
<attribute name="required-participant"> <attribute name="required-participant">
<text/> <ref name="single-role-type"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="can-join-after-offset"> <element name="can-join-after-offset">
<data type="dateTime"> <data type="dateTime">
<param name="pattern">.+T.+Z.*</param> <param name="pattern">.+T.+Z.*</param>
</data> </data>
</element> </element>
skipping to change at page 53, line 17 skipping to change at page 55, line 24
<ref name="mix-mode-type"/> <ref name="mix-mode-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="codecs"> <element name="codecs">
<ref name="codecs-type"/> <ref name="codecs-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="controls"> <element name="controls">
<ref name="controls-type"/>
</element>
</optional>
<zeroOrMore>
<ref name="anyElement"/>
</zeroOrMore>
</define>
<!--
CONTROLS TYPE
-->
<define name="controls-type">
<ref name="anyAttribute"/>
<zeroOrMore>
<element name="control">
<ref name="control-type"/> <ref name="control-type"/>
</element> </element>
</zeroOrMore> </optional>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
MIX MODE TYPE MIX MODE TYPE
--> -->
<define name="mix-mode-type"> <define name="mix-mode-type">
<choice> <choice>
<value type="string">moderator-controlled</value> <value type="string">moderator-controlled</value>
<value type="string">FCFS</value> <value type="string">FCFS</value>
<value type="string">automatic</value> <value type="string">automatic</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
CODECS TYPE CODECS TYPE
--> -->
<define name="codecs-type"> <define name="codecs-type">
<attribute name="decision"> <attribute name="decision">
<ref name="decision-type"/> <ref name="decision-type"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
skipping to change at page 54, line 36 skipping to change at page 56, line 30
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
</define> </define>
<!-- <!--
DECISION TYPE DECISION TYPE
--> -->
<define name="decision-type"> <define name="decision-type">
<choice> <choice>
<value type="string">automatic</value> <value type="string">automatic</value>
<value type="string">moderator-controlled</value> <value type="string">moderator-controlled</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
POLICY TYPE POLICY TYPE
--> -->
<define name="policy-type"> <define name="policy-type">
<choice> <choice>
<value type="string">allowed</value> <value type="string">allowed</value>
<value type="string">disallowed</value> <value type="string">disallowed</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
CONTROL TYPE CONTROL TYPE
--> -->
<define name="control-type"> <define name="control-type">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<choice> <zeroOrMore>
<element name="mute"> <element name="mute">
<data type="boolean"/> <data type="boolean"/>
</element> </element>
<element name="pause-video"> <element name="pause-video">
<data type="boolean"/> <data type="boolean"/>
</element> </element>
<element name="gain"> <element name="gain">
<data type="int"> <data type="int">
<param name="minInclusive">-127</param> <param name="minInclusive">-127</param>
<param name="maxInclusive">127</param> <param name="maxInclusive">127</param>
skipping to change at page 55, line 29 skipping to change at page 57, line 25
<value type="string">single-view</value> <value type="string">single-view</value>
<value type="string">dual-view</value> <value type="string">dual-view</value>
<value type="string">dual-view-crop</value> <value type="string">dual-view-crop</value>
<value type="string">dual-view-2x1</value> <value type="string">dual-view-2x1</value>
<value type="string">dual-view-2x1-crop</value> <value type="string">dual-view-2x1-crop</value>
<value type="string">quad-view</value> <value type="string">quad-view</value>
<value type="string">multiple-3x3</value> <value type="string">multiple-3x3</value>
<value type="string">multiple-4x4</value> <value type="string">multiple-4x4</value>
<value type="string">multiple-5x1</value> <value type="string">multiple-5x1</value>
<value type="string">automatic</value> <value type="string">automatic</value>
<text/>
</choice> </choice>
</element> </element>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</choice> </zeroOrMore>
</define> </define>
<!-- <!--
CONFERENCE STATE TYPE CONFERENCE STATE TYPE
--> -->
<define name="conference-state-type"> <define name="conference-state-type">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<optional> <optional>
<element name="allow-conference-event-subscription"> <element name="allow-conference-event-subscription">
<data type="boolean"/> <data type="boolean"/>
</element> </element>
skipping to change at page 56, line 47 skipping to change at page 58, line 44
</zeroOrMore> </zeroOrMore>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
FLOOR REQUEST TYPE FLOOR REQUEST TYPE
--> -->
<define name="floor-request-type"> <define name="floor-request-type">
<choice> <choice>
<value type="string">block</value> <value type="string">block</value>
<value type="string">confirm</value> <value type="string">confirm</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
CONFERENCE FLOOR POLICY CONFERENCE FLOOR POLICY
--> -->
<define name="Conference-floor-policy"> <define name="Conference-floor-policy">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<oneOrMore> <oneOrMore>
<element name="floor"> <element name="floor">
<attribute name="id">
<text/>
</attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<oneOrMore> <oneOrMore>
<element name="media-label"> <element name="media-label">
<data type="nonNegativeInteger"/> <data type="nonNegativeInteger"/>
</element> </element>
</oneOrMore> </oneOrMore>
<zeroOrMore> <zeroOrMore>
<element name="algorithm"> <element name="algorithm">
<choice> <choice>
<value type="string">moderator-controlled</value> <value type="string">moderator-controlled</value>
<value type="string">FCFS</value> <value type="string">FCFS</value>
<value type="string">random</value> <value type="string">random</value>
<text/>
</choice> </choice>
</element> </element>
<element name="max-floor-users"> <element name="max-floor-users">
<data type="nonNegativeInteger"/> <data type="nonNegativeInteger"/>
</element> </element>
<element name="moderator-id"> <element name="moderator-id">
<text/> <text/>
</element> </element>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
skipping to change at page 58, line 8 skipping to change at page 60, line 10
<element name="user-admission-policy"> <element name="user-admission-policy">
<ref name="user-admission-policy-type"/> <ref name="user-admission-policy-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="allowed-users-list"> <element name="allowed-users-list">
<ref name="UserList"/> <ref name="UserList"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="denied-users-list"> <element name="deny-users-list">
<ref name="deny-user-list"/> <ref name="deny-user-list"/>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<element name="user"> <element name="user">
<ref name="user-type"/> <ref name="user-type"/>
</element> </element>
</zeroOrMore> </zeroOrMore>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
USERS ADMISSION POLICY USERS ADMISSION POLICY
--> -->
<define name="user-admission-policy-type"> <define name="user-admission-policy-type">
<choice> <choice>
<value type="string">closedAuthenticated</value> <value type="string">closedAuthenticated</value>
<value type="string">openAuthenticated</value> <value type="string">openAuthenticated</value>
<value type="string">anonymous</value> <value type="string">anonymous</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
JOIN HANDLING TYPE JOIN HANDLING TYPE
--> -->
<define name="join-handling-type"> <define name="join-handling-type">
<choice> <choice>
<value type="string">block</value> <value type="string">block</value>
<value type="string">confirm</value> <value type="string">confirm</value>
<value type="string">allow</value> <value type="string">allow</value>
<value type="string">authenticate</value> <value type="string">authenticate</value>
<value type="string">directed-operator</value> <value type="string">directed-operator</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
DENYUSERLIST DENYUSERLIST
--> -->
<define name="deny-user-list"> <define name="deny-user-list">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<zeroOrMore> <zeroOrMore>
<element name="target"> <element name="target">
skipping to change at page 59, line 36 skipping to change at page 61, line 40
<optional> <optional>
<element name="persistent-list"> <element name="persistent-list">
<zeroOrMore> <zeroOrMore>
<element name="user"> <element name="user">
<attribute name="name"> <attribute name="name">
<text/> <text/>
</attribute> </attribute>
<attribute name="nickname"> <attribute name="nickname">
<text/> <text/>
</attribute> </attribute>
<attribute name="id">
<text/>
</attribute>
<ref name="anyAttribute"/>
<zeroOrMore>
<element name="e-mail"> <element name="e-mail">
<text/> <text/>
</element> </element>
</zeroOrMore>
</element> </element>
</zeroOrMore> </zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</element> </element>
</optional> </optional>
</define> </define>
<!-- <!--
TARGET TYPE TARGET TYPE
--> -->
<define name="target-type"> <define name="target-type">
skipping to change at page 60, line 17 skipping to change at page 62, line 27
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
</define> </define>
<!-- <!--
METHOD TYPE METHOD TYPE
--> -->
<define name="method-type"> <define name="method-type">
<choice> <choice>
<value type="string">dial-in</value> <value type="string">dial-in</value>
<value type="string">dial-out</value> <value type="string">dial-out</value>
<value type="string">refer</value> <value type="string">refer</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
USER TYPE USER TYPE
--> -->
<define name="user-type"> <define name="user-type">
<attribute name="entity"> <attribute name="entity">
<data type="anyURI"/> <data type="anyURI"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
skipping to change at page 60, line 44 skipping to change at page 63, line 7
<zeroOrMore> <zeroOrMore>
<ref name="conference-info-urn"/> <ref name="conference-info-urn"/>
</zeroOrMore> </zeroOrMore>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="provide-anonymity"> <element name="provide-anonymity">
<choice> <choice>
<value>private</value> <value>private</value>
<value>semi-private</value> <value>semi-private</value>
<text/>
</choice> </choice>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="roles"> <element name="roles">
<text/> <ref name="single-role-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="languages"> <element name="languages">
<list> <list>
<data type="language"/> <data type="language"/>
</list> </list>
</element> </element>
</optional> </optional>
<optional> <optional>
skipping to change at page 62, line 46 skipping to change at page 65, line 10
<zeroOrMore> <zeroOrMore>
<ref name="conference-info-urn"/> <ref name="conference-info-urn"/>
</zeroOrMore> </zeroOrMore>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<element name="media"> <element name="media">
<ref name="media-type"/> <ref name="media-type"/>
</element> </element>
</zeroOrMore> </zeroOrMore>
<zeroOrMore>
<element name="floor">
<attribute name="id">
<text/>
</attribute>
<ref name="anyAttribute"/>
<data type="boolean"/>
</element>
</zeroOrMore>
<optional> <optional>
<element name="call-info"> <element name="call-info">
<zeroOrMore> <zeroOrMore>
<ref name="conference-info-urn"/> <ref name="conference-info-urn"/>
</zeroOrMore> </zeroOrMore>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
skipping to change at page 64, line 14 skipping to change at page 66, line 35
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
MIXER TYPE MIXER TYPE
--> -->
<define name="mixer-type"> <define name="mixer-type">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<optional> <optional>
<element name="floor">
<data type="boolean"/>
</element>
<element name="controls"> <element name="controls">
<ref name="controls-type"/> <ref name="control-type"/>
</element> </element>
</optional> </optional>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
SIDEBARS-BY-REF TYPE SIDEBARS-BY-REF TYPE
--> -->
<define name="sidebars-by-ref-type"> <define name="sidebars-by-ref-type">
skipping to change at page 65, line 8 skipping to change at page 67, line 26
<zeroOrMore> <zeroOrMore>
<element name="entry"> <element name="entry">
<ref name="conference-type"/> <ref name="conference-type"/>
</element> </element>
</zeroOrMore> </zeroOrMore>
<zeroOrMore> <zeroOrMore>
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
SINGLE ROLE TYPE
-->
<define name="single-role-type">
<choice>
<value type="string">administrator</value>
<value type="string">moderator</value>
<value type="string">user</value>
<value type="string">participant</value>
<value type="string">observer</value>
<value type="string">none</value>
<text/>
</choice>
</define>
<!--
********************************* *********************************
EXTENSIBILITY OF THE SCHEMA EXTENSIBILITY OF THE SCHEMA
********************************* *********************************
--> -->
<!-- <!--
EXTENSIBILITY ELEMENTS EXTENSIBILITY ELEMENTS
--> -->
<define name="anyElement"> <define name="anyElement">
<element> <element>
<anyName/> <anyName/>
skipping to change at page 66, line 46 skipping to change at page 69, line 30
<!-- <!--
DEFINITION OF ENDPOINT STATUS TYPE DEFINITION OF ENDPOINT STATUS TYPE
--> -->
<define name="media-status-type"> <define name="media-status-type">
<choice> <choice>
<value>recvonly</value> <value>recvonly</value>
<value>sendonly</value> <value>sendonly</value>
<value>sendrecv</value> <value>sendrecv</value>
<value>inactive</value> <value>inactive</value>
<text/>
</choice> </choice>
</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>
<value>dialing-out</value> <value>dialing-out</value>
<value>dialing-in</value> <value>dialing-in</value>
<value>alerting</value> <value>alerting</value>
<value>on-hold</value> <value>on-hold</value>
<value>connected</value> <value>connected</value>
<value>muted-via-focus</value> <value>muted-via-focus</value>
<value>disconnecting</value> <value>disconnecting</value>
<value>disconnected</value> <value>disconnected</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
JOINING TYPE JOINING TYPE
--> -->
<define name="joining-type"> <define name="joining-type">
<choice> <choice>
<value>dialed-in</value> <value>dialed-in</value>
<value>dialed-out</value> <value>dialed-out</value>
<value>focus-owner</value> <value>focus-owner</value>
<text/>
</choice> </choice>
</define> </define>
<!-- <!--
DISCONNECTION TYPE DISCONNECTION TYPE
--> -->
<define name="disconnection-type"> <define name="disconnection-type">
<choice> <choice>
<value>departed</value> <value>departed</value>
<value>booted</value> <value>booted</value>
<value>failed</value> <value>failed</value>
<value>busy</value> <value>busy</value>
<text/>
</choice> </choice>
</define> </define>
</grammar> </grammar>
Authors' Addresses Authors' Addresses
Oscar Novo Oscar Novo
Ericsson Ericsson
Hirsalantie 11 Hirsalantie 11
 End of changes. 199 change blocks. 
386 lines changed or deleted 534 lines changed or added

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