draft-ietf-xcon-common-data-model-08.txt   draft-ietf-xcon-common-data-model-09.txt 
XCON O. Novo XCON O. Novo
Internet-Draft G. Camarillo Internet-Draft G. Camarillo
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: June 18, 2008 D. Morgan Expires: August 25, 2008 D. Morgan
Fidelity Investments Fidelity Investments
R. Even R. Even
Polycom Polycom
December 16, 2007 February 22, 2008
Conference Information Data Model for Centralized Conferencing (XCON) Conference Information Data Model for Centralized Conferencing (XCON)
draft-ietf-xcon-common-data-model-08.txt draft-ietf-xcon-common-data-model-09.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 38
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on June 18, 2008. This Internet-Draft will expire on August 25, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines an Extensible Markup Language (XML)-based This document defines an Extensible Markup Language (XML)-based
conference information data model for centralized conferencing conference information data model for centralized conferencing
(XCON). A conference information data model is designed to convey (XCON). A conference information data model is designed to convey
information about the conference and about participation in the information about the conference and about participation in the
conference. The conference information data model defined in this conference. The conference information data model defined in this
document constitutes an extension of the data format specified in the document constitutes an extension of the data format specified in the
Session Initiation Protocol (SIP) Event Package for Conference State. Session Initiation Protocol (SIP) Event Package for Conference State.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6 3.1. Data Model Format . . . . . . . . . . . . . . . . . . . . 6
3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6 3.2. Data Model Namespace . . . . . . . . . . . . . . . . . . . 6
3.3. The Conference Object Identifier . . . . . . . . . . . . . 7 3.3. The Conference Object Identifier . . . . . . . . . . . . . 7
3.3.1. Conference URI Definition . . . . . . . . . . . . . . 9 3.3.1. Conference Object URI Definition . . . . . . . . . . . 9
3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9 3.4. Data Model Structure . . . . . . . . . . . . . . . . . . . 9
4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10 4. Data Model Definition . . . . . . . . . . . . . . . . . . . . 10
4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13 4.1. <conference-info> . . . . . . . . . . . . . . . . . . . . 13
4.2. <conference-description> . . . . . . . . . . . . . . . . . 14 4.2. <conference-description> . . . . . . . . . . . . . . . . . 14
4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.1. <language> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14 4.2.2. <display-text> . . . . . . . . . . . . . . . . . . . . 14
4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.3. <subject> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 14 4.2.4. <free-text> . . . . . . . . . . . . . . . . . . . . . 14
4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 14 4.2.5. <keywords> . . . . . . . . . . . . . . . . . . . . . . 14
4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15 4.2.6. <allow-sidebars> . . . . . . . . . . . . . . . . . . . 15
skipping to change at page 3, line 27 skipping to change at page 3, line 27
8. Security Considerations . . . . . . . . . . . . . . . . . . . 45 8. Security Considerations . . . . . . . . . . . . . . . . . . . 45
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 45 8.1. Authentication . . . . . . . . . . . . . . . . . . . . . . 45
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 46 8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 46
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 46 8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 46
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 46 9.1. Relax NG Schema Registration . . . . . . . . . . . . . . . 46
9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 47 9.2. XML Namespace Registration . . . . . . . . . . . . . . . . 47
9.3. Conference Object Identifier Registration . . . . . . . . 47 9.3. Conference Object Identifier Registration . . . . . . . . 47
9.4. Conference User Identifier Registration . . . . . . . . . 48 9.4. Conference User Identifier Registration . . . . . . . . . 48
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49
11.1. Normative References . . . . . . . . . . . . . . . . . . . 48 11.1. Normative References . . . . . . . . . . . . . . . . . . . 49
11.2. Informative References . . . . . . . . . . . . . . . . . . 49 11.2. Informative References . . . . . . . . . . . . . . . . . . 49
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML
Syntax . . . . . . . . . . . . . . . . . . . . . . . 50 Syntax . . . . . . . . . . . . . . . . . . . . . . . 50
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 71
Intellectual Property and Copyright Statements . . . . . . . . . . 72 Intellectual Property and Copyright Statements . . . . . . . . . . 72
1. Introduction 1. Introduction
There is a core data set of conference information that is utilized There is a core data set of conference information that is utilized
in any conference, independent of the specific conference media. in any conference, independent of the specific conference media.
This core data set called the 'conference information data model' is This core data set called the 'conference information data model' is
defined in this document using an Extensible Markup Language (XML)- defined in this document using an Extensible Markup Language (XML)-
based. The conference information data model defined in this based. The conference information data model defined in this
document is logically represented by the conference object. document is logically represented by the conference object.
skipping to change at page 5, line 45 skipping to change at page 5, line 45
. | | +----------------------------------------------+ |||+ . . | | +----------------------------------------------+ |||+ .
. | +--------------------------------------------------+|+ . . | +--------------------------------------------------+|+ .
. +----^------------------^-------------^--------|------+ . . +----^------------------^-------------^--------|------+ .
. | | | | . . | | | | .
. +------v-------+ +--------v-----+ +-----v-+ +----v-------+ . . +------v-------+ +--------v-----+ +-----v-+ +----v-------+ .
. | Conference | | Floor | | | | | . . | Conference | | Floor | | | | | .
. | Control | | Control | |Foci | |Notification| . . | Control | | Control | |Foci | |Notification| .
. | Server | | Server | | | |Service | . . | Server | | Server | | | |Service | .
. +-----^--------+ +---^----------+ +-^-----+ +------------+ . . +-----^--------+ +---^----------+ +-^-----+ +------------+ .
........|..............|..............|..........|............. ........|..............|..............|..........|.............
|Conference |Binary Floor |Call |Notification |Conference |Floor |Call |Notification
|Control |Control |Signaling |Protocol |Control |Control |Signaling |Protocol
|Protocol |Protocol |Protocol | |Protocol |Protocol |Protocol |
........v..............v..............v..........v............. ........v..............v..............v..........v.............
. C o n f e r e n c i n g C l i e n t . . C o n f e r e n c i n g C l i e n t .
............................................................... ...............................................................
Figure 1: Conference Server Architecture Figure 1: Conference Server Architecture
The Session Initiation Protocol (SIP) Event Package for Conference The Session Initiation Protocol (SIP) Event Package for Conference
State, specified in [RFC4575], already defines a data format for State, specified in [RFC4575], already defines a data format for
conferences. However, that model is SIP specific and lacks elements conferences. However, that model is SIP specific and lacks elements
skipping to change at page 9, line 7 skipping to change at page 9, line 7
implicitly linked to the top level conference object identifier e.g. implicitly linked to the top level conference object identifier e.g.
H323 and SIP URIs that represent a conference instance. It should be H323 and SIP URIs that represent a conference instance. It should be
noted that a conferencing system is free to structure such noted that a conferencing system is free to structure such
relationships as required and this information is just included as a relationships as required and this information is just included as a
guideline that can be used. guideline that can be used.
Further elements can be added to the tree representation in Figure 2 Further elements can be added to the tree representation in Figure 2
to enable a complete representation of a conference instance within a to enable a complete representation of a conference instance within a
conferencing system. conferencing system.
3.3.1. Conference URI Definition 3.3.1. Conference Object URI Definition
XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host, port, and unreserved are defined in RFC3986[RFC3986] host, port, and unreserved are defined in RFC3986[RFC3986]
3.4. Data Model Structure 3.4. Data Model Structure
The information in this data model is structured in the following The information in this data model is structured in the following
skipping to change at page 13, line 45 skipping to change at page 13, line 45
The following sections describe these elements in detail. The full The following sections describe these elements in detail. The full
Relax NG schema is provided Section 5. Relax NG schema is provided Section 5.
4.1. <conference-info> 4.1. <conference-info>
A conference object document begins with the root element tag A conference object document begins with the root element tag
<conference-info>, which is defined in [RFC4575]. The <conference- <conference-info>, which is defined in [RFC4575]. The <conference-
info> attributes are described in [RFC4575]. Note that the info> attributes are described in [RFC4575]. Note that the
<conference-info> element does not have the attributes 'state' and <conference-info> element does not have the attributes 'state' and
'version' defined in [RFC4575] for this element because this 'version' defined in [RFC4575] for this element because these
attribute only applies to notifications mechanism. attributes only applies to notification mechanisms.
In addition, [RFC4575] defines an 'entity' attribute that contains In addition, [RFC4575] defines an 'entity' attribute that contains
the conference object identifier (XCON-URI) that identifies the the conference object identifier (XCON-URI) that identifies the
conference being described in the document. conference being described in the document.
The <conference-info> element contains the <conference-description>, The <conference-info> element contains the <conference-description>,
<host-info>, <conference-state>, <floor-information>, <users>, <host-info>, <conference-state>, <floor-information>, <users>,
<sidebars-by-ref>, and <sidebars-by-val> child elements. All these <sidebars-by-ref>, and <sidebars-by-val> child elements. All these
elements, except <floor-information>, are defined in [RFC4575]. A elements, except <floor-information>, are defined in [RFC4575]. A
conference document MUST at least include the <conference- conference document MUST at least include the <conference-
skipping to change at page 14, line 29 skipping to change at page 14, line 29
uris>, <service-uris>, <maximum-user-count>, and <available-media>. uris>, <service-uris>, <maximum-user-count>, and <available-media>.
The following sections describe these elements in more detail. Other The following sections describe these elements in more detail. Other
child elements MAY be defined in the future to extend the child elements MAY be defined in the future to extend the
<conference-description> element. <conference-description> element.
4.2.1. <language> 4.2.1. <language>
The <language> element indicates the predominant language that is The <language> element indicates the predominant language that is
expected to be employed within a conference. This element is not expected to be employed within a conference. This element is not
enforcing the language of the conference, only informs to the enforcing the language of the conference, but only informs the
participants about the desirable language that they should used in participants about the desirable language that they should use in the
the conference. Participants are free to switch to other languages conference. Participants are free to switch to other languages if
if they like. they like.
4.2.2. <display-text> 4.2.2. <display-text>
The <display-text> element is described in section 5.3 of [RFC4575]. The <display-text> element is described in section 5.3 of [RFC4575].
4.2.3. <subject> 4.2.3. <subject>
The <subject> element is described in section 5.3 of [RFC4575]. The <subject> element is described in section 5.3 of [RFC4575].
4.2.4. <free-text> 4.2.4. <free-text>
skipping to change at page 20, line 24 skipping to change at page 20, line 24
The <floor-information> element contains the <conference-ID>, <allow- The <floor-information> element contains the <conference-ID>, <allow-
floor-events>, <floor-request-handling>, and <conference-floor- floor-events>, <floor-request-handling>, and <conference-floor-
policy> child elements. Other elements from different namespaces MAY policy> child elements. Other elements from different namespaces MAY
be present for the purposes of extensibility. The absence of this be present for the purposes of extensibility. The absence of this
element from an XML document indicates that the conference does not element from an XML document indicates that the conference does not
have a floor. have a floor.
4.5.1. <conference-ID> 4.5.1. <conference-ID>
The <conference-ID> is a 32-bit BFCP conference identifier defined in The <conference-ID> represents a conference instance within floor
[RFC4582] section 5.1. that identifies the BFCP conference the control. When created within the conferencing system, the
message belongs to. This identifier represents a conference instance 'conference-ID' can be represented by the unique conference object
within floor control. When created within the conferencing system, Identifier (XCON-URI). When BFCP serves as the floor control
the 'conference-ID' has a 1:1 mapping to the unique conference object protocol, the <conference-ID> is a 32-bit BFCP conference identifier
Identifier (XCON-URI). defined in [RFC4582] section 5.1 and there is a 1:1 mapping to the
XCON-URI.
4.5.2. <allow-floor-events> 4.5.2. <allow-floor-events>
The <allow-floor-events> element represents a boolean action. If set The <allow-floor-events> element represents a boolean action. If set
to TRUE, the focus is instructed to accept the subscription to floor to TRUE, the focus is instructed to accept the subscription to floor
control events. If set to FALSE, the focus is instructed to reject control events. If set to FALSE, the focus is instructed to reject
the subscription. If this element is undefined, it has a default the subscription. If this element is undefined, it has a default
value of FALSE, causing the subscription to floor control events to value of FALSE, causing the subscription to floor control events to
be rejected. be rejected.
skipping to change at page 21, line 23 skipping to change at page 21, line 24
Note that this section discusses floor control information, Note that this section discusses floor control information,
therefore, the value "block" in a <floor-request-handling> element is therefore, the value "block" in a <floor-request-handling> element is
not related with the "block" value in the <join-handling> element not related with the "block" value in the <join-handling> element
(see Section 4.6). (see Section 4.6).
4.5.4. <conference-floor-policy> 4.5.4. <conference-floor-policy>
The <conference-floor-policy> element has one or more <floor> child The <conference-floor-policy> element has one or more <floor> child
elements. Every <floor> child elements has an attribute 'id' which elements. Every <floor> child elements has an attribute 'id' which
uniquely identifies a floor or floors within a conference. The 'id' uniquely identifies a floor or floors within a conference. In the
attribute corresponds to the floor-id identifier defined in [RFC4582] case of BFCP [RFC4582], the 'id' attribute corresponds to the
section 5.2.2. Each <floor> element has the following child floor-id identifier defined in [RFC4582] section 5.2.2.
elements:
o <media-label>: Every floor is identified for one or more mandatory o <media-label>: Every floor is identified for one or more mandatory
<media-label> element. If the <available-media> information is <media-label> element. If the <available-media> information is
included in the conference document, the value of this element included in the conference document, the value of this element
MUST be equal to the 'label' value of the corresponding media MUST be equal to the 'label' value of the corresponding media
stream <entry> in the <available-media> container. The number of stream <entry> in the <available-media> container. The number of
those elements indicates how many floors the conference can have. those elements indicates how many floors the conference can have.
A floor can be used for one or more media types; A floor can be used for one or more media types;
o <algorithm>: A floor can be controlled using many algorithms; the o <algorithm>: A floor can be controlled using many algorithms; the
mandatory <algorithm> element MUST be set to any of the mandatory <algorithm> element MUST be set to any of the
"moderator-controlled", "FCFS" or "random" values indicating the "moderator-controlled", "FCFS" or "random" values indicating the
algorithm. The "Moderator-controlled" value indicates that the algorithm. The "Moderator-controlled" value indicates that the
moderator of the conference controls the floor. The "FCFS" value moderator of the conference controls the floor. The "FCFS" value
states for 'first-come-first-served' floor control. states for 'first-come-first-served' floor control.
o <max-floor-users>: The <max-floor-users> child element in the o <max-floor-users>: The <max-floor-users> child element in the
<floor> element is optional and, if present, dictates the maximum <floor> element is optional and, if present, dictates the maximum
number of users who can have the floor at one time. number of users who can have the floor at one time.
o <moderator-id>: The optional <moderator-id> indicates the 'User o <moderator-id>: The optional <moderator-id> indicates the 'User
ID' of the moderator. The 'User ID' is a BFCP identifier defined ID' of the moderator. It MUST be set if the element <algorithm>
in [RFC4582] section 5.1. It MUST be set if the element is set to "Moderator-controlled" value. When the floor is created
<algorithm> is set to "Moderator-controlled" value. Note that within the conferencing system, the XCON-User identifier MAY be
[RFC4582] refers to the moderator role as a 'floor chair'. used as the moderator-id. In the case of BFCP as the floor
control protocol, the <moderator-id> is defined in [RFC4582]
section 5.1. Note that [RFC4582] refers to the moderator role as
a 'floor chair'.
4.6. <users> 4.6. <users>
The <users> element is described in [RFC4575] and contains the <join- The <users> element is described in [RFC4575] and contains the <join-
handling>, <user-admission-policy>, <allowed-users-list> and <deny- handling>, <user-admission-policy>, <allowed-users-list> and <deny-
users-list> defined in this document and <user> child elements users-list> defined in this document and <user> child elements
defined in [RFC4575]. Note that the <users> element does not have defined in [RFC4575]. Note that the <users> element does not have
the attribute 'state' defined in [RFC4575] for this element because the attribute 'state' defined in [RFC4575] for this element because
this attribute only applies to notifications mechanism. The this attribute only applies to notifications mechanism. The
following sections describe these elements in more detail. Other following sections describe these elements in more detail. Other
skipping to change at page 24, line 6 skipping to change at page 24, line 6
The <allowed-users-list> element has a <persistent-list> child The <allowed-users-list> element has a <persistent-list> child
element as well. Some chatroom systems allow -- and some require -- element as well. Some chatroom systems allow -- and some require --
registration of detailed information about a user before they are registration of detailed information about a user before they are
allowed to join a chatroom. The <persistent-list> child element allowed to join a chatroom. The <persistent-list> child element
stores persistent information about users who are not actively part stores persistent information about users who are not actively part
of an ongoing chatroom session. The <persistent-list> element stores of an ongoing chatroom session. The <persistent-list> element stores
the following information: the following information:
o user: The <user> element stores the name, nickname, the conference o user: The <user> element stores the name, nickname, the conference
user identifier (XCON_USERID) and email address of a user. It has user identifier (XCON-USERID) and email address of a user. It has
three attributes: 'name', 'nickname' and 'id' and an <email> three attributes: 'name', 'nickname' and 'id' and an <email>
element. Future extensions to this schema may define new elements element. Future extensions to this schema may define new elements
for the <user> element. for the <user> element.
Future extensions to this schema may define new elements for the Future extensions to this schema may define new elements for the
<target> element. <target> element.
4.6.4. <deny-users-list> 4.6.4. <deny-users-list>
The <deny-users-list> child element contains a list of user URIs, The <deny-users-list> child element contains a list of user URIs,
roles, or domains (*@example.com) that the focus uses to determine roles, or domains (*@example.com) that the focus uses to determine
who has been 'banned' from the conference. Such banned users are who has been 'banned' from the conference. Such banned users are
prevented from re-joining the chatroom until they have been un- prevented from re-joining the chatroom until they have been un-
banned. banned.
4.6.5. <user> and Its <user> Sub-elements 4.6.5. <user> and Its <user> Sub-elements
The element <user> is described in RFC4575[RFC4575] and describes a The element <user> is described in [RFC4575] and describes a single
single participant in the conference. The <user> element has an participant in the conference. The <user> element has an attribute
attribute 'entity'. Note that the <user> element does not have the 'entity'. Note that the <user> element does not have the attribute
attribute 'state' defined in [RFC4575] for this element because this 'state' defined in [RFC4575] for this element because this attribute
attribute only applies to notifications mechanism. only applies to notifications mechanism.
The attribute 'entity' contains a unique conference user identifier The attribute 'entity' contains a unique conference user identifier
(XCON_USERID). The URI format of this identifier is as follow: (XCON-USERID) within the scope of a conferencing system. The URI
format of this identifier is as follow:
XCON_USERID = "xcon_userid" ":" conf-object-id XCON-USERID = "xcon-userid" ":" conf-user-id
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-user-id = 1*(unreserved)
[unreserved is defined in RFC3986] [unreserved is defined in RFC3986]
Other user identifiers can be associated with this conference user Other user identifiers can be associated with this conference user
identifier and enable the conferencing system to correlate and map identifier and enable the conferencing system to correlate and map
these multiple authenticated user identities to a single global user these multiple authenticated user identities to a single global user
identifier. Figure 6 illustrates an example using the conference identifier. Figure 6 illustrates an example using the conference
user identifier in association with the user identity defined for user identifier in association with the user identity defined for
BFCP, SIP, and H323 user identity. It should be noted that a BFCP, SIP, and H323 user identity. It should be noted that a
conferencing system is free to structure such relationships as conferencing system is free to structure such relationships as
required and this information is just included as a guideline that required and this information is just included as a guideline that
can be used. can be used.
+--------------+ +----------------+
| Conference | | Conference |
| User | | User |
| Identifier | | Identifier |
+--------------+ +----------------+
| John | |xcon-userid:John|
+------+-------+ +-------+--------+
| |
| |
| |
+----------------------+-------------------------+ +----------------------+-------------------------+
| | | | | |
+-------+--------+ +-----------+-----------+ +-----------+-----------+ +-------+--------+ +-----------+-----------+ +-----------+-----------+
| BFCP User ID | | SIP User URI | | H323 User URI | | BFCP User ID | | SIP User URI | | H323 User URI |
+----------------+ +-----------------------+ +-----------------------+ +----------------+ +-----------------------+ +-----------------------+
| 543 | |sip:851221@example.com | |h323:taeduk@example.com| | 543 | |sip:851221@example.com | |h323:taeduk@example.com|
+----------------+ +-----------------------+ +-----------------------+ +----------------+ +-----------------------+ +-----------------------+
Figure 6: Conference Object Mapping Figure 6: Conference User Mapping
The element <user> element contains the <display-text>, <associated- The element <user> element contains the <display-text>, <associated-
aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>, aors>, <provide-anonymity>, <roles>, <languages>, <cascaded-focus>,
<allow-refer-users-dynamically>, <allow-invite-users-dynamically>, <allow-refer-users-dynamically>, <allow-invite-users-dynamically>,
<allow-remove-users-dynamically>, and <endpoint>. The following <allow-remove-users-dynamically>, and <endpoint>. The following
sections describe these elements in more detail. sections describe these elements in more detail.
4.6.5.1. <display-text> 4.6.5.1. <display-text>
The <display-text> child element is explained in [RFC4575], section The <display-text> child element is explained in [RFC4575], section
skipping to change at page 25, line 45 skipping to change at page 25, line 45
4.6.5.2. <associated-aors> 4.6.5.2. <associated-aors>
The <associated-aors> child element is explained in [RFC4575], The <associated-aors> child element is explained in [RFC4575],
section 5.6.2. section 5.6.2.
4.6.5.3. <provide-anonymity> 4.6.5.3. <provide-anonymity>
The <provide-anonymity> element provides anonymity to the user. In The <provide-anonymity> element provides anonymity to the user. In
this case, the focus provides to the rest of the participants an this case, the focus provides to the rest of the participants an
anonymous identity for that user, for example anonymousX. This anonymous identity for that user, for example anonymousX, or it does
element only affects the way the user information is provided to the not provide any information for that user such that other users can
other participants. The real information about the user is still not see he is a participant in the conference. This element only
stored in the data model. This can be achieved by using the affects the way the user information is provided to the other
<provide-anonymity> element. This element has two values: 'private' participants. The real information about the user is still stored in
and 'semi-private'. The 'private' value specifies that this user is the data model. This can be achieved by using the <provide-
completely anonymous in the conference. 'semi-private' value anonymity> element. This element has three values: 'private', 'semi-
private' and 'hidden'. The 'private' value specifies that this user
is completely anonymous in the conference. 'semi-private' value
specifies that this user is anonymous to all users with equal or specifies that this user is anonymous to all users with equal or
lesser permissions in the conference. lesser permissions in the conference. 'hidden' value specifies that
other users can not see this participant in the conference.
4.6.5.4. <roles> 4.6.5.4. <roles>
A role provides the context for the set of conference operations that A role provides the context for the set of conference operations that
a participant can perform. This element can contain one of the a participant can perform. This element can contain one of the
following values: "administrator", "moderator", "user", following values: "administrator", "moderator", "user",
"participant", "observer", and "none". The roles semantic definition "participant", "observer", and "none". The roles semantic definition
is out of the scope of this document and is subject to future policy is out of the scope of this document and is subject to future policy
documents. This element can be extended with new roles in future documents. This element can be extended with new roles in future
documents. documents.
skipping to change at page 31, line 40 skipping to change at page 31, line 41
conference-state-type = conference-state-type =
anyAttribute, anyAttribute,
element allow-conference-event-subscription { xsd:boolean }?, element allow-conference-event-subscription { xsd:boolean }?,
element user-count { xsd:unsignedInt }?, element user-count { xsd:unsignedInt }?,
element active { xsd:boolean }?, element active { xsd:boolean }?,
element locked { xsd:boolean }?, element locked { xsd:boolean }?,
anyElement* anyElement*
# FLOOR INFORMATION TYPE # FLOOR INFORMATION TYPE
floor-information-type = floor-information-type =
anyAttribute, anyAttribute,
(element conference-ID { xsd:unsignedInt }, (element conference-ID { xsd:unsignedLong },
element allow-floor-events { xsd:boolean }, element allow-floor-events { xsd:boolean },
element floor-request-handling { floor-request-type }, element floor-request-handling { floor-request-type },
element conference-floor-policy { Conference-floor-policy }, element conference-floor-policy { Conference-floor-policy },
anyElement*)* anyElement*)*
# FLOOR REQUEST TYPE # FLOOR REQUEST TYPE
floor-request-type =xsd:string "block" | xsd:string "confirm" | text floor-request-type =xsd:string "block" | xsd:string "confirm" | text
# CONFERENCE FLOOR POLICY # CONFERENCE FLOOR POLICY
Conference-floor-policy = Conference-floor-policy =
anyAttribute, anyAttribute,
element floor { element floor {
skipping to change at page 33, line 31 skipping to change at page 33, line 32
xsd:string "dial-in" xsd:string "dial-in"
| xsd:string "dial-out" | xsd:string "dial-out"
| xsd:string "refer" | xsd:string "refer"
| text | text
# USER TYPE # USER TYPE
user-type = user-type =
attribute entity { xsd:anyURI }, attribute entity { xsd:anyURI },
anyAttribute, anyAttribute,
element display-text { text }?, element display-text { text }?,
element associated-aors { conference-info-urn* }?, element associated-aors { conference-info-urn* }?,
element provide-anonymity { "private" | "semi-private" | text }?, element provide-anonymity { "private" | "semi-private" |
"hidden" | text }?,
element roles { single-role-type }?, element roles { single-role-type }?,
element languages { element languages {
list { xsd:language } list { xsd:language }
}?, }?,
element cascaded-focus { xsd:anyURI }?, element cascaded-focus { xsd:anyURI }?,
element allow-refer-users-dynamically { xsd:boolean }?, element allow-refer-users-dynamically { xsd:boolean }?,
element allow-invite-users-dynamically { xsd:boolean }?, element allow-invite-users-dynamically { xsd:boolean }?,
element allow-remove-users-dynamically { xsd:boolean }?, element allow-remove-users-dynamically { xsd:boolean }?,
element endpoint { endpoint-type }*, element endpoint { endpoint-type }*,
anyElement* anyElement*
skipping to change at page 47, line 28 skipping to change at page 47, line 29
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title> Centralized Conferencing Namespace</title> <title> Centralized Conferencing Namespace</title>
</head> </head>
<body> <body>
<h1>Namespace for Centralized COnferencing</h1> <h1>Namespace for Centralized Conferencing</h1>
<h2>urn:ietf:params:xml:ns:consent-rules</h2> <h2>urn:ietf:params:xml:ns:xcon-conference-info</h2>
<p>See <a href="[URL of published RFC]">RFCXXXX <p>See <a href="[URL of published RFC]">RFCXXXX
[NOTE TO IANA/RFC-EDITOR: [NOTE TO IANA/RFC-EDITOR:
Please replace XXXX with the RFC number of this Please replace XXXX with the RFC number of this
specification.]</a>.</p> specification.]</a>.</p>
</body> </body>
</html> </html>
END END
9.3. Conference Object Identifier Registration 9.3. Conference Object Identifier Registration
skipping to change at page 47, line 46 skipping to change at page 48, line 4
END END
9.3. Conference Object Identifier Registration 9.3. Conference Object Identifier Registration
The IANA is requested to register the following URI scheme The IANA is requested to register the following URI scheme
under the Permanent URI Schemes register. under the Permanent URI Schemes register.
XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx] XCON-URI = "xcon" ":" [conf-object-id "@"] host [ ":" port ] [RFC xxxx]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-object-id = 1*( unreserved / "+" / "=" / "/" )
host, port, and unreserved are defined in RFC3986[RFC3986] host, port, and unreserved are defined in RFC3986[RFC3986]
[Note to the RFC Editor: replace xxxx with the number this RFC gets [Note to the RFC Editor: replace xxxx with the number this RFC gets
assigned.] assigned.]
Subject: Request for XCON-URI Registration
Person & email address to contact for further information:
Oscar Novo <oscar novo_at_ericsson.com>
Specification: RFC XXXX
Author/Change Controller: IESG
Comments:
Identifies the Conference
9.4. Conference User Identifier Registration 9.4. Conference User Identifier Registration
The IANA is requested to register the following URI scheme The IANA is requested to register the following URI scheme
under the Permanent URI Schemes register. under the Permanent URI Schemes register.
XCON_USERID = "xcon_userid" ":" conf-object-id [ RFC xxxx ] XCON-USERID = "xcon-userid" ":" conf-user-id [ RFC xxxx ]
conf-object-id = 1*( unreserved / "+" / "=" / "/" ) conf-user-id = 1*(unreserved)
unreserved is defined in RFC3986[RFC3986] unreserved is defined in RFC3986[RFC3986]
[Note to the RFC Editor: replace xxxx with the number this RFC gets [Note to the RFC Editor: replace xxxx with the number this RFC gets
assigned.] assigned.]
Subject: Request for XCON-USERID Registration
Person & email address to contact for further information:
Oscar Novo <oscar novo_at_ericsson.com>
Specification: RFC XXXX
Author/Change Controller: IESG
Comments:
Identifies the User in the conference
10. Acknowledgements 10. Acknowledgements
This document is really a distillation of many ideas discussed over a This document is really a distillation of many ideas discussed over a
long period of time. These ideas were contributed by many different long period of time. These ideas were contributed by many different
drafts in the XCON working group and the SIPPING working group. We drafts in the XCON working group and the SIPPING working group. We
would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris would like to thank Orit Levin, Adam Roach, Mary Barnes, Chris
Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Aki Boulton, Umesh Chandra, Hisham Khartabil, Petri Koskelainen, Aki
Niemi, Jari Urpilainen, Rohan Mahy, and Henning Schulzrinne for their Niemi, Jari Urpilainen, Rohan Mahy, Jonathan Lennox, and Henning
comments. Also, we would like to thank Mary Barnes, and Chris Schulzrinne for their comments. Also, we would like to thank Mary
Boulton for letting us use the conference and user identifier Barnes, and Chris Boulton for letting us use the conference and user
information of their xcon drafts. Last but not least, I would like identifier information of their xcon drafts. Last but not least, we
to express my gratitude to all those reviewers for their invaluable would like to express our gratitude to all those reviewers for their
contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia Castaldi, invaluable contribution: Simon Pietro Romano, Lorenzo Miniero, Tobia
Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom Houri, and Castaldi, Miguel Garcia, Mary Barnes, Srivatsa Srinivasan, Avshalom
Ben Campbell. Houri, Pierre Tane, and Ben Campbell.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and [RFC2445] Dawson, F. and Stenerson, D., "Internet Calendaring and
Scheduling Core Object Specification (iCalendar)", Scheduling Core Object Specification (iCalendar)",
skipping to change at page 49, line 50 skipping to change at page 50, line 24
for Binary Floor Control Protocol (BFCP) Streams", for Binary Floor Control Protocol (BFCP) Streams",
RFC 4583, November 2006. RFC 4583, November 2006.
[RFC4855] Casner, S., "Media Type Registration of RTP Payload [RFC4855] Casner, S., "Media Type Registration of RTP Payload
Formats", RFC 4855, February 2007. Formats", RFC 4855, February 2007.
[RFC5018] Camarillo, G., "Connection Establishment in the Binary [RFC5018] Camarillo, G., "Connection Establishment in the Binary
Floor Control Protocol (BFCP)", RFC 5018, September 2007. Floor Control Protocol (BFCP)", RFC 5018, September 2007.
[W3C.REC-xml-20001006] [W3C.REC-xml-20001006]
Paoli, J., Maler, E., Sperberg-McQueen, C., and T. Bray, Paoli, J., Maler, E., Bray, T., and C. Sperberg-McQueen,
"Extensible Markup Language (XML) 1.0 (Second Edition)", "Extensible Markup Language (XML) 1.0 (Second Edition)",
World Wide Web Consortium FirstEdition REC-xml-20001006, World Wide Web Consortium FirstEdition REC-xml-20001006,
October 2000, October 2000,
<http://www.w3.org/TR/2000/REC-xml-20001006>. <http://www.w3.org/TR/2000/REC-xml-20001006>.
Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Syntax Appendix A. Appendix A. Non-Normative RELAX NG Schema in XML Syntax
<?xml version="1.0" encoding="UTF-8"?>
<grammar ns="urn:ietf:params:xml:ns:xcon-conference-info" <grammar ns="urn:ietf:params:xml:ns:xcon-conference-info"
xmlns="http://relaxng.org/ns/structure/1.0" xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0" xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes"> datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">
<start> <start>
<element name="conference-info"> <element name="conference-info">
<ref name="conference-type"/> <ref name="conference-type"/>
</element> </element>
</start> </start>
<!-- <!--
skipping to change at page 58, line 21 skipping to change at page 58, line 43
<ref name="anyElement"/> <ref name="anyElement"/>
</zeroOrMore> </zeroOrMore>
</define> </define>
<!-- <!--
FLOOR INFORMATION TYPE FLOOR INFORMATION TYPE
--> -->
<define name="floor-information-type"> <define name="floor-information-type">
<ref name="anyAttribute"/> <ref name="anyAttribute"/>
<zeroOrMore> <zeroOrMore>
<element name="conference-ID"> <element name="conference-ID">
<data type="unsignedInt"/> <data type="unsignedLong"/>
</element> </element>
<element name="allow-floor-events"> <element name="allow-floor-events">
<data type="boolean"/> <data type="boolean"/>
</element> </element>
<element name="floor-request-handling"> <element name="floor-request-handling">
<ref name="floor-request-type"/> <ref name="floor-request-type"/>
</element> </element>
<element name="conference-floor-policy"> <element name="conference-floor-policy">
<ref name="Conference-floor-policy"/> <ref name="Conference-floor-policy"/>
</element> </element>
skipping to change at page 63, line 7 skipping to change at page 63, line 29
<zeroOrMore> <zeroOrMore>
<ref name="conference-info-urn"/> <ref name="conference-info-urn"/>
</zeroOrMore> </zeroOrMore>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="provide-anonymity"> <element name="provide-anonymity">
<choice> <choice>
<value>private</value> <value>private</value>
<value>semi-private</value> <value>semi-private</value>
<value>hidden</value>
<text/> <text/>
</choice> </choice>
</element> </element>
</optional> </optional>
<optional> <optional>
<element name="roles"> <element name="roles">
<ref name="single-role-type"/> <ref name="single-role-type"/>
</element> </element>
</optional> </optional>
<optional> <optional>
skipping to change at page 72, line 7 skipping to change at page 72, line 7
Roni Even Roni Even
Polycom Polycom
94 Derech Em Hamoshavot 94 Derech Em Hamoshavot
Petach Tikva 49130 Petach Tikva 49130
Israel Israel
Email: roni.even@polycom.co.il Email: roni.even@polycom.co.il
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
 End of changes. 40 change blocks. 
72 lines changed or deleted 96 lines changed or added

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