idnits 2.17.1 

draft-ietf-xcon-common-data-model-06.txt:

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  https://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

  ** It looks like you're using RFC 3978 boilerplate.  You should update this
     to the boilerplate described in the IETF Trust License Policy document
     (see https://trustee.ietf.org/license-info), which is required now.

  -- Found old boilerplate from RFC 3978, Section 5.1 on line 19.

  -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on
     line 3011.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3022.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3029.

  -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3035.


  Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to https://www.ietf.org/id-info/checklist :
  ----------------------------------------------------------------------------

     No issues found here.

  Miscellaneous warnings:
  ----------------------------------------------------------------------------

  == The copyright year in the IETF Trust Copyright Line does not match the
     current year

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If you
     have contacted all the original authors and they are all willing to grant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer. 
     (See the Legal Provisions document at
     https://trustee.ietf.org/license-info for more information.)

  -- The document date (October 31, 2007) is 6015 days in the past.  Is this
     intentional?

  -- Found something which looks like a code comment -- if you have code
     sections in the document, please surround them with '<CODE BEGINS>' and
     '<CODE ENDS>' lines.


  Checking references for intended status: Proposed Standard
  ----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative references
     to lower-maturity documents in RFCs)

  ** Obsolete normative reference: RFC 2445 (ref. '3') (Obsoleted by RFC 5545)

  == Outdated reference: A later version (-11) exists of
     draft-ietf-xcon-framework-09

  -- Obsolete informational reference (is this intentional?): RFC 4582 (ref.
     '5') (Obsoleted by RFC 8855)

  -- Obsolete informational reference (is this intentional?): RFC 3265 (ref.
     '6') (Obsoleted by RFC 6665)

  -- Obsolete informational reference (is this intentional?): RFC 4583 (ref.
     '12') (Obsoleted by RFC 8856)


     Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 11 comments (--).

     Run idnits with the --verbose option for more detailed information about
     the items above.

--------------------------------------------------------------------------------


2	XCON                                                             O. Novo
3	Internet-Draft                                              G. Camarillo
4	Intended status: Standards Track                                Ericsson
5	Expires: May 3, 2008                                           D. Morgan
6	                                                    Fidelity Investments
7	                                                                 R. Even
8	                                                                 Polycom
9	                                                        October 31, 2007

11	 Conference Information Data Model for Centralized Conferencing (XCON)
12	                draft-ietf-xcon-common-data-model-06.txt

14	Status of this Memo

16	   By submitting this Internet-Draft, each author represents that any
17	   applicable patent or other IPR claims of which he or she is aware
18	   have been or will be disclosed, and any of which he or she becomes
19	   aware will be disclosed, in accordance with Section 6 of BCP 79.

21	   Internet-Drafts are working documents of the Internet Engineering
22	   Task Force (IETF), its areas, and its working groups.  Note that
23	   other groups may also distribute working documents as Internet-
24	   Drafts.

26	   Internet-Drafts are draft documents valid for a maximum of six months
27	   and may be updated, replaced, or obsoleted by other documents at any
28	   time.  It is inappropriate to use Internet-Drafts as reference
29	   material or to cite them other than as "work in progress."

31	   The list of current Internet-Drafts can be accessed at
32	   http://www.ietf.org/ietf/1id-abstracts.txt.

34	   The list of Internet-Draft Shadow Directories can be accessed at
35	   http://www.ietf.org/shadow.html.

37	   This Internet-Draft will expire on May 3, 2008.

39	Copyright Notice

41	   Copyright (C) The IETF Trust (2007).

43	Abstract

45	   This document defines an Extensible Markup Language (XML)-based
46	   conference information data model for centralized conferencing
47	   (XCON).  A conference information data model is designed to convey
48	   information about the conference and about participation in the
49	   conference.  The conference information data model defined in this
50	   document constitutes an extension of the data format specified in the
51	   Session Initiation Protocol (SIP) Event Package for Conference State.

53	Table of Contents

55	   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
56	   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
57	   3.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  6
58	     3.1.  Data Model Format  . . . . . . . . . . . . . . . . . . . .  6
59	     3.2.  Data Model Namespace . . . . . . . . . . . . . . . . . . .  6
60	     3.3.  The Conference Object Identifier . . . . . . . . . . . . .  7
61	     3.4.  Data Model Structure . . . . . . . . . . . . . . . . . . .  8
62	   4.  Data Model Definition  . . . . . . . . . . . . . . . . . . . .  9
63	     4.1.  <conference-info>  . . . . . . . . . . . . . . . . . . . . 12
64	     4.2.  <conference-description> . . . . . . . . . . . . . . . . . 13
65	       4.2.1.  <display-text> . . . . . . . . . . . . . . . . . . . . 13
66	       4.2.2.  <subject>  . . . . . . . . . . . . . . . . . . . . . . 13
67	       4.2.3.  <free-text>  . . . . . . . . . . . . . . . . . . . . . 13
68	       4.2.4.  <keywords> . . . . . . . . . . . . . . . . . . . . . . 13
69	       4.2.5.  <allow-sidebars> . . . . . . . . . . . . . . . . . . . 13
70	       4.2.6.  <conference-time>  . . . . . . . . . . . . . . . . . . 14
71	       4.2.7.  <conf-uris>  . . . . . . . . . . . . . . . . . . . . . 15
72	       4.2.8.  <service-uris> . . . . . . . . . . . . . . . . . . . . 15
73	       4.2.9.  <maximum-user-count> . . . . . . . . . . . . . . . . . 15
74	       4.2.10. <available-media>  . . . . . . . . . . . . . . . . . . 15
75	     4.3.  <host-info>  . . . . . . . . . . . . . . . . . . . . . . . 18
76	     4.4.  <conference-state> . . . . . . . . . . . . . . . . . . . . 18
77	       4.4.1.  <allow-conference-event-subscription>  . . . . . . . . 18
78	       4.4.2.  <user-count> . . . . . . . . . . . . . . . . . . . . . 18
79	       4.4.3.  <active> . . . . . . . . . . . . . . . . . . . . . . . 18
80	       4.4.4.  <locked> . . . . . . . . . . . . . . . . . . . . . . . 19
81	     4.5.  <floor-information>  . . . . . . . . . . . . . . . . . . . 19
82	       4.5.1.  <conference-ID>  . . . . . . . . . . . . . . . . . . . 19
83	       4.5.2.  <allow-floor-events> . . . . . . . . . . . . . . . . . 19
84	       4.5.3.  <floor-request-handling> . . . . . . . . . . . . . . . 19
85	       4.5.4.  <conference-floor-policy>  . . . . . . . . . . . . . . 20
86	     4.6.  <users>  . . . . . . . . . . . . . . . . . . . . . . . . . 20
87	       4.6.1.  <join-handling>  . . . . . . . . . . . . . . . . . . . 21
88	       4.6.2.  <user-admission-policy>  . . . . . . . . . . . . . . . 21
89	       4.6.3.  <allowed-users-list> . . . . . . . . . . . . . . . . . 22
90	       4.6.4.  <user> and Its <user> Sub-elements . . . . . . . . . . 22
91	         4.6.4.1.  <display-text> . . . . . . . . . . . . . . . . . . 23
92	         4.6.4.2.  <associated-aors>  . . . . . . . . . . . . . . . . 23
93	         4.6.4.3.  <provide-anonymity>  . . . . . . . . . . . . . . . 24
94	         4.6.4.4.  <roles>  . . . . . . . . . . . . . . . . . . . . . 24
95	         4.6.4.5.  <languages>  . . . . . . . . . . . . . . . . . . . 24
96	         4.6.4.6.  <cascaded-focus> . . . . . . . . . . . . . . . . . 24
97	         4.6.4.7.  <allow-refer-users-dynamically>  . . . . . . . . . 24
98	         4.6.4.8.  <allow-invite-users-dynamically> . . . . . . . . . 24
99	         4.6.4.9.  <allow-remove-users-dynamically> . . . . . . . . . 25
100	         4.6.4.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 25
101	     4.7.  <sidebars-by-ref>  . . . . . . . . . . . . . . . . . . . . 26
102	     4.8.  <sidebars-by-val>  . . . . . . . . . . . . . . . . . . . . 26
103	   5.  RELAX NG Schema  . . . . . . . . . . . . . . . . . . . . . . . 26
104	   6.  XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 33
105	   7.  XML Example  . . . . . . . . . . . . . . . . . . . . . . . . . 33
106	   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 41
107	     8.1.  Authentication . . . . . . . . . . . . . . . . . . . . . . 41
108	     8.2.  Confidentiality  . . . . . . . . . . . . . . . . . . . . . 41
109	     8.3.  Integrity  . . . . . . . . . . . . . . . . . . . . . . . . 42
110	   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 42
111	     9.1.  Conference Relax NG Schema Registration  . . . . . . . . . 42
112	     9.2.  Conference Namespace Registration  . . . . . . . . . . . . 42
113	     9.3.  Conference Object Identifier Registration  . . . . . . . . 42
114	     9.4.  Conference User Identifier Registration  . . . . . . . . . 43
115	   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43
116	   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43
117	     11.1. Normative References . . . . . . . . . . . . . . . . . . . 43
118	     11.2. Informative References . . . . . . . . . . . . . . . . . . 43
119	   Appendix A.  Appendix A.  Non-Normative RELAX NG Schema in XML
120	                Syntax  . . . . . . . . . . . . . . . . . . . . . . . 44
121	   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 63
122	   Intellectual Property and Copyright Statements . . . . . . . . . . 65

124	1.  Introduction

126	   There is a core data set of conference information that is utilized
127	   in any conference, independent of the specific conference media.
128	   This core data set called the 'conference information data model' is
129	   defined in this document using an Extensible Markup Language (XML)-
130	   based.  The conference information data model defined in this
131	   document is logically represented by the conference object.

133	   Conference objects are a fundamental concept in Centralized
134	   Conferencing, as described in the Centralized Conferencing Framework
135	   [4].  A conference object contains data that represents a conference
136	   during each of its various stages (e.g., created/creation, reserved/
137	   reservation, active/activation, completed/completion).  A conference
138	   object can be manipulated using a conference control protocol at a
139	   conference server.  The conference object represents a particular
140	   instantiation of a conference information data model.  Consequently,
141	   conference objects follow the XML format defined in this document.

143	   A conference object contains the core information of a conference
144	   (i.e., capabilities, membership, call control signaling, media, etc.)
145	   and specifies who, and in which way that information can be
146	   manipulated.

148	   Figure 1 shows the logical functional elements of a conference server
149	   as defined by the Centralized Conferencing Framework [4].  They are a
150	   Conference Control Server, a Floor Control Server, a number of Foci,
151	   and a Notification Service.  A conference control protocol provides
152	   the interface between a conference control client and the conference
153	   control server.  A floor control protocol (e.g., BFCP [5]) provides
154	   the interface between a floor control client and the floor control
155	   server.  A call signaling protocol (e.g., SIP, H.323, Q.931, ISUP,
156	   etc.) provides the interface between a call signaling client and a
157	   Focus.  A notification protocol (e.g., SIP-based event notifications
158	   [6]) provides the interface between the conferencing client and the
159	   Notification Service.  Within a conference, the conference control
160	   server, floor control server, and focus can modify the information in
161	   the conference object.

163	      ...............................................................
164	      . Conferencing Server                                         .
165	      .       +---------------------------------------------------+ .
166	      .       |       C o n f e r e n c e   o b j e c t           | .
167	      .     +-+--------------------------------------------------+| .
168	      .     |       C o n f e r e n c e   o b j e c t            || .
169	      .   +-+---------------------------------------------------+|| .
170	      .   |       C o n f e r e n c e   o b j e c t             ||| .
171	      .   | +--------------------------------------------------+||| .
172	      .   | | Conference Information Data Model                |||| .
173	      .   | | +----------------------------------------------+ |||| .
174	      .   | | | Conference description  (times, duration)    | |||| .
175	      .   | | +----------------------------------------------+ |||| .
176	      .   | | +----------------------------------------------+ |||| .
177	      .   | | | Host information                             | |||| .
178	      .   | | +----------------------------------------------+ |||| .
179	      .   | | +----------------------------------------------+ |||| .
180	      .   | | | Conference state                             | |||| .
181	      .   | | +----------------------------------------------+ |||| .
182	      .   | | +----------------------------------------------+ |||| .
183	      .   | | | Floor information                            | |||| .
184	      .   | | +----------------------------------------------+ |||| .
185	      .   | | +----------------------------------------------+ |||| .
186	      .   | | | Membership (users, capacity)                 | |||| .
187	      .   | | +----------------------------------------------+ |||| .
188	      .   | | +----------------------------------------------+ |||| .
189	      .   | | | Sidebars, Etc.                               | |||| .
190	      .   | | +----------------------------------------------+ |||| .
191	      .   | | +----------------------------------------------+ |||| .
192	      .   | | | Etc.                                         | |||| .
193	      .   | | +----------------------------------------------+ |||+ .
194	      .   | +--------------------------------------------------+|+  .
195	      .   +----^------------------^-------------^--------|------+   .
196	      .        |                  |             |        |          .
197	      . +------v-------+ +--------v-----+ +-----v-+ +----v-------+  .
198	      . | Conference   | | Floor        | |       | |            |  .
199	      . | Control      | | Control      | |Foci   | |Notification|  .
200	      . | Server       | | Server       | |       | |Service     |  .
201	      . +-----^--------+ +---^----------+ +-^-----+ +------------+  .
202	      ........|..............|..............|..........|.............
203	              |Conference    |Binary Floor  |Call      |Notification
204	              |Control       |Control       |Signaling |Protocol
205	              |Protocol      |Protocol      |Protocol  |
206	      ........v..............v..............v..........v.............
207	      .     C  o  n  f  e  r  e  n  c  i  n  g     C  l i  e  n  t  .
208	      ...............................................................

210	                 Figure 1: Conference Server Architecture

212	   The Session Initiation Protocol (SIP) Event Package for Conference
213	   State, specified in RFC4575 [1], already defines a data format for
214	   conferences.  However, that model is SIP specific and lacks elements
215	   related to some of the functionality defined by the Centralized
216	   Conferencing Framework [4] (e.g., floor control).  The data model
217	   defined in this document constitutes a superset of the data format
218	   defined in RFC4575 [1].  The result is a data format that supports
219	   more call signaling protocols besides SIP and that covers all the
220	   functionality defined in the Centralized Conferencing Framework [4].

222	2.  Terminology

224	   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
225	   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
226	   document are to be interpreted as described in RFC 2119 [2].

228	   This document uses the terminology defined in the Centralized
229	   Conferencing Framework [4], the SIPPING conferencing framework [7]
230	   and the BFCP (Binary Floor Control Protocol) specification [5].
231	   Readers of this document should be familiar with the terminology used
232	   in those documents.

234	3.  Overview

236	   The data model specified in this document is the result of extending
237	   the data format defined in RFC4575 [1] with new elements.  Examples
238	   of such extensions include scheduling elements, media control
239	   elements, floor control elements, non-SIP URIs, and addition of
240	   localization extensions to text elements.  This data model can be
241	   used by conference servers providing different types of basic
242	   conferences.  It is expected that this data model can be further
243	   extended with new elements in the future in order to implement
244	   additional advanced features.

246	3.1.  Data Model Format

248	   A conference object document is an XML [8] document that MUST be well
249	   formed and SHOULD be valid.  Conference object documents MUST be
250	   based on XML 1.0 and SHOULD be encoded using UTF-8.

252	3.2.  Data Model Namespace

254	   This specification defines a new namespace specification for
255	   identifying the elements defined in the data model.  This namespace
256	   is as follows:

258	   urn:ietf:params:xml:ns:xcon-conference-info

260	3.3.  The Conference Object Identifier

262	   The conference object identifier (XCON-URI) can be viewed as a key to
263	   accessing a specific conference object.  It can be used, for
264	   instance, by the conference control protocol to access, manipulate
265	   and delete a conference object.  A conference object identifier is
266	   provided to the conferencing client by the conference notification
267	   service or through out-of-band mechanisms (e.g.  E-Mail).

269	   A conferencing system may maintain a relationship between the
270	   conference object identifiers and the identifiers associated with
271	   each of the complementary centralized conferencing protocols (e.g.,
272	   call signaling protocols, BFCP, etc.).  To facilitate the maintenance
273	   of these relationships, the conference object identifier acts as a
274	   top level identifier within the conferencing system for the purpose
275	   of identifying the interfaces for these other protocols.  This
276	   implicit binding provides a structured mapping of the various
277	   protocols with the associated conference object Identifier.  Figure 2
278	   illustrates the relationship between the identifiers used for the
279	   protocols and the general conference object identifier (XCON-URI).

281	                            +--------------------------+
282	                            |       Conference         |
283	                            |         Object           |
284	                            |       Identifier         |
285	                            +--------------------------+
286	                            |  xcon:Ji092i@example.com |
287	                            +------+-------------------+
288	                                        |
289	                                        |
290	                                        |
291	                      +-----------------+---------------+
292	                      |                                 |
293	          +-----------+-----------+          +----------+---------+
294	          |   CSP Conference IDs  |          |BFCP 'Conference ID'|
295	          +-----------------------+          +--------------------+
296	          |h323:Ji092i@example.com|          |        Ji092i      |
297	          |tel:+44(0)2920930033   |          +----------+---------+
298	          |sip:Ji092i@example.com |                     |
299	          +-----------------------+             +-------|--------+
300	                                                | BFCP 'Floor ID'|
301	                                                +----------------+
302	                                                |      543       |
303	                                                |     09cnJk     |
304	                                                +----------------+

306	                    Figure 2: Conference Object Mapping

308	   In Figure 2, the conference object identifier acts as the top level
309	   key in the identification process.  The call signaling protocols have
310	   an associated conference user identifier, often represented in the
311	   form of URIs.  The binary floor control protocol, as defined in [5],
312	   defines the 'conference ID' identifier which represents a conference
313	   instance within floor control.  When created within the conferencing
314	   system, the 'conference ID' has a 1:1 mapping to the unique
315	   conference object Identifier(XCON-URI).  Operations associated with
316	   the conference control protocols are directly associated with the
317	   conference object, thus the primary identifier associated with these
318	   protocols is the conference object identifier(XCON-URI).  The
319	   mappings between additional protocols/interface is not strictly 1:1
320	   and does allow for multiple occurrences.  For example, multiple call
321	   signaling protocols will each have a representation that is
322	   implicitly linked to the top level conference object identifier e.g.
323	   H323 and SIP URIs that represent a conference instance.  It should be
324	   noted that a conferencing system is free to structure such
325	   relationships as required and this information is just included as a
326	   guideline that can be used.

328	   Further elements can be added to the tree representation in Figure 2
329	   to enable a complete representation of a conference instance within a
330	   conferencing system.

332	3.4.  Data Model Structure

334	   The information in this data model is structured in the following
335	   manner.  All the information related to a conference is contained in
336	   a <conference-info> element.  The <conference-info> element contains
337	   the following child elements:

339	   o  The <conference-description> element describes the conference as a
340	      whole.  It has, for instance, information about the URI of the
341	      conference, maximum users allowed in the conference, media
342	      available in the conference, or the time the conference will
343	      start.
344	   o  The <host-info> element contains information about the entity
345	      hosting the conference (e.g., its URI).
346	   o  The <conference-state> element informs the subscribers about the
347	      changes in the overall conference information.
348	   o  The <floor-information> element contains information about the
349	      status of the different floors in the conference.
350	   o  The <users> element describes the membership information as a
351	      whole.  The <users> element contains a set of <user> child
352	      elements, each describing a single participant in the conference.

354	   o  If a participant in the main conference joins a sidebar, a new
355	      element is created in the conference referenced from the
356	      <sidebars-by-ref> element or under one of the <sidebars-by-val>
357	      elements.

359	   Note that some of the elements described above such <conference-
360	   info>, <conference-description>, <sidebars-by-ref>, or <sidebars-by-
361	   val> are not defined in the data model but are defined in the data
362	   format of RFC 4575 [1].  We describe them here because they are part
363	   of the basic structure of the data model.

365	4.  Data Model Definition

367	   The following non-normative diagram shows the structure of conference
368	   object documents.  The operator "!" preceding an element indicates
369	   that the element is mandatory in the data model.  The operator "*"
370	   following an element indicates that the element is introduced and
371	   defined in this document.  That is, elements without a "*" have
372	   already been defined in RFC 4575 [1].

374	   !<conference-info>
375	        |
376	        |--!<conference-description>
377	        |     |--<display-text>
378	        |     |--<subject>
379	        |     |--<free-text>
380	        |     |--<keywords>
381	        |     |--<allow-sidebars>*
382	        |     |--<conference-time>*
383	        |     |      |--<entry>*
384	        |     |      |    |--<base>*
385	        |     |      |    |--<mixing-start-offset>*
386	        |     |      |    |--<mixing-end-offset>*
387	        |     |      |    |--<can-join-after-offset>*
388	        |     |      |    |--<must-join-before-offset>*
389	        |     |      |    |--<request-user>*
390	        |     |      |    |--<notify-end-of-conference>*
391	        |     |      |    |--<allowed-extend-mixing-end-offset>*
392	        |     |           ...
393	        |     |--<conf-uris>
394	        |     |      |--<entry>
395	        |     |      |    |--<uri>
396	        |     |      |    |--<display-text>
397	        |     |      |    |--<purpose>
398	        |     |      ...
399	        |     |--<service-uris>
400	        |     |      |--<entry>
401	        |     |      |    |--<uri>
402	        |     |      |    |--<display-text>
403	        |     |      |    |--<purpose>
404	        |     |      ...
405	        |     |--<maximum-user-count>
406	        |     |      ...
407	        |     |--<available-media>
408	        |     |      |--!<entry>
409	        |     |      |     |--<type>
410	        |     |      |     |--<display-text>
411	        |     |      |     |--<status>
412	        |     |      |     |--<mixing-mode>*
413	        |     |      |     |--<codecs>*
414	        |     |      |     |    |--<entry>*
415	        |     |      |     |    |--<entry>*
416	        |     |      |     |    ...
417	        |     |      |     |--<controls>*
418	        |     |      |     |    |--<mute>*
419	        |     |      |     |    |--<gain>*
420	        |     |      |     |   ...
421	        |     |      |--<entry>
422	        |     |      |     |--<type>
423	        |     |      |     |--<display-text>
424	        |     |      |     |--<status>
425	        |     |      |     |--<mixing-mode>*
426	        |     |      |     |--<codecs>*
427	        |     |      |     |    |--<entry>*
428	        |     |      |     |    |--<entry>*
429	        |     |      |     |    ...
430	        |     |      |     |--<controls>*
431	        |     |      |     |    |--<pause-video>*
432	        |     |      |     |    |--<video-layout>*
433	        |     |      |     |   ...
434	        |     |      ...
435	        |
436	        |--<host-info>
437	        |     |--<display-text>
438	        |     |--<web-page>
439	        |     |--<uris>
440	        |     |     |--<entry>
441	        |     |     |    |--<uri>
442	        |     |     |    |--<display-text>
443	        |           ...
444	        |--<conference-state>
445	        |     |--<allow-conference-event-subscription>*
446	        |     |--<user-count>
447	        |     |--<active>
448	        |     |--<locked>
449	        |
450	        |--<floor-information>*
451	        |     |--<conference-ID>*
452	        |     |--<allow-floor-events>*
453	        |     |--<floor-request-handling>*
454	        |     |--<conference-floor-policy>*
455	        |     |     |--<floor>*
456	        |     |     |    |--!<media-label>*
457	        |     |     |    |--!<algorithm>*
458	        |     |     |    |--<max-floor-users>*
459	        |     |     |    |--<moderator-id>*
460	        |     |     |   ...
461	        |     |     ...
462	        |
463	        |--!<users>
464	        |     |--<join-handling>*
465	        |     |--<user-admission-policy>*
466	        |     |--<allowed-users-list>*
467	        |     |     |--<target>*
468	        |     |     |-- ...
469	        |     |
470	        |     |
471	        |     |--<user>
472	        |     |    |--<display-text>
473	        |     |    |--<associated-aors>
474	        |     |    |--<provide-anonymity>*
475	        |     |    |--<roles>
476	        |     |    |    |
477	        |     |    |   ...
478	        |     |    |--<languages>
479	        |     |    |--<cascaded-focus>
480	        |     |    |--<allow-refer-users-dynamically>*
481	        |     |    |--<allow-invite-users-dynamically>*
482	        |     |    |--<allow-remove-users-dynamically>*
483	        |     |    |--!<endpoint>
484	        |     |    |      |--<display-text>
485	        |     |    |      |--<referred>
486	        |     |    |      |--<status>
487	        |     |    |      |--<joining-method>
488	        |     |    |      |--<joining-info>
489	        |     |    |      |--<disconnection-method>
490	        |     |    |      |--<disconnection-info>
491	        |     |    |      |--<media>
492	        |     |    |      |    |--<type>
493	        |     |    |      |    |--<display-text>
494	        |     |    |      |    |--<label>
495	        |     |    |      |    |--<src-id>
496	        |     |    |      |    |--<status>
497	        |     |    |      |    |--<to-mixer>*
498	        |     |    |      |    |      |--<floor>*
499	        |     |    |      |    |      |--<controls>*
500	        |     |    |      |    |      |      |--<mute>*
501	        |     |    |      |    |      |      |--<gain>*
502	        |     |    |      |    |      |     ...
503	        |     |    |      |    |--<from-mixer>*
504	        |     |    |      |    |      |--<floor>*
505	        |     |    |      |    |      |--<controls>*
506	        |     |    |      |    |      |      |--<pause-video>*
507	        |     |    |      |    |      |     ...
508	        |     |    |      |   ...
509	        |     |    |      |--<call-info>
510	        |     |    |      |    |--<sip>
511	        |     |    |      |    |   |--<display-text>
512	        |     |    |      |    |   |--<call-id>
513	        |     |    |      |    |   |--<from-tag>
514	        |     |    |      |    |   |--<to-tag>
515	        |          ...    ...
516	        |--<sidebars-by-ref>
517	        |     |--<entry>
518	        |     |     |-- <user>
519	        |     |     |-- <display-text>
520	        |     |--<entry>
521	        |     |     |-- <user>
522	        |     |     |-- <display-text>
523	        |     ...
524	        |--<sidebars-by-val>
525	        |     |--<entry>
526	        |     |     |
527	        |     |    ...
528	        |     |--<entry>
529	        |     |     |
530	        |     ...   ...

532	                      Figure 3: Non-normative diagram

534	   The following sections describe these elements in detail.  The full
535	   Relax NG schema is provided Section 5.

537	4.1.  <conference-info>

539	   A conference object document begins with the root element tag
540	   <conference-info>, which is defined in RFC4575 [1].  The <conference-
541	   info> attributes are described in RFC4575 [1].  Notice that the
542	   <conference-info> element does not have the attributes 'state' and
543	   'version' defined in RFC4575[1] for this element because this
544	   attribute only applies to notifications mechanism.  RFC4575 [1]
545	   defines as well an 'entity' attribute that contains the conference
546	   object identifier (XCON-URI) that identifies the conference being
547	   described in the document.

549	   The <conference-info> element contains the <conference-description>,
550	   <host-info>, <conference-state>, <floor-information>, <users>,
551	   <sidebars-by-ref>, and <sidebars-by-val> child elements.  All these
552	   elements, except <floor-information>, are defined in [1].  A
553	   conference document MUST at least include the <conference-
554	   description> and <users> child elements.

556	4.2.  <conference-description>

558	   The <conference-description> element, which is defined in RFC4575
559	   [1], describes the conference as a whole.  It should have an extra
560	   attribute 'lang' to specify the language used in the contents of this
561	   element.  It is comprised of <display-text>, <subject>, <free-text>,
562	   <keywords>, <allow-sidebars>, <conference-time>, <conf-uris>,
563	   <service-uris>, <maximum-user-count>, and <available-media>.

565	   The following sections describe these elements in more detail.  Other
566	   child elements MAY be defined in the future to extend the
567	   <conference-description> element.

569	4.2.1.  <display-text>

571	   The <display-text> element is described in section 5.3 of RFC 4575
572	   [1].

574	4.2.2.  <subject>

576	   The <subject> element is described in section 5.3 of RFC 4575 [1].

578	4.2.3.  <free-text>

580	   The <free-text> element is described in section 5.3 of RFC 4575 [1].

582	4.2.4.  <keywords>

584	   The <keywords> element is described in section 5.3 of RFC 4575 [1].

586	4.2.5.  <allow-sidebars>

588	   The <allow-sidebars> element represents a boolean action.  If set to
589	   TRUE, the conference is allowed to create sidebar conferences.

591	4.2.6.  <conference-time>

593	   The <conference-time> element contains the information related to
594	   conference time and duration of a conference.  The <conference-time>
595	   element contains one or more <entry> elements each defining the time
596	   information specifying a single conference occurrence.

598	   Every <entry> element contains the following child elements:

600	   o  <base>: The <base> child element specifies the iCalendar object of
601	      the conference.  The iCalendar object components are defined in
602	      RFC 2445 [3].
603	   o  <mixing-start-offset>: The <mixing-start-offset> child element
604	      specifies when the conference media mixing starts before the
605	      conference starts.  The <mixing-start-offset> child element
606	      expresses the offset as signed integers representing seconds
607	      before/after the iCalendar DTSTART field [3].  If the <mixing-
608	      start-offset> element is not present, it indicates that the
609	      conference media mixing starts immediately.  The <mixing-start-
610	      offset> has the mandatory 'required-participant' attribute.  This
611	      attribute has one of 4 values: "none", "administrator",
612	      "moderator", and "participant".  This attribute allows a
613	      privileged user to define when media mixing starts based on the
614	      latter of the mixing start time, and the time the first
615	      participant, administrator, or moderator arrives.  If the value is
616	      set to "none'", mixing starts according to the mixing start time.
617	   o  <mixing-end-offset>: The <mixing-end-offset> child element that
618	      specifies the time a conference media mixing stops after the
619	      conference stops.  The <mixing-end-offset> child element expresses
620	      the offset as signed integers representing seconds before/after
621	      the iCalendar DTEND field [3].  If the <mixing-end-offset> element
622	      is not present, it indicates that the conference occurrence is not
623	      bounded.  The <mixing-end-offset> elements both have the mandatory
624	      'required-participant' attribute.  This attribute has one of 4
625	      values: "none", "administrator", "moderator", and "participant".
626	      This attribute allows a privileged user to define when media
627	      mixing ends based on the earlier of the <mixing-end-offset>, and
628	      the time the last participant, or moderator leaves.  If the value
629	      is set to "none", mixing stops according to the <mixing-end-
630	      offset>.  If the conference policy was modified so that last
631	      privileged user is now a normal conference participant, and the
632	      conference requires a privileged user to continue; that conference
633	      MUST terminate.
634	   o  <can-join-after-offset>: An administrator can indicate the time
635	      when users can join a conference by populating the <can-join-
636	      after-offset> element.

638	   o  <must-join-before-offset>: An administrator can define the time
639	      after which new users are not allowed to join the conference
640	      anymore.  This is done by populating the <must-join-before-offset>
641	      element expressing the offset as signed integers representing
642	      seconds before/after DTSTART field.
643	   o  <request-user>: It is possible to define the time when users or
644	      resources on the <allowed-users-list> are requested to join the
645	      conference by using the <request-users> element.  This element
646	      expresses the offset as signed integers representing seconds
647	      before/after DTSTART field.
648	   o  <notify-end-of-conference>: The <notify-end-of-conference> element
649	      defines in seconds when the system has to send a notification when
650	      the end of the conference is approaching.  If the <notify-end-of-
651	      conference> element is not present, it indicates that the system
652	      does not notify the users when the end of the conference is
653	      approaching.  The <notify-end-of-conference> child element
654	      expresses the offset as signed integers representing seconds after
655	      DTSTART field.
656	   o  <allowed-extend-mixing-end-offset>: The <allowed-extend-mixing-
657	      end-offset> refers to the possibility to extend the conference.
658	      It has a boolean value.

660	4.2.7.  <conf-uris>

662	   The <conf-uris> contains the identifiers to be used in order to
663	   access the conference by different signaling means.  The <conf-uris>
664	   element is described in section 5.3.1 of RFC 4575[1].  Future
665	   extensions to this schema may define new values and register them
666	   with IANA.

668	4.2.8.  <service-uris>

670	   The <service-uris> describes auxiliary services available for the
671	   conference.  The <service-uris> element is described in section 5.3.2
672	   of RFC4575[1].  Future extensions to this schema may define new
673	   values and register them with IANA.

675	4.2.9.  <maximum-user-count>

677	   The <maximum-user-count> contains the overall number of users allowed
678	   to join the conference.  Note that this value is set by an
679	   administrator and can reflect any local policies such as network
680	   consumption, CPU processing power, and licensing rules.

682	4.2.10.  <available-media>

684	   The <available-media> has the 'label' attribute that is the media
685	   stream identifier assigned by the conferencing server.  The attribute
686	   'label' is described in RFC 4575 [1], section 5.3.4.  The <available-
687	   media> element contains a sequence of <entry> child elements.  Each
688	   <entry> element contains the following child elements:

690	   o  The <type> element is described in section 5.3.4 of RFC 4575 [1].
691	   o  The <display-text> element is described in section 5.3.4 of RFC
692	      4575 [1].
693	   o  The <status> element is described in section 5.3.4 of RFC 4575
694	      [1].
695	   o  The child element <mixing-mode> describes a default policy by
696	      which the mixer will build the outgoing stream from the incoming
697	      streams.  Notice that this policy is different than the policy
698	      describing the floors for each media.  The <mixing-mode> child
699	      element MUST contain one and only one of the "Moderator-
700	      controlled", "FCFS", and "Automatic" values indicating the default
701	      algorithm to use with every media stream.  The "Moderator-
702	      controlled" value indicates that the moderator of the conference,
703	      controls the media stream policy.  The "FCFS" value indicates a
704	      'first-come-first-served' policy.
705	   o  The <codecs> element specifies the allowed codecs in the
706	      conference.  It has an attribute 'decision' that specifies if the
707	      focus decides the common codec automatically or needs the approval
708	      of the moderator of the conference ("automatic", "moderator-
709	      controlled").  The <codecs> element contains <entry> elements.  A
710	      <entry> element can have the attribute 'name' and 'policy'.  The
711	      'name' attribute identifies a codec.  The list of possible codecs
712	      accepted as a 'name' attribute is defined by the IANA registry for
713	      RTP Payload Types.  The possible values of the attribute 'name'
714	      are the values of the 'subtype' column of the RTP Payload Format
715	      media types per RFC4855[9] defined in IANA [10].  The 'policy'
716	      attribute contains the policy for that codec (allowed, or
717	      disallowed).
718	   o  The <controls> element contains the basic audio and video global
719	      control elements for a conference.  It is expected that for the
720	      majority of the basic conferences, these controls are sufficient.
721	      If the conference server wants to support more advanced controls,
722	      then it is recommended that an extension to the data model be
723	      used.  In the <controls> element the schema is extensible, hence
724	      new control types can be added in the future.  So moderator
725	      controls that affect all media output would go under the
726	      <available-media> element.  The following controls elements are
727	      defined for <controls>:
728	      *  The <mute> element is used in conjunction with an audio stream
729	         to cease transmission of associated media.  That means that for
730	         the entire duration where mute is applicable, all current and
731	         future participants of the conference are muted and will not
732	         receive any audio.  It has a "boolean" value.  If this control
733	         is not specified, access to the control is not available to the
734	         client.
735	      *  The <pause-video> element is used in conjunction with a video
736	         stream to cease transmission of associated media.  It has a
737	         "boolean" value.  If this control is not specified, the access
738	         to the control is not available to the client.
739	      *  The <gain> element is used in conjunction with a media output
740	         stream to indicate the amount of amplification of an audio
741	         stream.  It has an "int" number value.  This control has two
742	         attributes that defines the minimum and maximum amplification
743	         levels: 'min' and 'max'.  If this control is not specified,
744	         access to the control is not available to the client.
745	      *  The <video-layout> element is used in conjunction with a video
746	         stream to specify how the video streams (of participants) are
747	         viewed by each participant.  Only one layout type can be
748	         specified for each output stream.  If there are fewer
749	         participants than panels in the specified layout, then blanking
750	         (black screen) MAY be mixed into the stream on the behalf of
751	         the missing input streams.  If unspecified, the <video-layout>
752	         default type SHOULD be "single-view".  The <layout> types are
753	         as follows, although any number of custom layouts may be
754	         specified in future extensions:
755	         +  single-view: Only one stream is presented by the focus to
756	            all participants in one panel.
757	         +  dual-view: This dual view option will present the video
758	            side-by-side in 2 panels and not alter the aspect ratio of
759	            the streams.  This will require the focus to introduce
760	            blanking on parts of the overall image as viewed by the
761	            participants.
762	         +  dual-view-crop: This side-by-side layout option instructs
763	            the focus to alter the aspect ratio of the streams (alter-
764	            aspect-ratio=TRUE) so that blanking is not necessary.  The
765	            focus handles the cropping of the streams.
766	         +  dual-view-2x1: This layout option instructs the focus to
767	            place one stream above the other, in essence with two rows
768	            and one column.  In this option the aspect ratio is not
769	            altered and blanking is introduced.
770	         +  dual-view-2x1-crop: This layout option also instructs the
771	            focus to place one stream above the other, in essence with
772	            two rows and one column.  In this option the aspect ratio is
773	            altered and the video streams are cropped.
774	         +  quad-view: Four equal-sized panels in a 2x2 layout is
775	            presented by the focus to all participants.  Typically the
776	            aspect ratio of the streams are maintained (alter-aspect-
777	            ratio= FALSE).
778	         +  multiple-3x3: Nine equal-sized panels in a 3x3 layout is
779	            presented by the focus to all participants.  Typically the
780	            aspect ratio of the streams are preserved.

782	         +  multiple-4x4: Sixteen equal-sized panels in a 4x4 layout is
783	            presented by the focus to all participants.  Typically the
784	            aspect ratio of the streams are preserved.
785	         +  multiple-5x1: This option refers to a 5x1 layout where one
786	            panel will occupy 4/9 of the mixed video stream while the
787	            others will each occupy 1/9 of the stream.  Typically the
788	            aspect ratio of the streams is preserved.
789	         +  automatic: This option allows the focus to add panels as
790	            streams are added.

792	4.3.  <host-info>

794	   The <host-info> element contains information about the entity hosting
795	   the conference.  This information is set before conference
796	   activation, and is rarely changed during the conference lifetime.
797	   The <host-info> element and its child elements are described in
798	   RFC4575[1], section 5.4.  Future extensions to the <host-info>
799	   element may define new values.

801	4.4.  <conference-state>

803	   The <conference-state> is introduced in RFC4575 [1].  The
804	   <conference-state> element contains the <allow-conference-event-
805	   subscription>, <user-count>, <active>, and <locked> child elements.

807	4.4.1.  <allow-conference-event-subscription>

809	   The <allow-conference-event-subscription> element represents a
810	   boolean action.  If set to TRUE, the focus is instructed to allow the
811	   subscription to conference state events, such as RFC4575 'SIP Event
812	   Package for Conference State' [1].  If set to FALSE, the subscription
813	   to conference state events would be rejected.  If this element is
814	   undefined it has a default value of TRUE, causing the subscription to
815	   conference state events to be accepted.

817	4.4.2.  <user-count>

819	   The <user-count> child element is explained in RFC 4575 [1], section
820	   5.5.1.

822	4.4.3.  <active>

824	   The <active> child element is explained in RFC 4575 [1], section
825	   5.5.2.

827	4.4.4.  <locked>

829	   The <locked> child element is explained in RFC 4575 [1], section
830	   5.5.3.

832	4.5.  <floor-information>

834	   The <floor-information> element contains the <conference-ID>, <allow-
835	   floor-events>, <floor-request-handling>, and <conference-floor-
836	   policy> child elements.  Other elements from different namespaces MAY
837	   be present for the purposes of extensibility.  The absence of this
838	   element from an XML document indicates that the conference does not
839	   have a floor.

841	4.5.1.  <conference-ID>

843	   The <conference-ID> is a 32-bit BFCP conference identifier defined in
844	   RFC4582 [5] section 5.1. that identifies the BFCP conference the
845	   message belongs to.  This identifier represents a conference instance
846	   within floor control.  When created within the conferencing system,
847	   the 'conference-ID' has a 1:1 mapping to the unique conference object
848	   Identifier (XCON-URI).

850	4.5.2.  <allow-floor-events>

852	   The <allow-floor-events> element represents a boolean action.  If set
853	   to TRUE, the focus is instructed to accept the subscription to floor
854	   control events.  If set to FALSE, the focus is instructed to reject
855	   the subscription.  If this element is undefined, it has a default
856	   value of FALSE, causing the subscription to floor control events to
857	   be rejected.

859	   There are two methods which a conference participant subscribes
860	   himself to a floor control event.  One method is using an offer/
861	   answer exchange mechanism (RFC3264 [11]) using SIP INVITE and BFCP
862	   parameters in the SDP (RFC4583 [12]).  The other method is a general
863	   authorization mechanism described in section 9 of RFC4582 [5] and in
864	   RFC5018 [13].  Future documentation may define additional connection
865	   mechanisms.

867	4.5.3.  <floor-request-handling>

869	   The <floor-request-handling> element defines the actions used by the
870	   conference focus to control floor requests.  This element defines the
871	   action that the focus is to take when processing a particular request
872	   to a floor within a conference.  This element defines values of:

874	   o  "block": This action instructs the focus to deny the floor
875	      request.  This action is the default action taken in the absence
876	      of any other actions.
877	   o  "confirm": This action instructs the focus to allow the request.
878	      The focus then uses the defined floor algorithm to further allow
879	      or deny the floor.  The algorithms used are outside the scope of
880	      this document.

882	   Note that this section discusses floor control information,
883	   therefore, the value "block" in a <floor-request-handling> element is
884	   not related with the "block" value in the <join-handling> element
885	   (see Section 4.6).

887	4.5.4.  <conference-floor-policy>

889	   The <conference-floor-policy> element is mandatory.  One or more
890	   <floor> elements can appear in the <conference-floor-policy> element.

892	   Each <floor> element has the following child elements:

894	   o  <media-label>: Every floor is identified for one or more mandatory
895	      <media-label> element.  If the <available-media> information is
896	      included in the conference document, the value of this element
897	      MUST be equal to the 'label' value of the corresponding media
898	      stream <entry> in the <available-media> container.  The number of
899	      those elements indicates how many floors the conference can have.
900	      A floor can be used for one or more media types;
901	   o  <algorithm>: A floor can be controlled using many algorithms; the
902	      mandatory <algorithm> element MUST be set to any of the
903	      "moderator-controlled", "FCFS" or "random" values indicating the
904	      algorithm.  The "Moderator-controlled" value indicates that the
905	      moderator of the conference controls the floor.  The "FCFS" value
906	      states for 'first-come-first-served' floor control.
907	   o  <max-floor-users>: The <max-floor-users> child element in the
908	      <floor> element is optional and, if present, dictates the maximum
909	      number of users who can have the floor at one time.
910	   o  <moderator-id>: The optional <moderator-id> indicates the 'User
911	      ID' of the moderator.  The 'User ID' is a BFCP identifier defined
912	      in RFC4582 [5] section 5.1.  It MUST be set if the element
913	      <algorithm> is set to "Moderator-controlled" value.  Note that
914	      RFC4582 [5] refers to the moderator role as a 'floor chair'.

916	4.6.  <users>

918	   The <users> element is described in RFC4575 [1] and contains the
919	   <join-handling>, <user-admission-policy>, and <allowed-users-list>
920	   defined in this document and <user> child elements defined in
921	   RFC4575[1].  Notice that the <users> element does not have the
922	   attribute 'state' defined in RFC4575[1] for this element because this
923	   attribute only applies to notifications mechanism.  The following
924	   sections describe these elements in more detail.  Other child
925	   elements and attributes can be used to extend <users> in the future.

927	4.6.1.  <join-handling>

929	   The <join-handling> element defines the actions used by the
930	   conference focus to control conference participation.  This element
931	   defines the action that the focus is to take when processing a
932	   particular request to join a conference.  This element defines values
933	   of:
934	   o  "block": This action instructs the focus to deny access to the
935	      conference.  This action is the default action taken in the
936	      absence of any other actions.
937	   o  "confirm": This action instructs the focus to place the
938	      participant on a pending list (e.g., by parking the call on a
939	      music-on-hold server), awaiting moderator input for further
940	      actions.
941	   o  "allow": This action instructs the focus to accept the conference
942	      join request and grant access to the conference within the
943	      instructions specified in the transformations of this rule.
944	   o  "authenticate": This action instructs the focus that the user has
945	      to provide a combination of username/password.
946	   o  "directed-operator": This action instructs the focus to direct the
947	      user to an operator.

949	4.6.2.  <user-admission-policy>

951	   The <user-admission-policy> is an element that lets an organizer (or
952	   a participant with appropriate rights) choose a policy for the
953	   conference that controls how users are allowed into the conference.
954	   The list of possible values are:

956	   o  "closedAuthenticated": A 'closedAuthenticated' policy requires
957	      each conference participant to be in the allowed users list
958	      (listed under the <allowed-users-list> XML element) with each
959	      participant being sufficiently (up to local policy) authenticated.
960	      Conference join requests for users not in the allowed users list
961	      or participants not authenticated should be rejected unless a
962	      <join-handling> action of 'confirm' is selected in which case the
963	      user is placed on a pending list as indicated earlier.
964	   o  "openAuthenticated": An 'openAuthenticated' policy requires each
965	      conferencing participant to be sufficiently authenticated (as
966	      before) but does not restrict which participants can join the
967	      conference.  Typically this implies that anyone capable of
968	      authenticating with the conferencing system may join the
969	      conference.

971	   o  "anonymous": An 'anonymous' policy allows any join requests in and
972	      is the least restrictive policy.

974	4.6.3.  <allowed-users-list>

976	   The <allowed-users-list> child element contains a list of user URIs,
977	   PSTN phone numbers, roles, or domains (*@example.com) that the focus
978	   uses to determine who can join the conference, who can be invited to
979	   join a conference, or who the focus needs to "refer to" the
980	   conference.  The <allowed-users-list> element includes zero or more
981	   <target> child elements.  This child element includes the mandatory
982	   'uri' attribute and the mandatory 'method' attribute.  The same 'uri'
983	   attribute with different method values can appear in the list more
984	   than once.

986	   The 'method' attribute is a list with the following values:

988	   o  "dial-in": The value "dial-in" is used by the focus to determine
989	      who can join the conference.
990	   o  "dial-out": The value "dial-out" contains a list of resources that
991	      the focus will initiate a session with.
992	   o  "refer": The value "refer" is used by the focus to determine the
993	      resources that the focus needs to "refer to" the conference.  In
994	      SIP, this is achieved by the focus sending a REFER request to
995	      those potential participants.  In a different paradigm, this could
996	      also mean that the focus sends an SMS or an email to the referred
997	      user.  This list can be updated during the conference lifetime so
998	      it can be used for mid-conference refers as well.

1000	   The "refer" value differs from the "dial-out" in that the resources
1001	   on the "refer" value are expected to initiate the session
1002	   establishment toward the focus themselves.  It is also envisioned
1003	   that different users will have different access rights to those lists
1004	   and therefore a separation between the two is needed.

1006	4.6.4.  <user> and Its <user> Sub-elements

1008	   The element <user> is described in RFC5475[1] and describes a single
1009	   participant in the conference.  The <user> element has an attribute
1010	   'entity'.  Notice that the <user> element does not have the attribute
1011	   'state' defined in RFC4575[1] for this element because this attribute
1012	   only applies to notifications mechanism.

1014	   o  The attribute 'entity' contains a unique conference user
1015	      identifier (XCON_USERID).  Other user identifiers can be
1016	      associated with this conference user identifier and enable the
1017	      conferencing system to correlate and map these multiple
1018	      authenticated user identities to a single global user identifier.

1020	      Figure 4 illustrates an example using the conference user
1021	      identifier in association with the user identity defined for BFCP,
1022	      SIP, and H323 user identity.  It should be noted that a
1023	      conferencing system is free to structure such relationships as
1024	      required and this information is just included as a guideline that
1025	      can be used.

1027	                                 +--------------+
1028	                                 |  Conference  |
1029	                                 |     User     |
1030	                                 |  Identifier  |
1031	                                 +--------------+
1032	                                 |    John      |
1033	                                 +------+-------+
1034	                                        |
1035	                                        |
1036	                                        |
1037	                  +---------------------+---------------------+
1038	                  |                     |                     |
1039	          +-------+--------+    +-------+-------+    +--------+-------+
1040	          |  BFCP User ID  |    |  SIP User ID  |    |  H323 User ID  |
1041	          +----------------+    +---------------+    +----------------+
1042	          |   HK37ihdaj    |    |    123674     |    |     928373     |
1043	          +----------------+    +---------------+    +----------------+

1045	                    Figure 4: Conference Object Mapping

1047	   The element <user> element contains the <display-text>, <associated-
1048	   aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>,
1049	   <allow-refer-users-dynamically>, <allow-invite-users-dynamically>,
1050	   <allow-remove-users-dynamically>, and <endpoint>.  The following
1051	   sections describe these elements in more detail.

1053	4.6.4.1.  <display-text>

1055	   The <display-text> child element is explained in RFC 4575 [1],
1056	   section 5.6.1.

1058	4.6.4.2.  <associated-aors>

1060	   The <associated-aors> child element is explained in RFC 4575 [1],
1061	   section 5.6.2.

1063	4.6.4.3.  <provide-anonymity>

1065	   The <provide-anonymity> element provides anonymity to the user.  In
1066	   this case, the focus provides to the rest of the participants an
1067	   anonymous identity for that user, for example anonymousX.  This
1068	   element only affects the way the user information is provided to the
1069	   other participants.  The real information about the user is still
1070	   stored in the data model.  This can be achieved by using the
1071	   <provide-anonymity> element.  It is a boolean transformation.  If set
1072	   to TRUE, the conference participants will see an anonymous identity
1073	   for the user.

1075	4.6.4.4.  <roles>

1077	   The <roles> child element is explained in RFC 4575 [1], section
1078	   5.6.3.

1080	4.6.4.5.  <languages>

1082	   The <languages> child element is explained in RFC 4575 [1], section
1083	   5.6.4.

1085	4.6.4.6.  <cascaded-focus>

1087	   The <cascaded-focus> child element is explained in RFC 4575 [1],
1088	   section 5.6.5.

1090	4.6.4.7.  <allow-refer-users-dynamically>

1092	   The <allow-refer-users-dynamically> element represents a boolean
1093	   action.  If set to TRUE, a participant is allowed to instruct the
1094	   focus to refer a user to the conference without modifying the
1095	   <allowed-users-list> (in SIP terms, a participant is allowed to send
1096	   a REFER request to the focus which results in the focus sending a
1097	   REFER request to the user the referrer wishes to join the
1098	   conference).  If set to FALSE, the refer request is rejected.  If
1099	   this element is undefined it has a value of FALSE, causing the refer
1100	   to be rejected.

1102	4.6.4.8.  <allow-invite-users-dynamically>

1104	   The <allow-invite-users-dynamically> element represents a boolean
1105	   action.  If set to TRUE, a participant is allowed to instruct the
1106	   focus to invite a user to the conference without modifying the
1107	   <allowed-users-list> list (in SIP terms, a participant is allowed to
1108	   send a REFER request to the focus which results in the focus sending
1109	   an INVITE request to the user the referrer wishes to join the
1110	   conference).  If set to FALSE, the refer request is rejected.  If
1111	   this element is undefined it has a value of FALSE, causing the refer
1112	   to be rejected.

1114	4.6.4.9.  <allow-remove-users-dynamically>

1116	   The <allow-remove-users-dynamically> element represents a boolean
1117	   action.  If set to TRUE, a participant is allowed to instruct the
1118	   focus to remove a user from the conference without modifying the
1119	   ruleset (in SIP terms, a participant is allowed to send a REFER
1120	   request to the focus which results in the focus sending an BYE
1121	   request to the user the referrer wishes to leave the conference).  If
1122	   set to FALSE, the refer request is rejected.  If this element is
1123	   undefined it has a value of FALSE, causing the refer to be rejected.

1125	4.6.4.10.  <endpoint>

1127	   The <endpoint> child element is defined in RFC4575[1].  It can
1128	   provide the desired level of detail about the user's devices and
1129	   their signaling sessions taking part in the conference and has the
1130	   following child elements defined in RFC4575 [1]: <display-text>,
1131	   <referred>, <status>, <joining-method>, <joining-info>,
1132	   <disconnection-method>, <disconnection-info>, <media>, and <call-
1133	   info>.  Notice that the <endpoint> element does not have the
1134	   attribute 'state' defined in RFC4575[1] for this element because this
1135	   attribute only applies to notifications mechanism.

1137	   Besides the <endpoint>/<media> child elements defined in RFC 4575[1],
1138	   the <endpoint>/<media> element has two other child elements: <to-
1139	   mixer>, and <from-mixer> described in the following list:

1141	   o  <from-mixer>, <to-mixer>: These are controls that apply to a
1142	      user's media stream being sent from the mixer to the participants
1143	      endpoint or to the mixer from the participants endpoint.  The <to-
1144	      mixer> element details properties associated with the incoming
1145	      streams to the mixer (streams sent to the mixer from the
1146	      participant).  The <from-mixer> element details properties
1147	      associated with the outgoing streams from the mixer (sent from the
1148	      mixer to the participant).  Both of these elements have the
1149	      attribute 'name'.  The 'name' attribute has the values "VideoIn",
1150	      "VideoOut", "AudioOut", and "AudioIn".  The "VideoOut" and
1151	      "AudioOut" media streams detail properties associated with the
1152	      outgoing video and audio from the mixer.  The "VideoIn" and
1153	      "AudioIn" media stream details properties associated with the
1154	      incoming video and audio to the mixer.  More values can be defined
1155	      in the future.  Each of these elements have the <floor> and
1156	      <controls> child elements:

1158	      *  The <floor> element describes a floor that joins this
1159	         participant in the conference.  If a participant, for instance,
1160	         needs to talk in the conference, it first needs to get the
1161	         floor from the chair of the conference.  The <floor> element
1162	         has a "Boolean" value.  A value of FALSE indicates that this
1163	         user does not hold the floor in this moment.  If this control
1164	         is not specified, this user SHOULD NOT specify the floor
1165	         option.
1166	      *  Controls that apply to a specific user would appear under the
1167	         <controls> element.

1169	4.7.  <sidebars-by-ref>

1171	   The <sidebars-by-ref> element contains a set of <entry> child
1172	   elements.  This element is described in RFC4575 [1], 5.9.1.  Notice
1173	   that the <sidebars-by-ref> element does not have the attribute
1174	   'state' defined in RFC4575[1] for this element because this attribute
1175	   only applies to notifications mechanism.

1177	4.8.  <sidebars-by-val>

1179	   The <sidebars-by-val> element contains a set of <entry> child
1180	   elements each containing information about a single sidebar.  This
1181	   element is described in RFC4575 [1], 5.9.2.  Notice that the
1182	   <sidebars-by-val> element does not have the attribute 'state' defined
1183	   in RFC4575[1] for this element because this attribute only applies to
1184	   notifications mechanism.

1186	5.  RELAX NG Schema

1188	   In accordance with the Centralized Conferencing Framework document
1189	   [4], the Conference Object is a logical representation of a
1190	   conference instance.  The conference information schema contains core
1191	   information that is utilized in any conference.  It also contains the
1192	   variable information part of the Conference Object.

1194	   This specification defines some document fragments in RELAX NG format
1195	   [14].

1197	   namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
1198	   namespace local = ""
1199	   namespace ns2 = "urn:ietf:params:xml:ns:conference-info"
1200	   default namespace ns1 = "urn:ietf:params:xml:ns:xcon-conference-info"

1202	   start = element conference-info { conference-type }
1203	   # CONFERENCE TYPE
1204	   conference-type =
1205	     attribute entity { text },
1206	     anyAttribute,
1207	     conference-description-type,
1208	     element host-info { conference-info-urn* }?,
1209	     element conference-state { conference-state-type }?,
1210	     element floor-information { floor-information-type }?,
1211	     element users { users-type },
1212	     element sidebars-by-ref { sidebars-by-ref-type }?,
1213	     element sidebars-by-val { sidebars-by-val-type }?,
1214	     anyElement*
1215	   # CONFERENCE DESCRIPTION TYPE
1216	   conference-description-type =
1217	     element conference-description {
1218	       attribute lang { xsd:language }?,
1219	       anyAttribute,
1220	       element display-text { text }?,
1221	       element subject { text }?,
1222	       element free-text { text }?,
1223	       element keywords {
1224	         list { xsd:string* }
1225	       }?,
1226	       element allow-sidebars { xsd:boolean }?,
1227	       element conference-time { conferencetime-type }?,
1228	       element conf-uris { conference-info-urn* }?,
1229	       element service-uris { conference-info-urn* }?,
1230	       element maximum-user-count { xsd:int }?,
1231	       element available-media { conference-media-type }?,
1232	       anyElement*
1233	     }
1234	   # CONFERENCE TIME
1235	   conferencetime-type =
1236	     anyAttribute,
1237	     element entry {
1238	       element base { text }?,
1239	       element mixing-start-offset {
1240	         xsd:dateTime { pattern = ".+T.+Z.*" },
1241	         attribute required-participant { single-role-type },
1242	         anyAttribute
1243	       }?,
1244	       element mixing-end-offset {
1245	         xsd:dateTime { pattern = ".+T.+Z.*" },
1246	         attribute required-participant { single-role-type },
1247	         anyAttribute
1248	       }?,
1249	       element can-join-after-offset {
1250	         xsd:dateTime { pattern = ".+T.+Z.*" }
1251	       }?,
1252	       element must-join-before-offset {
1253	         xsd:dateTime { pattern = ".+T.+Z.*" }
1254	       }?,
1255	       element notify-end-of-conference { xsd:int }?,
1256	       element allowed-extend-mixing-end-offset { xsd:boolean }?,
1257	       anyElement*
1258	     }*,
1259	     anyElement*
1260	   # CONFERENCE MEDIA TYPE
1261	   conference-media-type =
1262	     anyAttribute,
1263	     element entry { conference-medium-type }*,
1264	     anyElement*
1265	   # CONFERENCE MEDIUM TYPE
1266	   conference-medium-type =
1267	     attribute label { text },
1268	     anyAttribute,
1269	     element display-text { text }?,
1270	     element type { text }?,
1271	     element status { media-status-type }?,
1272	     element mixing-mode { mix-mode-type }?,
1273	     element codecs { codecs-type }?,
1274	     element controls { controls-type }?,
1275	     anyElement*
1276	   # CONTROLS TYPE
1277	   controls-type =
1278	     anyAttribute,
1279	     element control { control-type }*,
1280	     anyElement*
1281	   # MIX MODE TYPE
1282	   mix-mode-type =
1283	     xsd:string "moderator-controlled"
1284	     | xsd:string "FCFS"
1285	     | xsd:string "automatic"
1286	   # CODECS TYPE
1287	   codecs-type =
1288	     attribute decision { decision-type },
1289	     anyAttribute,
1290	     element codec { codec-type }*,
1291	     anyElement*
1292	   # CODEC TYPE
1293	   codec-type =
1294	     attribute name { text },
1295	     attribute policy { policy-type },
1296	     anyAttribute
1297	   # DECISION TYPE
1298	   decision-type =
1299	     xsd:string "automatic" | xsd:string "moderator-controlled"
1300	   # POLICY TYPE
1301	   policy-type = xsd:string "allowed" | xsd:string "disallowed"
1302	   # CONTROL TYPE
1303	   control-type =
1304	     anyAttribute,
1305	     (element mute { xsd:boolean }
1306	      | element pause-video { xsd:boolean }
1307	      | element gain {
1308	          xsd:int { minInclusive = "-127" maxInclusive = "127" }
1309	        }
1310	      | element video-layout {
1311	          xsd:string "single-view"
1312	          | xsd:string "dual-view"
1313	          | xsd:string "dual-view-crop"
1314	          | xsd:string "dual-view-2x1"
1315	          | xsd:string "dual-view-2x1-crop"
1316	          | xsd:string "quad-view"
1317	          | xsd:string "multiple-3x3"
1318	          | xsd:string "multiple-4x4"
1319	          | xsd:string "multiple-5x1"
1320	          | xsd:string "automatic"
1321	        }
1322	      | anyElement*)
1323	   # CONFERENCE STATE TYPE
1324	   conference-state-type =
1325	     anyAttribute,
1326	     element allow-conference-event-subscription { xsd:boolean }?,
1327	     element user-count { xsd:unsignedInt }?,
1328	     element active { xsd:boolean }?,
1329	     element locked { xsd:boolean }?,
1330	     anyElement*
1331	   # FLOOR INFORMATION TYPE
1332	   floor-information-type =
1333	     anyAttribute,
1334	     (element conference-ID { xsd:unsignedInt },
1335	      element allow-floor-events { xsd:boolean },
1336	      element floor-request-handling { floor-request-type },
1337	      element conference-floor-policy { Conference-floor-policy },
1338	      anyElement*)*
1339	   # FLOOR REQUEST TYPE
1340	   floor-request-type = xsd:string "block" | xsd:string "confirm"
1341	   # CONFERENCE FLOOR POLICY
1342	   Conference-floor-policy =
1343	     anyAttribute,
1344	     element floor {
1345	       anyAttribute,
1346	       element media-label { xsd:nonNegativeInteger }+,
1347	       (element algorithm {
1348	          xsd:string "moderator-controlled"
1349	          | xsd:string "FCFS"
1350	          | xsd:string "random"
1351	        },
1352	        element max-floor-users { xsd:nonNegativeInteger },
1353	        element moderator-id { text },
1354	        anyElement*)*
1355	     }+
1356	   # USERS TYPE
1357	   users-type =
1358	     anyAttribute,
1359	     element join-handling { join-handling-type }?,
1360	     element user-admission-policy { user-admission-policy-type }?,
1361	     element user-must-be-specified { xsd:boolean }?,
1362	     element allowed-users-list { UserList }?,
1363	     element user { user-type }*,
1364	     anyElement*
1365	   # USERS ADMISSION POLICY
1366	   user-admission-policy-type =
1367	     xsd:string "closedAuthenticated"
1368	     | xsd:string "openAuthenticated"
1369	     | xsd:string "anonymous"
1370	   # JOIN HANDLING TYPE
1371	   join-handling-type =
1372	     xsd:string "block"
1373	     | xsd:string "confirm"
1374	     | xsd:string "allow"
1375	     | xsd:string "authenticate"
1376	     | xsd:string "directed-operator"
1377	   # USERLIST
1378	   UserList =
1379	     anyAttribute,
1380	     element target { target-type }*,
1381	     anyElement*
1382	   # TARGET TYPE
1383	   target-type =
1384	     attribute uri { xsd:anyURI },
1385	     attribute method { method-type },
1386	     anyAttribute
1387	   # METHOD TYPE
1388	   method-type =
1389	     xsd:string "dial-in" | xsd:string "dial-out" | xsd:string "refer"
1390	   # USER TYPE
1391	   user-type =
1392	     attribute entity { xsd:anyURI },
1393	     anyAttribute,
1394	     element display-text { text }?,
1395	     element associated-aors { conference-info-urn* }?,
1396	     element provide-anonymity { xsd:boolean }?,
1397	     element roles { text }?,
1398	     element languages {
1399	       list { xsd:language }
1400	     }?,
1401	     element cascaded-focus { xsd:anyURI }?,
1402	     element allow-refer-users-dynamically { xsd:boolean }?,
1403	     element allow-invite-users-dynamically { xsd:boolean }?,
1404	     element allow-remove-users-dynamically { xsd:boolean }?,
1405	     element endpoint { endpoint-type }*,
1406	     anyElement*
1407	   # ENDPOINT TYPE
1408	   endpoint-type =
1409	     attribute entity { text },
1410	     anyAttribute,
1411	     element display-text { text }?,
1412	     element referred { conference-info-urn* }?,
1413	     element status { endpoint-status-type }?,
1414	     element joining-method { joining-type }?,
1415	     element joining-info { conference-info-urn* }?,
1416	     element disconnection-method { disconnection-type }?,
1417	     element disconnection-info { conference-info-urn* }?,
1418	     element media { media-type }*,
1419	     element call-info { conference-info-urn* }?,
1420	     anyElement*
1421	   # MEDIA TYPE
1422	   media-type =
1423	     attribute id { xsd:int },
1424	     anyAttribute,
1425	     element display-text { text }?,
1426	     element type { text }?,
1427	     element label { text }?,
1428	     element src-id { text }?,
1429	     element status { media-status-type }?,
1430	     element to-mixer { mixer-type }?,
1431	     element from-mixer { mixer-type }?,
1432	     anyElement*
1433	   # MIXER TYPE
1434	   mixer-type =
1435	     anyAttribute,
1436	     (element floor { xsd:boolean },
1437	      element controls { controls-type })?,
1438	     anyElement*
1439	   # SIDEBARS-BY-REF TYPE
1440	   sidebars-by-ref-type =
1441	     anyAttribute,
1442	     element entry { conference-info-urn* }*,
1443	     anyElement*
1444	   # SIDEBARS-BY-VAL TYPE
1445	   sidebars-by-val-type =
1446	     anyAttribute,
1447	     element entry { conference-type }*,
1448	     anyElement*
1449	   # SINGLE ROLE TYPE
1450	   single-role-type =
1451	     xsd:string "administrator"
1452	     | xsd:string "moderator"
1453	     | xsd:string "participant"
1454	     | xsd:string "none"
1455	   # *********************************
1456	   # EXTENSIBILITY OF THE SCHEMA
1457	   # *********************************

1459	   # EXTENSIBILITY ELEMENTS
1460	   anyElement =
1461	     element * {
1462	       (attribute * { text }
1463	        | text
1464	        | anyElement)*
1465	     }
1466	   # EXTENSIBILITY ATTRIBUTES
1467	   anyAttribute =
1468	     attribute * - (entity
1469	                    | lang
1470	                    | required-participant
1471	                    | label
1472	                    | decision
1473	                    | name
1474	                    | policy
1475	                    | uri
1476	                    | method
1477	                    | id
1478	                    | local:*
1479	                    | ns1:*) { text }*
1480	   # *************************************************************
1481	   # TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
1482	   #  -  RFC4575 -
1483	   # *************************************************************

1485	   # WILDCARD FOR EVENT-PACKAGE NAMESPACE
1486	   conference-info-urn =
1487	     element * - (ns2:* | local:*) {
1488	       mixed {
1489	         (attribute * { text }
1490	          | conference-info-urn)*
1491	       }
1492	     }

1494	   # DEFINITION OF ENDPOINT STATUS TYPE
1495	   media-status-type = "recvonly" | "sendonly" | "sendrecv" | "inactive"
1496	   # ENDPOINT STATUS TYPE
1497	   endpoint-status-type =
1498	     "pending"
1499	     | "dialing-out"
1500	     | "dialing-in"
1501	     | "alerting"
1502	     | "on-hold"
1503	     | "connected"
1504	     | "muted-via-focus"
1505	     | "disconnecting"
1506	     | "disconnected"
1507	   # JOINING TYPE
1508	   joining-type = "dialed-in" | "dialed-out" | "focus-owner"
1509	   # DISCONNECTION TYPE
1510	   disconnection-type = "departed" | "booted" | "failed" | "busy"

1512	6.  XML Schema Extensibility

1514	   The Conference Information Data Model defined in this document is
1515	   meant to be extensible toward specific application domains.  Such
1516	   extensions are accomplished by defining elements, child elements and
1517	   attributes that are specific to the desired application domain.  The
1518	   IETF MAY extend the data model schema with extension elements from
1519	   the same namespace, but other instances are free to extend it from
1520	   other than urn:ietf:params:xml:ns:xcon-conference-info.

1522	   Elements or attributes from unknown namespaces MUST be ignored.

1524	7.  XML Example

1526	   The following is an example of a conference information document.
1527	   The conference starts on October 17, 2007, at 10:30 AM in New York
1528	   City and finishes the same day at 12:30 PM every week.  In this
1529	   example, there are currently 3 participants in a conference, one
1530	   administrator, one moderator, and one participant.  Note that
1531	   sidebars are allowed in this conference and there is one sidebar in
1532	   the conference.  Also note that there is one floor moderator for the
1533	   audio and a different floor moderator for the video.

1535	 <?xml version="1.0" encoding="UTF-8"?>
1536	   <conference-info xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
1537	       entity="conference123@example.com">
1538	       <!--
1539	           CONFERENCE DESCRIPTION

1541	       -->

1543	       <conference-description lang="en-us">
1544	           <display-text>Discussion of Formula-1 racing</display-text>
1545	           <subject> Sports:Formula-1</subject>
1546	           <free-text>This is a conference example</free-text>
1547	           <keywords>Formula-1, cars</keywords>
1548	           <webpage>http://www.example.com/users/formula-1</webpage>
1549	           <allow-sidebars>true</allow-sidebars>
1550	           <!--
1551	           CONFERENCE TIME
1552	           -->
1553	           <conference-time>
1554	               <entry>
1555	                   <base>BEGIN:VCALENDAR
1556	 PRODID:-//LlamaSpinner Inc.//NONSGML CamelCall//EN
1557	 VERSION:2.0
1558	 BEGIN:VEVENT
1559	 DTSTAMP:20061103T140728Z
1560	 UID:20061103T140728Z-345FDA-carol@example.com
1561	 ORGANIZER:MAILTO:carol@example.com
1562	 DTSTART:20071017T143000Z
1563	 RRULE:FREQ=WEEKLY
1564	 DTEND:20071217T163000Z
1565	 END:VEVENT
1566	 END:VCALENDAR</base>
1567	                   <mixing-start-offset required-participant="moderator"
1568	                      > 2007-10-17T14:29:00Z</mixing-start-offset>
1569	                   <mixing-end-offset required-participant="participant"
1570	                      > 2007-10-17T16:31:00Z</mixing-end-offset>
1571	                   <must-join-before-offset
1572	                      > 2007-10-17T15:30:00Z</must-join-before-offset>
1573	               </entry>
1574	           </conference-time>
1575	           <!--
1576	           CONFERENCE UNIQUE IDENTIFIERS
1577	           -->
1578	           <conf-uris>
1579	               <entry>
1580	                   <uri>tel:+3585671234</uri>
1581	                   <display-text>Conference Bridge</display-text>
1582	                   <purpose>participation</purpose>
1583	               </entry>
1584	               <entry>
1585	                   <uri>http://www.example.com/live.ram</uri>
1586	                   <purpose>streaming</purpose>
1587	               </entry>
1588	           </conf-uris>
1589	           <!--
1590	             SERVICE URIS
1591	           -->
1592	           <service-uris>
1593	               <entry>
1594	                   <uri>http://www.example.com/formula1/</uri>
1595	                   <purpose>web-page</purpose>
1596	               </entry>
1597	           </service-uris>
1598	           <!--
1599	             MAXIMUM USER COUNT
1600	           -->
1601	           <maximum-user-count>
1602	               <entry role="administrator">2</entry>
1603	               <entry role="moderator">5</entry>
1604	               <entry role="participant">150</entry>
1605	           </maximum-user-count>
1606	           <!--
1607	             AVAILABLE MEDIA
1608	           -->
1609	           <available-media>
1610	               <entry label="10234">
1611	                   <display-text>main audio</display-text>
1612	                   <type>audio</type>
1613	                   <status>sendrecv</status>
1614	                   <mixing-mode>automatic</mixing-mode>
1615	                   <mix-level>3</mix-level>
1616	                   <codecs decision="automatic">
1617	                       <codec name="PCMU" policy="allowed"/>
1618	                   </codecs>
1619	               </entry>
1620	               <entry label="10235">
1621	                   <display-text>main video</display-text>
1622	                   <type>video</type>
1623	                   <status>sendrecv</status>
1624	                   <mixing-mode>automatic</mixing-mode>
1625	                   <mix-level>4</mix-level>
1626	                   <codecs decision="automatic">
1627	                       <codec name="H.263" policy="allowed"/>
1628	                   </codecs>
1629	               </entry>
1630	           </available-media>
1631	       </conference-description>
1632	       <!--
1633	           HOST INFO
1634	         -->
1635	       <host-info>
1636	           <display-text>Formula1</display-text>
1637	           <web-page>http://www.example.com/formula1/</web-page>
1638	           <uris>
1639	               <entry>
1640	                   <uri>sip:alice@example.com</uri>
1641	               </entry>
1642	               <entry>
1643	                   <uri>sip:carol@example.com</uri>
1644	               </entry>
1645	           </uris>
1646	       </host-info>
1647	       <!--
1648	           CONFERENCE STATE
1649	         -->
1650	       <conference-state>
1651	           <allow-conference-state>true</allow-conference-state>
1652	           <user-count>3</user-count>
1653	           <active>true</active>
1654	           <locked>false</locked>
1655	       </conference-state>
1656	       <!--
1657	           FLOOR INFORMATION
1658	         -->
1659	       <floor-information>
1660	           <conference-ID>567</conference-ID>
1661	           <allow-floor-events>true</allow-floor-events>
1662	           <floor-request-handling>confirm</floor-request-handling>
1663	           <conference-floor-policy>
1664	               <floor>
1665	                   <media-label>10234</media-label>
1666	                   <media-label>10235</media-label>
1667	                   <algorithm>moderator-controlled</algorithm>
1668	                   <max-floor-users>1</max-floor-users>
1669	                   <moderator-id>234</moderator-id>
1670	               </floor>
1671	           </conference-floor-policy>
1672	       </floor-information>
1673	       <!--
1674	           USERS
1675	         -->
1676	       <users>
1677	           <join-handling>allow</join-handling>
1678	           <user-admission-policy
1679	               >openAuthenticated</user-admission-policy>
1680	           <!--
1681	            ALLOWED USERS LIST
1682	           -->
1683	           <allowed-users-list>
1684	               <target uri="sip:bob@example.com" method="dial-out"/>
1685	               <target uri="sip:alice@example.com" method="dial-out"/>
1686	               <target uri="sip:carol@example.com" method="dial-out"/>
1687	               <target uri="sip:john@example.com" method="refer"/>
1688	           </allowed-users-list>
1689	           <!--
1690	             USER BOB
1691	           -->
1692	           <user entity="bob534">
1693	               <display-text>Bob Hoskins</display-text>
1694	               <associated-aors>
1695	                   <SIP>
1696	                       <uri>mailto:bob@example.com</uri>
1697	                       <display-text>email</display-text>
1698	                   </SIP>
1699	               </associated-aors>
1700	               <provide-anonymity>false</provide-anonymity>
1701	               <roles>
1702	                   <entry>participant</entry>
1703	               </roles>
1704	               <languages>en</languages>
1705	               <allow-refer-users-dynamically
1706	                   >false</allow-refer-users-dynamically>
1707	               <allow-invite-users-dynamically
1708	                   >false</allow-invite-users-dynamically>
1709	               <allow-remove-users-dynamically
1710	                   >false</allow-remove-users-dynamically>
1711	               <!--
1712	                   ENDPOINTS
1713	               -->
1714	               <endpoint entity="sip:bob@example.com">
1715	                   <display-text>Bob's Laptop</display-text>
1716	                   <referred>
1717	                       <when>2006-10-17T14:00:00Z</when>
1718	                       <reason>expert required</reason>
1719	                       <by>sip:alice@example.com</by>
1720	                   </referred>
1721	                   <status>connected</status>
1722	                   <joining-method>dialed-out</joining-method>
1723	                   <joining-info>
1724	                       <when>2006-10-17T14:00:00Z</when>
1725	                       <reason>invitation</reason>
1726	                       <by>sip:alice@example.com</by>
1727	                   </joining-info>

1729	                   <!--
1730	                       MEDIA
1731	                   -->
1732	                   <media id="1">
1733	                       <label>10235</label>
1734	                       <src-id>432424</src-id>
1735	                   </media>
1736	                   <!--
1737	                       CALL INFO
1738	                   -->
1739	                   <call-info>
1740	                       <sip>
1741	                           <display-text>full info</display-text>
1742	                           <call-id>hsjh8980vhsb78</call-id>
1743	                           <from-tag>vav738dvbs</from-tag>
1744	                           <to-tag>8954jgjg8432</to-tag>
1745	                       </sip>
1746	                   </call-info>
1747	               </endpoint>
1748	           </user>

1750	           <!--
1751	               USER ALICE
1752	           -->

1754	           <user entity="alice334">
1755	               <display-text>Alice Kay</display-text>
1756	               <associated-aors>
1757	                   <SIP>
1758	                       <uri>mailto:alice@example.com</uri>
1759	                       <display-text>email</display-text>
1760	                   </SIP>
1761	               </associated-aors>
1762	               <provide-anonymity>false</provide-anonymity>
1763	               <roles>
1764	                   <entry>moderator</entry>
1765	               </roles>
1766	               <languages>en</languages>
1767	               <allow-refer-users-dynamically
1768	                   >true</allow-refer-users-dynamically>
1769	               <allow-invite-users-dynamically
1770	                   >true</allow-invite-users-dynamically>
1771	               <allow-remove-users-dynamically
1772	                   >true</allow-remove-users-dynamically>
1773	               <!--
1774	                   ENDPOINTS
1775	               -->
1776	               <endpoint entity="sip:alice@example.com">
1777	                   <display-text>Alice's Desktop</display-text>
1778	                   <status>connected</status>
1779	                   <joining-method>dialed-in</joining-method>
1780	                   <joining-info>
1781	                       <when>2006-10-17T13:35:08Z</when>
1782	                       <reason>invitation</reason>
1783	                       <by>sip:conference@example.com</by>
1784	                   </joining-info>
1785	                   <!--
1786	                       MEDIA
1787	                   -->
1788	                   <media id="1">
1789	                       <label>10235</label>
1790	                       <src-id>432424</src-id>
1791	                       <status>sendrecv</status>
1792	                   </media>
1793	                   <media id="2">
1794	                       <label>10234</label>
1795	                       <src-id>532535</src-id>
1796	                       <status>sendrecv</status>
1797	                   </media>
1798	                   <!--
1799	                       CALL INFO
1800	                   -->
1801	                   <call-info>
1802	                       <sip>
1803	                           <display-text>full info</display-text>
1804	                           <call-id>truy45469123478</call-id>
1805	                           <from-tag>asd456cbgt</from-tag>
1806	                           <to-tag>3456jgjg1234</to-tag>
1807	                       </sip>
1808	                   </call-info>
1809	               </endpoint>
1810	           </user>

1812	           <!--
1813	                  USER CAROL
1814	                   -->
1815	           <user entity="carol233">
1816	               <display-text>Carol More</display-text>
1817	               <associated-aors>
1818	                   <SIP>
1819	                       <uri>mailto:carol@example.com</uri>
1820	                       <display-text>email</display-text>
1821	                   </SIP>
1822	               </associated-aors>
1823	               <provide-anonymity>false</provide-anonymity>
1824	               <roles>
1825	                   <entry>administrator</entry>
1826	               </roles>
1827	               <languages>en</languages>
1828	               <allow-refer-users-dynamically
1829	                   >true</allow-refer-users-dynamically>
1830	               <allow-invite-users-dynamically
1831	                   >true</allow-invite-users-dynamically>
1832	               <allow-remove-users-dynamically
1833	                   >true</allow-remove-users-dynamically>
1834	               <!--
1835	                   ENDPOINTS
1836	               -->
1837	               <endpoint entity="sip:carol@example.com">
1838	                   <display-text>Carol's Computer</display-text>
1839	                   <status>connected</status>
1840	                   <joining-method>dialed-in</joining-method>
1841	                   <joining-info>
1842	                       <when>2006-10-17T13:30:05Z</when>
1843	                       <reason>invitation</reason>
1844	                       <by>sip:conference@example.com</by>
1845	                   </joining-info>
1846	                   <!--
1847	                       MEDIA
1848	                   -->
1849	                   <media id="1">
1850	                       <label>10235</label>
1851	                       <src-id>432424</src-id>
1852	                       <status>sendrecv</status>
1853	                   </media>
1854	                   <media id="2">
1855	                       <label>10234</label>
1856	                       <src-id>532535</src-id>
1857	                       <status>sendrecv</status>
1858	                   </media>
1859	                   <!--
1860	                       CALL INFO
1861	                   -->
1862	                   <call-info>
1863	                       <sip>
1864	                           <display-text>full info</display-text>
1865	                           <call-id>wevb12562321894</call-id>
1866	                           <from-tag>asw456wedf</from-tag>
1867	                           <to-tag>2365dfrt3497</to-tag>
1868	                       </sip>
1869	                   </call-info>
1870	               </endpoint>
1871	           </user>
1872	       </users>
1873	       <!--
1874	            SIDEBARS BY REFERENCE
1875	          -->
1876	       <sidebars-by-ref>
1877	           <entry>
1878	               <uri>conf223</uri>
1879	               <display-text>private with Bob</display-text>
1880	           </entry>
1881	       </sidebars-by-ref>
1882	       <!--
1883	            SIDEBARS BY VALUE
1884	          -->
1885	       <sidebars-by-val>
1886	           <entry entity="conf223">
1887	               <users>
1888	                   <user entity="bob534"/>
1889	                   <user entity="carol233"/>
1890	               </users>
1891	           </entry>
1892	       </sidebars-by-val>
1893	   </conference-info>

1895	   Note that due to RFC formatting conventions, this documents splits
1896	   lines whose content would exceed 72 characters.  Two backslash
1897	   characters mark where line folding has taken place.  These
1898	   backslashes would not appear in the actual XML data model.

1900	8.  Security Considerations

1902	   There are numerous security considerations for this document.  This
1903	   section considers them.

1905	8.1.  Authentication

1907	   A malicious user can manipulate parts of the Conference Information
1908	   Data Model privileges document giving themselves and others
1909	   privileges to manipulate the document.  It is very important that
1910	   only authorized clients are able to manipulate the Conference
1911	   Information Data Model document.

1913	   The security considerations for authentication (section 10.1)
1914	   described in the centralized conferencing framework [1] applies to
1915	   this document.  The focus must ensure that only authorized entities
1916	   are able to manipulate the data to access the information.

1918	8.2.  Confidentiality

1920	   Participants of a conference may not want to reveal some private
1921	   information to other users.  The Conference Information Data Model
1922	   contains sensitive data which should not be analyzed or given to
1923	   anyone.  Confidentiality is provided through encryption.  Strong end-
1924	   to-end authentication and encryption can be done using public keys,
1925	   and end-to-end encryption can be done using private keys.  It is
1926	   RECOMMENDED that the protocols that manipulated the conference
1927	   information data model use a strong encryption for conference
1928	   information protection.

1930	8.3.  Integrity

1932	   It is important that the Conference Information Data Model can only
1933	   be accessed or modified by those authorized users.  Without
1934	   integrity, the Conference Information Data Model could be modified,
1935	   fooling the user into believing incorrect information.  Measures
1936	   taken to ensure integrity include maintaining rigorous authentication
1937	   practices.

1939	9.  IANA Considerations

1941	9.1.  Conference Relax NG Schema Registration

1943	     URI:  urn:ietf:params:xml:ns:xcon-conference-info

1945	     Relax NG Schema:  The Relax NG schema to be registered is contained
1946	        in Section 5.  Its first line is

1948	     namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"

1950	        and its last line is

1952	     disconnection-type = "departed" | "booted" | "failed" | "busy"

1954	9.2.  Conference Namespace Registration

1956	   URI: urn:ietf:params:xml:ns:xcon-conference-info

1958	9.3.  Conference Object Identifier Registration

1960	    XCON_URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ]

1962	    conf-object-id = 1*( unreserved / "+" / "=" / "/" )

1964	   host, port, and unreserved are defined in RFC3986[15]

1966	9.4.  Conference User Identifier Registration

1968	    XCON_USERID = "xcon_userid" ":" conf-object-id

1970	    conf-object-id = 1*( unreserved / "+" / "=" / "/" )

1972	   unreserved is defined in RFC3986[15]

1974	10.  Acknowledgements

1976	   This document is really a distillation of many ideas discussed over a
1977	   long period of time.  These ideas were contributed by many different
1978	   drafts in the XCON working group and the SIPPING working group.  We
1979	   would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris
1980	   Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Aki
1981	   Niemi, Jari Urpilainen, Rohan Mahy, and Henning Schulzrinne for their
1982	   comments.  Also, we would like to thank Mary Barnes, and Chris
1983	   Boulton for letting us use the conference and user identifier
1984	   information of their xcon drafts.  Last but not least, I would like
1985	   to express my gratitude to all those reviewers for their invaluable
1986	   contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi,
1987	   Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, and
1988	   Ben Campbell.

1990	11.  References

1992	11.1.  Normative References

1994	   [1]   Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
1995	         Initiation Protocol (SIP) Event Package for Conference State",
1996	         RFC 4575, August 2006.

1998	   [2]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
1999	         Levels", BCP 14, RFC 2119, March 1997.

2001	   [3]   Dawson, F. and Stenerson, D., "Internet Calendaring and
2002	         Scheduling Core Object Specification (iCalendar)", RFC 2445,
2003	         November 1998.

2005	11.2.  Informative References

2007	   [4]   Barnes, M., "A Framework for Centralized Conferencing",
2008	         draft-ietf-xcon-framework-09 (work in progress), August 2007.

2010	   [5]   Camarillo, G., Ott, J., and K. Drage, "The Binary Floor Control
2011	         Protocol (BFCP)", RFC 4582, November 2006.

2013	   [6]   Roach, A., "Session Initiation Protocol (SIP)-Specific Event
2014	         Notification", RFC 3265, June 2002.

2016	   [7]   Rosenberg, J., "A Framework for Conferencing with the Session
2017	         Initiation Protocol (SIP)", RFC 4353, February 2006.

2019	   [8]   Paoli, J., Maler, E., Sperberg-McQueen, C., and T. Bray,
2020	         "Extensible Markup Language (XML) 1.0 (Second Edition)", World
2021	         Wide Web Consortium FirstEdition REC-xml-20001006,
2022	         October 2000, <http://www.w3.org/TR/2000/REC-xml-20001006>.

2024	   [9]   Casner, S., "Media Type Registration of RTP Payload Formats",
2025	         RFC 4855, February 2007.

2027	   [10]  "IANA registry for RTP Payload Types"
2028	         "http://www.iana.org/assignments/rtp-parameters".

2030	   [11]  Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model with
2031	         Session Description Protocol (SDP)", RFC 3264, June 2002.

2033	   [12]  Camarillo, G., "Session Description Protocol (SDP) Format for
2034	         Binary Floor Control Protocol (BFCP) Streams", RFC 4583,
2035	         November 2006.

2037	   [13]  Camarillo, G., "Connection Establishment in the Binary Floor
2038	         Control Protocol (BFCP)", RFC 5018, September 2007.

2040	   [14]  "RELAX NG Home Page" "http://relaxng.org/".

2042	   [15]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
2043	         Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986,
2044	         January 2005.

2046	Appendix A.  Appendix A.  Non-Normative RELAX NG Schema in XML Syntax

2048	   <?xml version="1.0" encoding="UTF-8"?>
2049	   <grammar ns="urn:ietf:params:xml:ns:xcon-conference-info"
2050	    xmlns="http://relaxng.org/ns/structure/1.0"
2051	    xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
2052	    datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
2053	    <start>
2054	     <element name="conference-info">
2055	      <ref name="conference-type"/>
2056	     </element>

2058	    </start>
2059	    <!--
2060	           CONFERENCE TYPE
2061	       -->
2062	    <define name="conference-type">
2063	     <attribute name="entity">
2064	      <text/>
2065	     </attribute>
2066	     <ref name="anyAttribute"/>
2067	     <ref name="conference-description-type"/>
2068	     <optional>
2069	      <element name="host-info">
2070	        <zeroOrMore>
2071	         <ref name="conference-info-urn"/>
2072	        </zeroOrMore>
2073	      </element>
2074	     </optional>
2075	     <optional>
2076	     <element name="conference-state">
2077	       <ref name="conference-state-type"/>
2078	     </element>
2079	     </optional>
2080	     <optional>
2081	      <element name="floor-information">
2082	       <ref name="floor-information-type"/>
2083	      </element>
2084	     </optional>
2085	     <element name="users">
2086	      <ref name="users-type"/>
2087	     </element>
2088	     <optional>
2089	      <element name="sidebars-by-ref">
2090	       <ref name="sidebars-by-ref-type"/>
2091	      </element>
2092	     </optional>
2093	     <optional>
2094	      <element name="sidebars-by-val">
2095	       <ref name="sidebars-by-val-type"/>
2096	      </element>
2097	     </optional>
2098	     <zeroOrMore>
2099	      <ref name="anyElement"/>
2100	     </zeroOrMore>
2101	    </define>
2102	    <!--
2103	           CONFERENCE DESCRIPTION TYPE
2104	       -->
2105	    <define name="conference-description-type">
2106	     <element name="conference-description">
2107	      <optional>
2108	       <attribute name="lang">
2109	        <data type="language"/>
2110	       </attribute>
2111	      </optional>
2112	      <ref name="anyAttribute"/>
2113	      <optional>
2114	       <element name="display-text">
2115	        <text/>
2116	       </element>
2117	      </optional>
2118	      <optional>
2119	       <element name="subject">
2120	        <text/>
2121	       </element>
2122	      </optional>
2123	      <optional>
2124	       <element name="free-text">
2125	        <text/>
2126	       </element>
2127	      </optional>
2128	      <optional>
2129	       <element name="keywords">
2130	        <list>
2131	         <zeroOrMore>
2132	          <data type="string"/>
2133	         </zeroOrMore>
2134	        </list>
2135	       </element>
2136	      </optional>
2137	      <optional>
2138	       <element name="allow-sidebars">
2139	        <data type="boolean"/>
2140	       </element>
2141	      </optional>
2142	      <optional>
2143	       <element name="conference-time">
2144	        <ref name="conferencetime-type"/>
2145	       </element>
2146	      </optional>
2147	      <optional>
2148	       <element name="conf-uris">
2149	         <zeroOrMore>
2150	          <ref name="conference-info-urn"/>
2151	         </zeroOrMore>
2152	       </element>
2153	      </optional>
2154	      <optional>
2155	       <element name="service-uris">
2156	         <zeroOrMore>
2157	          <ref name="conference-info-urn"/>
2158	         </zeroOrMore>
2159	       </element>
2160	      </optional>
2161	      <optional>
2162	       <element name="maximum-user-count">
2163	        <data type="int"/>
2164	       </element>
2165	      </optional>
2166	      <optional>
2167	       <element name="available-media">
2168	        <ref name="conference-media-type"/>
2169	       </element>
2170	       </optional>
2171	      <zeroOrMore>
2172	       <ref name="anyElement"/>
2173	      </zeroOrMore>
2174	     </element>
2175	    </define>
2176	    <!--
2177	           CONFERENCE TIME
2178	       -->
2179	    <define name="conferencetime-type">
2180	     <ref name="anyAttribute"/>
2181	     <zeroOrMore>
2182	      <element name="entry">
2183	       <optional>
2184	        <element name="base">
2185	         <text/>
2186	        </element>
2187	       </optional>
2188	       <optional>
2189	        <element name="mixing-start-offset">
2190	         <data type="dateTime">
2191	          <param name="pattern">.+T.+Z.*</param>
2192	         </data>
2193	         <attribute name="required-participant">
2194	          <ref name="single-role-type"/>
2195	         </attribute>
2196	         <ref name="anyAttribute"/>
2197	        </element>
2198	       </optional>
2199	       <optional>
2200	        <element name="mixing-end-offset">
2201	         <data type="dateTime">
2202	          <param name="pattern">.+T.+Z.*</param>
2203	         </data>
2204	         <attribute name="required-participant">
2205	          <ref name="single-role-type"/>
2206	         </attribute>
2207	         <ref name="anyAttribute"/>
2208	        </element>
2209	       </optional>
2210	       <optional>
2211	        <element name="can-join-after-offset">
2212	         <data type="dateTime">
2213	          <param name="pattern">.+T.+Z.*</param>
2214	         </data>
2215	        </element>
2216	       </optional>
2217	       <optional>
2218	        <element name="must-join-before-offset">
2219	         <data type="dateTime">
2220	          <param name="pattern">.+T.+Z.*</param>
2221	         </data>
2222	        </element>
2223	       </optional>
2224	       <optional>
2225	        <element name="notify-end-of-conference">
2226	         <data type="int"/>
2227	        </element>
2228	       </optional>
2229	       <optional>
2230	        <element name="allowed-extend-mixing-end-offset">
2231	         <data type="boolean"/>
2232	        </element>
2233	       </optional>
2234	       <zeroOrMore>
2235	        <ref name="anyElement"/>
2236	       </zeroOrMore>
2237	      </element>
2238	     </zeroOrMore>
2239	     <zeroOrMore>
2240	      <ref name="anyElement"/>
2241	     </zeroOrMore>
2242	    </define>

2244	    <!--
2245	           CONFERENCE MEDIA TYPE
2246	       -->
2247	    <define name="conference-media-type">
2248	     <ref name="anyAttribute"/>
2249	     <zeroOrMore>
2250	      <element name="entry">
2251	       <ref name="conference-medium-type"/>
2252	      </element>
2253	     </zeroOrMore>
2254	     <zeroOrMore>
2255	      <ref name="anyElement"/>
2256	     </zeroOrMore>
2257	    </define>
2258	    <!--
2259	           CONFERENCE MEDIUM TYPE
2260	       -->
2261	    <define name="conference-medium-type">
2262	     <attribute name="label">
2263	      <text/>
2264	     </attribute>
2265	     <ref name="anyAttribute"/>
2266	     <optional>
2267	      <element name="display-text">
2268	       <text/>
2269	      </element>
2270	     </optional>
2271	     <optional>
2272	      <element name="type">
2273	       <text/>
2274	      </element>
2275	     </optional>
2276	     <optional>
2277	      <element name="status">
2278	       <ref name="media-status-type"/>
2279	      </element>
2280	     </optional>
2281	     <optional>
2282	      <element name="mixing-mode">
2283	       <ref name="mix-mode-type"/>
2284	      </element>
2285	     </optional>
2286	     <optional>
2287	      <element name="codecs">
2288	       <ref name="codecs-type"/>
2289	      </element>
2290	     </optional>
2291	     <optional>
2292	      <element name="controls">
2293	       <ref name="controls-type"/>
2294	      </element>
2295	     </optional>
2296	     <zeroOrMore>
2297	      <ref name="anyElement"/>

2299	     </zeroOrMore>
2300	    </define>
2301	    <!--
2302	           CONTROLS TYPE
2303	       -->
2304	    <define name="controls-type">
2305	     <ref name="anyAttribute"/>
2306	     <zeroOrMore>
2307	      <element name="control">
2308	       <ref name="control-type"/>
2309	      </element>
2310	     </zeroOrMore>
2311	     <zeroOrMore>
2312	      <ref name="anyElement"/>
2313	     </zeroOrMore>
2314	    </define>
2315	    <!--
2316	           MIX MODE TYPE
2317	       -->
2318	    <define name="mix-mode-type">
2319	     <choice>
2320	      <value type="string">moderator-controlled</value>
2321	      <value type="string">FCFS</value>
2322	      <value type="string">automatic</value>
2323	     </choice>
2324	    </define>
2325	    <!--
2326	           CODECS TYPE
2327	       -->
2328	    <define name="codecs-type">
2329	     <attribute name="decision">
2330	      <ref name="decision-type"/>
2331	     </attribute>
2332	     <ref name="anyAttribute"/>
2333	     <zeroOrMore>
2334	      <element name="codec">
2335	       <ref name="codec-type"/>
2336	      </element>
2337	     </zeroOrMore>
2338	     <zeroOrMore>
2339	      <ref name="anyElement"/>
2340	     </zeroOrMore>
2341	    </define>
2342	    <!--
2343	           CODEC TYPE
2344	       -->
2345	    <define name="codec-type">
2346	     <attribute name="name">
2347	      <text/>
2348	     </attribute>
2349	     <attribute name="policy">
2350	      <ref name="policy-type"/>
2351	     </attribute>
2352	     <ref name="anyAttribute"/>
2353	    </define>
2354	    <!--
2355	           DECISION TYPE
2356	       -->
2357	    <define name="decision-type">
2358	     <choice>
2359	      <value type="string">automatic</value>
2360	      <value type="string">moderator-controlled</value>
2361	     </choice>
2362	    </define>
2363	    <!--
2364	           POLICY TYPE
2365	       -->
2366	    <define name="policy-type">
2367	     <choice>
2368	      <value type="string">allowed</value>
2369	      <value type="string">disallowed</value>
2370	     </choice>
2371	    </define>
2372	    <!--
2373	           CONTROL TYPE
2374	       -->
2375	    <define name="control-type">
2376	     <ref name="anyAttribute"/>
2377	     <choice>
2378	      <element name="mute">
2379	       <data type="boolean"/>
2380	      </element>
2381	      <element name="pause-video">
2382	       <data type="boolean"/>
2383	      </element>
2384	      <element name="gain">
2385	       <data type="int">
2386	        <param name="minInclusive">-127</param>
2387	        <param name="maxInclusive">127</param>
2388	       </data>
2389	      </element>
2390	      <element name="video-layout">
2391	       <choice>
2392	        <value type="string">single-view</value>
2393	        <value type="string">dual-view</value>
2394	        <value type="string">dual-view-crop</value>
2395	        <value type="string">dual-view-2x1</value>
2396	        <value type="string">dual-view-2x1-crop</value>
2397	        <value type="string">quad-view</value>
2398	        <value type="string">multiple-3x3</value>
2399	        <value type="string">multiple-4x4</value>
2400	        <value type="string">multiple-5x1</value>
2401	        <value type="string">automatic</value>
2402	       </choice>
2403	      </element>
2404	      <zeroOrMore>
2405	       <ref name="anyElement"/>
2406	      </zeroOrMore>
2407	     </choice>
2408	    </define>
2409	    <!--
2410	           CONFERENCE STATE TYPE
2411	       -->
2412	    <define name="conference-state-type">
2413	     <ref name="anyAttribute"/>
2414	     <optional>
2415	      <element name="allow-conference-event-subscription">
2416	       <data type="boolean"/>
2417	      </element>
2418	     </optional>
2419	     <optional>
2420	      <element name="user-count">
2421	       <data type="unsignedInt"/>
2422	      </element>
2423	     </optional>
2424	     <optional>
2425	      <element name="active">
2426	       <data type="boolean"/>
2427	      </element>
2428	     </optional>
2429	     <optional>
2430	      <element name="locked">
2431	       <data type="boolean"/>
2432	      </element>
2433	     </optional>
2434	     <zeroOrMore>
2435	      <ref name="anyElement"/>
2436	     </zeroOrMore>
2437	    </define>
2438	    <!--
2439	           FLOOR INFORMATION TYPE
2440	       -->
2441	    <define name="floor-information-type">
2442	     <ref name="anyAttribute"/>
2443	     <zeroOrMore>
2444	      <element name="conference-ID">
2445	       <data type="unsignedInt"/>
2446	      </element>
2447	      <element name="allow-floor-events">
2448	       <data type="boolean"/>
2449	      </element>
2450	      <element name="floor-request-handling">
2451	       <ref name="floor-request-type"/>
2452	      </element>
2453	      <element name="conference-floor-policy">
2454	       <ref name="Conference-floor-policy"/>
2455	      </element>
2456	      <zeroOrMore>
2457	       <ref name="anyElement"/>
2458	      </zeroOrMore>
2459	     </zeroOrMore>
2460	    </define>
2461	    <!--
2462	           FLOOR REQUEST TYPE
2463	       -->
2464	    <define name="floor-request-type">
2465	     <choice>
2466	      <value type="string">block</value>
2467	      <value type="string">confirm</value>
2468	     </choice>
2469	    </define>
2470	    <!--
2471	           CONFERENCE FLOOR POLICY
2472	       -->
2473	    <define name="Conference-floor-policy">
2474	     <ref name="anyAttribute"/>
2475	     <oneOrMore>
2476	      <element name="floor">
2477	       <ref name="anyAttribute"/>
2478	       <oneOrMore>
2479	        <element name="media-label">
2480	         <data type="nonNegativeInteger"/>
2481	        </element>
2482	        </oneOrMore>
2483	        <zeroOrMore>
2484	        <element name="algorithm">
2485	         <choice>
2486	          <value type="string">moderator-controlled</value>
2487	          <value type="string">FCFS</value>
2488	          <value type="string">random</value>
2489	         </choice>
2490	        </element>
2491	        <element name="max-floor-users">
2492	         <data type="nonNegativeInteger"/>
2493	        </element>
2494	        <element name="moderator-id">
2495	         <text/>
2496	        </element>
2497	        <zeroOrMore>
2498	         <ref name="anyElement"/>
2499	        </zeroOrMore>
2500	       </zeroOrMore>
2501	      </element>
2502	     </oneOrMore>
2503	    </define>
2504	    <!--
2505	           USERS TYPE
2506	       -->
2507	    <define name="users-type">
2508	     <ref name="anyAttribute"/>
2509	     <optional>
2510	      <element name="join-handling">
2511	       <ref name="join-handling-type"/>
2512	      </element>
2513	     </optional>
2514	     <optional>
2515	      <element name="user-admission-policy">
2516	       <ref name="user-admission-policy-type"/>
2517	      </element>
2518	     </optional>
2519	     <optional>
2520	      <element name="user-must-be-specified">
2521	       <data type="boolean"/>
2522	      </element>
2523	     </optional>
2524	     <optional>
2525	      <element name="allowed-users-list">
2526	       <ref name="UserList"/>
2527	      </element>
2528	     </optional>
2529	     <zeroOrMore>
2530	      <element name="user">
2531	       <ref name="user-type"/>
2532	      </element>
2533	     </zeroOrMore>
2534	     <zeroOrMore>
2535	      <ref name="anyElement"/>
2536	     </zeroOrMore>
2537	    </define>
2538	    <!--
2539	           USERS ADMISSION POLICY
2540	       -->
2541	    <define name="user-admission-policy-type">
2542	     <choice>
2543	      <value type="string">closedAuthenticated</value>
2544	      <value type="string">openAuthenticated</value>
2545	      <value type="string">anonymous</value>
2546	     </choice>
2547	    </define>
2548	    <!--
2549	           JOIN HANDLING TYPE
2550	       -->
2551	    <define name="join-handling-type">
2552	     <choice>
2553	      <value type="string">block</value>
2554	      <value type="string">confirm</value>
2555	      <value type="string">allow</value>
2556	      <value type="string">authenticate</value>
2557	      <value type="string">directed-operator</value>
2558	     </choice>
2559	    </define>
2560	    <!--
2561	           USERLIST
2562	       -->
2563	    <define name="UserList">
2564	     <ref name="anyAttribute"/>
2565	     <zeroOrMore>
2566	      <element name="target">
2567	       <ref name="target-type"/>
2568	      </element>
2569	     </zeroOrMore>
2570	     <zeroOrMore>
2571	      <ref name="anyElement"/>
2572	     </zeroOrMore>
2573	    </define>
2574	    <!--
2575	           TARGET TYPE
2576	       -->
2577	    <define name="target-type">
2578	     <attribute name="uri">
2579	      <data type="anyURI"/>
2580	     </attribute>
2581	     <attribute name="method">
2582	      <ref name="method-type"/>
2583	     </attribute>
2584	     <ref name="anyAttribute"/>
2585	    </define>
2586	    <!--
2587	           METHOD TYPE
2588	       -->
2589	    <define name="method-type">
2590	     <choice>
2591	      <value type="string">dial-in</value>
2592	      <value type="string">dial-out</value>
2593	      <value type="string">refer</value>
2594	     </choice>
2595	    </define>
2596	    <!--
2597	           USER TYPE
2598	       -->
2599	    <define name="user-type">
2600	     <attribute name="entity">
2601	      <data type="anyURI"/>
2602	     </attribute>
2603	     <ref name="anyAttribute"/>
2604	     <optional>
2605	      <element name="display-text">
2606	       <text/>
2607	      </element>
2608	     </optional>
2609	     <optional>
2610	      <element name="associated-aors">
2611	       <zeroOrMore>
2612	        <ref name="conference-info-urn"/>
2613	       </zeroOrMore>
2614	      </element>
2615	     </optional>
2616	     <optional>
2617	      <element name="provide-anonymity">
2618	       <data type="boolean"/>
2619	      </element>
2620	     </optional>
2621	     <optional>
2622	      <element name="roles">
2623	       <text/>
2624	      </element>
2625	     </optional>
2626	     <optional>
2627	      <element name="languages">
2628	       <list>
2629	        <data type="language"/>
2630	       </list>
2631	      </element>
2632	     </optional>
2633	     <optional>
2634	      <element name="cascaded-focus">
2635	       <data type="anyURI"/>
2636	      </element>
2637	     </optional>
2638	     <optional>
2639	      <element name="allow-refer-users-dynamically">
2640	       <data type="boolean"/>
2641	      </element>
2642	     </optional>
2643	     <optional>
2644	      <element name="allow-invite-users-dynamically">
2645	       <data type="boolean"/>
2646	      </element>
2647	     </optional>
2648	     <optional>
2649	      <element name="allow-remove-users-dynamically">
2650	       <data type="boolean"/>
2651	      </element>
2652	     </optional>
2653	     <zeroOrMore>
2654	      <element name="endpoint">
2655	       <ref name="endpoint-type"/>
2656	      </element>
2657	     </zeroOrMore>
2658	     <zeroOrMore>
2659	      <ref name="anyElement"/>
2660	     </zeroOrMore>
2661	    </define>
2662	    <!--
2663	           ENDPOINT TYPE
2664	       -->
2665	    <define name="endpoint-type">
2666	     <attribute name="entity">
2667	      <text/>
2668	     </attribute>
2669	     <ref name="anyAttribute"/>
2670	     <optional>
2671	      <element name="display-text">
2672	       <text/>
2673	      </element>
2674	     </optional>
2675	     <optional>
2676	      <element name="referred">
2677	       <zeroOrMore>
2678	        <ref name="conference-info-urn"/>
2679	       </zeroOrMore>
2680	      </element>
2681	     </optional>
2682	     <optional>
2683	      <element name="status">
2684	       <ref name="endpoint-status-type"/>
2685	      </element>
2686	     </optional>
2687	     <optional>
2688	      <element name="joining-method">
2689	       <ref name="joining-type"/>
2690	      </element>
2691	     </optional>
2692	     <optional>
2693	      <element name="joining-info">
2694	       <zeroOrMore>
2695	        <ref name="conference-info-urn"/>
2696	       </zeroOrMore>
2697	      </element>
2698	     </optional>
2699	     <optional>
2700	      <element name="disconnection-method">
2701	       <ref name="disconnection-type"/>
2702	      </element>
2703	     </optional>
2704	     <optional>
2705	      <element name="disconnection-info">
2706	       <zeroOrMore>
2707	        <ref name="conference-info-urn"/>
2708	       </zeroOrMore>
2709	      </element>
2710	     </optional>
2711	     <zeroOrMore>
2712	      <element name="media">
2713	       <ref name="media-type"/>
2714	      </element>
2715	     </zeroOrMore>
2716	     <optional>
2717	      <element name="call-info">
2718	       <zeroOrMore>
2719	        <ref name="conference-info-urn"/>
2720	       </zeroOrMore>
2721	      </element>
2722	     </optional>
2723	     <zeroOrMore>
2724	      <ref name="anyElement"/>
2725	     </zeroOrMore>
2726	    </define>
2727	    <!--
2728	           MEDIA TYPE
2729	       -->
2730	    <define name="media-type">
2731	     <attribute name="id">
2732	      <data type="int"/>
2733	     </attribute>
2734	     <ref name="anyAttribute"/>
2735	     <optional>
2736	      <element name="display-text">
2737	       <text/>
2738	      </element>
2739	     </optional>
2740	     <optional>
2741	      <element name="type">
2742	       <text/>
2743	      </element>
2744	     </optional>
2745	     <optional>
2746	      <element name="label">
2747	       <text/>
2748	      </element>
2749	     </optional>
2750	     <optional>
2751	      <element name="src-id">
2752	       <text/>
2753	      </element>
2754	     </optional>
2755	     <optional>
2756	      <element name="status">
2757	       <ref name="media-status-type"/>
2758	      </element>
2759	     </optional>
2760	     <optional>
2761	      <element name="to-mixer">
2762	       <ref name="mixer-type"/>
2763	      </element>
2764	     </optional>
2765	     <optional>
2766	      <element name="from-mixer">
2767	       <ref name="mixer-type"/>
2768	      </element>
2769	     </optional>
2770	     <zeroOrMore>
2771	      <ref name="anyElement"/>
2772	     </zeroOrMore>
2773	    </define>
2774	    <!--
2775	           MIXER TYPE
2776	       -->
2777	    <define name="mixer-type">
2778	     <ref name="anyAttribute"/>
2779	     <optional>
2780	      <element name="floor">
2781	       <data type="boolean"/>
2782	      </element>
2783	      <element name="controls">
2784	       <ref name="controls-type"/>
2785	      </element>
2786	     </optional>
2787	     <zeroOrMore>
2788	      <ref name="anyElement"/>
2789	     </zeroOrMore>
2790	    </define>
2791	    <!--
2792	           SIDEBARS-BY-REF TYPE
2793	       -->
2794	    <define name="sidebars-by-ref-type">
2795	     <ref name="anyAttribute"/>
2796	     <zeroOrMore>
2797	      <element name="entry">
2798	       <zeroOrMore>
2799	        <ref name="conference-info-urn"/>
2800	       </zeroOrMore>
2801	      </element>
2802	     </zeroOrMore>
2803	     <zeroOrMore>
2804	      <ref name="anyElement"/>
2805	     </zeroOrMore>
2806	    </define>
2807	    <!--
2808	           SIDEBARS-BY-VAL TYPE
2809	       -->
2810	    <define name="sidebars-by-val-type">
2811	     <ref name="anyAttribute"/>
2812	     <zeroOrMore>
2813	      <element name="entry">
2814	       <ref name="conference-type"/>
2815	      </element>
2816	     </zeroOrMore>
2817	     <zeroOrMore>
2818	      <ref name="anyElement"/>
2819	     </zeroOrMore>
2820	    </define>
2821	    <!--
2822	           SINGLE ROLE TYPE
2823	       -->
2824	    <define name="single-role-type">
2825	     <choice>
2826	      <value type="string">administrator</value>
2827	      <value type="string">moderator</value>
2828	      <value type="string">participant</value>
2829	      <value type="string">none</value>
2830	     </choice>
2831	    </define>
2832	    <!--
2833	           *********************************
2834	           EXTENSIBILITY OF THE SCHEMA
2835	           *********************************
2836	       -->
2837	    <!--
2838	           EXTENSIBILITY ELEMENTS
2839	       -->
2840	    <define name="anyElement">
2841	     <element>
2842	      <anyName/>
2843	      <zeroOrMore>
2844	       <choice>
2845	        <attribute>
2846	         <anyName/>
2847	        </attribute>
2848	        <text/>
2849	        <ref name="anyElement"/>
2850	       </choice>
2851	      </zeroOrMore>
2852	     </element>
2853	    </define>
2854	    <!--
2855	           EXTENSIBILITY ATTRIBUTES
2856	       -->
2857	    <define name="anyAttribute">
2858	     <zeroOrMore>
2859	      <attribute>
2860	       <anyName>
2861	        <except>
2862	         <name ns="">entity</name>
2863	         <name ns="">lang</name>
2864	         <name ns="">required-participant</name>
2865	         <name ns="">label</name>
2866	         <name ns="">decision</name>
2867	         <name ns="">name</name>
2868	         <name ns="">policy</name>
2869	         <name ns="">uri</name>
2870	         <name ns="">method</name>
2871	         <name ns="">id</name>
2872	         <nsName ns=""/>
2873	         <nsName ns="urn:ietf:params:xml:ns:xcon-conference-info"/>
2874	        </except>

2876	       </anyName>
2877	       <text/>
2878	      </attribute>
2879	     </zeroOrMore>
2880	    </define>
2881	    <!--
2882	           *************************************************************
2883	           TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
2884	           -  RFC4575 -
2885	           *************************************************************
2886	       -->
2887	    <!--
2888	           WILDCARD FOR EVENT-PACKAGE NAMESPACE
2889	       -->
2890	    <define name="conference-info-urn">
2891	     <element>
2892	      <anyName>
2893	       <except>
2894	      <nsName ns="urn:ietf:params:xml:ns:conference-info"/>
2895	        <nsName ns=""/>
2896	       </except>
2897	      </anyName>
2898	      <mixed>
2899	      <zeroOrMore>
2900	        <choice>
2901	         <attribute>
2902	          <anyName/>
2903	         </attribute>
2904	         <ref name="conference-info-urn"/>
2905	        </choice>
2906	       </zeroOrMore>
2907	      </mixed>
2908	     </element>
2909	    </define>

2911	    <!--
2912	           DEFINITION OF ENDPOINT STATUS TYPE
2913	       -->
2914	    <define name="media-status-type">
2915	     <choice>
2916	      <value>recvonly</value>
2917	      <value>sendonly</value>
2918	      <value>sendrecv</value>
2919	      <value>inactive</value>
2920	     </choice>
2921	    </define>
2922	    <!--
2923	           ENDPOINT STATUS TYPE

2925	       -->
2926	    <define name="endpoint-status-type">
2927	     <choice>
2928	      <value>pending</value>
2929	      <value>dialing-out</value>
2930	      <value>dialing-in</value>
2931	      <value>alerting</value>
2932	      <value>on-hold</value>
2933	      <value>connected</value>
2934	      <value>muted-via-focus</value>
2935	      <value>disconnecting</value>
2936	      <value>disconnected</value>
2937	     </choice>
2938	    </define>
2939	    <!--
2940	           JOINING TYPE
2941	       -->
2942	    <define name="joining-type">
2943	     <choice>
2944	      <value>dialed-in</value>
2945	      <value>dialed-out</value>
2946	      <value>focus-owner</value>
2947	     </choice>
2948	    </define>
2949	    <!--
2950	           DISCONNECTION TYPE
2951	       -->
2952	    <define name="disconnection-type">
2953	     <choice>
2954	      <value>departed</value>
2955	      <value>booted</value>
2956	      <value>failed</value>
2957	      <value>busy</value>
2958	     </choice>
2959	    </define>

2961	   </grammar>

2963	Authors' Addresses

2965	   Oscar Novo
2966	   Ericsson
2967	   Hirsalantie 11
2968	   Jorvas  02420
2969	   Finland

2971	   Email: Oscar.Novo@ericsson.com

2973	   Gonzalo Camarillo
2974	   Ericsson
2975	   Hirsalantie 11
2976	   Jorvas  02420
2977	   Finland

2979	   Email: Gonzalo.Camarillo@ericsson.com

2981	   David P. Morgan
2982	   Fidelity Investments
2983	   82 Devonshire St, MZ V3C
2984	   Boston, MA  02109-3614
2985	   USA

2987	   Email: Dave.Morgan@fmr.com

2989	   Roni Even
2990	   Polycom
2991	   94 Derech Em Hamoshavot
2992	   Petach Tikva  49130
2993	   Israel

2995	   Email: roni.even@polycom.co.il

2997	Full Copyright Statement

2999	   Copyright (C) The IETF Trust (2007).

3001	   This document is subject to the rights, licenses and restrictions
3002	   contained in BCP 78, and except as set forth therein, the authors
3003	   retain all their rights.

3005	   This document and the information contained herein are provided on an
3006	   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
3007	   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
3008	   THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
3009	   OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
3010	   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
3011	   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

3013	Intellectual Property

3015	   The IETF takes no position regarding the validity or scope of any
3016	   Intellectual Property Rights or other rights that might be claimed to
3017	   pertain to the implementation or use of the technology described in
3018	   this document or the extent to which any license under such rights
3019	   might or might not be available; nor does it represent that it has
3020	   made any independent effort to identify any such rights.  Information
3021	   on the procedures with respect to rights in RFC documents can be
3022	   found in BCP 78 and BCP 79.

3024	   Copies of IPR disclosures made to the IETF Secretariat and any
3025	   assurances of licenses to be made available, or the result of an
3026	   attempt made to obtain a general license or permission for the use of
3027	   such proprietary rights by implementers or users of this
3028	   specification can be obtained from the IETF on-line IPR repository at
3029	   http://www.ietf.org/ipr.

3031	   The IETF invites any interested party to bring to its attention any
3032	   copyrights, patents or patent applications, or other proprietary
3033	   rights that may cover technology that may be required to implement
3034	   this standard.  Please address the information to the IETF at
3035	   ietf-ipr@ietf.org.

3037	Acknowledgment

3039	   Funding for the RFC Editor function is provided by the IETF
3040	   Administrative Support Activity (IASA).