draft-ietf-xcon-common-data-model-31.txt   draft-ietf-xcon-common-data-model-32.txt 
XCON O. Novo XCON O. Novo
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: December 19, 2011 D. Morgan Expires: March 23, 2012 D. Morgan
Fidelity Investments Fidelity Investments
J. Urpalainen J. Urpalainen
Nokia Nokia
Jun 17, 2011 Sep 20, 2011
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-31.txt draft-ietf-xcon-common-data-model-32.txt
Abstract Abstract
RFC5239 defines the idea of a centralized conferencing (XCON) as an RFC5239 defines the idea of a centralized conferencing (XCON) as an
association of participants with a central focus. The state of a association of participants with a central focus. The state of a
conference is represented by a conference object. This document conference is represented by a conference object. This document
defines an Extensible Markup Language (XML)-based conference defines an Extensible Markup Language (XML)-based conference
information data model to be used for conference objects. A information data model to be used for conference objects. A
conference information data model is designed to convey information conference information data model is designed to convey information
about the conference and about participation in the conference. The about the conference and about participation in the conference. The
skipping to change at page 1, line 43 skipping to change at page 1, line 43
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 19, 2011. This Internet-Draft will expire on March 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 8 skipping to change at page 3, line 8
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 7 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 8 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6
3.3. The Conference Object Identifier . . . . . . . . . . . . . 8 3.3. The Conference Object Identifier . . . . . . . . . . . . . 6
3.3.1. Conference Object URI Definition . . . . . . . . . . . 10 3.3.1. Conference Object URI Definition . . . . . . . . . . . 8
3.3.2. Normalization and Conference Object URI Comparison . . 10 3.3.2. Normalization and Conference Object URI Comparison . . 8
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 10 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 8
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 11 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 9
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 15 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13
4.2. <conference-description> . . . . . . . . . . . . . . . . . 15 4.2. <conference-description> . . . . . . . . . . . . . . . . . 13
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 16 4.2.2. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 14
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.3. <cloning-parent> . . . . . . . . . . . . . . . . . . . 14
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 16 4.2.4. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 14
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 16 4.2.5. <conference-time> . . . . . . . . . . . . . . . . . . 14
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 16 4.2.6. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 16
4.2.7. <cloning-parent> . . . . . . . . . . . . . . . . . . . 16 4.2.7. <available-media> . . . . . . . . . . . . . . . . . . 16
4.2.8. <sidebar-parent> . . . . . . . . . . . . . . . . . . . 16 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19
4.2.9. <conference-time> . . . . . . . . . . . . . . . . . . 17 4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 19
4.2.10. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 18 4.4.1. <allow-conference-event-subscription> . . . . . . . . 19
4.2.11. <service-uris> . . . . . . . . . . . . . . . . . . . . 18 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 19
4.2.12. <maximum-user-count> . . . . . . . . . . . . . . . . . 19 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 19
4.2.13. <available-media> . . . . . . . . . . . . . . . . . . 19 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 20
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 21 4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 20
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 22 4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 20
4.4.1. <allow-conference-event-subscription> . . . . . . . . 22 4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.4.2. <user-count> . . . . . . . . . . . . . . . . . . . . . 22 4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 21
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 22 4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 22
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 22 4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 22 4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 22 4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 24
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 23 4.6.5.1. <provide-anonymity> . . . . . . . . . . . . . . . 26
4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 23 4.6.5.2. <roles> . . . . . . . . . . . . . . . . . . . . . 26
4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 23 4.6.5.3. <allow-refer-users-dynamically> . . . . . . . . . 26
4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 24 4.6.5.4. <allow-invite-users-dynamically> . . . . . . . . . 26
4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 24 4.6.5.5. <allow-remove-users-dynamically> . . . . . . . . . 27
4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 25 4.6.5.6. <endpoint> . . . . . . . . . . . . . . . . . . . . 27
4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 26 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 28
4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 27 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 28
4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 27 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 29
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 29 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 39
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 29 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 29 8. Security Considerations . . . . . . . . . . . . . . . . . . . 49
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 29 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 51
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 29 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 51
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 29 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 51
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 30 9.3. Conference Object Identifier Registration . . . . . . . . 52
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 30 9.4. Conference User Identifier Registration . . . . . . . . . 53
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 30 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 30 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 32 11.1. Normative References . . . . . . . . . . . . . . . . . . . 54
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 32 11.2. Informative References . . . . . . . . . . . . . . . . . . 55
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 32 Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 55
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 43 Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 83
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 93
8. Security Considerations . . . . . . . . . . . . . . . . . . . 53
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 54
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 55
9.3. Conference Object Identifier Registration . . . . . . . . 55
9.4. Conference User Identifier Registration . . . . . . . . . 56
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 57
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 57
11.1. Normative References . . . . . . . . . . . . . . . . . . . 57
11.2. Informative References . . . . . . . . . . . . . . . . . . 58
Appendix A. Non-Normative RELAX NG Schema in XML Syntax . . . . . 58
Appendix B. Non-Normative W3C XML Schema . . . . . . . . . . . . 86
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 96
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 format. The conference information data model defined in this based format. 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
[RFC5239]. A conference object contains data that represents a [RFC5239]. The conference object represents a particular
conference during each of its various stages (e.g., created/creation, instantiation of a conference information data model. Consequently,
reserved/reservation, active/activation, completed/completion). A conference objects use the XML format defined in this document.
conference object can be manipulated using a conference control
protocol at a conference server. The conference object represents a
particular instantiation of a conference information data model.
Consequently, conference objects use the XML format defined in this
document.
A conference object contains the core information of a conference
(i.e., capabilities, membership, call control signaling, media, etc.)
and specifies by whom, and in which way, that information can be
manipulated.
Figure 1 shows the logical functional elements of a conference server
as defined by the Centralized Conferencing Framework [RFC5239]. They
are a Conference Control Server, a Floor Control Server, a number of
Foci, and a Notification Service. A conference control protocol
provides the interface between a conference control client and the
conference control server. A floor control protocol (e.g., BFCP
[RFC4582]) provides the interface between a floor control client and
the floor control server. A call signaling protocol (e.g., SIP,
H.323, Q.931, ISUP, etc.) provides the interface between a call
signaling client and a Focus. A 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 server, floor control server, and
focus can modify the information in the conference object.
...............................................................
. 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 ||| .
. | +--------------------------------------------------+||| .
. | | Conference Information Data Model |||| .
. | | +----------------------------------------------+ |||| .
. | | | Conference description (times, duration) | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Host information | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Conference state | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Floor information | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Membership (users, capacity) | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Sidebars, Etc. | |||| .
. | | +----------------------------------------------+ |||| .
. | | +----------------------------------------------+ |||| .
. | | | Etc. | |||| .
. | | +----------------------------------------------+ |||+ .
. | +--------------------------------------------------+|+ .
. +----^------------------^-------------^--------|------+ .
. | | | | .
. +------v-------+ +--------v-----+ +-----v-+ +----v-------+ .
. | Conference | | Floor | | | | | .
. | Control | | Control | |Foci | |Notification| .
. | Server | | Server | | | |Service | .
. +-----^--------+ +---^----------+ +-^-----+ +------------+ .
........|..............|..............|..........|.............
|Conference |Floor |Call |Notification
|Control |Control |Signaling |Protocol
|Protocol |Protocol |Protocol |
........v..............v..............v..........v.............
. C o n f e r e n c i n g C l i e n t .
...............................................................
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], 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 [RFC5239] (e.g., floor control). The data Conferencing Framework [RFC5239] (e.g., floor control). The data
model defined in this document constitutes a superset of the data model defined in this document constitutes a superset of the data
format defined in [RFC4575]. The result is a data format that format defined in [RFC4575]. The result is a data format that
supports more call signaling protocols besides SIP and that covers supports more call signaling protocols besides SIP and that covers
all the functionality defined in the Centralized Conferencing all the functionality defined in the Centralized Conferencing
skipping to change at page 8, line 30 skipping to change at page 6, line 45
service or through out-of-band mechanisms (e.g. E-Mail). service or through out-of-band mechanisms (e.g. E-Mail).
A conferencing system may maintain a relationship between the A conferencing system may maintain a relationship between the
conference object identifiers and the identifiers associated with conference object identifiers and the identifiers associated with
each of the complementary centralized conferencing protocols (e.g., each of the complementary centralized conferencing protocols (e.g.,
call signaling protocols, BFCP, etc.). To facilitate the maintenance call signaling protocols, BFCP, etc.). To facilitate the maintenance
of these relationships, the conference object identifier acts as a of these relationships, the conference object identifier acts as a
top level identifier within the conferencing system for the purpose top level identifier within the conferencing system for the purpose
of identifying the interfaces for these other protocols. This of identifying the interfaces for these other protocols. This
implicit binding provides a structured mapping of the various implicit binding provides a structured mapping of the various
protocols with the associated conference object Identifier. Figure 2 protocols with the associated conference object Identifier. Figure 1
illustrates the relationship between the identifiers used for the illustrates the relationship between the identifiers used for the
protocols and the general conference object identifier (XCON-URI). protocols and the general conference object identifier (XCON-URI).
+--------------------------+ +--------------------------+
| Conference | | Conference |
| Object | | Object |
| Identifier | | Identifier |
+--------------------------+ +--------------------------+
| xcon:Ji092i@example.com | | xcon:Ji092i@example.com |
+------+-------------------+ +------+-------------------+
skipping to change at page 9, line 30 skipping to change at page 7, line 30
| h323:i092@example.com | | i092 | | h323:i092@example.com | | i092 |
| tel:+44(0)2920930033 | +----------+---------+ | tel:+44(0)2920930033 | +----------+---------+
| sip:i092@example.com | | | sip:i092@example.com | |
+-----------------------+ +-------+--------+ +-----------------------+ +-------+--------+
| BFCP 'Floor ID'| | BFCP 'Floor ID'|
+----------------+ +----------------+
| 543 | | 543 |
| 236 | | 236 |
+----------------+ +----------------+
Figure 2: Conference Object Mapping Figure 1: Conference Object Mapping
In Figure 2, the conference object identifier acts as the top level In Figure 1, 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 form of URIs. The binary floor control protocol, as defined in
[RFC4582], defines the 'conference ID' identifier which represents a [RFC4582], defines the 'conference ID' identifier which represents a
conference instance within floor control. When created within the conference instance within floor control. When created within the
conferencing system, the 'conference ID' has a 1:1 mapping to the conferencing system, the 'conference ID' has a 1:1 mapping to the
unique conference object Identifier(XCON-URI). Operations associated unique conference object Identifier(XCON-URI). Operations associated
with the conference control protocols are directly associated with with the conference control protocols are directly associated with
the conference object, thus the primary identifier associated with the conference object, thus the primary identifier associated with
these 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 1
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 Object URI Definition 3.3.1. Conference Object URI Definition
XCON-URI = "xcon" ":" [conf-object-id "@"] host XCON-URI = "xcon" ":" [conf-object-id "@"] host
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host and unreserved are defined in RFC3986[RFC3986] host and unreserved are defined in RFC3986[RFC3986]
skipping to change at page 15, line 19 skipping to change at page 13, line 19
| |--<entry> | |--<entry>
| | | | | |
| ... ... | ... ...
The following sections describe these elements in detail. The full The following sections describe these elements in detail. The full
Relax NG schema is provided in Section 5. Relax NG schema is provided in Section 5.
4.1. <conference-info> 4.1. <conference-info>
A conference object document begins with the root element A conference object document begins with the root element
<conference-info>, which is defined in [RFC4575]. The attributes of <conference-info>, which is defined in [RFC4575]. The 'state' and
the <conference-info> element are also defined in [RFC4575]. 'version' attributes of the <conference-info> element are defined in
However, when the <conference-info> element is used in the context of [RFC4575] and are not used in the context of the XCON Conference
the XCON Conference Information Model, the 'state' and 'version' Information Model since they apply only to notification mechanisms.
attributes defined in [RFC4575] are not used, since they apply only
to notification mechanisms.
In addition, [RFC4575] defines an 'entity' attribute that contains In addition, [RFC4575] defines an 'entity' attribute that contains
the conference object identifier (XCON-URI) that identifies the the SIP URI identifier. This especification extends the meaning of
conference being described in the document. the 'entity' attribute to the conference object identifier (XCON-URI)
explained in Section 3.3.
The <conference-info> element contains the <conference-description>, This specification adds to the <conference-info> element the <floor-
<host-info>, <conference-state>, <floor-information>, <users>, information> child elements.
<sidebars-by-ref>, and <sidebars-by-val> child elements. All these
elements, except <floor-information>, are defined in [RFC4575]. A
conference document MUST at least include the <conference-
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],
describes the conference as a whole. It SHOULD have an attribute describes the conference as a whole. It SHOULD have an attribute
'lang' to specify the language used in the contents of this element. 'lang' to specify the language used in the contents of this element.
It is comprised of <language>, <display-text>, <subject>, <free- It is comprised of <language>, <display-text>, <subject>, <free-
text>, <keywords>, <allow-sidebars>, <cloning-parent>, <sidebar- text>, <keywords>, <allow-sidebars>, <cloning-parent>, <sidebar-
parent>, <conference-time>, <conf-uris>, <service-uris>, <maximum- parent>, <conference-time>, <conf-uris>, <service-uris>, <maximum-
user-count>, and <available-media>. user-count>, and <available-media>. The <display-text>, <subject>,
<free-text>, <keywords>, <service-uris>,and <maximum-user-count>
elements are described in section 5.3 of [RFC4575].
The following sections describe these elements in more detail. Other The following sections describe these elements in more detail. Other
child elements MAY be defined in the future to extend the child elements MAY be defined in the future to extend the
<conference-description> element. <conference-description> element.
4.2.1. <language> 4.2.1. <language>
The <language> element indicates the predominant language that is The <language> element indicates the predominant language that is
expected to be employed within a conference. This element contains expected to be employed within a conference. This element contains
only one language. The possible values of this element are the only one language. The possible values of this element are the
values of the 'Subtag' column of the [RFC5646] defined in [IANA-Lan]. values of the 'Subtag' column of the [RFC5646] defined in [IANA-Lan].
This element does not enforce the language of the conference, but This element does not enforce the language of the conference, but
only informs the participants about the desirable language that they only informs the participants about the desirable language that they
should use in the conference. Participants are free to switch to should use in the conference. Participants are free to switch to
other languages if they like. other languages if they like.
4.2.2. <display-text> 4.2.2. <allow-sidebars>
The <display-text> element is described in section 5.3 of [RFC4575].
4.2.3. <subject>
The <subject> element is described in section 5.3 of [RFC4575].
4.2.4. <free-text>
The <free-text> element is described in section 5.3 of [RFC4575].
4.2.5. <keywords>
The <keywords> element is described in section 5.3 of [RFC4575].
4.2.6. <allow-sidebars>
The <allow-sidebars> element represents a boolean value. If set to The <allow-sidebars> element represents a boolean value. If set to
"true" or "1", the conference is allowed to create sidebar "true" or "1", the conference is allowed to create sidebar
conferences. If absent, or set to "false" or "0", the conference can conferences. If absent, or set to "false" or "0", the conference can
not create sidebar conferences. not create sidebar conferences.
4.2.7. <cloning-parent> 4.2.3. <cloning-parent>
When the <cloning-parent> is present, it indicates that the When the <cloning-parent> is present, it indicates that the
conference object is a child of a parent conference. The <cloning- conference object is a child of a parent conference. The <cloning-
parent> element contains the conference object Identifier (XCON-URI) parent> element contains the conference object Identifier (XCON-URI)
(different from the main XCON-URI) of the parent. (different from the main XCON-URI) of the parent.
4.2.8. <sidebar-parent> 4.2.4. <sidebar-parent>
When the <sidebar-parent> is present, it indicates that the When the <sidebar-parent> is present, it indicates that the
conference object represents a sidebar of another conference. The conference object represents a sidebar of another conference. The
<sidebar-parent> element contains the conference object Identifier <sidebar-parent> element contains the conference object Identifier
(XCON-URI) (different from the main XCON-URI) of the parent. (XCON-URI) (different from the main XCON-URI) of the parent.
4.2.9. <conference-time> 4.2.5. <conference-time>
The <conference-time> element contains the information related to The <conference-time> element contains the information related to
conference time, policy, and duration of a conference. The conference time, policy, and duration of a conference. The
<conference-time> element contains one or more <entry> elements each <conference-time> element contains one or more <entry> elements each
defining the time and policy information specifying a single defining the time and policy information specifying a single
conference occurrence. The <conference-time> element differs from conference occurrence. The <conference-time> element differs from
the iCalendar objects [RFC5545] in the possibility to define the iCalendar objects [RFC5545] in the possibility to define
different policies (<can-join-after-offset>, <must-join-before- different policies (<can-join-after-offset>, <must-join-before-
offset>) for the same conference at different times. offset>) for the same conference at different times.
skipping to change at page 18, line 30 skipping to change at page 16, line 16
defines in seconds when the system MUST send a notification when defines in seconds when the system MUST send a notification when
the end of the conference is approaching. If the <notify-end-of- the end of the conference is approaching. If the <notify-end-of-
conference> element is not present, it indicates that the system conference> element is not present, it indicates that the system
does not notify the users when the end of the conference is does not notify the users when the end of the conference is
approaching. approaching.
o <allowed-extend-mixing-end-offset>: The <allowed-extend-mixing- o <allowed-extend-mixing-end-offset>: The <allowed-extend-mixing-
end-offset> element indicates if the conference is allowed to be end-offset> element indicates if the conference is allowed to be
extended. It has a boolean value. extended. It has a boolean value.
4.2.10. <conf-uris> 4.2.6. <conf-uris>
The <conf-uris> element contains the identifiers to be used in order The <conf-uris> contains a set of <entry> child elements - each
to access the conference by different signaling means. This element containing a new element, <conference-password>. This element
contains a set of <entry> child elements - each containing a new contains the password(s) of the conference, for instance, PSTN
element, <conference-password>. This element contains the conference will store the 'PIN code' in this element. All the other
password(s) of the conference, for instance, PSTN conference will <conf-uris> child element are described in section 5.3.1 of
store the 'PIN code' in this element. All the other <conf-uris> [RFC4575].
child element are described in section 5.3.1 of [RFC4575].
The schema in Section 5 allows <conference-password> to appear The schema in Section 5 allows <conference-password> to appear
anywhere uris-type is expanded. This document only provides meaning anywhere uris-type is expanded. This document only provides meaning
for <conference-password> appearing as a descendent of the <conf- for <conference-password> appearing as a descendent of the <conf-
uris> element. Future standardization may give meaning to uris> element. Future standardization may give meaning to
<conference-password> appearing in other elements of type uris-type. <conference-password> appearing in other elements of type uris-type.
In the absence of such standardization, <conference-password> MUST In the absence of such standardization, <conference-password> MUST
NOT appear in elements of type uris-type other than <conf-uris>. NOT appear in elements of type uris-type other than <conf-uris>.
4.2.11. <service-uris> 4.2.7. <available-media>
The <service-uris> describes auxiliary services available for the
conference. The <service-uris> element is described in section 5.3.2
of [RFC4575].
4.2.12. <maximum-user-count>
The <maximum-user-count> contains the overall number of users allowed
to join the conference. Note that this value is typically set by an
administrator and can reflect any local policies such as network
consumption, CPU processing power, and licensing rules.
4.2.13. <available-media>
The <available-media> element consists of a sequence of <entry> child The <available-media> element consists of a sequence of <entry> child
elements. Each <entry> element contain the 'label' attribute that is elements. Each <entry> element MAY contain the following child
the media stream identifier assigned by the conferencing server. The elements:
attribute 'label' is described in [RFC4575], section 5.3.4. Each
<entry> element MAY contain the following child elements:
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
[RFC4575].
o The <status> element is described in section 5.3.4 of [RFC4575]. o The <type>, <display-text>, and <status> elements are described in
section 5.3.4 of [RFC4575].
o The child element <mixing-mode> describes a default scheduling o The child element <mixing-mode> describes a default scheduling
policy by which the mixer will build the outgoing stream from the policy by which the mixer will build the outgoing stream from the
incoming streams. Note that this policy is different than the incoming streams. Note that this policy is different than the
policy describing the floors for each media. The <mixing-mode> policy describing the floors for each media. The <mixing-mode>
child element MUST contain one and only one of the "Moderator- child element MUST contain one and only one of the "Moderator-
controlled", "FCFS", and "Automatic" values, indicating the controlled", "FCFS", and "Automatic" values, indicating the
default algorithm to use with every media stream. The "Moderator- default 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
skipping to change at page 21, line 49 skipping to change at page 19, line 11
+ multiple-5x1: This option refers to a 5x1 layout where one + multiple-5x1: This option refers to a 5x1 layout where one
panel will occupy 4/9 of the mixed video stream while the panel will occupy 4/9 of the mixed video stream while the
others will each occupy 1/9 of the stream. Typically the others will each occupy 1/9 of the stream. Typically the
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 conference. This information is usually set before conference
activation, and is rarely changed during the conference lifetime.
The <host-info> element and its child elements are described in The <host-info> element and its child elements are described in
[RFC4575], section 5.4.
[RFC4575], section 5.4. Future extensions to the <host-info> element
may define new values.
4.4. <conference-state> 4.4. <conference-state>
The <conference-state> is introduced in [RFC4575]. The <conference- The <conference-state> is introduced in [RFC4575]. The <conference-
state> element contains the <allow-conference-event-subscription>, state> element contains the <allow-conference-event-subscription>,
<user-count>, <active>, and <locked> child elements. <user-count>, <active>, and <locked> child elements. The <user-
count>, <active>, and <locked> child elements are defined in
[RFC4575], section 5.5.
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 'SIP Event Package subscription to conference state events, such as 'SIP Event Package
for Conference State' [RFC4575]. If set to FALSE, the subscription for Conference State' [RFC4575]. If set to FALSE, the subscription
to conference state events MUST be rejected. If this element is to conference state events MUST be rejected. If this element is
undefined it has a default value of TRUE, causing the subscription to undefined it has a default value of TRUE, causing the subscription to
conference state events to be accepted. conference state events to be accepted.
4.4.2. <user-count>
The <user-count> child element is explained in [RFC4575], section
5.5.1.
4.4.3. <active>
The <active> child element is explained in [RFC4575], section 5.5.2.
4.4.4. <locked>
The <locked> child element is explained in [RFC4575], section 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. The absence of this element from an XML policy> child elements. The absence of this element from an XML
document indicates that the conference does not have a floor. document indicates that the conference does not have a floor.
4.5.1. <conference-ID> 4.5.1. <conference-ID>
The <conference-ID> represents a conference instance within floor The <conference-ID> represents a conference instance within floor
skipping to change at page 26, line 27 skipping to change at page 23, line 27
these lists must provide clear guidance on how to process the lists these lists must provide clear guidance on how to process the lists
when they occur concurrently, especially when both lists contain the when they occur concurrently, especially when both lists contain the
same user. For example, such specification could disallow both list same user. For example, such specification could disallow both list
from appearing at the same time similar to user-admission-policy from appearing at the same time similar to user-admission-policy
values defined in this document. values defined in this document.
4.6.3. <allowed-users-list> 4.6.3. <allowed-users-list>
The <allowed-users-list> child element contains a list of user URIs The <allowed-users-list> child element contains a list of user URIs
(e.g. xcon-userid defined in Section 4.6.5), roles (defined in (e.g. xcon-userid defined in Section 4.6.5), roles (defined in
Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus Section 4.6.5.2), or domains (e.g.: *@example.com) that the focus
uses to determine who can join the conference, who can be invited to uses to determine who can join the conference, who can be invited to
join a conference, or who the focus needs to "refer to" the join a conference, or who the focus needs to "refer to" the
conference. The <allowed-users-list> element includes zero or more conference. The <allowed-users-list> element includes zero or more
<target> child elements. This child element includes the mandatory <target> child elements. This child element includes the mandatory
'uri' attribute and the mandatory 'method' attribute. The same 'uri' 'uri' attribute and the mandatory 'method' attribute. The same 'uri'
attribute with different method values can appear in the list more attribute with different method values can appear in the list more
than once. than once.
The 'method' attribute is a list with the following values: The 'method' attribute is a list with the following values:
skipping to change at page 27, line 32 skipping to change at page 24, line 32
element. Future extensions to this schema may define new elements element. Future extensions to this schema may define new elements
for the <user> element. 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
(e.g. SIP URI, xcon-userid defined in Section 4.6.5), roles (defined (e.g. SIP URI, xcon-userid defined in Section 4.6.5), roles (defined
in Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus in Section 4.6.5.2), or domains (e.g.: *@example.com) that the focus
uses to determine who has been 'banned' from the conference. Such uses to determine who has been 'banned' from the conference. Such
banned users are prevented from re-joining the chatroom until they banned users are prevented from re-joining the chatroom until they
have been un-banned. have been un-banned.
4.6.5. <user> and Its <user> Sub-elements 4.6.5. <user> and Its <user> Sub-elements
The element <user> is described in [RFC4575] and describes a single The element <user> is described in [RFC4575] and describes a single
participant in the conference. The <user> element has an attribute participant in the conference. The <user> element has an attribute
'entity'. However, when the <user> element is used in the context of 'entity'. However, when the <user> element is used in the context of
the XCON Conference Information Model, the 'state' and 'version' the XCON Conference Information Model, the 'state' and 'version'
skipping to change at page 28, line 20 skipping to change at page 25, line 20
In order to facilitate the comparison of the XCON-USERID identifiers, In order to facilitate the comparison of the XCON-USERID identifiers,
all the components of the identifiers MUST be converted to lowercase. all the components of the identifiers MUST be converted to lowercase.
After normalizing the URI strings, the URIs comparison MUST applied a After normalizing the URI strings, the URIs comparison MUST applied a
codepoint-by-codepoint after conversion to a common character codepoint-by-codepoint after conversion to a common character
encoding as prescribed by [RFC3986], Section 6.2.1. encoding as prescribed by [RFC3986], Section 6.2.1.
Other user identifiers can be associated with this conference user Other user identifiers can be associated with this conference user
identifier and enable the conferencing system to correlate and map identifier and enable the conferencing system to correlate and map
these multiple authenticated user identities to a single global user these multiple authenticated user identities to a single global user
identifier. Figure 3 illustrates an example using the conference identifier. Figure 2 illustrates an example using the conference
user identifier in association with the user identity defined for user identifier in association with the user identity defined for
BFCP, SIP, and H323 user identity. It should be noted that a BFCP, SIP, and H323 user identity. It should be noted that a
conferencing system is free to structure such relationships as conferencing system is free to structure such relationships as
required and this information is just included as a guideline. required and this information is just included as a guideline.
+----------------+ +----------------+
| Conference | | Conference |
| User | | User |
| Identifier | | Identifier |
+----------------+ +----------------+
skipping to change at page 28, line 44 skipping to change at page 25, line 44
| |
| |
+----------------------+-------------------------+ +----------------------+-------------------------+
| | | | | |
+-------+--------+ +-----------+-----------+ +-----------+-----------+ +-------+--------+ +-----------+-----------+ +-----------+-----------+
| BFCP User ID | | SIP User URI | | H323 User URI | | BFCP User ID | | SIP User URI | | H323 User URI |
+----------------+ +-----------------------+ +-----------------------+ +----------------+ +-----------------------+ +-----------------------+
| 543 | |sip:851221@example.com | |h323:taeduk@example.com| | 543 | |sip:851221@example.com | |h323:taeduk@example.com|
+----------------+ +-----------------------+ +-----------------------+ +----------------+ +-----------------------+ +-----------------------+
Figure 3: Conference User Mapping Figure 2: Conference User 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. The <display-text>,
<associated-aors>, <languages>, and <cascaded-focus> are defined in
4.6.5.1. <display-text> in [RFC4575], section 5.6.
The <display-text> child element is explained in [RFC4575], section
5.6.1.
4.6.5.2. <associated-aors>
The <associated-aors> child element is explained in [RFC4575],
section 5.6.2.
4.6.5.3. <provide-anonymity> 4.6.5.1. <provide-anonymity>
The <provide-anonymity> element specifies what level of anonymity the The <provide-anonymity> element specifies what level of anonymity the
server should provide to the user. In this case, the focus provides server should provide to the user. In this case, the focus provides
to the rest of the participants an anonymous identity for that user, to the rest of the participants an anonymous identity for that user,
for example anonymousX, or it does not provide any information for for example anonymousX, or it does not provide any information for
that user such that other users can not see he is a participant in that user such that other users can not see he is a participant in
the conference. This element only affects the way the user the conference. This element only affects the way the user
information is provided to the other participants. The real user information is provided to the other participants. The real user
information is stored in the data model but SHOULD NOT be provided to information is stored in the data model but SHOULD NOT be provided to
the other participants of the conference. This can be achieved by the other participants of the conference. This can be achieved by
using the <provide-anonymity> element. This element has three using the <provide-anonymity> element. This element has three
values: 'private', 'semi-private' and 'hidden'. The 'private' value values: 'private', 'semi-private' and 'hidden'. The 'private' value
specifies that this user is completely anonymous in the conference. specifies that this user is completely anonymous in the conference.
'semi-private' value specifies that this user is anonymous to all 'semi-private' value specifies that this user is anonymous to all
users who have not been granted permission to see him. 'hidden' value users who have not been granted permission to see him. 'hidden' value
specifies that other users can not see this participant in the specifies that other users can not see this participant in the
conference. conference.
4.6.5.4. <roles> 4.6.5.2. <roles>
A role provides the context for the set of conference operations that A role provides the context for the set of conference operations that
a participant can perform. This element can contain one or more of a participant can perform. This element can contain one or more of
the following values: "administrator", "moderator", "user", the following values: "administrator", "moderator", "user",
"participant", "observer", and "none". A role of "none" indicates "participant", "observer", and "none". A role of "none" indicates
that any role is assigned; The roles semantic definition is out of that any role is assigned; The roles semantic definition is out of
the scope of this document and is subject to future policy documents. the scope of this document and is subject to future policy documents.
This element can be extended with new roles in future documents. This element can be extended with new roles in future documents.
4.6.5.5. <languages> 4.6.5.3. <allow-refer-users-dynamically>
The <languages> child element is explained in [RFC4575], section
5.6.4.
4.6.5.6. <cascaded-focus>
The <cascaded-focus> child element is explained in [RFC4575], section
5.6.5.
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
value. If set to TRUE, a participant is allowed to instruct the value. If set to TRUE, a participant is allowed to instruct the
focus to refer a user to the conference without modifying the focus to refer a user to the conference without modifying the
<allowed-users-list> (in SIP terms, a participant is allowed to send <allowed-users-list> (in SIP terms, a participant is allowed to send
a REFER request [RFC3515] to the focus which results in the focus a REFER request [RFC3515] to the focus which results in the focus
sending a REFER request to the user the referrer wishes to join the sending a REFER request to the user the referrer wishes to join the
conference). If set to FALSE, the refer request is rejected. If conference). If set to FALSE, the refer request is rejected. If
this element is undefined it has a value of FALSE, causing the refer this element is undefined it has a value of FALSE, causing the refer
to be rejected. to be rejected.
4.6.5.8. <allow-invite-users-dynamically> 4.6.5.4. <allow-invite-users-dynamically>
The <allow-invite-users-dynamically> element represents a boolean The <allow-invite-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 invite a user to the conference without modifying the focus to invite a user to the conference without modifying the
<allowed-users-list> list (in SIP terms, a participant is allowed to <allowed-users-list> list (in SIP terms, a participant is allowed to
send a REFER request [RFC3515] to the focus which results in the send a REFER request [RFC3515] to the focus which results in the
focus sending an INVITE request to the user the referrer wishes to focus sending an INVITE request to the user the referrer wishes to
join the conference). If set to FALSE, the refer request is join the conference). If set to FALSE, the refer request is
rejected. If this element is undefined it has a value of FALSE, rejected. If this element is undefined it has a value of FALSE,
causing the refer to be rejected. causing the refer to be rejected.
4.6.5.9. <allow-remove-users-dynamically> 4.6.5.5. <allow-remove-users-dynamically>
The <allow-remove-users-dynamically> element represents a boolean The <allow-remove-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 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 [RFC3515] to the focus which results in the focus sending an request [RFC3515] to the focus which results in the focus sending an
BYE request to the user the referrer wishes to leave the conference). BYE request to the user the referrer wishes to leave the conference).
If set to FALSE, the refer request is rejected. If this element is If set to FALSE, the refer request is rejected. If this element is
undefined it has a value of FALSE, causing the refer to be rejected. undefined it has a value of FALSE, causing the refer to be rejected.
4.6.5.10. <endpoint> 4.6.5.6. <endpoint>
The <endpoint> child element is identical to the element with the The <endpoint> child element is identical to the element with the
same name in [RFC4575] except that the 'state' attribute is not same name in [RFC4575] except that the 'state' attribute is not
included. When the <endpoint> element is used in the context of the included. When the <endpoint> element is used in the context of the
XCON Conference Information Model, the 'state' and 'version' XCON Conference Information Model, the 'state' and 'version'
attributes defined in [RFC4575] are not used, since they apply only attributes defined in [RFC4575] are not used, since they apply only
to notification mechanisms. The <endpoint> element can provide the to notification mechanisms. The <endpoint> element can provide the
desired level of detail about the user's devices and their signaling desired level of detail about the user's devices and their signaling
sessions taking part in the conference. sessions taking part in the conference.
skipping to change at page 33, line 9 skipping to change at page 29, line 39
& element host-info { host-type }? & element host-info { host-type }?
& element conference-state { conference-state-type }? & element conference-state { conference-state-type }?
& element users { users-type }? & element users { users-type }?
& element sidebars-by-ref { uris-type }? & element sidebars-by-ref { uris-type }?
& element sidebars-by-val { sidebars-by-val-type }? & element sidebars-by-val { sidebars-by-val-type }?
& element xcon:floor-information { floor-information-type }? & element xcon:floor-information { floor-information-type }?
& anyElement* & anyElement*
# CONFERENCE DESCRIPTION TYPE # CONFERENCE DESCRIPTION TYPE
conference-description-type = conference-description-type =
element conference-description { element conference-description {
attribute lang { xsd:language }? attribute xml:lang { xsd:language }?
& anyAttribute & anyAttribute
& element display-text { text }? & element display-text { text }?
& element subject { text }? & element subject { text }?
& element free-text { text }? & element free-text { text }?
& element keywords { & element keywords {
list { xsd:string* } list { xsd:string* }
}? }?
& element conf-uris { uris-type }? & element conf-uris { uris-type }?
& element service-uris { uris-type }? & element service-uris { uris-type }?
& element maximum-user-count { xsd:int }? & element maximum-user-count { xsd:int }?
skipping to change at page 42, line 47 skipping to change at page 39, line 29
element * { element * {
(attribute * { text } (attribute * { text }
| text | text
| any)* | any)*
} }
# EXTENSIBILITY ATTRIBUTES # EXTENSIBILITY ATTRIBUTES
# #
anyAttribute = anyAttribute =
attribute * - (lang attribute * - (xml:lang
| entity | entity
| required-participant | required-participant
| label | label
| decision | decision
| name | name
| policy | policy
| uri | uri
| method | method
| id | id
| nickname) { text }* | nickname) { text }*
skipping to change at page 43, line 43 skipping to change at page 40, line 27
moment, Alice is assigned to use the floor. moment, Alice is assigned to use the floor.
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<conference-info <conference-info
xmlns="urn:ietf:params:xml:ns:conference-info" xmlns="urn:ietf:params:xml:ns:conference-info"
xmlns:xcon="urn:ietf:params:xml:ns:xcon-conference-info" xmlns:xcon="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 xml:lang="en-us">
<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>
<!-- <!--
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>
<xcon:conference-password <xcon:conference-password
>5678</xcon:conference-password> >5678</xcon:conference-password>
</entry> </entry>
skipping to change at page 54, line 46 skipping to change at page 51, line 30
<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
in Section 5. Its first line is in Section 5. Its first line is
default namespace = "urn:ietf:params:xml:ns:conference-info" default namespace = "urn:ietf:params:xml:ns:conference-info"
and its last line is and its last line is
anyAttribute = attribute * - (lang | entity anyAttribute = attribute * - (xml:lang | entity
| required-participant | label | decision | name | required-participant | label | decision | name
| policy | uri | method | id | nickname) { text }* | policy | uri | method | id | nickname) { text }*
9.2. XML Namespace Registration 9.2. XML Namespace Registration
This section registers a new XML namespace. This section registers a new XML namespace.
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>
XML: XML:
skipping to change at page 58, line 21 skipping to change at page 55, line 21
"IANA Language Subtag Registry" "IANA Language Subtag Registry"
"http://www.iana.org/assignments/ "http://www.iana.org/assignments/
language-subtag-registry". language-subtag-registry".
[RELAX] "RELAX NG Home Page" "ISO/IEC 19757-2:2008". [RELAX] "RELAX NG Home Page" "ISO/IEC 19757-2:2008".
[RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model [RFC3264] Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
with Session Description Protocol (SDP)", RFC 3264, with Session Description Protocol (SDP)", RFC 3264,
June 2002. June 2002.
[RFC3265] Roach, A., "Session Initiation Protocol (SIP)-Specific
Event Notification", RFC 3265, June 2002.
[RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer [RFC3515] Sparks, R., "The Session Initiation Protocol (SIP) Refer
Method", RFC 3515, April 2003. Method", RFC 3515, April 2003.
[RFC4353] Rosenberg, J., "A Framework for Conferencing with the [RFC4353] Rosenberg, J., "A Framework for Conferencing with the
Session Initiation Protocol (SIP)", RFC 4353, Session Initiation Protocol (SIP)", RFC 4353,
February 2006. February 2006.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[RFC5018] Camarillo, G., "Connection Establishment in the Binary [RFC5018] Camarillo, G., "Connection Establishment in the Binary
Floor Control Protocol (BFCP)", RFC 5018, September 2007. Floor Control Protocol (BFCP)", RFC 5018, September 2007.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[W3C.REC-xml-20081126] [W3C.REC-xml-20081126]
Maler, E., Yergeau, F., Sperberg-McQueen, C., Paoli, J., Sperberg-McQueen, C., Yergeau, F., Bray, T., Paoli, J.,
and T. Bray, "Extensible Markup Language (XML) 1.0 (Fifth and E. Maler, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", World Wide Web Consortium Recommendation REC- Edition)", World Wide Web Consortium Recommendation REC-
xml-20081126, November 2008, xml-20081126, November 2008,
<http://www.w3.org/TR/2008/REC-xml-20081126>. <http://www.w3.org/TR/2008/REC-xml-20081126>.
Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. Non-Normative RELAX NG Schema in XML Syntax
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<grammar <grammar
ns="urn:ietf:params:xml:ns:conference-info" ns="urn:ietf:params:xml:ns:conference-info"
xmlns="http://relaxng.org/ns/structure/1.0" xmlns="http://relaxng.org/ns/structure/1.0"
skipping to change at page 60, line 19 skipping to change at page 57, line 16
</zeroOrMore> </zeroOrMore>
</interleave> </interleave>
</define> </define>
<!-- <!--
CONFERENCE DESCRIPTION TYPE CONFERENCE DESCRIPTION TYPE
--> -->
<define name="conference-description-type"> <define name="conference-description-type">
<element name="conference-description"> <element name="conference-description">
<interleave> <interleave>
<optional> <optional>
<attribute name="lang"> <attribute name="xml:lang">
<data type="language"/> <data type="language"/>
</attribute> </attribute>
</optional> </optional>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<optional> <optional>
<element name="display-text"> <element name="display-text">
<text/> <text/>
</element> </element>
</optional> </optional>
<optional> <optional>
skipping to change at page 91, line 4 skipping to change at page 87, line 48
</xs:complexType> </xs:complexType>
<!-- GAIN TYPE --> <!-- GAIN TYPE -->
<xs:simpleType name="gain-type"> <xs:simpleType name="gain-type">
<xs:restriction base="xs:integer"> <xs:restriction base="xs:integer">
<xs:minInclusive value="-127"/> <xs:minInclusive value="-127"/>
<xs:maxInclusive value="127"/> <xs:maxInclusive value="127"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<!-- VIDEO LAYOUT TYPE -->
<!-- VIDEO LAYOUT TYPE -->
<xs:simpleType name="video-layout-type"> <xs:simpleType name="video-layout-type">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="single-view"/> <xs:pattern value="single-view"/>
<xs:pattern value="dual-view"/> <xs:pattern value="dual-view"/>
<xs:pattern value="dual-view-crop"/> <xs:pattern value="dual-view-crop"/>
<xs:pattern value="dual-view-2x1"/> <xs:pattern value="dual-view-2x1"/>
<xs:pattern value="dual-view-2x1-crop"/> <xs:pattern value="dual-view-2x1-crop"/>
<xs:pattern value="quad-view"/> <xs:pattern value="quad-view"/>
<xs:pattern value="multiple-3x3"/> <xs:pattern value="multiple-3x3"/>
<xs:pattern value="multiple-4x4"/> <xs:pattern value="multiple-4x4"/>
 End of changes. 49 change blocks. 
284 lines changed or deleted 121 lines changed or added

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