idnits 2.17.1 

draft-ietf-xcon-common-data-model-11.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 3425.

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

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

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


  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 (June 10, 2008) is 5792 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)

  ** Obsolete normative reference: RFC 4582 (Obsoleted by RFC 8855)

  ** Obsolete normative reference: RFC 4583 (Obsoleted by RFC 8856)

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


     Summary: 4 errors (**), 0 flaws (~~), 1 warning (==), 9 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: December 12, 2008                                     D. Morgan
6	                                                    Fidelity Investments
7	                                                                 R. Even
8	                                                                 Polycom
9	                                                           June 10, 2008

11	 Conference Information Data Model for Centralized Conferencing (XCON)
12	                draft-ietf-xcon-common-data-model-11.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 December 12, 2008.

39	Abstract

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

49	Table of Contents

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

122	1.  Introduction

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

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

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

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

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

209	                 Figure 1: Conference Server Architecture

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

222	2.  Terminology

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

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

234	3.  Overview

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

246	3.1.  Data Model Format

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

253	3.2.  Data Model Namespace

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

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

261	3.3.  The Conference Object Identifier

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

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

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

307	                    Figure 2: Conference Object Mapping

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

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

333	3.3.1.  Conference Object URI Definition

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

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

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

341	3.4.  Data Model Structure

343	   The information in this data model is structured in the following
344	   manner.  All the information related to a conference is contained in
345	   a <conference-info> element.  The <conference-info> element contains
346	   the following child elements:

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

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

373	4.  Data Model Definition

375	   The following non-normative diagram shows the structure of conference
376	   object documents.  The operator "!" preceding an element indicates
377	   that the element is mandatory in the data model.  The operator "*"
378	   following an element indicates that the element is introduced and
379	   defined in this document.  That is, elements without a "*" have
380	   already been defined in [RFC4575].

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

550	                      Figure 3: Non-normative diagram

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

555	4.1.  <conference-info>

557	   A conference object document begins with the root element tag
558	   <conference-info>, which is defined in [RFC4575].  The <conference-
559	   info> attributes are described in [RFC4575].  Note that the
560	   <conference-info> element does not have the attributes 'state' and
561	   'version' defined in [RFC4575] for this element because these
562	   attributes only apply to notification mechanisms.

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

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

575	4.2.  <conference-description>

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

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

588	4.2.1.  <language>

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

597	4.2.2.  <display-text>

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

601	4.2.3.  <subject>

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

605	4.2.4.  <free-text>

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

609	4.2.5.  <keywords>

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

613	4.2.6.  <allow-sidebars>

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

618	4.2.7.  <conference-time>

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

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

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

680	4.2.8.  <conf-uris>

682	   The <conf-uris> contains the identifiers to be used in order to
683	   access the conference by different signaling means.  This document
684	   describes a new element, <conference-password>.  This element
685	   contains the password(s) of the conference, for instance, PSTN
686	   conference will store the 'PIN code' in this element.  All the other
687	   <conf-uris> child element are described in section 5.3.1 of
688	   [RFC4575].  Future extensions to this schema may define new values
689	   and register them with IANA.

691	4.2.9.  <service-uris>

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

698	4.2.10.  <maximum-user-count>

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

705	4.2.11.  <available-media>

707	   The <available-media> has the 'label' attribute that is the media
708	   stream identifier assigned by the conferencing server.  The attribute
709	   'label' is described in [RFC4575], section 5.3.4.  The <available-
710	   media> element contains a sequence of <entry> child elements.  Each
711	   <entry> element contains the following child elements:

713	   o  The <type> element is described in section 5.3.4 of [RFC4575].
714	   o  The <display-text> element is described in section 5.3.4 of
715	      [RFC4575].
716	   o  The <status> element is described in section 5.3.4 of [RFC4575].
717	   o  The child element <mixing-mode> describes a default policy by
718	      which the mixer will build the outgoing stream from the incoming
719	      streams.  Note that this policy is different than the policy
720	      describing the floors for each media.  The <mixing-mode> child
721	      element MUST contain one and only one of the "Moderator-
722	      controlled", "FCFS", and "Automatic" values indicating the default
723	      algorithm to use with every media stream.  The "Moderator-
724	      controlled" value indicates that the moderator of the conference,
725	      controls the media stream policy.  The "FCFS" value indicates a
726	      'first-come-first-served' policy.
727	   o  The <codecs> element specifies the allowed codecs in the
728	      conference.  It has an attribute 'decision' that specifies if the
729	      focus decides the common codec automatically or needs the approval
730	      of the moderator of the conference ("automatic", "moderator-
731	      controlled").  The <codecs> element contains <codec> elements.  A
732	      <codec> element can have the attribute 'name' and 'policy'.  The
733	      'name' attribute is a codec identifier assigned by the
734	      conferencing server.  The 'policy' attribute contains the policy
735	      for that codec (allowed, or disallowed).  The <codec> element has
736	      the child element <subtype> which stores the codec's name.  The
737	      possible values of this element are the values of the 'subtype'
738	      column of the RTP Payload Format media types per [RFC4855] defined
739	      in IANA [IANA].  It is expected that future conferencing
740	      specifications will define corresponding schema extensions, as
741	      appropriate.
742	   o  The <controls> element contains the basic audio and video global
743	      control elements for a conference.  It is expected that for the
744	      majority of the basic conferences, these controls are sufficient.
745	      If the conference server wants to support more advanced controls,
746	      then it is recommended that an extension to the data model be
747	      used.  In the <controls> element the schema is extensible, hence
748	      new control types can be added in the future.  So moderator
749	      controls that affect all media output would go under the
750	      <available-media> element.  The following controls elements are
751	      defined for <controls>:

753	      *  The <mute> element is used in conjunction with an audio stream
754	         to cease transmission of associated media.  That means that for
755	         the entire duration where mute is applicable, all current and
756	         future participants of the conference are muted and will not
757	         receive any audio.  It has a "boolean" value.  If this control
758	         is not specified, access to the control is not available to the
759	         client.
760	      *  The <pause-video> element is used in conjunction with a video
761	         stream to cease transmission of associated media.  It has a
762	         "boolean" value.  If this control is not specified, the access
763	         to the control is not available to the client.
764	      *  The <gain> element is used in conjunction with a media output
765	         stream to indicate the amount of amplification of an audio
766	         stream.  The value is an integer number that ranges from -127
767	         to 127.  If this control is not specified, access to the
768	         control is not available to the client.
769	      *  The <video-layout> element is used in conjunction with a video
770	         stream to specify how the video streams (of participants) are
771	         viewed by each participant.  Only one layout type can be
772	         specified for each output stream.  If there are fewer
773	         participants than panels in the specified layout, then blanking
774	         (black screen) MAY be mixed into the stream on the behalf of
775	         the missing input streams.  If unspecified, the <video-layout>
776	         default type SHOULD be "single-view".  The <video-layout> types
777	         are as follows, although any number of custom layouts may be
778	         specified in future extensions:
779	         +  single-view: Only one stream is presented by the focus to
780	            all participants in one panel.
781	         +  dual-view: This dual view option will present the video
782	            side-by-side in 2 panels and not alter the aspect ratio of
783	            the streams.  This will require the focus to introduce
784	            blanking on parts of the overall image as viewed by the
785	            participants.
786	         +  dual-view-crop: This side-by-side layout option instructs
787	            the focus to alter the aspect ratio of the streams (alter-
788	            aspect-ratio=TRUE) so that blanking is not necessary.  The
789	            focus handles the cropping of the streams.
790	         +  dual-view-2x1: This layout option instructs the focus to
791	            place one stream above the other, in essence with two rows
792	            and one column.  In this option the aspect ratio is not
793	            altered and blanking is introduced.
794	         +  dual-view-2x1-crop: This layout option also instructs the
795	            focus to place one stream above the other, in essence with
796	            two rows and one column.  In this option the aspect ratio is
797	            altered and the video streams are cropped.
798	         +  quad-view: Four equal-sized panels in a 2x2 layout is
799	            presented by the focus to all participants.  Typically the
800	            aspect ratio of the streams are maintained (alter-aspect-
801	            ratio= FALSE).
802	         +  multiple-3x3: Nine equal-sized panels in a 3x3 layout is
803	            presented by the focus to all participants.  Typically the
804	            aspect ratio of the streams are preserved.
805	         +  multiple-4x4: Sixteen equal-sized panels in a 4x4 layout is
806	            presented by the focus to all participants.  Typically the
807	            aspect ratio of the streams are preserved.
808	         +  multiple-5x1: This option refers to a 5x1 layout where one
809	            panel will occupy 4/9 of the mixed video stream while the
810	            others will each occupy 1/9 of the stream.  Typically the
811	            aspect ratio of the streams is preserved.
812	         +  automatic: This option allows the focus to add panels as
813	            streams are added.

815	4.3.  <host-info>

817	   The <host-info> element contains information about the entity hosting
818	   the conference.  This information is set before conference
819	   activation, and is rarely changed during the conference lifetime.
820	   The <host-info> element and its child elements are described in
821	   [RFC4575], section 5.4.  Future extensions to the <host-info> element
822	   may define new values.

824	4.4.  <conference-state>

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

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

832	   The <allow-conference-event-subscription> element represents a
833	   boolean action.  If set to TRUE, the focus is instructed to allow the
834	   subscription to conference state events, such as RFC4575 'SIP Event
835	   Package for Conference State' [RFC4575].  If set to FALSE, the
836	   subscription to conference state events would be rejected.  If this
837	   element is undefined it has a default value of TRUE, causing the
838	   subscription to conference state events to be accepted.

840	4.4.2.  <user-count>

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

845	4.4.3.  <active>

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

849	4.4.4.  <locked>

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

853	4.5.  <floor-information>

855	   The <floor-information> element contains the <conference-ID>, <allow-
856	   floor-events>, <floor-request-handling>, and <conference-floor-
857	   policy> child elements.  Other elements from different namespaces MAY
858	   be present for the purposes of extensibility.  The absence of this
859	   element from an XML document indicates that the conference does not
860	   have a floor.

862	4.5.1.  <conference-ID>

864	   The <conference-ID> represents a conference instance within floor
865	   control.  When created within the conferencing system, the
866	   'conference-ID' can be represented by the unique conference object
867	   Identifier (XCON-URI).  When BFCP serves as the floor control
868	   protocol, the <conference-ID> is a 32-bit BFCP conference identifier
869	   defined in [RFC4582] section 5.1 and there is a 1:1 mapping to the
870	   XCON-URI.

872	4.5.2.  <allow-floor-events>

874	   The <allow-floor-events> element represents a boolean action.  If set
875	   to TRUE, the focus is instructed to accept the subscription to floor
876	   control events.  If set to FALSE, the focus is instructed to reject
877	   the subscription.  If this element is undefined, it has a default
878	   value of FALSE, causing the subscription to floor control events to
879	   be rejected.

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

889	4.5.3.  <floor-request-handling>

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

896	   o  "block": This action instructs the focus to deny the floor
897	      request.  This action is the default action taken in the absence
898	      of any other actions.
899	   o  "confirm": This action instructs the focus to allow the request.
900	      The focus then uses the defined floor algorithm to further allow
901	      or deny the floor.  The algorithms used are outside the scope of
902	      this document.

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

909	4.5.4.  <conference-floor-policy>

911	   The <conference-floor-policy> element has one or more <floor> child
912	   elements.  Every <floor> child elements has an attribute 'id' which
913	   uniquely identifies a floor or floors within a conference.  In the
914	   case of BFCP [RFC4582], the 'id' attribute corresponds to the
915	   floor-id identifier defined in [RFC4582] section 5.2.2.

917	   o  <media-label>: Every floor is identified for one or more mandatory
918	      <media-label> element.  If the <available-media> information is
919	      included in the conference document, the value of this element
920	      MUST be equal to the 'label' value of the corresponding media
921	      stream <entry> in the <available-media> container.  The number of
922	      those elements indicates how many floors the conference can have.
923	      A floor can be used for one or more media types;
924	   o  <algorithm>: A floor can be controlled using many algorithms; the
925	      mandatory <algorithm> element MUST be set to any of the
926	      "moderator-controlled", "FCFS" or "random" values indicating the
927	      algorithm.  The "Moderator-controlled" value indicates that the
928	      moderator of the conference controls the floor.  The "FCFS" value
929	      states for 'first-come-first-served' floor control.
930	   o  <max-floor-users>: The <max-floor-users> child element in the
931	      <floor> element is optional and, if present, dictates the maximum
932	      number of users who can have the floor at one time.
933	   o  <moderator-id>: The optional <moderator-id> indicates the 'User
934	      ID' of the moderator(s).  It MUST be set if the element
935	      <algorithm> is set to "Moderator-controlled" value.  When the
936	      floor is created within the conferencing system, the XCON-User
937	      identifier MAY be used as the moderator-id.  In the case of BFCP
938	      as the floor control protocol, the <moderator-id> is defined in
939	      [RFC4582] section 3.  Note that [RFC4582] refers to the moderator
940	      role as a 'floor chair'.

942	4.6.  <users>

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

954	4.6.1.  <join-handling>

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

976	4.6.2.  <user-admission-policy>

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

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

1000	4.6.3.  <allowed-users-list>

1002	   The <allowed-users-list> child element contains a list of user URIs
1003	   (e.g.  SIP URI, xcon-userid defined in Section 4.6.5), roles (defined
1004	   in Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus
1005	   uses to determine who can join the conference, who can be invited to
1006	   join a conference, or who the focus needs to "refer to" the
1007	   conference.  The <allowed-users-list> element includes zero or more
1008	   <target> child elements.  This child element includes the mandatory
1009	   'uri' attribute and the mandatory 'method' attribute.  The same 'uri'
1010	   attribute with different method values can appear in the list more
1011	   than once.

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

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

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

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

1041	   o  user: The <user> element stores the name, nickname, the conference
1042	      user identifier (XCON-USERID) and email address of a user.  It has
1043	      three attributes: 'name', 'nickname' and 'id' and an <email>
1044	      element.  Future extensions to this schema may define new elements
1045	      for the <user> element.

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

1050	4.6.4.  <deny-users-list>

1052	   The <deny-users-list> child element contains a list of user URIs
1053	   (e.g.  SIP URI, xcon-userid defined in Section 4.6.5), roles (defined
1054	   in Section 4.6.5.4), or domains (e.g.: *@example.com) that the focus
1055	   uses to determine who has been 'banned' from the conference.  Such
1056	   banned users are prevented from re-joining the chatroom until they
1057	   have been un-banned.

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

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

1067	   The attribute 'entity' contains a unique conference user identifier
1068	   (XCON-USERID) within the scope of a conferencing system.  The URI
1069	   format of this identifier is as follow:

1071	    XCON-USERID = "xcon-userid" ":" conf-user-id

1073	    conf-user-id = 1*(unreserved)

1075	   [unreserved is defined in RFC3986]

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

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

1105	                     Figure 4: Conference User Mapping

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

1113	4.6.5.1.  <display-text>

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

1118	4.6.5.2.  <associated-aors>

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

1123	4.6.5.3.  <provide-anonymity>

1125	   The <provide-anonymity> element provides anonymity to the user.  In
1126	   this case, the focus provides to the rest of the participants an
1127	   anonymous identity for that user, for example anonymousX, or it does
1128	   not provide any information for that user such that other users can
1129	   not see he is a participant in the conference.  This element only
1130	   affects the way the user information is provided to the other
1131	   participants.  The real information about the user is still stored in
1132	   the data model.  This can be achieved by using the <provide-
1133	   anonymity> element.  This element has three values: 'private', 'semi-
1134	   private' and 'hidden'.  The 'private' value specifies that this user
1135	   is completely anonymous in the conference. 'semi-private' value
1136	   specifies that this user is anonymous to all users with equal or
1137	   lesser permissions in the conference. 'hidden' value specifies that
1138	   other users can not see this participant 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	   [RFC5239], the Conference Object is a logical representation of a
1265	   conference instance.  The conference information schema contains core
1266	   information that is utilized in any conference.  It also contains the
1267	   variable information part of the Conference Object.

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

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

1277	   start = element conference-info { conference-type }

1279	   # CONFERENCE TYPE

1281	   conference-type =
1282	     attribute entity { text },
1283	     anyAttribute,
1284	     conference-description-type,
1285	     element language { xsd:language }?,
1286	     element host-info { conference-info-urn* }?,
1287	     element conference-state { conference-state-type }?,
1288	     element floor-information { floor-information-type }?,
1289	     element users { users-type },
1290	     element sidebars-by-ref { sidebars-by-ref-type }?,
1291	     element sidebars-by-val { sidebars-by-val-type }?,
1292	     anyElement*

1294	   # CONFERENCE DESCRIPTION TYPE

1296	   conference-description-type =
1297	     element conference-description {
1298	       attribute lang { xsd:language }?,
1299	       anyAttribute,
1300	       element display-text { text }?,
1301	       element subject { text }?,
1302	       element free-text { text }?,
1303	       element keywords {
1304	         list { xsd:string* }
1305	       }?,
1306	       element allow-sidebars { xsd:boolean }?,
1307	       element conference-time { conferencetime-type }?,
1308	       element conf-uris {
1309	         (element conference-password { text }*,
1310	          conference-info-urn)*
1311	       }?,
1312	       element service-uris { conference-info-urn* }?,
1313	       element maximum-user-count { xsd:int }?,
1314	       element available-media { conference-media-type }?,
1315	       anyElement*
1316	     }

1318	   # CONFERENCE TIME
1319	   conferencetime-type =
1320	     anyAttribute,
1321	     element entry {
1322	       element base { text }?,
1323	       element mixing-start-offset {
1324	         xsd:dateTime { pattern = ".+T.+Z.*" },
1325	         attribute required-participant { single-role-type },
1326	         anyAttribute
1327	       }?,
1328	       element mixing-end-offset {
1329	         xsd:dateTime { pattern = ".+T.+Z.*" },
1330	         attribute required-participant { single-role-type },
1331	         anyAttribute
1332	       }?,
1333	       element can-join-after-offset {
1334	         xsd:dateTime { pattern = ".+T.+Z.*" }
1335	       }?,
1336	       element must-join-before-offset {
1337	         xsd:dateTime { pattern = ".+T.+Z.*" }
1338	       }?,
1339	       element notify-end-of-conference { xsd:int }?,
1340	       element allowed-extend-mixing-end-offset { xsd:boolean }?,
1341	       anyElement*
1342	     }*,
1343	     anyElement*

1345	   # CONFERENCE MEDIA TYPE

1347	   conference-media-type =
1348	     anyAttribute,
1349	     element entry { conference-medium-type }*,
1350	     anyElement*

1352	   # CONFERENCE MEDIUM TYPE

1354	   conference-medium-type =
1355	     attribute label { text },
1356	     anyAttribute,
1357	     element display-text { text }?,
1358	     element type { text }?,
1359	     element status { media-status-type }?,
1360	     element mixing-mode { mix-mode-type }?,
1361	     element codecs { codecs-type }?,
1362	     element controls { control-type }?,
1363	     anyElement*

1365	   # MIX MODE TYPE
1366	   mix-mode-type =
1367	     xsd:string "moderator-controlled"
1368	     | xsd:string "FCFS"
1369	     | xsd:string "automatic"
1370	     | text

1372	   # CODECS TYPE

1374	   codecs-type =
1375	     attribute decision { decision-type },
1376	     anyAttribute,
1377	     element codec { codec-type }*,
1378	     anyElement*

1380	   # CODEC TYPE

1382	   codec-type =
1383	     attribute name { text },
1384	     attribute policy { policy-type },
1385	     anyAttribute,
1386	     element subtype { text }?,
1387	     conference-info-urn*

1389	   # DECISION TYPE

1391	   decision-type =
1392	     xsd:string "automatic" | xsd:string "moderator-controlled" | text

1394	   # POLICY TYPE

1396	   policy-type = xsd:string "allowed" | xsd:string "disallowed" | text

1398	   # CONTROL TYPE

1400	   control-type =
1401	     anyAttribute,
1402	     (element mute { xsd:boolean },
1403	      element pause-video { xsd:boolean },
1404	      element gain {
1405	        xsd:int { minInclusive = "-127" maxInclusive = "127" }
1406	      },
1407	      element video-layout {
1408	        xsd:string "single-view"
1409	        | xsd:string "dual-view"
1410	        | xsd:string "dual-view-crop"
1411	        | xsd:string "dual-view-2x1"
1412	        | xsd:string "dual-view-2x1-crop"
1413	        | xsd:string "quad-view"
1414	        | xsd:string "multiple-3x3"
1415	        | xsd:string "multiple-4x4"
1416	        | xsd:string "multiple-5x1"
1417	        | xsd:string "automatic"
1418	        | text
1419	      },
1420	      anyElement*)*

1422	   # CONFERENCE STATE TYPE

1424	   conference-state-type =
1425	     anyAttribute,
1426	     element allow-conference-event-subscription { xsd:boolean }?,
1427	     element user-count { xsd:unsignedInt }?,
1428	     element active { xsd:boolean }?,
1429	     element locked { xsd:boolean }?,
1430	     anyElement*

1432	   # FLOOR INFORMATION TYPE

1434	   floor-information-type =
1435	     anyAttribute,
1436	     (element conference-ID { xsd:unsignedLong },
1437	      element allow-floor-events { xsd:boolean },
1438	      element floor-request-handling { floor-request-type },
1439	      element conference-floor-policy { conference-floor-policy },
1440	      anyElement*)*

1442	   # FLOOR REQUEST TYPE

1444	   floor-request-type = xsd:string "block" | xsd:string "confirm" | text

1446	   # CONFERENCE FLOOR POLICY

1448	   conference-floor-policy =
1449	     anyAttribute,
1450	     element floor {
1451	       attribute id { text },
1452	       anyAttribute,
1453	       element media-label { xsd:nonNegativeInteger }+,
1454	       (element algorithm {
1455	          xsd:string "moderator-controlled"
1456	          | xsd:string "FCFS"
1457	          | xsd:string "random"
1458	          | text
1459	        },
1460	        element max-floor-users { xsd:nonNegativeInteger },
1461	        element moderator-id { text }*,
1462	        anyElement*)*
1463	     }+

1465	   # USERS TYPE

1467	   users-type =
1468	     anyAttribute,
1469	     element join-handling { join-handling-type }?,
1470	     element user-admission-policy { user-admission-policy-type }?,
1471	     element allowed-users-list { UserList }?,
1472	     element deny-users-list { deny-user-list }?,
1473	     element user { user-type }*,
1474	     anyElement*

1476	   # USERS ADMISSION POLICY

1478	   user-admission-policy-type =
1479	     xsd:string "closedAuthenticated"
1480	     | xsd:string "openAuthenticated"
1481	     | xsd:string "anonymous"
1482	     | text

1484	   # JOIN HANDLING TYPE

1486	   join-handling-type =
1487	     xsd:string "block"
1488	     | xsd:string "confirm"
1489	     | xsd:string "allow"
1490	     | xsd:string "authenticate"
1491	     | xsd:string "directed-operator"
1492	     | text

1494	   # DENYUSERLIST

1496	   deny-user-list =
1497	     anyAttribute,
1498	     element target {
1499	       attribute uri { xsd:anyURI },
1500	       anyAttribute
1501	     }*,
1502	     anyElement*

1504	   # USERLIST

1506	   UserList =
1507	     anyAttribute,
1508	     element target { target-type }*,
1509	     anyElement*,
1510	     element persistent-list {
1511	       element user {
1512	         attribute name { text },
1513	         attribute nickname { text },
1514	         attribute id { text },
1515	         anyAttribute,
1516	         element e-mail { text }*
1517	       }*,
1518	       anyElement
1519	     }?

1521	   # TARGET TYPE

1523	   target-type =
1524	     attribute uri { xsd:anyURI },
1525	     attribute method { method-type },
1526	     anyAttribute

1528	   # METHOD TYPE

1530	   method-type =
1531	     xsd:string "dial-in"
1532	     | xsd:string "dial-out"
1533	     | xsd:string "refer"
1534	     | text

1536	   # USER TYPE

1538	   user-type =
1539	     attribute entity { xsd:anyURI },
1540	     anyAttribute,
1541	     element display-text { text }?,
1542	     element associated-aors { conference-info-urn* }?,
1543	     element provide-anonymity {
1544	       "private" | "semi-private" | "hidden" | text
1545	     }?,
1546	     element roles { single-role-type }?,
1547	     element languages {
1548	       list { xsd:language }
1549	     }?,
1550	     element cascaded-focus { xsd:anyURI }?,
1551	     element allow-refer-users-dynamically { xsd:boolean }?,
1552	     element allow-invite-users-dynamically { xsd:boolean }?,
1553	     element allow-remove-users-dynamically { xsd:boolean }?,
1554	     element endpoint { endpoint-type }*,
1555	     anyElement*

1557	   # ENDPOINT TYPE
1558	   endpoint-type =
1559	     attribute entity { text },
1560	     anyAttribute,
1561	     element display-text { text }?,
1562	     element referred { conference-info-urn* }?,
1563	     element status { endpoint-status-type }?,
1564	     element joining-method { joining-type }?,
1565	     element joining-info { conference-info-urn* }?,
1566	     element disconnection-method { disconnection-type }?,
1567	     element disconnection-info { conference-info-urn* }?,
1568	     element media { media-type }*,
1569	     element floor {
1570	       attribute id { text },
1571	       anyAttribute,
1572	       xsd:boolean
1573	     }*,
1574	     element call-info { conference-info-urn* }?,
1575	     anyElement*

1577	   # MEDIA TYPE

1579	   media-type =
1580	     attribute id { xsd:int },
1581	     anyAttribute,
1582	     element display-text { text }?,
1583	     element type { text }?,
1584	     element label { text }?,
1585	     element src-id { text }?,
1586	     element status { media-status-type }?,
1587	     element to-mixer { mixer-type }?,
1588	     element from-mixer { mixer-type }?,
1589	     anyElement*

1591	   # MIXER TYPE

1593	   mixer-type =
1594	     anyAttribute,
1595	     element controls { control-type }?,
1596	     anyElement*

1598	   # SIDEBARS-BY-REF TYPE

1600	   sidebars-by-ref-type =
1601	     anyAttribute,
1602	     element entry { conference-info-urn* }*,
1603	     anyElement*

1605	   # SIDEBARS-BY-VAL TYPE
1606	   sidebars-by-val-type =
1607	     anyAttribute,
1608	     element entry { conference-type }*,
1609	     anyElement*

1611	   # SINGLE ROLE TYPE

1613	   single-role-type =
1614	     xsd:string "administrator"
1615	     | xsd:string "moderator"
1616	     | xsd:string "user"
1617	     | xsd:string "participant"
1618	     | xsd:string "observer"
1619	     | xsd:string "none"
1620	     | text

1622	   # *********************************
1623	   # EXTENSIBILITY OF THE SCHEMA
1624	   # *********************************

1626	   # EXTENSIBILITY ELEMENTS

1628	   anyElement =
1629	     element * {
1630	       (attribute * { text }
1631	        | text
1632	        | anyElement)*
1633	     }

1635	   # EXTENSIBILITY ATTRIBUTES

1637	   anyAttribute =
1638	     attribute * - (entity
1639	                    | lang
1640	                    | required-participant
1641	                    | label
1642	                    | decision
1643	                    | name
1644	                    | policy
1645	                    | uri
1646	                    | method
1647	                    | id
1648	                    | local:*
1649	                    | ns2:*) { text }*

1651	   # *************************************************************
1652	   # TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
1653	   # -  RFC4575 -
1654	   # *************************************************************

1656	   # WILDCARD FOR EVENT-PACKAGE NAMESPACE

1658	   conference-info-urn =
1659	     element * - (ns1:* | local:*) {
1660	       mixed {
1661	         (attribute * { text }
1662	          | conference-info-urn)*
1663	       }
1664	     }

1666	   # DEFINITION OF ENDPOINT STATUS TYPE

1668	   media-status-type =
1669	     "recvonly" | "sendonly" | "sendrecv" | "inactive" | text

1671	   # ENDPOINT STATUS TYPE

1673	   endpoint-status-type =
1674	     "pending"
1675	     | "dialing-out"
1676	     | "dialing-in"
1677	     | "alerting"
1678	     | "on-hold"
1679	     | "connected"
1680	     | "muted-via-focus"
1681	     | "disconnecting"
1682	     | "disconnected"
1683	     | text

1685	   # JOINING TYPE

1687	   joining-type = "dialed-in" | "dialed-out" | "focus-owner" | text

1689	   # DISCONNECTION TYPE

1691	   disconnection-type = "departed" | "booted" | "failed" | "busy" | text

1693	6.  XML Schema Extensibility

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

1704	   Elements or attributes from unknown namespaces MUST be ignored.

1706	7.  XML Example

1708	   The following is an example of a conference information document.
1709	   The conference starts on October 17, 2007, at 10:30 AM in New York
1710	   City and finishes the same day at 12:30 PM every week.  In this
1711	   example, there are currently 3 participants in a conference, one
1712	   administrator, one moderator, and one participant.  Sidebars are
1713	   allowed in this conference and ,consequently, there is one sidebar in
1714	   the conference.  In addition, Alice and Carol are using a floor in
1715	   the main conference to manage the audio and video resources.  At the
1716	   moment, Alice is assigned to use the floor.

1718	 <?xml version="1.0" encoding="UTF-8"?>
1719	   <conference-info xmlns="urn:ietf:params:xml:ns:xcon-conference-info"
1720	       entity="conference123@example.com">
1721	       <!--
1722	           CONFERENCE DESCRIPTION
1723	       -->

1725	       <conference-description lang="en-us">
1726	           <language>En-us</language>
1727	           <display-text>Discussion of Formula-1 racing</display-text>
1728	           <subject>Sports:Formula-1</subject>
1729	           <free-text>This is a conference example</free-text>
1730	           <keywords>Formula-1, cars</keywords>
1731	           <allow-sidebars>true</allow-sidebars>
1732	           <!--
1733	           CONFERENCE TIME
1734	           -->
1735	           <conference-time>
1736	               <entry>
1737	                   <base>BEGIN:VCALENDAR
1738	 PRODID:-//LlamaSpinner Inc.//NONSGML CamelCall//EN
1739	 VERSION:2.0
1740	 BEGIN:VEVENT
1741	 DTSTAMP:20071003T140728Z
1742	 UID:20071003T140728Z-345FDA-carol@example.com
1743	 ORGANIZER:MAILTO:carol@example.com
1744	 DTSTART:20071017T143000Z
1745	 RRULE:FREQ=WEEKLY
1746	 DTEND:20071217T163000Z
1747	 END:VEVENT
1748	 END:VCALENDAR</base>
1749	                   <mixing-start-offset required-participant="moderator"
1750	                      > 2007-10-17T14:29:00Z</mixing-start-offset>
1751	                   <mixing-end-offset required-participant="participant"
1752	                      > 2007-10-17T16:31:00Z</mixing-end-offset>
1753	                   <must-join-before-offset
1754	                      > 2007-10-17T15:30:00Z</must-join-before-offset>
1755	               </entry>
1756	           </conference-time>
1757	           <!--
1758	           CONFERENCE UNIQUE IDENTIFIERS
1759	           -->
1760	           <conf-uris>
1761	               <entry>
1762	                   <uri>tel:+3585671234</uri>
1763	                   <display-text>Conference Bridge</display-text>
1764	                   <purpose>participation</purpose>
1765	                   <conference-password>5678</conference-password>
1766	               </entry>
1767	               <entry>
1768	                   <uri>http://www.example.com/live.ram</uri>
1769	                   <purpose>streaming</purpose>
1770	               </entry>
1771	           </conf-uris>
1772	           <!--
1773	             SERVICE URIS
1774	           -->
1775	           <service-uris>
1776	               <entry>
1777	                   <uri>http://www.example.com/formula1/</uri>
1778	                   <purpose>web-page</purpose>
1779	               </entry>
1780	           </service-uris>
1781	           <!--
1782	             MAXIMUM USER COUNT
1783	           -->
1784	           <maximum-user-count>50</maximum-user-count>
1785	           <!--
1786	             AVAILABLE MEDIA
1787	           -->
1788	           <available-media>
1789	               <entry label="10234">
1790	                   <display-text>main audio</display-text>
1791	                   <type>audio</type>
1792	                   <status>sendrecv</status>
1793	                   <mixing-mode>automatic</mixing-mode>
1794	                   <codecs decision="automatic">
1795	                       <codec name="122" policy="allowed"/>

1797	                          <subtype>PCMU</subtype>
1798	                   </codecs>
1799	                   <controls>
1800	                       <mute>true</mute>
1801	                       <gain>50</gain>
1802	                   </controls>
1803	               </entry>
1804	               <entry label="10235">
1805	                   <display-text>main video</display-text>
1806	                   <type>video</type>
1807	                   <status>sendrecv</status>
1808	                   <mixing-mode>automatic</mixing-mode>
1809	                   <codecs decision="automatic">
1810	                       <codec name="123" policy="allowed"/>

1812	                          <subtype>H.263</subtype>
1813	                   </codecs>
1814	                   <controls>
1815	                       <video-layout>single-view</video-layout>
1816	                   </controls>
1817	               </entry>
1818	           </available-media>
1819	       </conference-description>
1820	       <!--
1821	           HOST INFO
1822	         -->
1823	       <host-info>
1824	           <display-text>Formula1</display-text>
1825	           <web-page>http://www.example.com/formula1/</web-page>
1826	           <uris>
1827	               <entry>
1828	                   <uri>sip:alice@example.com</uri>
1829	               </entry>
1830	               <entry>
1831	                   <uri>sip:carol@example.com</uri>
1832	               </entry>
1833	           </uris>
1834	       </host-info>
1835	       <!--
1836	           CONFERENCE STATE
1837	         -->
1838	       <conference-state>
1839	           <allow-conference-event-subscription
1840	             >true</allow-conference-event-subscription>
1841	           <user-count>3</user-count>
1842	           <active>true</active>
1843	           <locked>false</locked>
1844	       </conference-state>
1845	       <!--
1846	           FLOOR INFORMATION
1847	         -->
1848	       <floor-information>
1849	           <conference-ID>567</conference-ID>
1850	           <allow-floor-events>true</allow-floor-events>
1851	           <floor-request-handling>confirm</floor-request-handling>
1852	           <conference-floor-policy>
1853	               <floor id="345">
1854	                   <media-label>10234</media-label>
1855	                   <media-label>10235</media-label>
1856	                   <algorithm>moderator-controlled</algorithm>
1857	                   <max-floor-users>1</max-floor-users>
1858	                   <moderator-id>234</moderator-id>
1859	               </floor>
1860	           </conference-floor-policy>
1861	       </floor-information>
1862	       <!--
1863	           USERS
1864	         -->
1865	       <users>
1866	           <join-handling>allow</join-handling>
1867	           <user-admission-policy
1868	              >openAuthenticated</user-admission-policy>
1869	           <!--
1870	            ALLOWED USERS LIST
1871	           -->
1872	           <allowed-users-list>
1873	               <target uri="sip:bob@example.com" method="dial-out"/>
1874	               <target uri="sip:alice@example.com" method="dial-out"/>
1875	               <target uri="sip:carol@example.com" method="dial-out"/>
1876	               <target uri="sip:john@example.com" method="refer"/>
1877	           </allowed-users-list>
1878	           <!--
1879	            DENY USERS LIST
1880	           -->
1881	           <deny-users-list>
1882	               <target uri="sip:charlie@example.com"/>
1883	           </deny-users-list>

1885	           <!--
1886	             USER BOB
1887	           -->

1889	           <user entity="bob534">
1890	               <display-text>Bob Hoskins</display-text>
1891	               <associated-aors>
1892	                   <entry>
1893	                       <uri>mailto:bob@example.com</uri>
1894	                       <display-text>email</display-text>
1895	                   </entry>
1896	               </associated-aors>
1897	               <provide-anonymity>semi-private</provide-anonymity>
1898	               <roles>
1899	                   <entry>participant</entry>
1900	               </roles>
1901	               <languages>en-us</languages>
1902	               <allow-refer-users-dynamically
1903	                   >false</allow-refer-users-dynamically>
1904	               <allow-invite-users-dynamically
1905	                   >false</allow-invite-users-dynamically>
1906	               <allow-remove-users-dynamically
1907	                   >false</allow-remove-users-dynamically>
1908	               <!--
1909	                   ENDPOINTS
1910	               -->
1911	               <endpoint entity="sip:bob@example.com">
1912	                   <display-text>Bob's Laptop</display-text>
1913	                   <referred>
1914	                       <when>2007-10-17T14:00:00Z</when>
1915	                       <reason>expert required</reason>
1916	                       <by>sip:alice@example.com</by>
1917	                   </referred>
1918	                   <status>connected</status>
1919	                   <joining-method>dialed-out</joining-method>
1920	                   <joining-info>
1921	                       <when>2007-10-17T14:00:00Z</when>
1922	                       <reason>invitation</reason>
1923	                       <by>sip:alice@example.com</by>
1924	                   </joining-info>

1926	                   <!--
1927	                       MEDIA
1928	                   -->
1929	                   <media id="1">
1930	                       <type>video</type>
1931	                       <label>10235</label>
1932	                       <src-id>432424</src-id>
1933	                       <status>sendrecv</status>
1934	                          <to-mixer name="VideoIn">
1935	                            <controls>
1936	                               <video-layout
1937	                                  >single-view</video-layout>
1938	                            </controls>

1940	                          </to-mixer>
1941	                   </media>
1942	                   <!--
1943	                       CALL INFO
1944	                   -->
1945	                   <call-info>
1946	                       <sip>
1947	                           <display-text>full info</display-text>
1948	                           <call-id>hsjh8980vhsb78</call-id>
1949	                           <from-tag>vav738dvbs</from-tag>
1950	                           <to-tag>8954jgjg8432</to-tag>
1951	                       </sip>
1952	                   </call-info>
1953	               </endpoint>
1954	           </user>

1956	           <!--
1957	               USER ALICE
1958	           -->

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

2024	                   <!--
2025	                       CALL INFO
2026	                   -->
2027	                   <call-info>
2028	                       <sip>
2029	                           <display-text>full info</display-text>
2030	                           <call-id>truy45469123478</call-id>
2031	                           <from-tag>asd456cbgt</from-tag>
2032	                           <to-tag>3456jgjg1234</to-tag>
2033	                       </sip>
2034	                   </call-info>
2035	               </endpoint>

2037	           </user>

2039	           <!--
2040	                  USER CAROL
2041	           -->

2043	           <user entity="carol233">
2044	               <display-text>Carol More</display-text>
2045	               <associated-aors>
2046	                   <entry>
2047	                       <uri>mailto:carol@example.com</uri>
2048	                       <display-text>email</display-text>
2049	                   </entry>
2050	               </associated-aors>
2051	               <provide-anonymity>private</provide-anonymity>
2052	               <roles>
2053	                   <entry>administrator</entry>
2054	               </roles>
2055	               <languages>en-us</languages>
2056	               <allow-refer-users-dynamically
2057	                   >true</allow-refer-users-dynamically>
2058	               <allow-invite-users-dynamically
2059	                   >true</allow-invite-users-dynamically>
2060	               <allow-remove-users-dynamically
2061	                   >true</allow-remove-users-dynamically>
2062	               <!--
2063	                   ENDPOINTS
2064	               -->
2065	               <endpoint entity="sip:carol@example.com">
2066	                   <display-text>Carol's Computer</display-text>
2067	                   <status>connected</status>
2068	                   <joining-method>dialed-in</joining-method>
2069	                   <joining-info>
2070	                       <when>2007-10-17T13:30:05Z</when>
2071	                       <reason>invitation</reason>
2072	                       <by>sip:conference@example.com</by>
2073	                   </joining-info>
2074	                   <!--
2075	                       MEDIA
2076	                   -->
2077	                   <media id="1">
2078	                       <type>video</type>
2079	                       <label>10235</label>
2080	                       <src-id>432424</src-id>
2081	                       <status>sendrecv</status>
2082	                       <to-mixer name="VideoIn">
2083	                        <controls>
2084	                           <video-layout
2085	                             >single-view</video-layout>
2086	                        </controls>
2087	                       </to-mixer>
2088	                   </media>
2089	                   <media id="2">
2090	                       <type>audio</type>
2091	                       <label>10234</label>
2092	                       <src-id>532535</src-id>
2093	                       <status>sendrecv</status>
2094	                       <to-mixer name="VideoIn">
2095	                         <controls>
2096	                           <gain>50</gain>
2097	                         </controls>
2098	                       </to-mixer>
2099	                       <from-mixer name="VideoOut">
2100	                         <controls>
2101	                           <gain>50</gain>
2102	                         </controls>
2103	                       </from-mixer>
2104	                   </media>
2105	                   <floor id="345">false</floor>

2107	                   <!--
2108	                       CALL INFO
2109	                   -->
2110	                   <call-info>
2111	                       <sip>
2112	                           <display-text>full info</display-text>
2113	                           <call-id>wevb12562321894</call-id>
2114	                           <from-tag>asw456wedf</from-tag>
2115	                           <to-tag>2365dfrt3497</to-tag>
2116	                       </sip>
2117	                   </call-info>
2118	               </endpoint>
2119	           </user>
2120	       </users>
2121	       <!--
2122	            SIDEBARS BY REFERENCE
2123	          -->
2124	       <sidebars-by-ref>
2125	           <entry>
2126	               <uri>conf223</uri>
2127	               <display-text>private with Bob</display-text>
2128	           </entry>
2129	       </sidebars-by-ref>
2130	       <!--
2131	            SIDEBARS BY VALUE
2132	          -->

2134	       <sidebars-by-val>
2135	           <entry entity="conf223">
2136	               <users>
2137	                   <user entity="bob534"/>
2138	                   <user entity="carol233"/>
2139	               </users>
2140	           </entry>
2141	       </sidebars-by-val>
2142	   </conference-info>

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

2149	8.  Security Considerations

2151	   There are numerous security considerations for this document.  This
2152	   section considers them.

2154	8.1.  Authentication

2156	   Different conferencing protocols will support different types of
2157	   authentication mechanisms.  Since a variety of signaling protocols
2158	   are possible, a variety of authentication mechanism may need to be
2159	   mapped from the different protocols.

2161	   Futhermore, users may use different namespaces to access to a
2162	   conference.  So a mapping database has to specify the acceptable
2163	   range of namespace for a user.  Doing so, a users will not access the
2164	   same conference twice using a different namespace.

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

2171	8.2.  Confidentiality

2173	   Participants of a conference may not want to reveal some private
2174	   information to other users.  The Conference Information Data Model
2175	   contains sensitive data which should not be analyzed or given to
2176	   anyone.  Confidentiality is provided through encryption.  Strong end-
2177	   to-end authentication and encryption can be done using public keys,
2178	   and end-to-end encryption can be done using private keys.  It is
2179	   RECOMMENDED that the protocols that manipulated the conference
2180	   information data model use a strong encryption for conference
2181	   information protection.

2183	8.3.  Integrity

2185	   A conferencing system may maintain a mapping database between the
2186	   conference object identifiers and the identifiers associated with
2187	   each of the complementary centralized conferencing protocols, as well
2188	   as, a mapping between the conference user identifiers and the
2189	   identifiers associated with each user in a conference.  This mapping
2190	   database contains sensitive data.  It is RECOMMENDED that the mapping
2191	   database has integrity when it is established, the integrity has to
2192	   be protected, and the database has to be maintained to ensure changes
2193	   in namespaces are accurately reflected.

2195	9.  IANA Considerations

2197	9.1.  Relax NG Schema Registration

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

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

2204	     Registrant Contact: IETF XCON working group,
2205	        <xcon@ietf.org>, Oscar Novo
2206	        <Oscar.Novo@ericsson.com>

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

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

2213	        and its last line is

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

2217	9.2.  XML Namespace Registration
2218	   This section registers a new XML namespace.

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

2222	      Registrant Contact: IETF XCON working group,
2223	         <xcon@ietf.org>, Oscar Novo
2224	         <Oscar.Novo@ericsson.com>

2226	       XML:

2228	         BEGIN
2229	         <?xml version="1.0"?>
2230	         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
2231	           "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
2232	         <html xmlns="http://www.w3.org/1999/xhtml">
2233	         <head>
2234	           <meta http-equiv="content-type"
2235	                 content="text/html;charset=iso-8859-1"/>
2236	           <title> Centralized Conferencing Namespace</title>
2237	         </head>
2238	         <body>
2239	           <h1>Namespace for Centralized Conferencing</h1>
2240	           <h2>urn:ietf:params:xml:ns:xcon-conference-info</h2>
2241	         <p>See <a href="[URL of published RFC]">RFCXXXX
2242	             [NOTE TO IANA/RFC-EDITOR:
2243	              Please replace XXXX with the RFC number of this
2244	             specification.]</a>.</p>
2245	         </body>
2246	         </html>
2247	         END

2249	9.3.  Conference Object Identifier Registration

2251	 The IANA is requested to register the following URI scheme
2252	 under the Permanent URI Schemes register.

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

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

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

2260	   [Note to the RFC Editor: replace xxxx with the number this RFC gets
2261	   assigned.]
2262	    Subject: Request for XCON-URI Registration
2263	    Person & email address to contact for further information:
2264	         Oscar Novo <oscar novo_at_ericsson.com>
2265	    Specification: RFC XXXX
2266	    Author/Change Controller: IESG
2267	    Comments:
2268	        Identifies the Conference

2270	9.4.  Conference User Identifier Registration

2272	   The IANA is requested to register the following URI scheme
2273	    under the Permanent URI Schemes register.

2275	    XCON-USERID = "xcon-userid" ":" conf-user-id  [ RFC xxxx ]

2277	    conf-user-id = 1*(unreserved)

2279	   unreserved is defined in RFC3986[RFC3986]

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

2284	    Subject: Request for XCON-USERID Registration
2285	    Person & email address to contact for further information:
2286	         Oscar Novo <oscar novo_at_ericsson.com>
2287	    Specification: RFC XXXX
2288	    Author/Change Controller: IESG
2289	    Comments:
2290	        Identifies the User in the conference

2292	10.  Acknowledgements

2294	   This document is really a distillation of many ideas discussed over a
2295	   long period of time.  These ideas were contributed by many different
2296	   drafts in the XCON working group and the SIPPING working group.  We
2297	   would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris
2298	   Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Aki
2299	   Niemi, Jari Urpilainen, Rohan Mahy, Jonathan Lennox, and Henning
2300	   Schulzrinne for their comments.  Also, we would like to thank Mary
2301	   Barnes, and Chris Boulton for letting us use the conference and user
2302	   identifier information of their xcon drafts.  Last but not least, we
2303	   would like to express our gratitude to all those reviewers for their
2304	   invaluable contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia
2305	   Castaldi, Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom
2306	   Houri, Pierre Tane, and Ben Campbell.

2308	11.  References

2310	11.1.  Normative References

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

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

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

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

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

2330	   [RFC5239]  Barnes, M., Boulton, C., and O. Levin, "A Framework for
2331	              Centralized Conferencing", RFC 5239, June 2008.

2333	11.2.  Informative References

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

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

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

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

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

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

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

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

2361	   [W3C.REC-xml-20001006]
2362	              Paoli, J., Bray, T., Maler, E., and C. Sperberg-McQueen,
2363	              "Extensible Markup Language (XML) 1.0 (Second Edition)",
2364	              World Wide Web Consortium FirstEdition REC-xml-20001006,
2365	              October 2000,
2366	              <http://www.w3.org/TR/2000/REC-xml-20001006>.

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

2370	      <grammar ns="urn:ietf:params:xml:ns:xcon-conference-info"
2371	       xmlns="http://relaxng.org/ns/structure/1.0"
2372	       xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
2373	       datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
2374	       <start>
2375	        <element name="conference-info">
2376	         <ref name="conference-type"/>
2377	        </element>
2378	       </start>
2379	       <!--
2380	              CONFERENCE TYPE
2381	          -->
2382	       <define name="conference-type">
2383	        <attribute name="entity">
2384	         <text/>
2385	        </attribute>
2386	        <ref name="anyAttribute"/>
2387	        <ref name="conference-description-type"/>
2388	        <optional>
2389	         <element name="language">
2390	          <data type="language"/>
2391	         </element>
2392	        </optional>
2393	        <optional>
2394	         <element name="host-info">
2395	           <zeroOrMore>
2396	            <ref name="conference-info-urn"/>
2397	           </zeroOrMore>

2399	         </element>
2400	        </optional>
2401	        <optional>
2402	        <element name="conference-state">
2403	          <ref name="conference-state-type"/>
2404	        </element>
2405	        </optional>
2406	        <optional>
2407	         <element name="floor-information">
2408	          <ref name="floor-information-type"/>
2409	         </element>
2410	        </optional>
2411	        <element name="users">
2412	         <ref name="users-type"/>
2413	        </element>
2414	        <optional>
2415	         <element name="sidebars-by-ref">
2416	          <ref name="sidebars-by-ref-type"/>
2417	         </element>
2418	        </optional>
2419	        <optional>
2420	         <element name="sidebars-by-val">
2421	          <ref name="sidebars-by-val-type"/>
2422	         </element>
2423	        </optional>
2424	        <zeroOrMore>
2425	         <ref name="anyElement"/>
2426	        </zeroOrMore>
2427	       </define>
2428	       <!--
2429	              CONFERENCE DESCRIPTION TYPE
2430	          -->
2431	       <define name="conference-description-type">
2432	        <element name="conference-description">
2433	         <optional>
2434	          <attribute name="lang">
2435	           <data type="language"/>
2436	          </attribute>
2437	         </optional>
2438	         <ref name="anyAttribute"/>
2439	         <optional>
2440	          <element name="display-text">
2441	           <text/>
2442	          </element>
2443	         </optional>
2444	         <optional>
2445	          <element name="subject">
2446	           <text/>

2448	          </element>
2449	         </optional>
2450	         <optional>
2451	          <element name="free-text">
2452	           <text/>
2453	          </element>
2454	         </optional>
2455	         <optional>
2456	          <element name="keywords">
2457	           <list>
2458	            <zeroOrMore>
2459	             <data type="string"/>
2460	            </zeroOrMore>
2461	           </list>
2462	          </element>
2463	         </optional>
2464	         <optional>
2465	          <element name="allow-sidebars">
2466	           <data type="boolean"/>
2467	          </element>
2468	         </optional>
2469	         <optional>
2470	          <element name="conference-time">
2471	           <ref name="conferencetime-type"/>
2472	          </element>
2473	         </optional>
2474	         <optional>
2475	          <element name="conf-uris">
2476	            <zeroOrMore>
2477	             <zeroOrMore>
2478	              <element name="conference-password">
2479	               <text/>
2480	              </element>
2481	              </zeroOrMore>
2482	             <ref name="conference-info-urn"/>
2483	            </zeroOrMore>
2484	          </element>
2485	         </optional>
2486	         <optional>
2487	          <element name="service-uris">
2488	            <zeroOrMore>
2489	             <ref name="conference-info-urn"/>
2490	            </zeroOrMore>
2491	          </element>
2492	         </optional>
2493	         <optional>
2494	          <element name="maximum-user-count">
2495	           <data type="int"/>

2497	          </element>
2498	         </optional>
2499	         <optional>
2500	          <element name="available-media">
2501	           <ref name="conference-media-type"/>
2502	          </element>
2503	          </optional>
2504	         <zeroOrMore>
2505	          <ref name="anyElement"/>
2506	         </zeroOrMore>
2507	        </element>
2508	       </define>
2509	       <!--
2510	              CONFERENCE TIME
2511	          -->
2512	       <define name="conferencetime-type">
2513	        <ref name="anyAttribute"/>
2514	        <zeroOrMore>
2515	         <element name="entry">
2516	          <optional>
2517	           <element name="base">
2518	            <text/>
2519	           </element>
2520	          </optional>
2521	          <optional>
2522	           <element name="mixing-start-offset">
2523	            <data type="dateTime">
2524	             <param name="pattern">.+T.+Z.*</param>
2525	            </data>
2526	            <attribute name="required-participant">
2527	             <ref name="single-role-type"/>
2528	            </attribute>
2529	            <ref name="anyAttribute"/>
2530	           </element>
2531	          </optional>
2532	          <optional>
2533	           <element name="mixing-end-offset">
2534	            <data type="dateTime">
2535	             <param name="pattern">.+T.+Z.*</param>
2536	            </data>
2537	            <attribute name="required-participant">
2538	             <ref name="single-role-type"/>
2539	            </attribute>
2540	            <ref name="anyAttribute"/>
2541	           </element>
2542	          </optional>
2543	          <optional>
2544	           <element name="can-join-after-offset">
2545	            <data type="dateTime">
2546	             <param name="pattern">.+T.+Z.*</param>
2547	            </data>
2548	           </element>
2549	          </optional>
2550	          <optional>
2551	           <element name="must-join-before-offset">
2552	            <data type="dateTime">
2553	             <param name="pattern">.+T.+Z.*</param>
2554	            </data>
2555	           </element>
2556	          </optional>
2557	          <optional>
2558	           <element name="notify-end-of-conference">
2559	            <data type="int"/>
2560	           </element>
2561	          </optional>
2562	          <optional>
2563	           <element name="allowed-extend-mixing-end-offset">
2564	            <data type="boolean"/>
2565	           </element>
2566	          </optional>
2567	          <zeroOrMore>
2568	           <ref name="anyElement"/>
2569	          </zeroOrMore>
2570	         </element>
2571	        </zeroOrMore>
2572	        <zeroOrMore>
2573	         <ref name="anyElement"/>
2574	        </zeroOrMore>
2575	       </define>

2577	       <!--
2578	              CONFERENCE MEDIA TYPE
2579	          -->
2580	       <define name="conference-media-type">
2581	        <ref name="anyAttribute"/>
2582	        <zeroOrMore>
2583	         <element name="entry">
2584	          <ref name="conference-medium-type"/>
2585	         </element>
2586	        </zeroOrMore>
2587	        <zeroOrMore>
2588	         <ref name="anyElement"/>
2589	        </zeroOrMore>
2590	       </define>
2591	       <!--
2592	              CONFERENCE MEDIUM TYPE

2594	          -->
2595	       <define name="conference-medium-type">
2596	        <attribute name="label">
2597	         <text/>
2598	        </attribute>
2599	        <ref name="anyAttribute"/>
2600	        <optional>
2601	         <element name="display-text">
2602	          <text/>
2603	         </element>
2604	        </optional>
2605	        <optional>
2606	         <element name="type">
2607	          <text/>
2608	         </element>
2609	        </optional>
2610	        <optional>
2611	         <element name="status">
2612	          <ref name="media-status-type"/>
2613	         </element>
2614	        </optional>
2615	        <optional>
2616	         <element name="mixing-mode">
2617	          <ref name="mix-mode-type"/>
2618	         </element>
2619	        </optional>
2620	        <optional>
2621	         <element name="codecs">
2622	          <ref name="codecs-type"/>
2623	         </element>
2624	        </optional>
2625	        <optional>
2626	         <element name="controls">
2627	          <ref name="control-type"/>
2628	         </element>
2629	        </optional>
2630	        <zeroOrMore>
2631	         <ref name="anyElement"/>
2632	        </zeroOrMore>
2633	       </define>
2634	       <!--
2635	              MIX MODE TYPE
2636	          -->
2637	       <define name="mix-mode-type">
2638	        <choice>
2639	         <value type="string">moderator-controlled</value>
2640	         <value type="string">FCFS</value>
2641	         <value type="string">automatic</value>
2642	         <text/>
2643	        </choice>
2644	       </define>
2645	       <!--
2646	              CODECS TYPE
2647	          -->
2648	       <define name="codecs-type">
2649	        <attribute name="decision">
2650	         <ref name="decision-type"/>
2651	        </attribute>
2652	        <ref name="anyAttribute"/>
2653	        <zeroOrMore>
2654	         <element name="codec">
2655	          <ref name="codec-type"/>
2656	         </element>
2657	        </zeroOrMore>
2658	        <zeroOrMore>
2659	         <ref name="anyElement"/>
2660	        </zeroOrMore>
2661	       </define>
2662	       <!--
2663	              CODEC TYPE
2664	          -->
2665	       <define name="codec-type">
2666	        <attribute name="name">
2667	         <text/>
2668	        </attribute>
2669	        <attribute name="policy">
2670	         <ref name="policy-type"/>
2671	        </attribute>
2672	        <ref name="anyAttribute"/>
2673	        <optional>
2674	         <element name="subtype">
2675	          <text/>
2676	         </element>
2677	        </optional>
2678	         <zeroOrMore>
2679	          <ref name="conference-info-urn"/>
2680	         </zeroOrMore>
2681	       </define>
2682	       <!--
2683	              DECISION TYPE
2684	          -->
2685	       <define name="decision-type">
2686	        <choice>
2687	         <value type="string">automatic</value>
2688	         <value type="string">moderator-controlled</value>
2689	         <text/>

2691	        </choice>
2692	       </define>
2693	       <!--
2694	              POLICY TYPE
2695	          -->
2696	       <define name="policy-type">
2697	        <choice>
2698	         <value type="string">allowed</value>
2699	         <value type="string">disallowed</value>
2700	         <text/>
2701	        </choice>
2702	       </define>
2703	       <!--
2704	              CONTROL TYPE
2705	          -->
2706	       <define name="control-type">
2707	        <ref name="anyAttribute"/>
2708	        <zeroOrMore>
2709	         <element name="mute">
2710	          <data type="boolean"/>
2711	         </element>
2712	         <element name="pause-video">
2713	          <data type="boolean"/>
2714	         </element>
2715	         <element name="gain">
2716	          <data type="int">
2717	           <param name="minInclusive">-127</param>
2718	           <param name="maxInclusive">127</param>
2719	          </data>
2720	         </element>
2721	         <element name="video-layout">
2722	          <choice>
2723	           <value type="string">single-view</value>
2724	           <value type="string">dual-view</value>
2725	           <value type="string">dual-view-crop</value>
2726	           <value type="string">dual-view-2x1</value>
2727	           <value type="string">dual-view-2x1-crop</value>
2728	           <value type="string">quad-view</value>
2729	           <value type="string">multiple-3x3</value>
2730	           <value type="string">multiple-4x4</value>
2731	           <value type="string">multiple-5x1</value>
2732	           <value type="string">automatic</value>
2733	           <text/>
2734	          </choice>
2735	         </element>
2736	         <zeroOrMore>

2738	          <ref name="anyElement"/>

2740	         </zeroOrMore>
2741	        </zeroOrMore>
2742	       </define>
2743	       <!--
2744	              CONFERENCE STATE TYPE
2745	          -->
2746	       <define name="conference-state-type">
2747	        <ref name="anyAttribute"/>
2748	        <optional>
2749	         <element name="allow-conference-event-subscription">
2750	          <data type="boolean"/>
2751	         </element>
2752	        </optional>
2753	        <optional>
2754	         <element name="user-count">
2755	          <data type="unsignedInt"/>
2756	         </element>
2757	        </optional>
2758	        <optional>
2759	         <element name="active">
2760	          <data type="boolean"/>
2761	         </element>
2762	        </optional>
2763	        <optional>
2764	         <element name="locked">
2765	          <data type="boolean"/>
2766	         </element>
2767	        </optional>
2768	        <zeroOrMore>
2769	         <ref name="anyElement"/>
2770	        </zeroOrMore>
2771	       </define>
2772	       <!--
2773	              FLOOR INFORMATION TYPE
2774	          -->
2775	       <define name="floor-information-type">
2776	        <ref name="anyAttribute"/>
2777	        <zeroOrMore>
2778	         <element name="conference-ID">
2779	          <data type="unsignedLong"/>
2780	         </element>
2781	         <element name="allow-floor-events">
2782	          <data type="boolean"/>
2783	         </element>
2784	         <element name="floor-request-handling">
2785	          <ref name="floor-request-type"/>
2786	         </element>
2787	         <element name="conference-floor-policy">
2788	          <ref name="conference-floor-policy"/>
2789	         </element>
2790	         <zeroOrMore>
2791	          <ref name="anyElement"/>
2792	         </zeroOrMore>
2793	        </zeroOrMore>
2794	       </define>
2795	       <!--
2796	              FLOOR REQUEST TYPE
2797	          -->
2798	       <define name="floor-request-type">
2799	        <choice>
2800	         <value type="string">block</value>
2801	         <value type="string">confirm</value>
2802	         <text/>
2803	        </choice>
2804	       </define>
2805	       <!--
2806	              CONFERENCE FLOOR POLICY
2807	          -->
2808	       <define name="conference-floor-policy">
2809	        <ref name="anyAttribute"/>
2810	        <oneOrMore>
2811	         <element name="floor">
2812	          <attribute name="id">
2813	           <text/>
2814	          </attribute>
2815	          <ref name="anyAttribute"/>
2816	          <oneOrMore>
2817	           <element name="media-label">
2818	            <data type="nonNegativeInteger"/>
2819	           </element>
2820	           </oneOrMore>
2821	           <zeroOrMore>
2822	           <element name="algorithm">
2823	            <choice>
2824	             <value type="string">moderator-controlled</value>
2825	             <value type="string">FCFS</value>
2826	             <value type="string">random</value>
2827	             <text/>
2828	            </choice>
2829	           </element>
2830	           <element name="max-floor-users">
2831	            <data type="nonNegativeInteger"/>
2832	           </element>
2833	           <zeroOrMore>
2834	           <element name="moderator-id">
2835	            <text/>
2836	           </element>
2837	            </zeroOrMore>
2838	           <zeroOrMore>
2839	            <ref name="anyElement"/>
2840	           </zeroOrMore>
2841	          </zeroOrMore>
2842	         </element>
2843	        </oneOrMore>
2844	       </define>
2845	       <!--
2846	              USERS TYPE
2847	          -->
2848	       <define name="users-type">
2849	        <ref name="anyAttribute"/>
2850	        <optional>
2851	         <element name="join-handling">
2852	          <ref name="join-handling-type"/>
2853	         </element>
2854	        </optional>
2855	        <optional>
2856	         <element name="user-admission-policy">
2857	          <ref name="user-admission-policy-type"/>
2858	         </element>
2859	        </optional>
2860	        <optional>
2861	         <element name="allowed-users-list">
2862	          <ref name="UserList"/>
2863	         </element>
2864	        </optional>
2865	        <optional>
2866	         <element name="deny-users-list">
2867	          <ref name="deny-user-list"/>
2868	         </element>
2869	        </optional>
2870	        <zeroOrMore>
2871	         <element name="user">
2872	          <ref name="user-type"/>
2873	         </element>
2874	        </zeroOrMore>
2875	        <zeroOrMore>
2876	         <ref name="anyElement"/>
2877	        </zeroOrMore>
2878	       </define>
2879	       <!--
2880	              USERS ADMISSION POLICY
2881	          -->
2882	       <define name="user-admission-policy-type">
2883	        <choice>
2884	         <value type="string">closedAuthenticated</value>

2886	         <value type="string">openAuthenticated</value>
2887	         <value type="string">anonymous</value>
2888	         <text/>
2889	        </choice>
2890	       </define>
2891	       <!--
2892	              JOIN HANDLING TYPE
2893	          -->
2894	       <define name="join-handling-type">
2895	        <choice>
2896	         <value type="string">block</value>
2897	         <value type="string">confirm</value>
2898	         <value type="string">allow</value>
2899	         <value type="string">authenticate</value>
2900	         <value type="string">directed-operator</value>
2901	         <text/>
2902	        </choice>
2903	       </define>

2905	       <!--
2906	        DENYUSERLIST
2907	       -->
2908	       <define name="deny-user-list">
2909	        <ref name="anyAttribute"/>
2910	        <zeroOrMore>
2911	         <element name="target">
2912	          <attribute name="uri">
2913	           <data type="anyURI"/>
2914	          </attribute>
2915	          <ref name="anyAttribute"/>
2916	         </element>
2917	        </zeroOrMore>
2918	        <zeroOrMore>
2919	         <ref name="anyElement"/>
2920	        </zeroOrMore>
2921	       </define>
2922	       <!--
2923	              USERLIST
2924	          -->
2925	       <define name="UserList">
2926	        <ref name="anyAttribute"/>
2927	        <zeroOrMore>
2928	         <element name="target">
2929	          <ref name="target-type"/>
2930	         </element>

2932	        </zeroOrMore>
2933	        <zeroOrMore>
2934	         <ref name="anyElement"/>

2936	        </zeroOrMore>
2937	        <optional>
2938	         <element name="persistent-list">
2939	          <zeroOrMore>
2940	           <element name="user">
2941	            <attribute name="name">
2942	            <text/>
2943	            </attribute>
2944	            <attribute name="nickname">
2945	             <text/>
2946	            </attribute>
2947	            <attribute name="id">
2948	             <text/>
2949	            </attribute>
2950	            <ref name="anyAttribute"/>
2951	          <zeroOrMore>
2952	            <element name="e-mail">
2953	             <text/>
2954	            </element>
2955	          </zeroOrMore>
2956	           </element>
2957	           </zeroOrMore>
2958	          <ref name="anyElement"/>
2959	         </element>
2960	        </optional>
2961	       </define>
2962	       <!--
2963	              TARGET TYPE
2964	          -->
2965	       <define name="target-type">
2966	        <attribute name="uri">
2967	         <data type="anyURI"/>
2968	        </attribute>
2969	        <attribute name="method">
2970	         <ref name="method-type"/>
2971	        </attribute>
2972	        <ref name="anyAttribute"/>
2973	       </define>
2974	       <!--
2975	              METHOD TYPE
2976	          -->
2977	       <define name="method-type">
2978	        <choice>
2979	         <value type="string">dial-in</value>
2980	         <value type="string">dial-out</value>
2981	         <value type="string">refer</value>
2982	         <text/>
2983	        </choice>

2985	       </define>
2986	       <!--
2987	              USER TYPE
2988	          -->
2989	       <define name="user-type">
2990	        <attribute name="entity">
2991	         <data type="anyURI"/>
2992	        </attribute>
2993	        <ref name="anyAttribute"/>
2994	        <optional>
2995	         <element name="display-text">
2996	          <text/>
2997	         </element>
2998	        </optional>
2999	        <optional>
3000	         <element name="associated-aors">
3001	          <zeroOrMore>
3002	           <ref name="conference-info-urn"/>
3003	          </zeroOrMore>
3004	         </element>
3005	        </optional>
3006	        <optional>
3007	         <element name="provide-anonymity">
3008	          <choice>
3009	           <value>private</value>
3010	           <value>semi-private</value>
3011	           <value>hidden</value>
3012	           <text/>
3013	           </choice>
3014	         </element>
3015	        </optional>
3016	        <optional>
3017	         <element name="roles">
3018	          <ref name="single-role-type"/>
3019	         </element>
3020	        </optional>
3021	        <optional>
3022	         <element name="languages">
3023	          <list>
3024	           <data type="language"/>
3025	          </list>
3026	         </element>
3027	        </optional>
3028	        <optional>
3029	         <element name="cascaded-focus">
3030	          <data type="anyURI"/>
3031	         </element>
3032	        </optional>

3034	        <optional>
3035	         <element name="allow-refer-users-dynamically">
3036	          <data type="boolean"/>
3037	         </element>
3038	        </optional>
3039	        <optional>
3040	         <element name="allow-invite-users-dynamically">
3041	          <data type="boolean"/>
3042	         </element>
3043	        </optional>
3044	        <optional>
3045	         <element name="allow-remove-users-dynamically">
3046	          <data type="boolean"/>
3047	         </element>
3048	        </optional>
3049	        <zeroOrMore>
3050	         <element name="endpoint">
3051	          <ref name="endpoint-type"/>
3052	         </element>
3053	        </zeroOrMore>
3054	        <zeroOrMore>
3055	         <ref name="anyElement"/>
3056	        </zeroOrMore>
3057	       </define>
3058	       <!--
3059	              ENDPOINT TYPE
3060	          -->
3061	       <define name="endpoint-type">
3062	        <attribute name="entity">
3063	         <text/>
3064	        </attribute>
3065	        <ref name="anyAttribute"/>
3066	        <optional>
3067	         <element name="display-text">
3068	          <text/>
3069	         </element>
3070	        </optional>
3071	        <optional>
3072	         <element name="referred">
3073	          <zeroOrMore>
3074	           <ref name="conference-info-urn"/>

3076	          </zeroOrMore>
3077	         </element>
3078	        </optional>
3079	        <optional>
3080	         <element name="status">
3081	          <ref name="endpoint-status-type"/>
3082	         </element>

3084	        </optional>
3085	        <optional>
3086	         <element name="joining-method">
3087	          <ref name="joining-type"/>
3088	         </element>
3089	        </optional>
3090	        <optional>
3091	         <element name="joining-info">
3092	          <zeroOrMore>
3093	           <ref name="conference-info-urn"/>
3094	          </zeroOrMore>
3095	         </element>
3096	        </optional>
3097	        <optional>
3098	         <element name="disconnection-method">
3099	          <ref name="disconnection-type"/>
3100	         </element>
3101	        </optional>
3102	        <optional>
3103	         <element name="disconnection-info">
3104	          <zeroOrMore>
3105	           <ref name="conference-info-urn"/>
3106	          </zeroOrMore>
3107	         </element>
3108	        </optional>
3109	        <zeroOrMore>
3110	         <element name="media">
3111	          <ref name="media-type"/>
3112	         </element>
3113	        </zeroOrMore>
3114	        <zeroOrMore>
3115	        <element name="floor">
3116	         <attribute name="id">
3117	          <text/>
3118	         </attribute>
3119	         <ref name="anyAttribute"/>
3120	         <data type="boolean"/>
3121	        </element>
3122	        </zeroOrMore>
3123	        <optional>
3124	         <element name="call-info">
3125	          <zeroOrMore>
3126	           <ref name="conference-info-urn"/>
3127	          </zeroOrMore>
3128	         </element>
3129	        </optional>
3130	        <zeroOrMore>
3131	         <ref name="anyElement"/>

3133	        </zeroOrMore>
3134	       </define>
3135	       <!--
3136	              MEDIA TYPE
3137	          -->
3138	       <define name="media-type">
3139	        <attribute name="id">
3140	         <data type="int"/>
3141	        </attribute>
3142	        <ref name="anyAttribute"/>
3143	        <optional>
3144	         <element name="display-text">
3145	          <text/>
3146	         </element>
3147	        </optional>
3148	        <optional>
3149	         <element name="type">
3150	          <text/>
3151	         </element>
3152	        </optional>
3153	        <optional>
3154	         <element name="label">
3155	          <text/>
3156	         </element>
3157	        </optional>
3158	        <optional>
3159	         <element name="src-id">
3160	          <text/>
3161	         </element>
3162	        </optional>
3163	        <optional>
3164	         <element name="status">
3165	          <ref name="media-status-type"/>
3166	         </element>
3167	        </optional>
3168	        <optional>
3169	         <element name="to-mixer">
3170	          <ref name="mixer-type"/>

3172	         </element>
3173	        </optional>
3174	        <optional>
3175	         <element name="from-mixer">
3176	          <ref name="mixer-type"/>
3177	         </element>
3178	        </optional>
3179	        <zeroOrMore>
3180	         <ref name="anyElement"/>
3181	        </zeroOrMore>
3182	       </define>
3183	       <!--
3184	              MIXER TYPE
3185	          -->
3186	       <define name="mixer-type">
3187	        <ref name="anyAttribute"/>
3188	        <optional>
3189	         <element name="controls">
3190	          <ref name="control-type"/>
3191	         </element>
3192	        </optional>
3193	        <zeroOrMore>
3194	         <ref name="anyElement"/>
3195	        </zeroOrMore>
3196	       </define>
3197	       <!--
3198	              SIDEBARS-BY-REF TYPE
3199	          -->
3200	       <define name="sidebars-by-ref-type">
3201	        <ref name="anyAttribute"/>
3202	        <zeroOrMore>
3203	         <element name="entry">
3204	          <zeroOrMore>
3205	           <ref name="conference-info-urn"/>
3206	          </zeroOrMore>
3207	         </element>
3208	        </zeroOrMore>
3209	        <zeroOrMore>
3210	         <ref name="anyElement"/>
3211	        </zeroOrMore>
3212	       </define>
3213	       <!--
3214	              SIDEBARS-BY-VAL TYPE
3215	          -->
3216	       <define name="sidebars-by-val-type">
3217	        <ref name="anyAttribute"/>
3218	        <zeroOrMore>
3219	         <element name="entry">
3220	          <ref name="conference-type"/>
3221	         </element>
3222	        </zeroOrMore>
3223	        <zeroOrMore>
3224	         <ref name="anyElement"/>
3225	        </zeroOrMore>
3226	       </define>
3227	       <!--
3228	        SINGLE ROLE TYPE
3229	       -->
3230	       <define name="single-role-type">
3231	        <choice>
3232	         <value type="string">administrator</value>
3233	         <value type="string">moderator</value>
3234	         <value type="string">user</value>
3235	         <value type="string">participant</value>
3236	         <value type="string">observer</value>
3237	         <value type="string">none</value>
3238	         <text/>
3239	        </choice>
3240	       </define>
3241	       <!--
3242	              *********************************
3243	              EXTENSIBILITY OF THE SCHEMA
3244	              *********************************
3245	          -->
3246	       <!--
3247	              EXTENSIBILITY ELEMENTS
3248	          -->
3249	       <define name="anyElement">
3250	        <element>
3251	         <anyName/>
3252	         <zeroOrMore>
3253	          <choice>
3254	           <attribute>
3255	            <anyName/>
3256	           </attribute>
3257	           <text/>
3258	           <ref name="anyElement"/>
3259	          </choice>
3260	         </zeroOrMore>
3261	        </element>
3262	       </define>
3263	       <!--
3264	              EXTENSIBILITY ATTRIBUTES
3265	          -->
3266	       <define name="anyAttribute">
3267	        <zeroOrMore>
3268	         <attribute>
3269	          <anyName>
3270	           <except>
3271	            <name ns="">entity</name>
3272	            <name ns="">lang</name>
3273	            <name ns="">required-participant</name>
3274	            <name ns="">label</name>
3275	            <name ns="">decision</name>
3276	            <name ns="">name</name>
3277	            <name ns="">policy</name>

3279	            <name ns="">uri</name>
3280	            <name ns="">method</name>
3281	            <name ns="">id</name>
3282	            <nsName ns=""/>
3283	            <nsName ns="urn:ietf:params:xml:ns:xcon-conference-info"/>
3284	           </except>
3285	          </anyName>
3286	          <text/>
3287	         </attribute>
3288	        </zeroOrMore>
3289	       </define>
3290	       <!--
3291	       *************************************************************
3292	       TYPES DEFINED IN THE EVENT PACKAGE FOR CONFERENCE STATE
3293	       -  RFC4575 -
3294	       *************************************************************
3295	          -->
3296	       <!--
3297	              WILDCARD FOR EVENT-PACKAGE NAMESPACE
3298	          -->
3299	       <define name="conference-info-urn">
3300	        <element>
3301	         <anyName>
3302	          <except>
3303	         <nsName ns="urn:ietf:params:xml:ns:conference-info"/>
3304	           <nsName ns=""/>
3305	          </except>
3306	         </anyName>
3307	         <mixed>
3308	         <zeroOrMore>
3309	           <choice>
3310	            <attribute>
3311	             <anyName/>
3312	            </attribute>
3313	            <ref name="conference-info-urn"/>
3314	           </choice>
3315	          </zeroOrMore>

3317	         </mixed>
3318	        </element>
3319	       </define>

3321	       <!--
3322	              DEFINITION OF ENDPOINT STATUS TYPE
3323	          -->
3324	       <define name="media-status-type">
3325	        <choice>
3326	         <value>recvonly</value>
3327	         <value>sendonly</value>

3329	         <value>sendrecv</value>
3330	         <value>inactive</value>
3331	         <text/>
3332	        </choice>
3333	       </define>
3334	       <!--
3335	              ENDPOINT STATUS TYPE
3336	          -->
3337	       <define name="endpoint-status-type">
3338	        <choice>
3339	         <value>pending</value>
3340	         <value>dialing-out</value>
3341	         <value>dialing-in</value>
3342	         <value>alerting</value>
3343	         <value>on-hold</value>
3344	         <value>connected</value>
3345	         <value>muted-via-focus</value>
3346	         <value>disconnecting</value>
3347	         <value>disconnected</value>
3348	         <text/>
3349	        </choice>
3350	       </define>
3351	       <!--
3352	              JOINING TYPE
3353	          -->
3354	       <define name="joining-type">
3355	        <choice>
3356	         <value>dialed-in</value>
3357	         <value>dialed-out</value>
3358	         <value>focus-owner</value>
3359	         <text/>
3360	        </choice>
3361	       </define>
3362	       <!--
3363	              DISCONNECTION TYPE
3364	          -->

3366	       <define name="disconnection-type">
3367	        <choice>
3368	         <value>departed</value>
3369	         <value>booted</value>
3370	         <value>failed</value>
3371	         <value>busy</value>
3372	         <text/>
3373	        </choice>
3374	       </define>

3376	      </grammar>

3378	Authors' Addresses

3380	   Oscar Novo
3381	   Ericsson
3382	   Hirsalantie 11
3383	   Jorvas  02420
3384	   Finland

3386	   Email: Oscar.Novo@ericsson.com

3388	   Gonzalo Camarillo
3389	   Ericsson
3390	   Hirsalantie 11
3391	   Jorvas  02420
3392	   Finland

3394	   Email: Gonzalo.Camarillo@ericsson.com

3396	   David P. Morgan
3397	   Fidelity Investments
3398	   82 Devonshire St, MZ V3C
3399	   Boston, MA  02109-3614
3400	   USA

3402	   Email: Dave.Morgan@fmr.com
3403	   Roni Even
3404	   Polycom
3405	   94 Derech Em Hamoshavot
3406	   Petach Tikva  49130
3407	   Israel

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

3411	Full Copyright Statement

3413	   Copyright (C) The IETF Trust (2008).

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

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

3427	Intellectual Property

3429	   The IETF takes no position regarding the validity or scope of any
3430	   Intellectual Property Rights or other rights that might be claimed to
3431	   pertain to the implementation or use of the technology described in
3432	   this document or the extent to which any license under such rights
3433	   might or might not be available; nor does it represent that it has
3434	   made any independent effort to identify any such rights.  Information
3435	   on the procedures with respect to rights in RFC documents can be
3436	   found in BCP 78 and BCP 79.

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

3445	   The IETF invites any interested party to bring to its attention any
3446	   copyrights, patents or patent applications, or other proprietary
3447	   rights that may cover technology that may be required to implement
3448	   this standard.  Please address the information to the IETF at
3449	   ietf-ipr@ietf.org.