idnits 2.17.1 

draft-ietf-xcon-common-data-model-08.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 3315.

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

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

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


  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 (December 16, 2007) is 5974 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 (Obsoleted by RFC 5545)

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

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

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

  -- Obsolete informational reference (is this intentional?): RFC 4583
     (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: June 18, 2008                                         D. Morgan
6	                                                    Fidelity Investments
7	                                                                 R. Even
8	                                                                 Polycom
9	                                                       December 16, 2007

11	 Conference Information Data Model for Centralized Conferencing (XCON)
12	                draft-ietf-xcon-common-data-model-08.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 June 18, 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.3.1.  Conference URI Definition  . . . . . . . . . . . . . .  9
62	     3.4.  Data Model Structure . . . . . . . . . . . . . . . . . . .  9
63	   4.  Data Model Definition  . . . . . . . . . . . . . . . . . . . . 10
64	     4.1.  <conference-info>  . . . . . . . . . . . . . . . . . . . . 13
65	     4.2.  <conference-description> . . . . . . . . . . . . . . . . . 14
66	       4.2.1.  <language> . . . . . . . . . . . . . . . . . . . . . . 14
67	       4.2.2.  <display-text> . . . . . . . . . . . . . . . . . . . . 14
68	       4.2.3.  <subject>  . . . . . . . . . . . . . . . . . . . . . . 14
69	       4.2.4.  <free-text>  . . . . . . . . . . . . . . . . . . . . . 14
70	       4.2.5.  <keywords> . . . . . . . . . . . . . . . . . . . . . . 14
71	       4.2.6.  <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15
72	       4.2.7.  <conference-time>  . . . . . . . . . . . . . . . . . . 15
73	       4.2.8.  <conf-uris>  . . . . . . . . . . . . . . . . . . . . . 16
74	       4.2.9.  <service-uris> . . . . . . . . . . . . . . . . . . . . 16
75	       4.2.10. <maximum-user-count> . . . . . . . . . . . . . . . . . 17
76	       4.2.11. <available-media>  . . . . . . . . . . . . . . . . . . 17
77	     4.3.  <host-info>  . . . . . . . . . . . . . . . . . . . . . . . 19
78	     4.4.  <conference-state> . . . . . . . . . . . . . . . . . . . . 19
79	       4.4.1.  <allow-conference-event-subscription>  . . . . . . . . 19
80	       4.4.2.  <user-count> . . . . . . . . . . . . . . . . . . . . . 19
81	       4.4.3.  <active> . . . . . . . . . . . . . . . . . . . . . . . 20
82	       4.4.4.  <locked> . . . . . . . . . . . . . . . . . . . . . . . 20
83	     4.5.  <floor-information>  . . . . . . . . . . . . . . . . . . . 20
84	       4.5.1.  <conference-ID>  . . . . . . . . . . . . . . . . . . . 20
85	       4.5.2.  <allow-floor-events> . . . . . . . . . . . . . . . . . 20
86	       4.5.3.  <floor-request-handling> . . . . . . . . . . . . . . . 20
87	       4.5.4.  <conference-floor-policy>  . . . . . . . . . . . . . . 21
88	     4.6.  <users>  . . . . . . . . . . . . . . . . . . . . . . . . . 22
89	       4.6.1.  <join-handling>  . . . . . . . . . . . . . . . . . . . 22
90	       4.6.2.  <user-admission-policy>  . . . . . . . . . . . . . . . 22
91	       4.6.3.  <allowed-users-list> . . . . . . . . . . . . . . . . . 23
92	       4.6.4.  <deny-users-list>  . . . . . . . . . . . . . . . . . . 24
93	       4.6.5.  <user> and Its <user> Sub-elements . . . . . . . . . . 24
94	         4.6.5.1.  <display-text> . . . . . . . . . . . . . . . . . . 25
95	         4.6.5.2.  <associated-aors>  . . . . . . . . . . . . . . . . 25
96	         4.6.5.3.  <provide-anonymity>  . . . . . . . . . . . . . . . 25
97	         4.6.5.4.  <roles>  . . . . . . . . . . . . . . . . . . . . . 26
98	         4.6.5.5.  <languages>  . . . . . . . . . . . . . . . . . . . 26
99	         4.6.5.6.  <cascaded-focus> . . . . . . . . . . . . . . . . . 26
100	         4.6.5.7.  <allow-refer-users-dynamically>  . . . . . . . . . 26
101	         4.6.5.8.  <allow-invite-users-dynamically> . . . . . . . . . 26
102	         4.6.5.9.  <allow-remove-users-dynamically> . . . . . . . . . 27
103	         4.6.5.10. <endpoint> . . . . . . . . . . . . . . . . . . . . 27
104	     4.7.  <sidebars-by-ref>  . . . . . . . . . . . . . . . . . . . . 28
105	     4.8.  <sidebars-by-val>  . . . . . . . . . . . . . . . . . . . . 28
106	   5.  RELAX NG Schema  . . . . . . . . . . . . . . . . . . . . . . . 28
107	   6.  XML Schema Extensibility . . . . . . . . . . . . . . . . . . . 36
108	   7.  XML Example  . . . . . . . . . . . . . . . . . . . . . . . . . 36
109	   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 45
110	     8.1.  Authentication . . . . . . . . . . . . . . . . . . . . . . 45
111	     8.2.  Confidentiality  . . . . . . . . . . . . . . . . . . . . . 46
112	     8.3.  Integrity  . . . . . . . . . . . . . . . . . . . . . . . . 46
113	   9.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 46
114	     9.1.  Relax NG Schema Registration . . . . . . . . . . . . . . . 46
115	     9.2.  XML Namespace Registration . . . . . . . . . . . . . . . . 47
116	     9.3.  Conference Object Identifier Registration  . . . . . . . . 47
117	     9.4.  Conference User Identifier Registration  . . . . . . . . . 48
118	   10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
119	   11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
120	     11.1. Normative References . . . . . . . . . . . . . . . . . . . 48
121	     11.2. Informative References . . . . . . . . . . . . . . . . . . 49
122	   Appendix A.  Appendix A.  Non-Normative RELAX NG Schema in XML
123	                Syntax  . . . . . . . . . . . . . . . . . . . . . . . 50
124	   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 70
125	   Intellectual Property and Copyright Statements . . . . . . . . . . 72

127	1.  Introduction

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

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

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

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

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

215	                 Figure 1: Conference Server Architecture

217	   The Session Initiation Protocol (SIP) Event Package for Conference
218	   State, specified in [RFC4575], already defines a data format for
219	   conferences.  However, that model is SIP specific and lacks elements
220	   related to some of the functionality defined by the Centralized
221	   Conferencing Framework [I-D.ietf-xcon-framework] (e.g., floor
222	   control).  The data model defined in this document constitutes a
223	   superset of the data format defined in [RFC4575].  The result is a
224	   data format that supports more call signaling protocols besides SIP
225	   and that covers all the functionality defined in the Centralized
226	   Conferencing Framework [I-D.ietf-xcon-framework].

228	2.  Terminology

230	   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
231	   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
232	   document are to be interpreted as described in RFC 2119 [RFC2119].

234	   This document uses the terminology defined in the Centralized
235	   Conferencing Framework [I-D.ietf-xcon-framework], the SIPPING
236	   conferencing framework [RFC4353] and the BFCP (Binary Floor Control
237	   Protocol) specification [RFC4582].  Readers of this document should
238	   be familiar with the terminology used in those documents.

240	3.  Overview

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

252	3.1.  Data Model Format

254	   A conference object document is an XML [W3C.REC-xml-20001006]
255	   document that MUST be well formed and SHOULD be valid.  Conference
256	   object documents MUST be based on XML 1.0 and SHOULD be encoded using
257	   UTF-8.

259	3.2.  Data Model Namespace

261	   This specification defines a new namespace specification for
262	   identifying the elements defined in the data model.  This namespace
263	   is as follows:

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

267	3.3.  The Conference Object Identifier

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

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

288	                            +--------------------------+
289	                            |       Conference         |
290	                            |         Object           |
291	                            |       Identifier         |
292	                            +--------------------------+
293	                            |  xcon:Ji092i@example.com |
294	                            +------+-------------------+
295	                                        |
296	                                        |
297	                                        |
298	                      +-----------------+---------------+
299	                      |                                 |
300	          +-----------+-----------+          +----------+---------+
301	          |   CSP Conference IDs  |          |BFCP 'Conference ID'|
302	          +-----------------------+          +--------------------+
303	          | h323:i092@example.com |          |        i092        |
304	          | tel:+44(0)2920930033  |          +----------+---------+
305	          | sip:i092@example.com  |                     |
306	          +-----------------------+             +-------+--------+
307	                                                | BFCP 'Floor ID'|
308	                                                +----------------+
309	                                                |      543       |
310	                                                |      236       |
311	                                                +----------------+

313	                    Figure 2: Conference Object Mapping

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

335	   Further elements can be added to the tree representation in Figure 2
336	   to enable a complete representation of a conference instance within a
337	   conferencing system.

339	3.3.1.  Conference URI Definition

341	   XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ]

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

345	   host, port, and unreserved are defined in RFC3986[RFC3986]

347	3.4.  Data Model Structure

349	   The information in this data model is structured in the following
350	   manner.  All the information related to a conference is contained in
351	   a <conference-info> element.  The <conference-info> element contains
352	   the following child elements:

354	   o  The <conference-description> element describes the conference as a
355	      whole.  It has, for instance, information about the URI of the
356	      conference, maximum users allowed in the conference, media
357	      available in the conference, or the time the conference will
358	      start.
359	   o  The <host-info> element contains information about the entity
360	      hosting the conference (e.g., its URI).
361	   o  The <conference-state> element informs the subscribers about the
362	      changes in the overall conference information.
363	   o  The <floor-information> element contains information about the
364	      status of the different floors in the conference.
365	   o  The <users> element describes the membership information as a
366	      whole.  The <users> element contains a set of <user> child
367	      elements, each describing a single participant in the conference.
368	   o  If a participant in the main conference joins a sidebar, a new
369	      element is created in the conference referenced from the
370	      <sidebars-by-ref> element or under one of the <sidebars-by-val>
371	      elements.

373	   Note that some of the elements described above such <conference-
374	   info>, <conference-description>, <sidebars-by-ref>, or <sidebars-by-
375	   val> are not defined in the data model but are defined in the data
376	   format of [RFC4575].  We describe them here because they are part of
377	   the basic structure of the data model.

379	4.  Data Model Definition

381	   The following non-normative diagram shows the structure of conference
382	   object documents.  The operator "!" preceding an element indicates
383	   that the element is mandatory in the data model.  The operator "*"
384	   following an element indicates that the element is introduced and
385	   defined in this document.  That is, elements without a "*" have
386	   already been defined in [RFC4575].

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

524	        |     |    |      |    |--<from-mixer>*
525	        |     |    |      |    |      |--<floor>*
526	        |     |    |      |    |      |--<controls>*
527	        |     |    |      |    |      |      |--<pause-video>*
528	        |     |    |      |    |      |     ...
529	        |     |    |      |   ...
530	        |     |    |      |--<call-info>
531	        |     |    |      |    |--<sip>
532	        |     |    |      |    |   |--<display-text>
533	        |     |    |      |    |   |--<call-id>
534	        |     |    |      |    |   |--<from-tag>
535	        |     |    |      |    |   |--<to-tag>
536	        |          ...    ...
537	        |--<sidebars-by-ref>
538	        |     |--<entry>
539	        |     |     |-- <user>
540	        |     |     |-- <display-text>
541	        |     |--<entry>
542	        |     |     |-- <user>
543	        |     |     |-- <display-text>
544	        |     ...
545	        |--<sidebars-by-val>
546	        |     |--<entry>
547	        |     |     |
548	        |     |    ...
549	        |     |--<entry>
550	        |     |     |
551	        |     ...   ...

553	                      Figure 4: Non-normative diagram

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

558	4.1.  <conference-info>

560	   A conference object document begins with the root element tag
561	   <conference-info>, which is defined in [RFC4575].  The <conference-
562	   info> attributes are described in [RFC4575].  Note that the
563	   <conference-info> element does not have the attributes 'state' and
564	   'version' defined in [RFC4575] for this element because this
565	   attribute only applies to notifications mechanism.

567	   In addition, [RFC4575] defines an 'entity' attribute that contains
568	   the conference object identifier (XCON-URI) that identifies the
569	   conference being described in the document.

571	   The <conference-info> element contains the <conference-description>,
572	   <host-info>, <conference-state>, <floor-information>, <users>,
573	   <sidebars-by-ref>, and <sidebars-by-val> child elements.  All these
574	   elements, except <floor-information>, are defined in [RFC4575].  A
575	   conference document MUST at least include the <conference-
576	   description> and <users> child elements.

578	4.2.  <conference-description>

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

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

591	4.2.1.  <language>

593	   The <language> element indicates the predominant language that is
594	   expected to be employed within a conference.  This element is not
595	   enforcing the language of the conference, only informs to the
596	   participants about the desirable language that they should used in
597	   the conference.  Participants are free to switch to other languages
598	   if they like.

600	4.2.2.  <display-text>

602	   The <display-text> element is described in section 5.3 of [RFC4575].

604	4.2.3.  <subject>

606	   The <subject> element is described in section 5.3 of [RFC4575].

608	4.2.4.  <free-text>

610	   The <free-text> element is described in section 5.3 of [RFC4575].

612	4.2.5.  <keywords>

614	   The <keywords> element is described in section 5.3 of [RFC4575].

616	4.2.6.  <allow-sidebars>

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

621	4.2.7.  <conference-time>

623	   The <conference-time> element contains the information related to
624	   conference time and duration of a conference.  The <conference-time>
625	   element contains one or more <entry> elements each defining the time
626	   information specifying a single conference occurrence.

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

630	   o  <base>: The <base> child element specifies the iCalendar object of
631	      the conference.  The iCalendar object components are defined in
632	      [RFC2445].
633	   o  <mixing-start-offset>: The <mixing-start-offset> child element
634	      specifies when the conference media mixing starts before the
635	      conference starts.  The <mixing-start-offset> child element
636	      expresses the offset as signed integers representing seconds
637	      before/after the iCalendar DTSTART field [RFC2445].  If the
638	      <mixing-start-offset> element is not present, it indicates that
639	      the conference media mixing starts immediately.  The <mixing-
640	      start-offset> has the mandatory 'required-participant' attribute.
641	      This attribute contains one of the following values: "none",
642	      "administrator", "moderator", "user", "observer", and
643	      "participant".  More values can be specified in the future.  The
644	      'required-participant' attribute allows a privileged user to
645	      define when media mixing starts based on the latter of the mixing
646	      start time, and the time the first participant arrives.  If the
647	      value is set to "none'", mixing starts according to the mixing
648	      start time.
649	   o  <mixing-end-offset>: The <mixing-end-offset> child element that
650	      specifies the time a conference media mixing stops after the
651	      conference stops.  The <mixing-end-offset> child element expresses
652	      the offset as signed integers representing seconds before/after
653	      the iCalendar DTEND field [RFC2445].  If the <mixing-end-offset>
654	      element is not present, it indicates that the conference
655	      occurrence is not bounded.  The <mixing-end-offset> elements both
656	      have the mandatory 'required-participant' attribute.  This
657	      attribute contains one of the following values: "none",
658	      "administrator", "moderator", "observer", "user", and
659	      "participant".  More values can be specified in the future.  The
660	      'required-participant' attribute allows a privileged user to
661	      define when media mixing ends based on the earlier of the <mixing-
662	      end-offset>, and the time the last participant leaves.  If the
663	      value is set to "none", mixing stops according to the <mixing-end-
664	      offset>.  If the conference policy was modified so that last
665	      privileged user is now a normal conference participant, and the
666	      conference requires a privileged user to continue; that conference
667	      MUST terminate.
668	   o  <can-join-after-offset>: An administrator can indicate the time
669	      when users can join a conference by populating the <can-join-
670	      after-offset> element.
671	   o  <must-join-before-offset>: An administrator can define the time
672	      after which new users are not allowed to join the conference
673	      anymore.  This is done by populating the <must-join-before-offset>
674	      element expressing the offset as signed integers representing
675	      seconds before/after DTSTART field.
676	   o  <request-user>: It is possible to define the time when users or
677	      resources on the <allowed-users-list> are requested to join the
678	      conference by using the <request-users> element.  This element
679	      expresses the offset as signed integers representing seconds
680	      before/after DTSTART field.
681	   o  <notify-end-of-conference>: The <notify-end-of-conference> element
682	      defines in seconds when the system has to send a notification when
683	      the end of the conference is approaching.  If the <notify-end-of-
684	      conference> element is not present, it indicates that the system
685	      does not notify the users when the end of the conference is
686	      approaching.  The <notify-end-of-conference> child element
687	      expresses the offset as signed integers representing seconds after
688	      DTSTART field.
689	   o  <allowed-extend-mixing-end-offset>: The <allowed-extend-mixing-
690	      end-offset> refers to the possibility to extend the conference.
691	      It has a boolean value.

693	4.2.8.  <conf-uris>

695	   The <conf-uris> contains the identifiers to be used in order to
696	   access the conference by different signaling means.  This document
697	   describes a new element, <conference-password>.  This element
698	   contains the password of the conference, for instance, PSTN
699	   conference will store the 'PIN code' in this element.  All the other
700	   <conf-uris> child element are described in section 5.3.1 of
701	   [RFC4575].  Future extensions to this schema may define new values
702	   and register them with IANA.

704	4.2.9.  <service-uris>

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

711	4.2.10.  <maximum-user-count>

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

718	4.2.11.  <available-media>

720	   The <available-media> has the 'label' attribute that is the media
721	   stream identifier assigned by the conferencing server.  The attribute
722	   'label' is described in [RFC4575], section 5.3.4.  The <available-
723	   media> element contains a sequence of <entry> child elements.  Each
724	   <entry> element contains the following child elements:

726	   o  The <type> element is described in section 5.3.4 of [RFC4575].
727	   o  The <display-text> element is described in section 5.3.4 of
728	      [RFC4575].
729	   o  The <status> element is described in section 5.3.4 of [RFC4575].
730	   o  The child element <mixing-mode> describes a default policy by
731	      which the mixer will build the outgoing stream from the incoming
732	      streams.  Note that this policy is different than the policy
733	      describing the floors for each media.  The <mixing-mode> child
734	      element MUST contain one and only one of the "Moderator-
735	      controlled", "FCFS", and "Automatic" values indicating the default
736	      algorithm to use with every media stream.  The "Moderator-
737	      controlled" value indicates that the moderator of the conference,
738	      controls the media stream policy.  The "FCFS" value indicates a
739	      'first-come-first-served' policy.
740	   o  The <codecs> element specifies the allowed codecs in the
741	      conference.  It has an attribute 'decision' that specifies if the
742	      focus decides the common codec automatically or needs the approval
743	      of the moderator of the conference ("automatic", "moderator-
744	      controlled").  The <codecs> element contains <codec> elements.  A
745	      <codec> element can have the attribute 'name' and 'policy'.  The
746	      'name' attribute identifies a codec.  The list of possible codecs
747	      accepted as a 'name' attribute is defined by the IANA registry for
748	      RTP Payload Types.  The possible values of the attribute 'name'
749	      are the values of the 'subtype' column of the RTP Payload Format
750	      media types per [RFC4855] defined in IANA [IANA].  The 'policy'
751	      attribute contains the policy for that codec (allowed, or
752	      disallowed).
753	   o  The <controls> element contains the basic audio and video global
754	      control elements for a conference.  It is expected that for the
755	      majority of the basic conferences, these controls are sufficient.
756	      If the conference server wants to support more advanced controls,
757	      then it is recommended that an extension to the data model be
758	      used.  In the <controls> element the schema is extensible, hence
759	      new control types can be added in the future.  So moderator
760	      controls that affect all media output would go under the
761	      <available-media> element.  The following controls elements are
762	      defined for <controls>:
763	      *  The <mute> element is used in conjunction with an audio stream
764	         to cease transmission of associated media.  That means that for
765	         the entire duration where mute is applicable, all current and
766	         future participants of the conference are muted and will not
767	         receive any audio.  It has a "boolean" value.  If this control
768	         is not specified, access to the control is not available to the
769	         client.
770	      *  The <pause-video> element is used in conjunction with a video
771	         stream to cease transmission of associated media.  It has a
772	         "boolean" value.  If this control is not specified, the access
773	         to the control is not available to the client.
774	      *  The <gain> element is used in conjunction with a media output
775	         stream to indicate the amount of amplification of an audio
776	         stream.  The value is an integer number that ranges from -127
777	         to 127.  If this control is not specified, access to the
778	         control is not available to the client.
779	      *  The <video-layout> element is used in conjunction with a video
780	         stream to specify how the video streams (of participants) are
781	         viewed by each participant.  Only one layout type can be
782	         specified for each output stream.  If there are fewer
783	         participants than panels in the specified layout, then blanking
784	         (black screen) MAY be mixed into the stream on the behalf of
785	         the missing input streams.  If unspecified, the <video-layout>
786	         default type SHOULD be "single-view".  The <video-layout> types
787	         are as follows, although any number of custom layouts may be
788	         specified in future extensions:
789	         +  single-view: Only one stream is presented by the focus to
790	            all participants in one panel.
791	         +  dual-view: This dual view option will present the video
792	            side-by-side in 2 panels and not alter the aspect ratio of
793	            the streams.  This will require the focus to introduce
794	            blanking on parts of the overall image as viewed by the
795	            participants.
796	         +  dual-view-crop: This side-by-side layout option instructs
797	            the focus to alter the aspect ratio of the streams (alter-
798	            aspect-ratio=TRUE) so that blanking is not necessary.  The
799	            focus handles the cropping of the streams.
800	         +  dual-view-2x1: This layout option instructs the focus to
801	            place one stream above the other, in essence with two rows
802	            and one column.  In this option the aspect ratio is not
803	            altered and blanking is introduced.
804	         +  dual-view-2x1-crop: This layout option also instructs the
805	            focus to place one stream above the other, in essence with
806	            two rows and one column.  In this option the aspect ratio is
807	            altered and the video streams are cropped.
808	         +  quad-view: Four equal-sized panels in a 2x2 layout is
809	            presented by the focus to all participants.  Typically the
810	            aspect ratio of the streams are maintained (alter-aspect-
811	            ratio= FALSE).
812	         +  multiple-3x3: Nine equal-sized panels in a 3x3 layout is
813	            presented by the focus to all participants.  Typically the
814	            aspect ratio of the streams are preserved.
815	         +  multiple-4x4: Sixteen equal-sized panels in a 4x4 layout is
816	            presented by the focus to all participants.  Typically the
817	            aspect ratio of the streams are preserved.
818	         +  multiple-5x1: This option refers to a 5x1 layout where one
819	            panel will occupy 4/9 of the mixed video stream while the
820	            others will each occupy 1/9 of the stream.  Typically the
821	            aspect ratio of the streams is preserved.
822	         +  automatic: This option allows the focus to add panels as
823	            streams are added.

825	4.3.  <host-info>

827	   The <host-info> element contains information about the entity hosting
828	   the conference.  This information is set before conference
829	   activation, and is rarely changed during the conference lifetime.
830	   The <host-info> element and its child elements are described in
831	   [RFC4575], section 5.4.  Future extensions to the <host-info> element
832	   may define new values.

834	4.4.  <conference-state>

836	   The <conference-state> is introduced in RFC4575 [RFC4575].  The
837	   <conference-state> element contains the <allow-conference-event-
838	   subscription>, <user-count>, <active>, and <locked> child elements.

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

842	   The <allow-conference-event-subscription> element represents a
843	   boolean action.  If set to TRUE, the focus is instructed to allow the
844	   subscription to conference state events, such as RFC4575 'SIP Event
845	   Package for Conference State' [RFC4575].  If set to FALSE, the
846	   subscription to conference state events would be rejected.  If this
847	   element is undefined it has a default value of TRUE, causing the
848	   subscription to conference state events to be accepted.

850	4.4.2.  <user-count>

852	   The <user-count> child element is explained in [RFC4575], section
853	   5.5.1.

855	4.4.3.  <active>

857	   The <active> child element is explained in [RFC4575], section 5.5.2.

859	4.4.4.  <locked>

861	   The <locked> child element is explained in [RFC4575], section 5.5.3.

863	4.5.  <floor-information>

865	   The <floor-information> element contains the <conference-ID>, <allow-
866	   floor-events>, <floor-request-handling>, and <conference-floor-
867	   policy> child elements.  Other elements from different namespaces MAY
868	   be present for the purposes of extensibility.  The absence of this
869	   element from an XML document indicates that the conference does not
870	   have a floor.

872	4.5.1.  <conference-ID>

874	   The <conference-ID> is a 32-bit BFCP conference identifier defined in
875	   [RFC4582] section 5.1. that identifies the BFCP conference the
876	   message belongs to.  This identifier represents a conference instance
877	   within floor control.  When created within the conferencing system,
878	   the 'conference-ID' has a 1:1 mapping to the unique conference object
879	   Identifier (XCON-URI).

881	4.5.2.  <allow-floor-events>

883	   The <allow-floor-events> element represents a boolean action.  If set
884	   to TRUE, the focus is instructed to accept the subscription to floor
885	   control events.  If set to FALSE, the focus is instructed to reject
886	   the subscription.  If this element is undefined, it has a default
887	   value of FALSE, causing the subscription to floor control events to
888	   be rejected.

890	   There are two methods which a conference participant subscribes
891	   himself to a floor control event.  One method is using an offer/
892	   answer exchange mechanism ([RFC3264]) using SIP INVITE and BFCP
893	   parameters in the SDP ([RFC4583]).  The other method is a general
894	   authorization mechanism described in section 9 of [RFC4582] and in
895	   [RFC5018].  Future documentation may define additional connection
896	   mechanisms.

898	4.5.3.  <floor-request-handling>

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

905	   o  "block": This action instructs the focus to deny the floor
906	      request.  This action is the default action taken in the absence
907	      of any other actions.
908	   o  "confirm": This action instructs the focus to allow the request.
909	      The focus then uses the defined floor algorithm to further allow
910	      or deny the floor.  The algorithms used are outside the scope of
911	      this document.

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

918	4.5.4.  <conference-floor-policy>

920	   The <conference-floor-policy> element has one or more <floor> child
921	   elements.  Every <floor> child elements has an attribute 'id' which
922	   uniquely identifies a floor or floors within a conference.  The 'id'
923	   attribute corresponds to the floor-id identifier defined in [RFC4582]
924	   section 5.2.2.  Each <floor> element has the following child
925	   elements:

927	   o  <media-label>: Every floor is identified for one or more mandatory
928	      <media-label> element.  If the <available-media> information is
929	      included in the conference document, the value of this element
930	      MUST be equal to the 'label' value of the corresponding media
931	      stream <entry> in the <available-media> container.  The number of
932	      those elements indicates how many floors the conference can have.
933	      A floor can be used for one or more media types;
934	   o  <algorithm>: A floor can be controlled using many algorithms; the
935	      mandatory <algorithm> element MUST be set to any of the
936	      "moderator-controlled", "FCFS" or "random" values indicating the
937	      algorithm.  The "Moderator-controlled" value indicates that the
938	      moderator of the conference controls the floor.  The "FCFS" value
939	      states for 'first-come-first-served' floor control.
940	   o  <max-floor-users>: The <max-floor-users> child element in the
941	      <floor> element is optional and, if present, dictates the maximum
942	      number of users who can have the floor at one time.
943	   o  <moderator-id>: The optional <moderator-id> indicates the 'User
944	      ID' of the moderator.  The 'User ID' is a BFCP identifier defined
945	      in [RFC4582] section 5.1.  It MUST be set if the element
946	      <algorithm> is set to "Moderator-controlled" value.  Note that
947	      [RFC4582] refers to the moderator role as a 'floor chair'.

949	4.6.  <users>

951	   The <users> element is described in [RFC4575] and contains the <join-
952	   handling>, <user-admission-policy>, <allowed-users-list> and <deny-
953	   users-list> defined in this document and <user> child elements
954	   defined in [RFC4575].  Note that the <users> element does not have
955	   the attribute 'state' defined in [RFC4575] for this element because
956	   this attribute only applies to notifications mechanism.  The
957	   following sections describe these elements in more detail.  Other
958	   child elements and attributes can be used to extend <users> in the
959	   future.

961	4.6.1.  <join-handling>

963	   The <join-handling> element defines the actions used by the
964	   conference focus to control conference participation.  This element
965	   defines the action that the focus is to take when processing a
966	   particular request to join a conference.  This element defines values
967	   of:
968	   o  "block": This action instructs the focus to deny access to the
969	      conference.  This action is the default action taken in the
970	      absence of any other actions.
971	   o  "confirm": This action instructs the focus to place the
972	      participant on a pending list (e.g., by parking the call on a
973	      music-on-hold server), awaiting moderator input for further
974	      actions.
975	   o  "allow": This action instructs the focus to accept the conference
976	      join request and grant access to the conference within the
977	      instructions specified in the transformations of this rule.
978	   o  "authenticate": This action instructs the focus that the user has
979	      to provide a combination of username/password.
980	   o  "directed-operator": This action instructs the focus to direct the
981	      user to an operator.

983	4.6.2.  <user-admission-policy>

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

990	   o  "closedAuthenticated": A 'closedAuthenticated' policy requires
991	      each conference participant to be in the allowed users list
992	      (listed under the <allowed-users-list> XML element) with each
993	      participant being sufficiently (up to local policy) authenticated.
994	      Conference join requests for users not in the allowed users list
995	      or participants not authenticated should be rejected unless a
996	      <join-handling> action of 'confirm' is selected in which case the
997	      user is placed on a pending list as indicated earlier.
998	   o  "openAuthenticated": An 'openAuthenticated' policy requires each
999	      conferencing participant to be sufficiently authenticated (as
1000	      before) but does not restrict which participants can join the
1001	      conference.  Typically this implies that anyone capable of
1002	      authenticating with the conferencing system may join the
1003	      conference.
1004	   o  "anonymous": An 'anonymous' policy allows any join requests in and
1005	      is the least restrictive policy.

1007	4.6.3.  <allowed-users-list>

1009	   The <allowed-users-list> child element contains a list of user URIs,
1010	   roles, or domains (*@example.com) that the focus uses to determine
1011	   who can join the conference, who can be invited to join a conference,
1012	   or who the focus needs to "refer to" the conference.  The <allowed-
1013	   users-list> element includes zero or more <target> child elements.
1014	   This child element includes the mandatory 'uri' attribute and the
1015	   mandatory 'method' attribute.  The same 'uri' attribute with
1016	   different method values can appear in the list more than once.

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

1020	   o  "dial-in": The value "dial-in" is used by the focus to determine
1021	      who can join the conference.
1022	   o  "dial-out": The value "dial-out" contains a list of resources that
1023	      the focus will initiate a session with.
1024	   o  "refer": The value "refer" is used by the focus to determine the
1025	      resources that the focus needs to "refer to" the conference.  In
1026	      SIP, this is achieved by the focus sending a REFER request to
1027	      those potential participants.  In a different paradigm, this could
1028	      also mean that the focus sends an SMS or an email to the referred
1029	      user.  This list can be updated during the conference lifetime so
1030	      it can be used for mid-conference refers as well.

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

1038	   The <allowed-users-list> element has a <persistent-list> child
1039	   element as well.  Some chatroom systems allow -- and some require --
1040	   registration of detailed information about a user before they are
1041	   allowed to join a chatroom.  The <persistent-list> child element
1042	   stores persistent information about users who are not actively part
1043	   of an ongoing chatroom session.  The <persistent-list> element stores
1044	   the following information:

1046	   o  user: The <user> element stores the name, nickname, the conference
1047	      user identifier (XCON_USERID) and email address of a user.  It has
1048	      three attributes: 'name', 'nickname' and 'id' and an <email>
1049	      element.  Future extensions to this schema may define new elements
1050	      for the <user> element.

1052	   Future extensions to this schema may define new elements for the
1053	   <target> element.

1055	4.6.4.  <deny-users-list>

1057	   The <deny-users-list> child element contains a list of user URIs,
1058	   roles, or domains (*@example.com) that the focus uses to determine
1059	   who has been 'banned' from the conference.  Such banned users are
1060	   prevented from re-joining the chatroom until they have been un-
1061	   banned.

1063	4.6.5.  <user> and Its <user> Sub-elements

1065	   The element <user> is described in RFC4575[RFC4575] and describes a
1066	   single participant in the conference.  The <user> element has an
1067	   attribute 'entity'.  Note that the <user> element does not have the
1068	   attribute 'state' defined in [RFC4575] for this element because this
1069	   attribute only applies to notifications mechanism.

1071	   The attribute 'entity' contains a unique conference user identifier
1072	   (XCON_USERID).  The URI format of this identifier is as follow:

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

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

1078	   [unreserved is defined in RFC3986]

1080	   Other user identifiers can be associated with this conference user
1081	   identifier and enable the conferencing system to correlate and map
1082	   these multiple authenticated user identities to a single global user
1083	   identifier.  Figure 6 illustrates an example using the conference
1084	   user identifier in association with the user identity defined for
1085	   BFCP, SIP, and H323 user identity.  It should be noted that a
1086	   conferencing system is free to structure such relationships as
1087	   required and this information is just included as a guideline that
1088	   can be used.

1090	                          +--------------+
1091	                          |  Conference  |
1092	                          |     User     |
1093	                          |  Identifier  |
1094	                          +--------------+
1095	                          |    John      |
1096	                          +------+-------+
1097	                                 |
1098	                                 |
1099	                                 |
1100	          +----------------------+-------------------------+
1101	          |                      |                         |
1102	  +-------+--------+ +-----------+-----------+ +-----------+-----------+
1103	  |  BFCP User ID  | |      SIP User URI     | |     H323 User URI     |
1104	  +----------------+ +-----------------------+ +-----------------------+
1105	  |      543       | |sip:851221@example.com | |h323:taeduk@example.com|
1106	  +----------------+ +-----------------------+ +-----------------------+

1108	                    Figure 6: Conference Object Mapping

1110	   The element <user> element contains the <display-text>, <associated-
1111	   aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>,
1112	   <allow-refer-users-dynamically>, <allow-invite-users-dynamically>,
1113	   <allow-remove-users-dynamically>, and <endpoint>.  The following
1114	   sections describe these elements in more detail.

1116	4.6.5.1.  <display-text>

1118	   The <display-text> child element is explained in [RFC4575], section
1119	   5.6.1.

1121	4.6.5.2.  <associated-aors>

1123	   The <associated-aors> child element is explained in [RFC4575],
1124	   section 5.6.2.

1126	4.6.5.3.  <provide-anonymity>

1128	   The <provide-anonymity> element provides anonymity to the user.  In
1129	   this case, the focus provides to the rest of the participants an
1130	   anonymous identity for that user, for example anonymousX.  This
1131	   element only affects the way the user information is provided to the
1132	   other participants.  The real information about the user is still
1133	   stored in the data model.  This can be achieved by using the
1134	   <provide-anonymity> element.  This element has two values: 'private'
1135	   and 'semi-private'.  The 'private' value specifies that this user is
1136	   completely anonymous in the conference. 'semi-private' value
1137	   specifies that this user is anonymous to all users with equal or
1138	   lesser permissions in the conference.

1140	4.6.5.4.  <roles>

1142	   A role provides the context for the set of conference operations that
1143	   a participant can perform.  This element can contain one of the
1144	   following values: "administrator", "moderator", "user",
1145	   "participant", "observer", and "none".  The roles semantic definition
1146	   is out of the scope of this document and is subject to future policy
1147	   documents.  This element can be extended with new roles in future
1148	   documents.

1150	4.6.5.5.  <languages>

1152	   The <languages> child element is explained in [RFC4575], section
1153	   5.6.4.

1155	4.6.5.6.  <cascaded-focus>

1157	   The <cascaded-focus> child element is explained in [RFC4575], section
1158	   5.6.5.

1160	4.6.5.7.  <allow-refer-users-dynamically>

1162	   The <allow-refer-users-dynamically> element represents a boolean
1163	   action.  If set to TRUE, a participant is allowed to instruct the
1164	   focus to refer a user to the conference without modifying the
1165	   <allowed-users-list> (in SIP terms, a participant is allowed to send
1166	   a REFER request to the focus which results in the focus sending a
1167	   REFER request to the user the referrer wishes to join the
1168	   conference).  If set to FALSE, the refer request is rejected.  If
1169	   this element is undefined it has a value of FALSE, causing the refer
1170	   to be rejected.

1172	4.6.5.8.  <allow-invite-users-dynamically>

1174	   The <allow-invite-users-dynamically> element represents a boolean
1175	   action.  If set to TRUE, a participant is allowed to instruct the
1176	   focus to invite a user to the conference without modifying the
1177	   <allowed-users-list> list (in SIP terms, a participant is allowed to
1178	   send a REFER request to the focus which results in the focus sending
1179	   an INVITE request to the user the referrer wishes to join the
1180	   conference).  If set to FALSE, the refer request is rejected.  If
1181	   this element is undefined it has a value of FALSE, causing the refer
1182	   to be rejected.

1184	4.6.5.9.  <allow-remove-users-dynamically>

1186	   The <allow-remove-users-dynamically> element represents a boolean
1187	   action.  If set to TRUE, a participant is allowed to instruct the
1188	   focus to remove a user from the conference without modifying the
1189	   ruleset (in SIP terms, a participant is allowed to send a REFER
1190	   request to the focus which results in the focus sending an BYE
1191	   request to the user the referrer wishes to leave the conference).  If
1192	   set to FALSE, the refer request is rejected.  If this element is
1193	   undefined it has a value of FALSE, causing the refer to be rejected.

1195	4.6.5.10.  <endpoint>

1197	   The <endpoint> child element is defined in [RFC4575].  It can provide
1198	   the desired level of detail about the user's devices and their
1199	   signaling sessions taking part in the conference.  The <endpoint>
1200	   element in this document does not defined the 'state' attribute
1201	   defined in [RFC4575] for the same element since the 'state' attribute
1202	   only applies to notification mechanisms.

1204	   The <endpoint> element has the following child elements: <display-
1205	   text>, <referred>, <status>, <joining-method>, <joining-info>,
1206	   <disconnection-method>, <disconnection-info>, <media>, <floor>,and
1207	   <call-info>.  All the <endpoint> child elements are defined in
1208	   [RFC4575] with the exception of the <floor> element.

1210	   The <floor> element describes a floor that joins this participant in
1211	   the conference.  If a participant, for instance, needs to talk in the
1212	   conference, it first needs to get the floor from the chair of the
1213	   conference.  The <floor> element has an attribute 'id' which uniquely
1214	   identifies a floor or floors within a conference.  The 'id' attribute
1215	   corresponds to the floor-id identifier defined in [RFC4582] section
1216	   5.2.2.  The <floor> element has a "Boolean" value.  A value of FALSE
1217	   indicates that this user does not hold the floor in this moment.  If
1218	   this control is not specified, this user SHOULD NOT specify the floor
1219	   option.

1221	   Besides the <floor> element, the <endpoint>/<media> element has two
1222	   other child elements defined in this document, the <to-mixer>, and
1223	   the <from-mixer>:

1225	   o  <from-mixer>, <to-mixer>: These are controls that apply to a
1226	      user's media stream being sent from the mixer to the participants
1227	      endpoint or to the mixer from the participants endpoint.  The <to-
1228	      mixer> element details properties associated with the incoming
1229	      streams to the mixer (streams sent to the mixer from the
1230	      participant).  The <from-mixer> element details properties
1231	      associated with the outgoing streams from the mixer (sent from the
1232	      mixer to the participant).  Both of these elements have the
1233	      attribute 'name'.  The 'name' attribute has the values "VideoIn",
1234	      "VideoOut", "AudioOut", and "AudioIn".  The "VideoOut" and
1235	      "AudioOut" media streams detail properties associated with the
1236	      outgoing video and audio from the mixer.  The "VideoIn" and
1237	      "AudioIn" media stream details properties associated with the
1238	      incoming video and audio to the mixer.  More values can be defined
1239	      in the future.  The <to-mixer> and <from-mixer> elements have the
1240	      <controls> child element:
1241	      *  Controls that apply to a specific user would appear under the
1242	         <controls> element.

1244	4.7.  <sidebars-by-ref>

1246	   The <sidebars-by-ref> element contains a set of <entry> child
1247	   elements.  This element is described in [RFC4575], 5.9.1.  Note that
1248	   the <sidebars-by-ref> element does not have the attribute 'state'
1249	   defined in [RFC4575] for this element because this attribute only
1250	   applies to notifications mechanism.

1252	4.8.  <sidebars-by-val>

1254	   The <sidebars-by-val> element contains a set of <entry> child
1255	   elements each containing information about a single sidebar.  This
1256	   element is described in [RFC4575], 5.9.2.  Note that the <sidebars-
1257	   by-val> element does not have the attribute 'state' defined in
1258	   [RFC4575] for this element because this attribute only applies to
1259	   notifications mechanism.

1261	5.  RELAX NG Schema

1263	   In accordance with the Centralized Conferencing Framework document
1264	   [I-D.ietf-xcon-framework], the Conference Object is a logical
1265	   representation of a conference instance.  The conference information
1266	   schema contains core information that is utilized in any conference.
1267	   It also contains the variable information part of the Conference
1268	   Object.

1270	   This specification defines some document fragments in RELAX NG format
1271	   [RELAX].

1273	   namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
1274	   namespace local = ""
1275	   default namespace ns1 ="urn:ietf:params:xml:ns:xcon-conference-info"
1276	   namespace ns2 = "urn:ietf:params:xml:ns:conference-info"

1278	   start = element conference-info { conference-type }
1279	   # CONFERENCE TYPE
1280	   conference-type =
1281	     attribute entity { text },
1282	     anyAttribute,
1283	     conference-description-type,
1284	     element language { xsd:language }?,
1285	     element host-info { conference-info-urn* }?,
1286	     element conference-state { conference-state-type }?,
1287	     element floor-information { floor-information-type }?,
1288	     element users { users-type },
1289	     element sidebars-by-ref { sidebars-by-ref-type }?,
1290	     element sidebars-by-val { sidebars-by-val-type }?,
1291	     anyElement*
1292	   # CONFERENCE DESCRIPTION TYPE
1293	   conference-description-type =
1294	     element conference-description {
1295	       attribute lang { xsd:language }?,
1296	       anyAttribute,
1297	       element display-text { text }?,
1298	       element subject { text }?,
1299	       element free-text { text }?,
1300	       element keywords {
1301	         list { xsd:string* }
1302	       }?,
1303	       element allow-sidebars { xsd:boolean }?,
1304	       element conference-time { conferencetime-type }?,
1305	       element conf-uris {
1306	         (element conference-password { text }?,
1307	          conference-info-urn)*
1308	       }?,
1309	       element service-uris { conference-info-urn* }?,
1310	       element maximum-user-count { xsd:int }?,
1311	       element available-media { conference-media-type }?,
1312	       anyElement*
1313	     }
1314	   # CONFERENCE TIME
1315	   conferencetime-type =
1316	     anyAttribute,
1317	     element entry {
1318	       element base { text }?,
1319	       element mixing-start-offset {
1320	         xsd:dateTime { pattern = ".+T.+Z.*" },
1321	         attribute required-participant { single-role-type },
1322	         anyAttribute
1323	       }?,
1324	       element mixing-end-offset {
1325	         xsd:dateTime { pattern = ".+T.+Z.*" },
1326	         attribute required-participant { single-role-type },
1327	         anyAttribute
1328	       }?,
1329	       element can-join-after-offset {
1330	         xsd:dateTime { pattern = ".+T.+Z.*" }
1331	       }?,
1332	       element must-join-before-offset {
1333	         xsd:dateTime { pattern = ".+T.+Z.*" }
1334	       }?,
1335	       element notify-end-of-conference { xsd:int }?,
1336	       element allowed-extend-mixing-end-offset { xsd:boolean }?,
1337	       anyElement*
1338	     }*,
1339	     anyElement*
1340	   # CONFERENCE MEDIA TYPE
1341	   conference-media-type =
1342	     anyAttribute,
1343	     element entry { conference-medium-type }*,
1344	     anyElement*
1345	   # CONFERENCE MEDIUM TYPE
1346	   conference-medium-type =
1347	     attribute label { text },
1348	     anyAttribute,
1349	     element display-text { text }?,
1350	     element type { text }?,
1351	     element status { media-status-type }?,
1352	     element mixing-mode { mix-mode-type }?,
1353	     element codecs { codecs-type }?,
1354	     element controls { control-type }?,
1355	     anyElement*
1356	   # MIX MODE TYPE
1357	   mix-mode-type =
1358	     xsd:string "moderator-controlled"
1359	     | xsd:string "FCFS"
1360	     | xsd:string "automatic"
1361	     | text
1362	   # CODECS TYPE
1363	   codecs-type =
1364	     attribute decision { decision-type },
1365	     anyAttribute,
1366	     element codec { codec-type }*,
1367	     anyElement*
1368	   # CODEC TYPE
1369	   codec-type =
1370	     attribute name { text },
1371	     attribute policy { policy-type },
1372	     anyAttribute
1373	   # DECISION TYPE
1374	   decision-type =
1375	     xsd:string "automatic" | xsd:string "moderator-controlled" | text
1376	   # POLICY TYPE
1377	   policy-type = xsd:string "allowed" | xsd:string "disallowed" | text
1378	   # CONTROL TYPE
1379	   control-type =
1380	     anyAttribute,
1381	     (element mute { xsd:boolean },
1382	      element pause-video { xsd:boolean },
1383	      element gain {
1384	        xsd:int { minInclusive = "-127" maxInclusive = "127" }
1385	      },
1386	      element video-layout {
1387	        xsd:string "single-view"
1388	        | xsd:string "dual-view"
1389	        | xsd:string "dual-view-crop"
1390	        | xsd:string "dual-view-2x1"
1391	        | xsd:string "dual-view-2x1-crop"
1392	        | xsd:string "quad-view"
1393	        | xsd:string "multiple-3x3"
1394	        | xsd:string "multiple-4x4"
1395	        | xsd:string "multiple-5x1"
1396	        | xsd:string "automatic"
1397	        | text
1398	      },
1399	      anyElement*)*
1400	   # CONFERENCE STATE TYPE
1401	   conference-state-type =
1402	     anyAttribute,
1403	     element allow-conference-event-subscription { xsd:boolean }?,
1404	     element user-count { xsd:unsignedInt }?,
1405	     element active { xsd:boolean }?,
1406	     element locked { xsd:boolean }?,
1407	     anyElement*
1408	   # FLOOR INFORMATION TYPE
1409	   floor-information-type =
1410	     anyAttribute,
1411	     (element conference-ID { xsd:unsignedInt },
1412	      element allow-floor-events { xsd:boolean },
1413	      element floor-request-handling { floor-request-type },
1414	      element conference-floor-policy { Conference-floor-policy },
1415	      anyElement*)*
1416	   # FLOOR REQUEST TYPE
1417	   floor-request-type =xsd:string "block" | xsd:string "confirm" | text
1418	   # CONFERENCE FLOOR POLICY
1419	   Conference-floor-policy =
1420	     anyAttribute,
1421	     element floor {
1422	       attribute id { text },
1423	       anyAttribute,
1424	       element media-label { xsd:nonNegativeInteger }+,
1425	       (element algorithm {
1426	          xsd:string "moderator-controlled"
1427	          | xsd:string "FCFS"
1428	          | xsd:string "random"
1429	          | text
1430	        },
1431	        element max-floor-users { xsd:nonNegativeInteger },
1432	        element moderator-id { text },
1433	        anyElement*)*
1434	     }+
1435	   # USERS TYPE
1436	   users-type =
1437	     anyAttribute,
1438	     element join-handling { join-handling-type }?,
1439	     element user-admission-policy { user-admission-policy-type }?,
1440	     element allowed-users-list { UserList }?,
1441	     element deny-users-list { deny-user-list }?,
1442	     element user { user-type }*,
1443	     anyElement*
1444	   # USERS ADMISSION POLICY
1445	   user-admission-policy-type =
1446	     xsd:string "closedAuthenticated"
1447	     | xsd:string "openAuthenticated"
1448	     | xsd:string "anonymous"
1449	     | text
1450	   # JOIN HANDLING TYPE
1451	   join-handling-type =
1452	     xsd:string "block"
1453	     | xsd:string "confirm"
1454	     | xsd:string "allow"
1455	     | xsd:string "authenticate"
1456	     | xsd:string "directed-operator"
1457	     | text
1458	   # DENYUSERLIST
1459	   deny-user-list =
1460	     anyAttribute,
1461	     element target {
1462	       attribute uri { xsd:anyURI },
1463	       anyAttribute
1464	     }*,
1465	     anyElement*
1466	   # USERLIST
1467	   UserList =
1468	     anyAttribute,
1469	     element target { target-type }*,
1470	     anyElement*,
1471	     element persistent-list {
1472	       element user {
1473	         attribute name { text },
1474	         attribute nickname { text },
1475	         attribute id { text },
1476	         anyAttribute,
1477	         element e-mail { text }*
1478	       }*,
1479	       anyElement
1480	     }?
1481	   # TARGET TYPE
1482	   target-type =
1483	     attribute uri { xsd:anyURI },
1484	     attribute method { method-type },
1485	     anyAttribute
1486	   # METHOD TYPE
1487	   method-type =
1488	     xsd:string "dial-in"
1489	     | xsd:string "dial-out"
1490	     | xsd:string "refer"
1491	     | text
1492	   # USER TYPE
1493	   user-type =
1494	     attribute entity { xsd:anyURI },
1495	     anyAttribute,
1496	     element display-text { text }?,
1497	     element associated-aors { conference-info-urn* }?,
1498	     element provide-anonymity { "private" | "semi-private" | text }?,
1499	     element roles { single-role-type }?,
1500	     element languages {
1501	       list { xsd:language }
1502	     }?,
1503	     element cascaded-focus { xsd:anyURI }?,
1504	     element allow-refer-users-dynamically { xsd:boolean }?,
1505	     element allow-invite-users-dynamically { xsd:boolean }?,
1506	     element allow-remove-users-dynamically { xsd:boolean }?,
1507	     element endpoint { endpoint-type }*,
1508	     anyElement*
1509	   # ENDPOINT TYPE
1510	   endpoint-type =
1511	     attribute entity { text },
1512	     anyAttribute,
1513	     element display-text { text }?,
1514	     element referred { conference-info-urn* }?,
1515	     element status { endpoint-status-type }?,
1516	     element joining-method { joining-type }?,
1517	     element joining-info { conference-info-urn* }?,
1518	     element disconnection-method { disconnection-type }?,
1519	     element disconnection-info { conference-info-urn* }?,
1520	     element media { media-type }*,
1521	     element floor {
1522	       attribute id { text },
1523	       anyAttribute,
1524	       xsd:boolean
1525	     }*,
1526	     element call-info { conference-info-urn* }?,
1527	     anyElement*
1528	   # MEDIA TYPE
1529	   media-type =
1530	     attribute id { xsd:int },
1531	     anyAttribute,
1532	     element display-text { text }?,
1533	     element type { text }?,
1534	     element label { text }?,
1535	     element src-id { text }?,
1536	     element status { media-status-type }?,
1537	     element to-mixer { mixer-type }?,
1538	     element from-mixer { mixer-type }?,
1539	     anyElement*
1540	   # MIXER TYPE
1541	   mixer-type =
1542	     anyAttribute,
1543	     element controls { control-type }?,
1544	     anyElement*
1545	   # SIDEBARS-BY-REF TYPE
1546	   sidebars-by-ref-type =
1547	     anyAttribute,
1548	     element entry { conference-info-urn* }*,
1549	     anyElement*
1550	   # SIDEBARS-BY-VAL TYPE
1551	   sidebars-by-val-type =
1552	     anyAttribute,
1553	     element entry { conference-type }*,
1554	     anyElement*
1555	   # SINGLE ROLE TYPE
1556	   single-role-type =
1557	     xsd:string "administrator"
1558	     | xsd:string "moderator"
1559	     | xsd:string "user"
1560	     | xsd:string "participant"
1561	     | xsd:string "observer"
1562	     | xsd:string "none"
1563	     | text
1564	   # *********************************
1565	   # EXTENSIBILITY OF THE SCHEMA
1566	   # *********************************
1567	   # EXTENSIBILITY ELEMENTS
1568	   anyElement =
1569	     element * {
1570	       (attribute * { text }
1571	        | text
1572	        | anyElement)*
1573	     }
1574	   # EXTENSIBILITY ATTRIBUTES
1575	   anyAttribute =
1576	     attribute * - (entity
1577	                    | lang
1578	                    | required-participant
1579	                    | label
1580	                    | decision
1581	                    | name
1582	                    | policy
1583	                    | uri
1584	                    | method
1585	                    | id
1586	                    | local:*
1587	                    | ns1:*) { text }*
1588	   # *************************************************************
1589	   # TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
1590	   # -  RFC4575 -
1591	   # *************************************************************

1593	   # WILDCARD FOR EVENT-PACKAGE NAMESPACE
1594	   conference-info-urn =
1595	     element * - (ns2:* | local:*) {
1596	       mixed {
1597	         (attribute * { text }
1598	          | conference-info-urn)*
1599	       }
1600	     }
1601	   # DEFINITION OF ENDPOINT STATUS TYPE
1602	   media-status-type =
1603	     "recvonly" | "sendonly" | "sendrecv" | "inactive" | text
1604	   # ENDPOINT STATUS TYPE
1605	   endpoint-status-type =
1606	     "pending"
1607	     | "dialing-out"
1608	     | "dialing-in"
1609	     | "alerting"
1610	     | "on-hold"
1611	     | "connected"
1612	     | "muted-via-focus"
1613	     | "disconnecting"
1614	     | "disconnected"
1615	     | text
1616	   # JOINING TYPE
1617	   joining-type = "dialed-in" | "dialed-out" | "focus-owner" | text
1618	   # DISCONNECTION TYPE
1619	   disconnection-type = "departed" | "booted" | "failed" | "busy" | text

1621	6.  XML Schema Extensibility

1623	   The Conference Information Data Model defined in this document is
1624	   meant to be extensible toward specific application domains.  Such
1625	   extensions are accomplished by defining elements, child elements and
1626	   attributes that are specific to the desired application domain.  The
1627	   IETF MAY extend the data model schema with extension elements from
1628	   the same namespace in future.  Other instances are free to define
1629	   extension elements under any namespace other than
1630	   urn:ietf:params:xml:ns:xcon-conference-info.

1632	   Elements or attributes from unknown namespaces MUST be ignored.

1634	7.  XML Example

1636	   The following is an example of a conference information document.
1637	   The conference starts on October 17, 2007, at 10:30 AM in New York
1638	   City and finishes the same day at 12:30 PM every week.  In this
1639	   example, there are currently 3 participants in a conference, one
1640	   administrator, one moderator, and one participant.  Sidebars are
1641	   allowed in this conference and ,consequently, there is one sidebar in
1642	   the conference.  In addition, Alice and Carol are using a floor in
1643	   the main conference to manage the audio and video resources.  At the
1644	   moment, Alice is assigned to use the floor.

1646	 <?xml version="1.0" encoding="UTF-8"?>
1647	   <conference-info xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
1648	       entity="conference123@example.com">
1649	       <!--
1650	           CONFERENCE DESCRIPTION
1651	       -->

1653	       <conference-description lang="en-us">
1654	           <language>En-us</language>
1655	           <display-text>Discussion of Formula-1 racing</display-text>
1656	           <subject>Sports:Formula-1</subject>
1657	           <free-text>This is a conference example</free-text>
1658	           <keywords>Formula-1, cars</keywords>
1659	           <allow-sidebars>true</allow-sidebars>
1660	           <!--
1661	           CONFERENCE TIME
1662	           -->
1663	           <conference-time>
1664	               <entry>
1665	                   <base>BEGIN:VCALENDAR
1666	 PRODID:-//LlamaSpinner Inc.//NONSGML CamelCall//EN
1667	 VERSION:2.0
1668	 BEGIN:VEVENT
1669	 DTSTAMP:20071003T140728Z
1670	 UID:20071003T140728Z-345FDA-carol@example.com
1671	 ORGANIZER:MAILTO:carol@example.com
1672	 DTSTART:20071017T143000Z
1673	 RRULE:FREQ=WEEKLY
1674	 DTEND:20071217T163000Z
1675	 END:VEVENT
1676	 END:VCALENDAR</base>
1677	                   <mixing-start-offset required-participant="moderator"
1678	                      > 2007-10-17T14:29:00Z</mixing-start-offset>
1679	                   <mixing-end-offset required-participant="participant"
1680	                      > 2007-10-17T16:31:00Z</mixing-end-offset>
1681	                   <must-join-before-offset
1682	                      > 2007-10-17T15:30:00Z</must-join-before-offset>
1683	               </entry>
1684	           </conference-time>
1685	           <!--
1686	           CONFERENCE UNIQUE IDENTIFIERS
1687	           -->
1688	           <conf-uris>
1689	               <entry>
1690	                   <uri>tel:+3585671234</uri>
1691	                   <display-text>Conference Bridge</display-text>
1692	                   <purpose>participation</purpose>
1693	                   <conference-password>5678</conference-password>
1694	               </entry>
1695	               <entry>
1696	                   <uri>http://www.example.com/live.ram</uri>
1697	                   <purpose>streaming</purpose>
1698	               </entry>
1699	           </conf-uris>
1700	           <!--
1701	             SERVICE URIS
1702	           -->
1703	           <service-uris>
1704	               <entry>
1705	                   <uri>http://www.example.com/formula1/</uri>
1706	                   <purpose>web-page</purpose>
1707	               </entry>
1708	           </service-uris>
1709	           <!--
1710	             MAXIMUM USER COUNT
1711	           -->
1712	           <maximum-user-count>50</maximum-user-count>
1713	           <!--
1714	             AVAILABLE MEDIA
1715	           -->
1716	           <available-media>
1717	               <entry label="10234">
1718	                   <display-text>main audio</display-text>
1719	                   <type>audio</type>
1720	                   <status>sendrecv</status>
1721	                   <mixing-mode>automatic</mixing-mode>
1722	                   <codecs decision="automatic">
1723	                       <codec name="PCMU" policy="allowed"/>
1724	                   </codecs>
1725	                   <controls>
1726	                       <mute>true</mute>
1727	                       <gain>50</gain>
1728	                   </controls>
1729	               </entry>
1730	               <entry label="10235">
1731	                   <display-text>main video</display-text>
1732	                   <type>video</type>
1733	                   <status>sendrecv</status>
1734	                   <mixing-mode>automatic</mixing-mode>
1735	                   <codecs decision="automatic">
1736	                       <codec name="H.263" policy="allowed"/>
1737	                   </codecs>
1738	                   <controls>
1739	                       <video-layout>single-view</video-layout>
1740	                   </controls>
1741	               </entry>
1742	           </available-media>
1743	       </conference-description>
1744	       <!--
1745	           HOST INFO
1746	         -->
1747	       <host-info>
1748	           <display-text>Formula1</display-text>
1749	           <web-page>http://www.example.com/formula1/</web-page>
1750	           <uris>
1751	               <entry>
1752	                   <uri>sip:alice@example.com</uri>
1753	               </entry>
1754	               <entry>
1755	                   <uri>sip:carol@example.com</uri>
1756	               </entry>

1758	           </uris>
1759	       </host-info>
1760	       <!--
1761	           CONFERENCE STATE
1762	         -->
1763	       <conference-state>
1764	           <allow-conference-event-subscription
1765	             >true</allow-conference-event-subscription>
1766	           <user-count>3</user-count>
1767	           <active>true</active>
1768	           <locked>false</locked>
1769	       </conference-state>
1770	       <!--
1771	           FLOOR INFORMATION
1772	         -->
1773	       <floor-information>
1774	           <conference-ID>567</conference-ID>
1775	           <allow-floor-events>true</allow-floor-events>
1776	           <floor-request-handling>confirm</floor-request-handling>
1777	           <conference-floor-policy>
1778	               <floor id="345">
1779	                   <media-label>10234</media-label>
1780	                   <media-label>10235</media-label>
1781	                   <algorithm>moderator-controlled</algorithm>
1782	                   <max-floor-users>1</max-floor-users>
1783	                   <moderator-id>234</moderator-id>
1784	               </floor>
1785	           </conference-floor-policy>
1786	       </floor-information>
1787	       <!--
1788	           USERS
1789	         -->
1790	       <users>
1791	           <join-handling>allow</join-handling>
1792	           <user-admission-policy
1793	              >openAuthenticated</user-admission-policy>
1794	           <!--
1795	            ALLOWED USERS LIST
1796	           -->
1797	           <allowed-users-list>
1798	               <target uri="sip:bob@example.com" method="dial-out"/>
1799	               <target uri="sip:alice@example.com" method="dial-out"/>
1800	               <target uri="sip:carol@example.com" method="dial-out"/>
1801	               <target uri="sip:john@example.com" method="refer"/>
1802	           </allowed-users-list>
1803	           <!--
1804	            DENY USERS LIST
1805	           -->
1806	           <deny-users-list>
1807	               <target uri="sip:charlie@example.com"/>
1808	           </deny-users-list>

1810	           <!--
1811	             USER BOB
1812	           -->

1814	           <user entity="bob534">
1815	               <display-text>Bob Hoskins</display-text>
1816	               <associated-aors>
1817	                   <entry>
1818	                       <uri>mailto:bob@example.com</uri>
1819	                       <display-text>email</display-text>
1820	                   </entry>
1821	               </associated-aors>
1822	               <provide-anonymity>semi-private</provide-anonymity>
1823	               <roles>
1824	                   <entry>participant</entry>
1825	               </roles>
1826	               <languages>en-us</languages>
1827	               <allow-refer-users-dynamically
1828	                   >false</allow-refer-users-dynamically>
1829	               <allow-invite-users-dynamically
1830	                   >false</allow-invite-users-dynamically>
1831	               <allow-remove-users-dynamically
1832	                   >false</allow-remove-users-dynamically>
1833	               <!--
1834	                   ENDPOINTS
1835	               -->
1836	               <endpoint entity="sip:bob@example.com">
1837	                   <display-text>Bob's Laptop</display-text>
1838	                   <referred>
1839	                       <when>2007-10-17T14:00:00Z</when>
1840	                       <reason>expert required</reason>
1841	                       <by>sip:alice@example.com</by>
1842	                   </referred>
1843	                   <status>connected</status>
1844	                   <joining-method>dialed-out</joining-method>
1845	                   <joining-info>
1846	                       <when>2007-10-17T14:00:00Z</when>
1847	                       <reason>invitation</reason>
1848	                       <by>sip:alice@example.com</by>
1849	                   </joining-info>

1851	                   <!--
1852	                       MEDIA
1853	                   -->
1854	                   <media id="1">
1855	                       <type>video</type>
1856	                       <label>10235</label>
1857	                       <src-id>432424</src-id>
1858	                       <status>sendrecv</status>
1859	                          <to-mixer name="VideoIn">
1860	                            <controls>
1861	                               <video-layout
1862	                                  >single-view</video-layout>
1863	                            </controls>
1864	                          </to-mixer>
1865	                   </media>
1866	                   <!--
1867	                       CALL INFO
1868	                   -->
1869	                   <call-info>
1870	                       <sip>
1871	                           <display-text>full info</display-text>
1872	                           <call-id>hsjh8980vhsb78</call-id>
1873	                           <from-tag>vav738dvbs</from-tag>
1874	                           <to-tag>8954jgjg8432</to-tag>
1875	                       </sip>
1876	                   </call-info>
1877	               </endpoint>
1878	           </user>

1880	           <!--
1881	               USER ALICE
1882	           -->

1884	           <user entity="alice334">
1885	               <display-text>Alice Kay</display-text>
1886	               <associated-aors>
1887	                   <entry>
1888	                       <uri>mailto:alice@example.com</uri>
1889	                       <display-text>email</display-text>
1890	                   </entry>
1891	               </associated-aors>
1892	               <provide-anonymity>private</provide-anonymity>
1893	               <roles>
1894	                   <entry>moderator</entry>
1895	               </roles>
1896	               <languages>en-us</languages>
1897	               <allow-refer-users-dynamically
1898	                   >true</allow-refer-users-dynamically>
1899	               <allow-invite-users-dynamically
1900	                   >true</allow-invite-users-dynamically>
1901	               <allow-remove-users-dynamically
1902	                   >true</allow-remove-users-dynamically>
1903	               <!--
1904	                   ENDPOINTS
1905	               -->
1906	               <endpoint entity="sip:alice@example.com">
1907	                   <display-text>Alice's Desktop</display-text>
1908	                   <status>connected</status>
1909	                   <joining-method>dialed-in</joining-method>
1910	                   <joining-info>
1911	                       <when>2007-10-17T13:35:08Z</when>
1912	                       <reason>invitation</reason>
1913	                       <by>sip:conference@example.com</by>
1914	                   </joining-info>
1915	                   <!--
1916	                       MEDIA
1917	                   -->
1918	                   <media id="1">
1919	                       <type>video</type>
1920	                       <label>10235</label>
1921	                       <src-id>432424</src-id>
1922	                       <status>sendrecv</status>
1923	                       <to-mixer name="VideoIn">
1924	                        <controls>
1925	                           <video-layout
1926	                             >single-view</video-layout>
1927	                        </controls>
1928	                       </to-mixer>
1929	                   </media>
1930	                   <media id="2">
1931	                       <type>audio</type>
1932	                       <label>10234</label>
1933	                       <src-id>532535</src-id>
1934	                       <status>sendrecv</status>
1935	                       <to-mixer name="VideoIn">
1936	                         <controls>
1937	                           <gain>50</gain>
1938	                         </controls>
1939	                       </to-mixer>
1940	                       <from-mixer name="VideoOut">
1941	                         <controls>
1942	                           <gain>50</gain>
1943	                         </controls>
1944	                       </from-mixer>
1945	                   </media>
1946	                   <floor id="345">true</floor>

1948	                   <!--
1949	                       CALL INFO

1951	                   -->
1952	                   <call-info>
1953	                       <sip>
1954	                           <display-text>full info</display-text>
1955	                           <call-id>truy45469123478</call-id>
1956	                           <from-tag>asd456cbgt</from-tag>
1957	                           <to-tag>3456jgjg1234</to-tag>
1958	                       </sip>
1959	                   </call-info>
1960	               </endpoint>
1961	           </user>

1963	           <!--
1964	                  USER CAROL
1965	           -->

1967	           <user entity="carol233">
1968	               <display-text>Carol More</display-text>
1969	               <associated-aors>
1970	                   <entry>
1971	                       <uri>mailto:carol@example.com</uri>
1972	                       <display-text>email</display-text>
1973	                   </entry>
1974	               </associated-aors>
1975	               <provide-anonymity>private</provide-anonymity>
1976	               <roles>
1977	                   <entry>administrator</entry>
1978	               </roles>
1979	               <languages>en-us</languages>
1980	               <allow-refer-users-dynamically
1981	                   >true</allow-refer-users-dynamically>
1982	               <allow-invite-users-dynamically
1983	                   >true</allow-invite-users-dynamically>
1984	               <allow-remove-users-dynamically
1985	                   >true</allow-remove-users-dynamically>
1986	               <!--
1987	                   ENDPOINTS
1988	               -->
1989	               <endpoint entity="sip:carol@example.com">
1990	                   <display-text>Carol's Computer</display-text>
1991	                   <status>connected</status>
1992	                   <joining-method>dialed-in</joining-method>
1993	                   <joining-info>
1994	                       <when>2007-10-17T13:30:05Z</when>
1995	                       <reason>invitation</reason>
1996	                       <by>sip:conference@example.com</by>
1997	                   </joining-info>
1998	                   <!--
1999	                       MEDIA
2000	                   -->
2001	                   <media id="1">
2002	                       <type>video</type>
2003	                       <label>10235</label>
2004	                       <src-id>432424</src-id>
2005	                       <status>sendrecv</status>
2006	                       <to-mixer name="VideoIn">
2007	                        <controls>
2008	                           <video-layout
2009	                             >single-view</video-layout>
2010	                        </controls>
2011	                       </to-mixer>
2012	                   </media>
2013	                   <media id="2">
2014	                       <type>audio</type>
2015	                       <label>10234</label>
2016	                       <src-id>532535</src-id>
2017	                       <status>sendrecv</status>
2018	                       <to-mixer name="VideoIn">
2019	                         <controls>
2020	                           <gain>50</gain>
2021	                         </controls>
2022	                       </to-mixer>
2023	                       <from-mixer name="VideoOut">
2024	                         <controls>
2025	                           <gain>50</gain>
2026	                         </controls>
2027	                       </from-mixer>
2028	                   </media>
2029	                   <floor id="345">false</floor>

2031	                   <!--
2032	                       CALL INFO
2033	                   -->
2034	                   <call-info>
2035	                       <sip>
2036	                           <display-text>full info</display-text>
2037	                           <call-id>wevb12562321894</call-id>
2038	                           <from-tag>asw456wedf</from-tag>
2039	                           <to-tag>2365dfrt3497</to-tag>
2040	                       </sip>
2041	                   </call-info>
2042	               </endpoint>
2043	           </user>
2044	       </users>
2045	       <!--
2046	            SIDEBARS BY REFERENCE

2048	          -->
2049	       <sidebars-by-ref>
2050	           <entry>
2051	               <uri>conf223</uri>
2052	               <display-text>private with Bob</display-text>
2053	           </entry>
2054	       </sidebars-by-ref>
2055	       <!--
2056	            SIDEBARS BY VALUE
2057	          -->
2058	       <sidebars-by-val>
2059	           <entry entity="conf223">
2060	               <users>
2061	                   <user entity="bob534"/>
2062	                   <user entity="carol233"/>
2063	               </users>
2064	           </entry>
2065	       </sidebars-by-val>
2066	   </conference-info>

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

2073	8.  Security Considerations

2075	   There are numerous security considerations for this document.  This
2076	   section considers them.

2078	8.1.  Authentication

2080	   Different conferencing protocols will support different types of
2081	   authentication mechanisms.  Since a variety of signaling protocols
2082	   are possible, a variety of authentication mechanism may need to be
2083	   mapped from the different protocols.

2085	   Futhermore, users may use different namespaces to access to a
2086	   conference.  So a mapping database has to specify the acceptable
2087	   range of namespace for a user.  Doing so, a users will not access the
2088	   same conference twice using a different namespace.

2090	   The security considerations for authentication (section 10.1)
2091	   described in the centralized conferencing framework [RFC4575] applies
2092	   to this document.  The focus must ensure that only authorized
2093	   entities are able to manipulate the data to access the information.

2095	8.2.  Confidentiality

2097	   Participants of a conference may not want to reveal some private
2098	   information to other users.  The Conference Information Data Model
2099	   contains sensitive data which should not be analyzed or given to
2100	   anyone.  Confidentiality is provided through encryption.  Strong end-
2101	   to-end authentication and encryption can be done using public keys,
2102	   and end-to-end encryption can be done using private keys.  It is
2103	   RECOMMENDED that the protocols that manipulated the conference
2104	   information data model use a strong encryption for conference
2105	   information protection.

2107	8.3.  Integrity

2109	   A conferencing system may maintain a mapping database between the
2110	   conference object identifiers and the identifiers associated with
2111	   each of the complementary centralized conferencing protocols, as well
2112	   as, a mapping between the conference user identifiers and the
2113	   identifiers associated with each user in a conference.  This mapping
2114	   database contains sensitive data.  It is RECOMMENDED that the mapping
2115	   database has integrity when it is established, the integrity has to
2116	   be protected, and the database has to be maintained to ensure changes
2117	   in namespaces are accurately reflected.

2119	9.  IANA Considerations

2121	9.1.  Relax NG Schema Registration

2123	  This specification registers a schema. The schema can be found
2124	  as the sole content of Section 5.

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

2128	     Registrant Contact: IETF XCON working group,
2129	        <xcon@ietf.org>, Oscar Novo
2130	        <Oscar.Novo@ericsson.com>

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

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

2137	        and its last line is

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

2141	9.2.  XML Namespace Registration

2143	   This section registers a new XML namespace.

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

2147	      Registrant Contact: IETF XCON working group,
2148	         <xcon@ietf.org>, Oscar Novo
2149	         <Oscar.Novo@ericsson.com>

2151	       XML:

2153	         BEGIN
2154	         <?xml version="1.0"?>
2155	         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
2156	           "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
2157	         <html xmlns="http://www.w3.org/1999/xhtml">
2158	         <head>
2159	           <meta http-equiv="content-type"
2160	                 content="text/html;charset=iso-8859-1"/>
2161	           <title> Centralized Conferencing Namespace</title>
2162	         </head>
2163	         <body>
2164	           <h1>Namespace for Centralized COnferencing</h1>
2165	           <h2>urn:ietf:params:xml:ns:consent-rules</h2>
2166	         <p>See <a href="[URL of published RFC]">RFCXXXX
2167	             [NOTE TO IANA/RFC-EDITOR:
2168	              Please replace XXXX with the RFC number of this
2169	             specification.]</a>.</p>
2170	         </body>
2171	         </html>
2172	         END

2174	9.3.  Conference Object Identifier Registration

2176	 The IANA is requested to register the following URI scheme
2177	 under the Permanent URI Schemes register.

2179	 XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx]

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

2183	   host, port, and unreserved are defined in RFC3986[RFC3986]

2185	   [Note to the RFC Editor: replace xxxx with the number this RFC gets
2186	   assigned.]

2188	9.4.  Conference User Identifier Registration

2190	   The IANA is requested to register the following URI scheme
2191	    under the Permanent URI Schemes register.

2193	    XCON_USERID = "xcon_userid" ":" conf-object-id  [ RFC xxxx ]

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

2197	   unreserved is defined in RFC3986[RFC3986]

2199	   [Note to the RFC Editor: replace xxxx with the number this RFC gets
2200	   assigned.]

2202	10.  Acknowledgements

2204	   This document is really a distillation of many ideas discussed over a
2205	   long period of time.  These ideas were contributed by many different
2206	   drafts in the XCON working group and the SIPPING working group.  We
2207	   would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris
2208	   Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Aki
2209	   Niemi, Jari Urpilainen, Rohan Mahy, and Henning Schulzrinne for their
2210	   comments.  Also, we would like to thank Mary Barnes, and Chris
2211	   Boulton for letting us use the conference and user identifier
2212	   information of their xcon drafts.  Last but not least, I would like
2213	   to express my gratitude to all those reviewers for their invaluable
2214	   contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi,
2215	   Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, and
2216	   Ben Campbell.

2218	11.  References

2220	11.1.  Normative References

2222	   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
2223	              Requirement Levels", BCP 14, RFC 2119, March 1997.

2225	   [RFC2445]  Dawson, F. and Stenerson, D., "Internet Calendaring and
2226	              Scheduling Core Object Specification (iCalendar)",
2227	              RFC 2445, November 1998.

2229	   [RFC4575]  Rosenberg, J., Schulzrinne, H., and O. Levin, "A Session
2230	              Initiation Protocol (SIP) Event Package for Conference
2231	              State", RFC 4575, August 2006.

2233	11.2.  Informative References

2235	   [I-D.ietf-xcon-framework]
2236	              Barnes, M., Boulton, C., and O. Levin, "A Framework for
2237	              Centralized Conferencing", draft-ietf-xcon-framework-10
2238	              (work in progress), November 2007.

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

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

2245	   [RFC3264]  Rosenberg, J. and H. Schulzrinne, "An Offer/Answer Model
2246	              with Session Description Protocol (SDP)", RFC 3264,
2247	              June 2002.

2249	   [RFC3265]  Roach, A., "Session Initiation Protocol (SIP)-Specific
2250	              Event Notification", RFC 3265, June 2002.

2252	   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
2253	              Resource Identifier (URI): Generic Syntax", STD 66,
2254	              RFC 3986, January 2005.

2256	   [RFC4353]  Rosenberg, J., "A Framework for Conferencing with the
2257	              Session Initiation Protocol (SIP)", RFC 4353,
2258	              February 2006.

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

2263	   [RFC4583]  Camarillo, G., "Session Description Protocol (SDP) Format
2264	              for Binary Floor Control Protocol (BFCP) Streams",
2265	              RFC 4583, November 2006.

2267	   [RFC4855]  Casner, S., "Media Type Registration of RTP Payload
2268	              Formats", RFC 4855, February 2007.

2270	   [RFC5018]  Camarillo, G., "Connection Establishment in the Binary
2271	              Floor Control Protocol (BFCP)", RFC 5018, September 2007.

2273	   [W3C.REC-xml-20001006]
2274	              Paoli, J., Maler, E., Sperberg-McQueen, C., and T. Bray,
2275	              "Extensible Markup Language (XML) 1.0 (Second Edition)",
2276	              World Wide Web Consortium FirstEdition REC-xml-20001006,
2277	              October 2000,
2278	              <http://www.w3.org/TR/2000/REC-xml-20001006>.

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

2282	   <?xml version="1.0" encoding="UTF-8"?>
2283	   <grammar ns="urn:ietf:params:xml:ns:xcon-conference-info"
2284	    xmlns="http://relaxng.org/ns/structure/1.0"
2285	    xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
2286	    datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
2287	    <start>
2288	     <element name="conference-info">
2289	      <ref name="conference-type"/>
2290	     </element>
2291	    </start>
2292	    <!--
2293	           CONFERENCE TYPE
2294	       -->
2295	    <define name="conference-type">
2296	     <attribute name="entity">
2297	      <text/>
2298	     </attribute>
2299	     <ref name="anyAttribute"/>
2300	     <ref name="conference-description-type"/>
2301	     <optional>
2302	      <element name="language">
2303	       <data type="language"/>
2304	      </element>
2305	     </optional>
2306	     <optional>
2307	      <element name="host-info">
2308	        <zeroOrMore>
2309	         <ref name="conference-info-urn"/>
2310	        </zeroOrMore>
2311	      </element>
2312	     </optional>
2313	     <optional>
2314	     <element name="conference-state">
2315	       <ref name="conference-state-type"/>
2316	     </element>
2317	     </optional>
2318	     <optional>
2319	      <element name="floor-information">
2320	       <ref name="floor-information-type"/>
2321	      </element>
2322	     </optional>
2323	     <element name="users">
2324	      <ref name="users-type"/>
2325	     </element>
2326	     <optional>
2327	      <element name="sidebars-by-ref">
2328	       <ref name="sidebars-by-ref-type"/>
2329	      </element>
2330	     </optional>
2331	     <optional>
2332	      <element name="sidebars-by-val">
2333	       <ref name="sidebars-by-val-type"/>
2334	      </element>
2335	     </optional>
2336	     <zeroOrMore>
2337	      <ref name="anyElement"/>
2338	     </zeroOrMore>
2339	    </define>
2340	    <!--
2341	           CONFERENCE DESCRIPTION TYPE
2342	       -->
2343	    <define name="conference-description-type">
2344	     <element name="conference-description">
2345	      <optional>
2346	       <attribute name="lang">
2347	        <data type="language"/>
2348	       </attribute>
2349	      </optional>
2350	      <ref name="anyAttribute"/>
2351	      <optional>
2352	       <element name="display-text">
2353	        <text/>
2354	       </element>
2355	      </optional>
2356	      <optional>
2357	       <element name="subject">
2358	        <text/>
2359	       </element>
2360	      </optional>
2361	      <optional>
2362	       <element name="free-text">
2363	        <text/>
2364	       </element>
2365	      </optional>
2366	      <optional>
2367	       <element name="keywords">
2368	        <list>
2369	         <zeroOrMore>
2370	          <data type="string"/>
2371	         </zeroOrMore>

2373	        </list>
2374	       </element>
2375	      </optional>
2376	      <optional>
2377	       <element name="allow-sidebars">
2378	        <data type="boolean"/>
2379	       </element>
2380	      </optional>
2381	      <optional>
2382	       <element name="conference-time">
2383	        <ref name="conferencetime-type"/>
2384	       </element>
2385	      </optional>
2386	      <optional>
2387	       <element name="conf-uris">
2388	         <zeroOrMore>
2389	          <optional>
2390	           <element name="conference-password">
2391	            <text/>
2392	           </element>
2393	          </optional>
2394	          <ref name="conference-info-urn"/>
2395	         </zeroOrMore>
2396	       </element>
2397	      </optional>
2398	      <optional>
2399	       <element name="service-uris">
2400	         <zeroOrMore>
2401	          <ref name="conference-info-urn"/>
2402	         </zeroOrMore>
2403	       </element>
2404	      </optional>
2405	      <optional>
2406	       <element name="maximum-user-count">
2407	        <data type="int"/>
2408	       </element>
2409	      </optional>
2410	      <optional>
2411	       <element name="available-media">
2412	        <ref name="conference-media-type"/>
2413	       </element>
2414	       </optional>
2415	      <zeroOrMore>
2416	       <ref name="anyElement"/>
2417	      </zeroOrMore>
2418	     </element>
2419	    </define>
2420	    <!--
2421	           CONFERENCE TIME
2422	       -->
2423	    <define name="conferencetime-type">
2424	     <ref name="anyAttribute"/>
2425	     <zeroOrMore>
2426	      <element name="entry">
2427	       <optional>
2428	        <element name="base">
2429	         <text/>
2430	        </element>
2431	       </optional>
2432	       <optional>
2433	        <element name="mixing-start-offset">
2434	         <data type="dateTime">
2435	          <param name="pattern">.+T.+Z.*</param>
2436	         </data>
2437	         <attribute name="required-participant">
2438	          <ref name="single-role-type"/>
2439	         </attribute>
2440	         <ref name="anyAttribute"/>
2441	        </element>
2442	       </optional>
2443	       <optional>
2444	        <element name="mixing-end-offset">
2445	         <data type="dateTime">
2446	          <param name="pattern">.+T.+Z.*</param>
2447	         </data>
2448	         <attribute name="required-participant">
2449	          <ref name="single-role-type"/>
2450	         </attribute>
2451	         <ref name="anyAttribute"/>
2452	        </element>
2453	       </optional>
2454	       <optional>
2455	        <element name="can-join-after-offset">
2456	         <data type="dateTime">
2457	          <param name="pattern">.+T.+Z.*</param>
2458	         </data>
2459	        </element>
2460	       </optional>
2461	       <optional>
2462	        <element name="must-join-before-offset">
2463	         <data type="dateTime">
2464	          <param name="pattern">.+T.+Z.*</param>
2465	         </data>
2466	        </element>
2467	       </optional>
2468	       <optional>
2469	        <element name="notify-end-of-conference">
2470	         <data type="int"/>
2471	        </element>
2472	       </optional>
2473	       <optional>
2474	        <element name="allowed-extend-mixing-end-offset">
2475	         <data type="boolean"/>
2476	        </element>
2477	       </optional>
2478	       <zeroOrMore>
2479	        <ref name="anyElement"/>
2480	       </zeroOrMore>
2481	      </element>
2482	     </zeroOrMore>
2483	     <zeroOrMore>
2484	      <ref name="anyElement"/>
2485	     </zeroOrMore>
2486	    </define>

2488	    <!--
2489	           CONFERENCE MEDIA TYPE
2490	       -->
2491	    <define name="conference-media-type">
2492	     <ref name="anyAttribute"/>
2493	     <zeroOrMore>
2494	      <element name="entry">
2495	       <ref name="conference-medium-type"/>
2496	      </element>
2497	     </zeroOrMore>
2498	     <zeroOrMore>
2499	      <ref name="anyElement"/>
2500	     </zeroOrMore>
2501	    </define>
2502	    <!--
2503	           CONFERENCE MEDIUM TYPE
2504	       -->
2505	    <define name="conference-medium-type">
2506	     <attribute name="label">
2507	      <text/>
2508	     </attribute>
2509	     <ref name="anyAttribute"/>
2510	     <optional>
2511	      <element name="display-text">
2512	       <text/>
2513	      </element>
2514	     </optional>
2515	     <optional>
2516	      <element name="type">
2517	       <text/>
2518	      </element>
2519	     </optional>
2520	     <optional>
2521	      <element name="status">
2522	       <ref name="media-status-type"/>
2523	      </element>
2524	     </optional>
2525	     <optional>
2526	      <element name="mixing-mode">
2527	       <ref name="mix-mode-type"/>
2528	      </element>
2529	     </optional>
2530	     <optional>
2531	      <element name="codecs">
2532	       <ref name="codecs-type"/>
2533	      </element>
2534	     </optional>
2535	     <optional>
2536	      <element name="controls">
2537	       <ref name="control-type"/>
2538	      </element>
2539	     </optional>
2540	     <zeroOrMore>
2541	      <ref name="anyElement"/>
2542	     </zeroOrMore>
2543	    </define>
2544	    <!--
2545	           MIX MODE TYPE
2546	       -->
2547	    <define name="mix-mode-type">
2548	     <choice>
2549	      <value type="string">moderator-controlled</value>
2550	      <value type="string">FCFS</value>
2551	      <value type="string">automatic</value>
2552	      <text/>
2553	     </choice>
2554	    </define>
2555	    <!--
2556	           CODECS TYPE
2557	       -->
2558	    <define name="codecs-type">
2559	     <attribute name="decision">
2560	      <ref name="decision-type"/>
2561	     </attribute>
2562	     <ref name="anyAttribute"/>
2563	     <zeroOrMore>
2564	      <element name="codec">
2565	       <ref name="codec-type"/>
2566	      </element>
2567	     </zeroOrMore>
2568	     <zeroOrMore>
2569	      <ref name="anyElement"/>
2570	     </zeroOrMore>
2571	    </define>
2572	    <!--
2573	           CODEC TYPE
2574	       -->
2575	    <define name="codec-type">
2576	     <attribute name="name">
2577	      <text/>
2578	     </attribute>
2579	     <attribute name="policy">
2580	      <ref name="policy-type"/>
2581	     </attribute>
2582	     <ref name="anyAttribute"/>
2583	    </define>
2584	    <!--
2585	           DECISION TYPE
2586	       -->
2587	    <define name="decision-type">
2588	     <choice>
2589	      <value type="string">automatic</value>
2590	      <value type="string">moderator-controlled</value>
2591	      <text/>
2592	     </choice>
2593	    </define>
2594	    <!--
2595	           POLICY TYPE
2596	       -->
2597	    <define name="policy-type">
2598	     <choice>
2599	      <value type="string">allowed</value>
2600	      <value type="string">disallowed</value>
2601	      <text/>
2602	     </choice>
2603	    </define>
2604	    <!--
2605	           CONTROL TYPE
2606	       -->
2607	    <define name="control-type">
2608	     <ref name="anyAttribute"/>
2609	     <zeroOrMore>
2610	      <element name="mute">
2611	       <data type="boolean"/>
2612	      </element>
2613	      <element name="pause-video">
2614	       <data type="boolean"/>
2615	      </element>
2616	      <element name="gain">
2617	       <data type="int">
2618	        <param name="minInclusive">-127</param>
2619	        <param name="maxInclusive">127</param>
2620	       </data>
2621	      </element>
2622	      <element name="video-layout">
2623	       <choice>
2624	        <value type="string">single-view</value>
2625	        <value type="string">dual-view</value>
2626	        <value type="string">dual-view-crop</value>
2627	        <value type="string">dual-view-2x1</value>
2628	        <value type="string">dual-view-2x1-crop</value>
2629	        <value type="string">quad-view</value>
2630	        <value type="string">multiple-3x3</value>
2631	        <value type="string">multiple-4x4</value>
2632	        <value type="string">multiple-5x1</value>
2633	        <value type="string">automatic</value>
2634	        <text/>
2635	       </choice>
2636	      </element>
2637	      <zeroOrMore>
2638	       <ref name="anyElement"/>
2639	      </zeroOrMore>
2640	     </zeroOrMore>
2641	    </define>
2642	    <!--
2643	           CONFERENCE STATE TYPE
2644	       -->
2645	    <define name="conference-state-type">
2646	     <ref name="anyAttribute"/>
2647	     <optional>
2648	      <element name="allow-conference-event-subscription">
2649	       <data type="boolean"/>
2650	      </element>
2651	     </optional>
2652	     <optional>
2653	      <element name="user-count">
2654	       <data type="unsignedInt"/>
2655	      </element>
2656	     </optional>
2657	     <optional>
2658	      <element name="active">
2659	       <data type="boolean"/>
2660	      </element>

2662	     </optional>
2663	     <optional>
2664	      <element name="locked">
2665	       <data type="boolean"/>
2666	      </element>
2667	     </optional>
2668	     <zeroOrMore>
2669	      <ref name="anyElement"/>
2670	     </zeroOrMore>
2671	    </define>
2672	    <!--
2673	           FLOOR INFORMATION TYPE
2674	       -->
2675	    <define name="floor-information-type">
2676	     <ref name="anyAttribute"/>
2677	     <zeroOrMore>
2678	      <element name="conference-ID">
2679	       <data type="unsignedInt"/>
2680	      </element>
2681	      <element name="allow-floor-events">
2682	       <data type="boolean"/>
2683	      </element>
2684	      <element name="floor-request-handling">
2685	       <ref name="floor-request-type"/>
2686	      </element>
2687	      <element name="conference-floor-policy">
2688	       <ref name="Conference-floor-policy"/>
2689	      </element>
2690	      <zeroOrMore>
2691	       <ref name="anyElement"/>
2692	      </zeroOrMore>
2693	     </zeroOrMore>
2694	    </define>
2695	    <!--
2696	           FLOOR REQUEST TYPE
2697	       -->
2698	    <define name="floor-request-type">
2699	     <choice>
2700	      <value type="string">block</value>
2701	      <value type="string">confirm</value>
2702	      <text/>
2703	     </choice>
2704	    </define>
2705	    <!--
2706	           CONFERENCE FLOOR POLICY
2707	       -->
2708	    <define name="Conference-floor-policy">
2709	     <ref name="anyAttribute"/>
2710	     <oneOrMore>
2711	      <element name="floor">
2712	       <attribute name="id">
2713	        <text/>
2714	       </attribute>
2715	       <ref name="anyAttribute"/>
2716	       <oneOrMore>
2717	        <element name="media-label">
2718	         <data type="nonNegativeInteger"/>
2719	        </element>
2720	        </oneOrMore>
2721	        <zeroOrMore>
2722	        <element name="algorithm">
2723	         <choice>
2724	          <value type="string">moderator-controlled</value>
2725	          <value type="string">FCFS</value>
2726	          <value type="string">random</value>
2727	          <text/>
2728	         </choice>
2729	        </element>
2730	        <element name="max-floor-users">
2731	         <data type="nonNegativeInteger"/>
2732	        </element>
2733	        <element name="moderator-id">
2734	         <text/>
2735	        </element>
2736	        <zeroOrMore>
2737	         <ref name="anyElement"/>
2738	        </zeroOrMore>
2739	       </zeroOrMore>
2740	      </element>
2741	     </oneOrMore>
2742	    </define>
2743	    <!--
2744	           USERS TYPE
2745	       -->
2746	    <define name="users-type">
2747	     <ref name="anyAttribute"/>
2748	     <optional>
2749	      <element name="join-handling">
2750	       <ref name="join-handling-type"/>
2751	      </element>
2752	     </optional>
2753	     <optional>
2754	      <element name="user-admission-policy">
2755	       <ref name="user-admission-policy-type"/>
2756	      </element>
2757	     </optional>
2758	     <optional>
2759	      <element name="allowed-users-list">
2760	       <ref name="UserList"/>
2761	      </element>
2762	     </optional>
2763	     <optional>
2764	      <element name="deny-users-list">
2765	       <ref name="deny-user-list"/>
2766	      </element>
2767	     </optional>
2768	     <zeroOrMore>
2769	      <element name="user">
2770	       <ref name="user-type"/>
2771	      </element>
2772	     </zeroOrMore>
2773	     <zeroOrMore>
2774	      <ref name="anyElement"/>
2775	     </zeroOrMore>
2776	    </define>
2777	    <!--
2778	           USERS ADMISSION POLICY
2779	       -->
2780	    <define name="user-admission-policy-type">
2781	     <choice>
2782	      <value type="string">closedAuthenticated</value>
2783	      <value type="string">openAuthenticated</value>
2784	      <value type="string">anonymous</value>
2785	      <text/>
2786	     </choice>
2787	    </define>
2788	    <!--
2789	           JOIN HANDLING TYPE
2790	       -->
2791	    <define name="join-handling-type">
2792	     <choice>
2793	      <value type="string">block</value>
2794	      <value type="string">confirm</value>
2795	      <value type="string">allow</value>
2796	      <value type="string">authenticate</value>
2797	      <value type="string">directed-operator</value>
2798	      <text/>
2799	     </choice>
2800	    </define>

2802	    <!--
2803	     DENYUSERLIST
2804	    -->
2805	    <define name="deny-user-list">
2806	     <ref name="anyAttribute"/>
2807	     <zeroOrMore>
2808	      <element name="target">
2809	       <attribute name="uri">
2810	        <data type="anyURI"/>
2811	       </attribute>
2812	       <ref name="anyAttribute"/>
2813	      </element>
2814	     </zeroOrMore>
2815	     <zeroOrMore>
2816	      <ref name="anyElement"/>
2817	     </zeroOrMore>
2818	    </define>
2819	    <!--
2820	           USERLIST
2821	       -->
2822	    <define name="UserList">
2823	     <ref name="anyAttribute"/>
2824	     <zeroOrMore>
2825	      <element name="target">
2826	       <ref name="target-type"/>
2827	      </element>
2828	     </zeroOrMore>
2829	     <zeroOrMore>
2830	      <ref name="anyElement"/>
2831	     </zeroOrMore>
2832	     <optional>
2833	      <element name="persistent-list">
2834	       <zeroOrMore>
2835	        <element name="user">
2836	         <attribute name="name">
2837	         <text/>
2838	         </attribute>
2839	         <attribute name="nickname">
2840	          <text/>
2841	         </attribute>
2842	         <attribute name="id">
2843	          <text/>
2844	         </attribute>
2845	         <ref name="anyAttribute"/>
2846	       <zeroOrMore>
2847	         <element name="e-mail">
2848	          <text/>
2849	         </element>
2850	       </zeroOrMore>
2851	        </element>
2852	        </zeroOrMore>
2853	       <ref name="anyElement"/>

2855	      </element>
2856	     </optional>
2857	    </define>
2858	    <!--
2859	           TARGET TYPE
2860	       -->
2861	    <define name="target-type">
2862	     <attribute name="uri">
2863	      <data type="anyURI"/>
2864	     </attribute>
2865	     <attribute name="method">
2866	      <ref name="method-type"/>
2867	     </attribute>
2868	     <ref name="anyAttribute"/>
2869	    </define>
2870	    <!--
2871	           METHOD TYPE
2872	       -->
2873	    <define name="method-type">
2874	     <choice>
2875	      <value type="string">dial-in</value>
2876	      <value type="string">dial-out</value>
2877	      <value type="string">refer</value>
2878	      <text/>
2879	     </choice>
2880	    </define>
2881	    <!--
2882	           USER TYPE
2883	       -->
2884	    <define name="user-type">
2885	     <attribute name="entity">
2886	      <data type="anyURI"/>
2887	     </attribute>
2888	     <ref name="anyAttribute"/>
2889	     <optional>
2890	      <element name="display-text">
2891	       <text/>
2892	      </element>
2893	     </optional>
2894	     <optional>
2895	      <element name="associated-aors">
2896	       <zeroOrMore>
2897	        <ref name="conference-info-urn"/>
2898	       </zeroOrMore>
2899	      </element>
2900	     </optional>
2901	     <optional>
2902	      <element name="provide-anonymity">
2903	       <choice>
2904	        <value>private</value>
2905	        <value>semi-private</value>
2906	        <text/>
2907	        </choice>
2908	      </element>
2909	     </optional>
2910	     <optional>
2911	      <element name="roles">
2912	       <ref name="single-role-type"/>
2913	      </element>
2914	     </optional>
2915	     <optional>
2916	      <element name="languages">
2917	       <list>
2918	        <data type="language"/>
2919	       </list>
2920	      </element>
2921	     </optional>
2922	     <optional>
2923	      <element name="cascaded-focus">
2924	       <data type="anyURI"/>
2925	      </element>
2926	     </optional>
2927	     <optional>
2928	      <element name="allow-refer-users-dynamically">
2929	       <data type="boolean"/>
2930	      </element>
2931	     </optional>
2932	     <optional>
2933	      <element name="allow-invite-users-dynamically">
2934	       <data type="boolean"/>
2935	      </element>
2936	     </optional>
2937	     <optional>
2938	      <element name="allow-remove-users-dynamically">
2939	       <data type="boolean"/>
2940	      </element>
2941	     </optional>
2942	     <zeroOrMore>
2943	      <element name="endpoint">
2944	       <ref name="endpoint-type"/>
2945	      </element>
2946	     </zeroOrMore>
2947	     <zeroOrMore>
2948	      <ref name="anyElement"/>
2949	     </zeroOrMore>
2950	    </define>
2951	    <!--
2952	           ENDPOINT TYPE
2953	       -->
2954	    <define name="endpoint-type">
2955	     <attribute name="entity">
2956	      <text/>
2957	     </attribute>
2958	     <ref name="anyAttribute"/>
2959	     <optional>
2960	      <element name="display-text">
2961	       <text/>
2962	      </element>
2963	     </optional>
2964	     <optional>
2965	      <element name="referred">
2966	       <zeroOrMore>
2967	        <ref name="conference-info-urn"/>
2968	       </zeroOrMore>
2969	      </element>
2970	     </optional>
2971	     <optional>
2972	      <element name="status">
2973	       <ref name="endpoint-status-type"/>
2974	      </element>
2975	     </optional>
2976	     <optional>
2977	      <element name="joining-method">
2978	       <ref name="joining-type"/>
2979	      </element>
2980	     </optional>
2981	     <optional>
2982	      <element name="joining-info">
2983	       <zeroOrMore>
2984	        <ref name="conference-info-urn"/>
2985	       </zeroOrMore>
2986	      </element>
2987	     </optional>
2988	     <optional>
2989	      <element name="disconnection-method">
2990	       <ref name="disconnection-type"/>
2991	      </element>
2992	     </optional>
2993	     <optional>
2994	      <element name="disconnection-info">
2995	       <zeroOrMore>
2996	        <ref name="conference-info-urn"/>
2997	       </zeroOrMore>
2998	      </element>

3000	     </optional>
3001	     <zeroOrMore>
3002	      <element name="media">
3003	       <ref name="media-type"/>
3004	      </element>
3005	     </zeroOrMore>
3006	     <zeroOrMore>
3007	     <element name="floor">
3008	      <attribute name="id">
3009	       <text/>
3010	      </attribute>
3011	      <ref name="anyAttribute"/>
3012	      <data type="boolean"/>
3013	     </element>
3014	     </zeroOrMore>
3015	     <optional>
3016	      <element name="call-info">
3017	       <zeroOrMore>
3018	        <ref name="conference-info-urn"/>
3019	       </zeroOrMore>
3020	      </element>
3021	     </optional>
3022	     <zeroOrMore>
3023	      <ref name="anyElement"/>
3024	     </zeroOrMore>
3025	    </define>
3026	    <!--
3027	           MEDIA TYPE
3028	       -->
3029	    <define name="media-type">
3030	     <attribute name="id">
3031	      <data type="int"/>
3032	     </attribute>
3033	     <ref name="anyAttribute"/>
3034	     <optional>
3035	      <element name="display-text">
3036	       <text/>
3037	      </element>
3038	     </optional>
3039	     <optional>
3040	      <element name="type">
3041	       <text/>
3042	      </element>
3043	     </optional>
3044	     <optional>
3045	      <element name="label">
3046	       <text/>
3047	      </element>

3049	     </optional>
3050	     <optional>
3051	      <element name="src-id">
3052	       <text/>
3053	      </element>
3054	     </optional>
3055	     <optional>
3056	      <element name="status">
3057	       <ref name="media-status-type"/>
3058	      </element>
3059	     </optional>
3060	     <optional>
3061	      <element name="to-mixer">
3062	       <ref name="mixer-type"/>
3063	      </element>
3064	     </optional>
3065	     <optional>
3066	      <element name="from-mixer">
3067	       <ref name="mixer-type"/>
3068	      </element>
3069	     </optional>
3070	     <zeroOrMore>
3071	      <ref name="anyElement"/>
3072	     </zeroOrMore>
3073	    </define>
3074	    <!--
3075	           MIXER TYPE
3076	       -->
3077	    <define name="mixer-type">
3078	     <ref name="anyAttribute"/>
3079	     <optional>
3080	      <element name="controls">
3081	       <ref name="control-type"/>
3082	      </element>
3083	     </optional>
3084	     <zeroOrMore>
3085	      <ref name="anyElement"/>
3086	     </zeroOrMore>
3087	    </define>
3088	    <!--
3089	           SIDEBARS-BY-REF TYPE
3090	       -->
3091	    <define name="sidebars-by-ref-type">
3092	     <ref name="anyAttribute"/>
3093	     <zeroOrMore>
3094	      <element name="entry">
3095	       <zeroOrMore>
3096	        <ref name="conference-info-urn"/>

3098	       </zeroOrMore>
3099	      </element>
3100	     </zeroOrMore>
3101	     <zeroOrMore>
3102	      <ref name="anyElement"/>
3103	     </zeroOrMore>
3104	    </define>
3105	    <!--
3106	           SIDEBARS-BY-VAL TYPE
3107	       -->
3108	    <define name="sidebars-by-val-type">
3109	     <ref name="anyAttribute"/>
3110	     <zeroOrMore>
3111	      <element name="entry">
3112	       <ref name="conference-type"/>
3113	      </element>
3114	     </zeroOrMore>
3115	     <zeroOrMore>
3116	      <ref name="anyElement"/>
3117	     </zeroOrMore>
3118	    </define>
3119	    <!--
3120	     SINGLE ROLE TYPE
3121	    -->
3122	    <define name="single-role-type">
3123	     <choice>
3124	      <value type="string">administrator</value>
3125	      <value type="string">moderator</value>
3126	      <value type="string">user</value>
3127	      <value type="string">participant</value>
3128	      <value type="string">observer</value>
3129	      <value type="string">none</value>
3130	      <text/>
3131	     </choice>
3132	    </define>
3133	    <!--
3134	           *********************************
3135	           EXTENSIBILITY OF THE SCHEMA
3136	           *********************************
3137	       -->
3138	    <!--
3139	           EXTENSIBILITY ELEMENTS
3140	       -->
3141	    <define name="anyElement">
3142	     <element>
3143	      <anyName/>
3144	      <zeroOrMore>
3145	       <choice>
3146	        <attribute>
3147	         <anyName/>
3148	        </attribute>
3149	        <text/>
3150	        <ref name="anyElement"/>
3151	       </choice>
3152	      </zeroOrMore>
3153	     </element>
3154	    </define>
3155	    <!--
3156	           EXTENSIBILITY ATTRIBUTES
3157	       -->
3158	    <define name="anyAttribute">
3159	     <zeroOrMore>
3160	      <attribute>
3161	       <anyName>
3162	        <except>
3163	         <name ns="">entity</name>
3164	         <name ns="">lang</name>
3165	         <name ns="">required-participant</name>
3166	         <name ns="">label</name>
3167	         <name ns="">decision</name>
3168	         <name ns="">name</name>
3169	         <name ns="">policy</name>
3170	         <name ns="">uri</name>
3171	         <name ns="">method</name>
3172	         <name ns="">id</name>
3173	         <nsName ns=""/>
3174	         <nsName ns="urn:ietf:params:xml:ns:xcon-conference-info"/>
3175	        </except>
3176	       </anyName>
3177	       <text/>
3178	      </attribute>
3179	     </zeroOrMore>
3180	    </define>
3181	    <!--
3182	    *************************************************************
3183	    TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
3184	    -  RFC4575 -
3185	    *************************************************************
3186	       -->
3187	    <!--
3188	           WILDCARD FOR EVENT-PACKAGE NAMESPACE
3189	       -->
3190	    <define name="conference-info-urn">
3191	     <element>
3192	      <anyName>
3193	       <except>

3195	      <nsName ns="urn:ietf:params:xml:ns:conference-info"/>
3196	        <nsName ns=""/>
3197	       </except>
3198	      </anyName>
3199	      <mixed>
3200	      <zeroOrMore>
3201	        <choice>
3202	         <attribute>
3203	          <anyName/>
3204	         </attribute>
3205	         <ref name="conference-info-urn"/>
3206	        </choice>
3207	       </zeroOrMore>
3208	      </mixed>
3209	     </element>
3210	    </define>

3212	    <!--
3213	           DEFINITION OF ENDPOINT STATUS TYPE
3214	       -->
3215	    <define name="media-status-type">
3216	     <choice>
3217	      <value>recvonly</value>
3218	      <value>sendonly</value>
3219	      <value>sendrecv</value>
3220	      <value>inactive</value>
3221	      <text/>
3222	     </choice>
3223	    </define>
3224	    <!--
3225	           ENDPOINT STATUS TYPE
3226	       -->
3227	    <define name="endpoint-status-type">
3228	     <choice>
3229	      <value>pending</value>
3230	      <value>dialing-out</value>
3231	      <value>dialing-in</value>
3232	      <value>alerting</value>
3233	      <value>on-hold</value>
3234	      <value>connected</value>
3235	      <value>muted-via-focus</value>
3236	      <value>disconnecting</value>
3237	      <value>disconnected</value>
3238	      <text/>
3239	     </choice>
3240	    </define>
3241	    <!--
3242	           JOINING TYPE

3244	       -->
3245	    <define name="joining-type">
3246	     <choice>
3247	      <value>dialed-in</value>
3248	      <value>dialed-out</value>
3249	      <value>focus-owner</value>
3250	      <text/>
3251	     </choice>
3252	    </define>
3253	    <!--
3254	           DISCONNECTION TYPE
3255	       -->
3256	    <define name="disconnection-type">
3257	     <choice>
3258	      <value>departed</value>
3259	      <value>booted</value>
3260	      <value>failed</value>
3261	      <value>busy</value>
3262	      <text/>
3263	     </choice>
3264	    </define>

3266	   </grammar>

3268	Authors' Addresses

3270	   Oscar Novo
3271	   Ericsson
3272	   Hirsalantie 11
3273	   Jorvas  02420
3274	   Finland

3276	   Email: Oscar.Novo@ericsson.com

3278	   Gonzalo Camarillo
3279	   Ericsson
3280	   Hirsalantie 11
3281	   Jorvas  02420
3282	   Finland

3284	   Email: Gonzalo.Camarillo@ericsson.com
3285	   David P. Morgan
3286	   Fidelity Investments
3287	   82 Devonshire St, MZ V3C
3288	   Boston, MA  02109-3614
3289	   USA

3291	   Email: Dave.Morgan@fmr.com

3293	   Roni Even
3294	   Polycom
3295	   94 Derech Em Hamoshavot
3296	   Petach Tikva  49130
3297	   Israel

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

3301	Full Copyright Statement

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

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

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

3317	Intellectual Property

3319	   The IETF takes no position regarding the validity or scope of any
3320	   Intellectual Property Rights or other rights that might be claimed to
3321	   pertain to the implementation or use of the technology described in
3322	   this document or the extent to which any license under such rights
3323	   might or might not be available; nor does it represent that it has
3324	   made any independent effort to identify any such rights.  Information
3325	   on the procedures with respect to rights in RFC documents can be
3326	   found in BCP 78 and BCP 79.

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

3335	   The IETF invites any interested party to bring to its attention any
3336	   copyrights, patents or patent applications, or other proprietary
3337	   rights that may cover technology that may be required to implement
3338	   this standard.  Please address the information to the IETF at
3339	   ietf-ipr@ietf.org.

3341	Acknowledgment

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