draft-ietf-xcon-common-data-model-09.txt   draft-ietf-xcon-common-data-model-10.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: August 25, 2008 D. Morgan Expires: September 29, 2008 D. Morgan
Fidelity Investments Fidelity Investments
R. Even R. Even
Polycom Polycom
February 22, 2008 March 28, 2008
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-09.txt draft-ietf-xcon-common-data-model-10.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 August 25, 2008. This Internet-Draft will expire on September 29, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines an Extensible Markup Language (XML)-based This document defines an Extensible Markup Language (XML)-based
conference information data model for centralized conferencing conference information data model for centralized conferencing
(XCON). A conference information data model is designed to convey (XCON). A conference information data model is designed to convey
information about the conference and about participation in the information about the conference and about participation in the
conference. The conference information data model defined in this conference. The conference information data model defined in this
document constitutes an extension of the data format specified in the document constitutes an extension of the data format specified in the
Session Initiation Protocol (SIP) Event Package for Conference State. Session Initiation Protocol (SIP) Event Package for Conference State.
skipping to change at page 2, line 25 skipping to change at page 2, line 22
3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 3.3. The Conference Object Identifier . . . . . . . . . . . . . 7
3.3.1. Conference Object URI Definition . . . . . . . . . . . 9 3.3.1. Conference Object URI Definition . . . . . . . . . . . 9
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13
4.2. <conference-description> . . . . . . . . . . . . . . . . . 14 4.2. <conference-description> . . . . . . . . . . . . . . . . . 14
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 14 4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 14
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 15
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15
4.2.7. <conference-time> . . . . . . . . . . . . . . . . . . 15 4.2.7. <conference-time> . . . . . . . . . . . . . . . . . . 15
4.2.8. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 16 4.2.8. <conf-uris> . . . . . . . . . . . . . . . . . . . . . 16
4.2.9. <service-uris> . . . . . . . . . . . . . . . . . . . . 16 4.2.9. <service-uris> . . . . . . . . . . . . . . . . . . . . 16
4.2.10. <maximum-user-count> . . . . . . . . . . . . . . . . . 17 4.2.10. <maximum-user-count> . . . . . . . . . . . . . . . . . 17
4.2.11. <available-media> . . . . . . . . . . . . . . . . . . 17 4.2.11. <available-media> . . . . . . . . . . . . . . . . . . 17
4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19 4.3. <host-info> . . . . . . . . . . . . . . . . . . . . . . . 19
4.4. <conference-state> . . . . . . . . . . . . . . . . . . . . 19 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> . . . . . . . . . . . . . . . . . . . . . 20
4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.3. <active> . . . . . . . . . . . . . . . . . . . . . . . 20
4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20 4.4.4. <locked> . . . . . . . . . . . . . . . . . . . . . . . 20
4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20 4.5. <floor-information> . . . . . . . . . . . . . . . . . . . 20
4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20 4.5.1. <conference-ID> . . . . . . . . . . . . . . . . . . . 20
4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 20 4.5.2. <allow-floor-events> . . . . . . . . . . . . . . . . . 20
4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 20 4.5.3. <floor-request-handling> . . . . . . . . . . . . . . . 21
4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21 4.5.4. <conference-floor-policy> . . . . . . . . . . . . . . 21
4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22 4.6. <users> . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22 4.6.1. <join-handling> . . . . . . . . . . . . . . . . . . . 22
4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 22 4.6.2. <user-admission-policy> . . . . . . . . . . . . . . . 22
4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23 4.6.3. <allowed-users-list> . . . . . . . . . . . . . . . . . 23
4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24 4.6.4. <deny-users-list> . . . . . . . . . . . . . . . . . . 24
4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 24 4.6.5. <user> and Its <user> Sub-elements . . . . . . . . . . 24
4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 25 4.6.5.1. <display-text> . . . . . . . . . . . . . . . . . . 25
4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 25 4.6.5.2. <associated-aors> . . . . . . . . . . . . . . . . 25
4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 25 4.6.5.3. <provide-anonymity> . . . . . . . . . . . . . . . 26
4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26 4.6.5.4. <roles> . . . . . . . . . . . . . . . . . . . . . 26
4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 26 4.6.5.5. <languages> . . . . . . . . . . . . . . . . . . . 26
4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 26 4.6.5.6. <cascaded-focus> . . . . . . . . . . . . . . . . . 26
4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 26 4.6.5.7. <allow-refer-users-dynamically> . . . . . . . . . 26
4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 26 4.6.5.8. <allow-invite-users-dynamically> . . . . . . . . . 27
4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27 4.6.5.9. <allow-remove-users-dynamically> . . . . . . . . . 27
4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 27 4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 27
4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 28 4.7. <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 28
4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 28 4.8. <sidebars-by-val> . . . . . . . . . . . . . . . . . . . . 28
5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 28 5. RELAX NG Schema . . . . . . . . . . . . . . . . . . . . . . . 28
6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 36 6. XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 38
7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 36 7. XML Example . . . . . . . . . . . . . . . . . . . . . . . . . 38
8. Security Considerations . . . . . . . . . . . . . . . . . . . 45 8. Security Considerations . . . . . . . . . . . . . . . . . . . 47
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 45 8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 47
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 46 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 47
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 46 8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 48
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 46 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 48
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 47 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 49
9.3. Conference Object Identifier Registration . . . . . . . . 47 9.3. Conference Object Identifier Registration . . . . . . . . 49
9.4. Conference User Identifier Registration . . . . . . . . . 48 9.4. Conference User Identifier Registration . . . . . . . . . 50
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 51
11.1. Normative References . . . . . . . . . . . . . . . . . . . 49 11.1. Normative References . . . . . . . . . . . . . . . . . . . 51
11.2. Informative References . . . . . . . . . . . . . . . . . . 49 11.2. Informative References . . . . . . . . . . . . . . . . . . 51
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML
Syntax . . . . . . . . . . . . . . . . . . . . . . . 50 Syntax . . . . . . . . . . . . . . . . . . . . . . . 52
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 73
Intellectual Property and Copyright Statements . . . . . . . . . . 72 Intellectual Property and Copyright Statements . . . . . . . . . . 75
1. Introduction 1. Introduction
There is a core data set of conference information that is utilized There is a core data set of conference information that is utilized
in any conference, independent of the specific conference media. in any conference, independent of the specific conference media.
This core data set called the 'conference information data model' is This core data set called the 'conference information data model' is
defined in this document using an Extensible Markup Language (XML)- defined in this document using an Extensible Markup Language (XML)-
based. The conference information data model defined in this based. The conference information data model defined in this
document is logically represented by the conference object. document is logically represented by the conference object.
skipping to change at page 11, line 7 skipping to change at page 11, line 7
| | ... | | ...
| |--<maximum-user-count> | |--<maximum-user-count>
| | ... | | ...
| |--<available-media> | |--<available-media>
| | |--!<entry> | | |--!<entry>
| | | |--<display-text> | | | |--<display-text>
| | | |--<type> | | | |--<type>
| | | |--<status> | | | |--<status>
| | | |--<mixing-mode>* | | | |--<mixing-mode>*
| | | |--<codecs>* | | | |--<codecs>*
| | | | |--<entry>* | | | | |--<codec>*
| | | | |--<entry>* | | | | | |--<subtype>*
| | | | |--<codec>*
| | | | | |--<subtype>*
| | | | ... | | | | ...
| | | |--<controls>* | | | |--<controls>*
| | | | |--<mute>* | | | | |--<mute>*
| | | | |--<gain>* | | | | |--<gain>*
| | | | ... | | | | ...
| | |--<entry> | | |--<entry>
| | | |--<display-text> | | | |--<display-text>
| | | |--<type> | | | |--<type>
| | | |--<status> | | | |--<status>
| | | |--<mixing-mode>* | | | |--<mixing-mode>*
| | | |--<codecs>* | | | |--<codecs>*
| | | | |--<entry>* | | | | |--<codec>*
| | | | |--<entry>* | | | | | |--<subtype>*
| | | | |--<codec>*
| | | | | |--<subtype>*
| | | | ... | | | | ...
| | | |--<controls>* | | | |--<controls>*
| | | | |--<pause-video>* | | | | |--<pause-video>*
| | | | |--<video-layout>* | | | | |--<video-layout>*
| | | | ... | | | | ...
| | ... | | ...
| |
|--<host-info> |--<host-info>
| |--<display-text> | |--<display-text>
| |--<web-page> | |--<web-page>
skipping to change at page 13, line 34 skipping to change at page 13, line 37
| | |-- <display-text> | | |-- <display-text>
| ... | ...
|--<sidebars-by-val> |--<sidebars-by-val>
| |--<entry> | |--<entry>
| | | | | |
| | ... | | ...
| |--<entry> | |--<entry>
| | | | | |
| ... ... | ... ...
Figure 4: Non-normative diagram Figure 3: 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]. The <conference- <conference-info>, which is defined in [RFC4575]. The <conference-
info> attributes are described in [RFC4575]. Note 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
skipping to change at page 17, line 40 skipping to change at page 17, line 42
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 <codec> elements. A controlled"). The <codecs> element contains <codec> elements. A
<codec> element can have the attribute 'name' and 'policy'. The <codec> element can have the attribute 'name' and 'policy'. The
'name' attribute identifies a codec. The list of possible codecs 'name' attribute is a codec identifier assigned by the
accepted as a 'name' attribute is defined by the IANA registry for conferencing server. The 'policy' attribute contains the policy
RTP Payload Types. The possible values of the attribute 'name' for that codec (allowed, or disallowed). The <codec> element has
are the values of the 'subtype' column of the RTP Payload Format the child element <subtype> which stores the codec's name. The
media types per [RFC4855] defined in IANA [IANA]. The 'policy' possible values of this element are the values of the 'subtype'
attribute contains the policy for that codec (allowed, or column of the RTP Payload Format media types per [RFC4855] defined
disallowed). in IANA [IANA]. It is expected that future conferencing
specifications will define corresponding schema extensions, as
appropriate.
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
<available-media> element. The following controls elements are <available-media> element. The following controls elements are
defined for <controls>: defined for <controls>:
skipping to change at page 24, line 43 skipping to change at page 25, line 5
XCON-USERID = "xcon-userid" ":" conf-user-id XCON-USERID = "xcon-userid" ":" conf-user-id
conf-user-id = 1*(unreserved) conf-user-id = 1*(unreserved)
[unreserved is defined in RFC3986] [unreserved is defined in RFC3986]
Other user identifiers can be associated with this conference user Other user identifiers can be associated with this conference user
identifier and enable the conferencing system to correlate and map identifier and enable the conferencing system to correlate and map
these multiple authenticated user identities to a single global user these multiple authenticated user identities to a single global user
identifier. Figure 6 illustrates an example using the conference identifier. Figure 4 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 that required and this information is just included as a guideline that
can be used. can be used.
+----------------+ +----------------+
| Conference | | Conference |
| User | | User |
| Identifier | | Identifier |
skipping to change at page 25, line 23 skipping to change at page 25, line 30
| |
| |
+----------------------+-------------------------+ +----------------------+-------------------------+
| | | | | |
+-------+--------+ +-----------+-----------+ +-----------+-----------+ +-------+--------+ +-----------+-----------+ +-----------+-----------+
| 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 6: Conference User Mapping Figure 4: 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.
4.6.5.1. <display-text> 4.6.5.1. <display-text>
The <display-text> child element is explained in [RFC4575], section The <display-text> child element is explained in [RFC4575], section
skipping to change at page 28, line 48 skipping to change at page 29, line 10
[I-D.ietf-xcon-framework], the Conference Object is a logical [I-D.ietf-xcon-framework], the Conference Object is a logical
representation of a conference instance. The conference information representation of a conference instance. The conference information
schema contains core information that is utilized in any conference. schema contains core information that is utilized in any conference.
It also contains the variable information part of the Conference It also contains the variable information part of the Conference
Object. Object.
This specification defines some document fragments in RELAX NG format This specification defines some document fragments in RELAX NG format
[RELAX]. [RELAX].
namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0" namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
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"
namespace local = ""
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 },
anyAttribute, anyAttribute,
conference-description-type, conference-description-type,
element language { xsd:language }?, element language { xsd:language }?,
element host-info { conference-info-urn* }?, element host-info { conference-info-urn* }?,
element conference-state { conference-state-type }?, element conference-state { conference-state-type }?,
element floor-information { floor-information-type }?, element floor-information { floor-information-type }?,
element users { users-type }, element users { users-type },
element sidebars-by-ref { sidebars-by-ref-type }?, element sidebars-by-ref { sidebars-by-ref-type }?,
skipping to change at page 30, line 34 skipping to change at page 31, line 6
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 { control-type }?, element controls { 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 | 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,
element subtype { text }?,
conference-info-urn*
# DECISION TYPE # DECISION TYPE
decision-type = decision-type =
xsd:string "automatic" | xsd:string "moderator-controlled" | text xsd:string "automatic" | xsd:string "moderator-controlled" | text
# POLICY TYPE # POLICY TYPE
policy-type = xsd:string "allowed" | xsd:string "disallowed" | text 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"
skipping to change at page 33, line 15 skipping to change at page 34, line 18
element persistent-list { element persistent-list {
element user { element user {
attribute name { text }, attribute name { text },
attribute nickname { text }, attribute nickname { text },
attribute id { text }, attribute id { text },
anyAttribute, anyAttribute,
element e-mail { text }* 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-in"
| xsd:string "dial-out" | xsd:string "dial-out"
| xsd:string "refer" | xsd:string "refer"
| text | 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 {
"hidden" | text }?, "private" | "semi-private" | "hidden" | text
}?,
element roles { single-role-type }?, 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*
skipping to change at page 35, line 27 skipping to change at page 37, line 5
| lang | lang
| required-participant | required-participant
| label | label
| decision | decision
| name | name
| policy | policy
| uri | uri
| method | method
| id | id
| local:* | local:*
| ns1:*) { text }* | ns1:*)
{ text }*
# ************************************************************* # *************************************************************
# TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE # TYPES DEFINED IN THE EVENT PACKAGE FOR
# CONFERENCE STATE
# - RFC4575 - # - RFC4575 -
# ************************************************************* # *************************************************************
# 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 = media-status-type =
"recvonly" | "sendonly" | "sendrecv" | "inactive" | text "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"
skipping to change at page 38, line 21 skipping to change at page 40, line 11
<!-- <!--
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>
<codecs decision="automatic"> <codecs decision="automatic">
<codec name="PCMU" policy="allowed"/> <codec name="122" policy="allowed"/>
<subtype>PCMU</subtype>
</codecs> </codecs>
<controls> <controls>
<mute>true</mute> <mute>true</mute>
<gain>50</gain> <gain>50</gain>
</controls> </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>
<codecs decision="automatic"> <codecs decision="automatic">
<codec name="H.263" policy="allowed"/> <codec name="123" policy="allowed"/>
<subtype>H.263</subtype>
</codecs> </codecs>
<controls> <controls>
<video-layout>single-view</video-layout> <video-layout>single-view</video-layout>
</controls> </controls>
</entry> </entry>
</available-media> </available-media>
</conference-description> </conference-description>
<!-- <!--
HOST INFO HOST INFO
--> -->
skipping to change at page 48, line 4 skipping to change at page 49, line 46
END END
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[RFC3986]
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.]
Subject: Request for XCON-URI Registration Subject: Request for XCON-URI Registration
Person & email address to contact for further information: Person & email address to contact for further information:
Oscar Novo <oscar novo_at_ericsson.com> Oscar Novo <oscar novo_at_ericsson.com>
Specification: RFC XXXX Specification: RFC XXXX
Author/Change Controller: IESG Author/Change Controller: IESG
Comments: Comments:
Identifies the Conference Identifies the Conference
skipping to change at page 50, line 24 skipping to change at page 52, line 23
for Binary Floor Control Protocol (BFCP) Streams", for Binary Floor Control Protocol (BFCP) Streams",
RFC 4583, November 2006. RFC 4583, November 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.
[W3C.REC-xml-20001006] [W3C.REC-xml-20001006]
Paoli, J., Maler, E., Bray, T., and C. Sperberg-McQueen, Paoli, J., Bray, T., Maler, E., and C. Sperberg-McQueen,
"Extensible Markup Language (XML) 1.0 (Second Edition)", "Extensible Markup Language (XML) 1.0 (Second Edition)",
World Wide Web Consortium FirstEdition REC-xml-20001006, World Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000, October 2000,
<http://www.w3.org/TR/2000/REC-xml-20001006>. <http://www.w3.org/TR/2000/REC-xml-20001006>.
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Syntax
<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"
skipping to change at page 56, line 44 skipping to change at page 58, line 42
CODEC TYPE CODEC TYPE
--> -->
<define name="codec-type"> <define name="codec-type">
<attribute name="name"> <attribute name="name">
<text/> <text/>
</attribute> </attribute>
<attribute name="policy"> <attribute name="policy">
<ref name="policy-type"/> <ref name="policy-type"/>
</attribute> </attribute>
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<optional>
<element name="subtype">
<text/>
</element>
</optional>
<zeroOrMore>
<ref name="conference-info-urn"/>
</zeroOrMore>
</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/> <text/>
</choice> </choice>
skipping to change at page 72, line 44 skipping to change at line 3453
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 54 change blocks. 
55 lines changed or deleted 100 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/