draft-ietf-sipping-conference-package-02.txt   draft-ietf-sipping-conference-package-03.txt 
SIPPING J. Rosenberg SIPPING J. Rosenberg
Internet-Draft dynamicsoft Internet-Draft dynamicsoft
Expires: April 26, 2004 H. Schulzrinne Expires: August 15, 2004 H. Schulzrinne
Columbia University Columbia University
O. Levin, Ed. O. Levin, Ed.
Microsoft Corporation Microsoft Corporation
October 27, 2003 February 15, 2004
A Session Initiation Protocol (SIP) Event Package for Conference A Session Initiation Protocol (SIP) Event Package for Conference
State State
draft-ietf-sipping-conference-package-02 draft-ietf-sipping-conference-package-03
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. 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 April 26, 2004. This Internet-Draft will expire on August 15, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document defines a conference event package for the Session This document defines a conference event package for the Session
Initiation Protocol (SIP) Events framework, along with a data format Initiation Protocol (SIP) Events framework, along with a data format
used in notifications for this package. The conference package allows used in notifications for this package. The conference package allows
users to subscribe to a conference URI. Notifications are sent about users to subscribe to a conference URI. Notifications are sent about
changes in the membership of this conference, the status of users' changes in the membership of this conference, the status of users'
participation in the conference, and the sidebars in the conference. participation in the conference, and the sidebars in the conference.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
3. Conference Event Package . . . . . . . . . . . . . . . . . 5 3. Conference Event Package . . . . . . . . . . . . . . . . . 5
3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5
3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5 3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5
3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5 3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5
3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 5 3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 6
3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6 3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6
3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6 3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6
3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 6 3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 7
3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7 3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7
3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7 3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7
3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7 3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7
4. Conference Data Format . . . . . . . . . . . . . . . . . . 8 4. Conference Data Format . . . . . . . . . . . . . . . . . . 8
4.1 Conference Information . . . . . . . . . . . . . . . . . . 8 4.1 Conference Information . . . . . . . . . . . . . . . . . . 8
4.1.1 User Element . . . . . . . . . . . . . . . . . . . . . . . 8 4.1.1 User Element . . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1.1 User Statuses . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1.1 User Statuses . . . . . . . . . . . . . . . . . . . . . . 9
4.1.1.2 Media Stream Information . . . . . . . . . . . . . . . . . 9 4.1.1.2 Media Stream Information . . . . . . . . . . . . . . . . . 10
4.1.2 Sidebar . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1.2 Sidebar . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2 Constructing Coherent State . . . . . . . . . . . . . . . 10 4.1.3 Additional Conference Identifiers . . . . . . . . . . . . 11
4.3 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.4 Policy URIs . . . . . . . . . . . . . . . . . . . . . . . 11
4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . 13 4.2 Constructing Coherent State . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . 15 4.3 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . 16 4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 conference Event Package Registration . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . 16
6.2 application/conference-info+xml MIME Registration . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . 17
6.1 conference Event Package Registration . . . . . . . . . . 17
6.2 application/conference-info+xml MIME Registration . . . . 17
6.3 URN Sub-Namespace Registration for 6.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 17 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 18
6.4 XML Schema Registration . . . . . . . . . . . . . . . . . 18 6.4 XML Schema Registration . . . . . . . . . . . . . . . . . 19
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 19 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 20
8. Changes since -01 . . . . . . . . . . . . . . . . . . . . 20 8. Changes since -02 . . . . . . . . . . . . . . . . . . . . 21
Normative References . . . . . . . . . . . . . . . . . . . 21 9. Changes since -01 . . . . . . . . . . . . . . . . . . . . 22
Informative References . . . . . . . . . . . . . . . . . . 22 Normative References . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 22 Informative References . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . 23 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . 26
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [3] Events framework [2] The Session Initiation Protocol (SIP) [3] Events framework [2]
defines general mechanisms for subscribing to, and receiving defines general mechanisms for subscribing to, and receiving
notifications of, events within SIP networks. It introduces the notifications of, events within SIP networks. It introduces the
notion of a package, which is a specific "instantiation" of the notion of a package, which is a specific "instantiation" of the
events framework for a well-defined set of events. Here, we define an events framework for a well-defined set of events. Here, we define an
event package for SIP conferences. This package provides the event package for SIP conferences. This package provides the
conference notification service as outlined in the SIP conferencing conference notification service as outlined in the SIP conferencing
framework [9]. As described there, subscriptions to a conference URI framework [9]. As described there, subscriptions to a conference URI
are routed to the focus that is handling the conference. It acts as are routed to the focus that is handling the conference. It acts as
the notifer, and provides clients with updates on conference state. the notifer, and provides clients with updates on conference state.
The information provided by this package is comprised of conference The information provided by this package is comprised of conference
identifier, conference participants (optionally with their statuses identifier(s), conference participants (optionally with their
and media types) and conference sidebars. statuses and media types) and conference sidebars.
2. Terminology 2. Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations. indicate requirement levels for compliant implementations.
3. Conference Event Package 3. Conference Event Package
The conference event package allows a user to subscribe to a The conference event package allows a user to subscribe to a
conference. In SIP, conferences are represented by URIs. These URIs conference. In SIP, conferences are represented by URIs. These URIs
route to a SIP user agent, called a focus, that is responsible for route to a SIP user agent, called a focus, that is responsible for
ensuring that all users in the conference can communicate with each ensuring that all users in the conference can communicate with each
other [9]. The focus has sufficient information about the state of other [9]. The focus has sufficient information about the state of
the conference to inform subscribers about it. the conference to inform subscribers about it.
It is possible a participant in the conference may in fact be another
focus. In order to provide a more complete participant list, the
focus MAY subscribe to the conference package of the other focus to
discover the participant list in the cascaded conference. This
information can then be included in notifications by using of the
"cascaded-focus" attribute as specified by this package.
This section provides the details for defining a SIP Events package, This section provides the details for defining a SIP Events package,
as specified by [2]. as specified by [2].
3.1 Event Package Name 3.1 Event Package Name
The name of this event package is "conference". This package name is The name of this event package is "conference". This package name is
carried in the Event and Allow-Events header, as defined in [2]. carried in the Event and Allow-Events header, as defined in [2].
3.2 SUBSCRIBE Bodies 3.2 SUBSCRIBE Bodies
A SUBSCRIBE for a dialog package MAY contain a body. This body A SUBSCRIBE for a conference package MAY contain a body. This body
defines a filter to apply to the subscription. Filter documents are defines a filter to apply to the subscription. Filter documents are
not specified in this document, and at the time of writing, are not specified in this document, and at the time of writing, are
expected to be the subject of future standardization activity. expected to be the subject of future standardization activity.
A SUBSCRIBE for a dialog package MAY be sent without a body. This A SUBSCRIBE for a conference package MAY be sent without a body. This
implies the default subscription filtering policy. The default policy implies the default subscription filtering policy. The default policy
is: is:
o Notifications are generated every time there is any change in the o Notifications are generated every time there is any change in the
state of the conference. state of the conference.
o Notifications do not normally contain full state; rather, they o Notifications do not normally contain full state; rather, they
only indicate the state that has changed. The exception is a only indicate the state that has changed. The exception is a
NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the
full state of the information requested by the subscriber. full state of the information requested by the subscriber.
skipping to change at page 7, line 8 skipping to change at page 7, line 15
3.7 Subscriber Processing of NOTIFY Requests 3.7 Subscriber Processing of NOTIFY Requests
The SIP Events framework expects packages to specify how a subscriber The SIP Events framework expects packages to specify how a subscriber
processes NOTIFY requests in any package specific ways, and in processes NOTIFY requests in any package specific ways, and in
particular, how it uses the NOTIFY requests to contruct a coherent particular, how it uses the NOTIFY requests to contruct a coherent
view of the state of the subscribed resource. view of the state of the subscribed resource.
Typically, the NOTIFY for the conference package will only contain Typically, the NOTIFY for the conference package will only contain
information about those users whose state in the conference has information about those users whose state in the conference has
changed. To construct a coherent view of the total state of all changed. To construct a coherent view of the total state of all
users, a subscriber to the dialog package will need to combine users, a subscriber to the conference package will need to combine
NOTIFYs received over time. NOTIFYs received over time.
Notifications within this package can convey partial information; Notifications within this package can convey partial information;
that is, they can indicate information about a subset of the state that is, they can indicate information about a subset of the state
associated with the subscription. This means that an explicit associated with the subscription. This means that an explicit
algorithm needs to be defined in order to construct coherent and algorithm needs to be defined in order to construct coherent and
consistent state. The details of this mechanism are specific to the consistent state. The details of this mechanism are specific to the
particular document type. See Section 4.2 for information on particular document type. See Section 4.2 for information on
constructing coherent information from an application/ constructing coherent information from an application/
conference-info+xml document. conference-info+xml document.
skipping to change at page 8, line 23 skipping to change at page 8, line 23
defined by [5] and extended by [6]. This URN is: defined by [5] and extended by [6]. This URN is:
urn:ietf:params:xml:ns:conference-info urn:ietf:params:xml:ns:conference-info
A conference information document begins with the root element tag A conference information document begins with the root element tag
"conference-info". "conference-info".
4.1 Conference Information 4.1 Conference Information
Conference information begins with the top level element Conference information begins with the top level element
"conference-info". This element has three mandatory attributes: "conference-info". This element has three mandatory and one optional
attributes:
version: This attribute allows the recipient of conference version: This mandatory attribute allows the recipient of conference
information documents to properly order them. Versions start at 0 information documents to properly order them. Versions start at 0
and increment by one for each new document sent to a subscriber. and increment by one for each new document sent to a subscriber.
Versions are scoped within a subscription. Versions MUST be Versions are scoped within a subscription. Versions MUST be
represented using a 32 bit integer. represented using a 32 bit integer.
state: This attribute indicates whether the document contains the state: This mandatory attribute indicates whether the document
full conference information, or whether it contains only the contains the full conference information, or whether it contains
information that has changed since the previous document only the information that has changed since the previous document
(partial). (partial).
entity: This attribute contains the conference URI that identifies entity: This mandatory attribute contains the conference URI that
the conference being described in the document. identifies the conference being described in the document.
recording: This optional attribute indicates whether the conference
is being recorded at this moment ("on") or not ("off").
The "conference-info" element has zero or more "user" sub-elements The "conference-info" element has zero or more "user" sub-elements
which contain information on the users in the conference. This is which contain information on the users in the conference. This is
followed by zero or more "sidebar" sub-elements which contain followed by zero or more "sidebar" sub-elements which contain
information on the sidebars in the conference. information on the sidebars in the conference. This is followed by
zero or more "conf-uri" sub-elements which contain information on
additional URIs that the conference can be accessed by. This is
followed by zero or more "policy-uri" sub-elements which contain
information on additional URIs that the conference policies can be
accessed by.
4.1.1 User Element 4.1.1 User Element
The user element has one mandatory attribute, "uri" that indicates The user element has one mandatory attribute, "uri" that indicates
the URI for the user in the conference. This is a logical identifier, the URI for the user in the conference. This is a logical identifier,
not a machine specific one (i.e., it's taken from the authenticated not a machine specific one (i.e., it's taken from the authenticated
identity of the participant). The optional attribute "display-name" identity of the participant). The optional attribute "display-name"
contains a display name for the user. The standard "xml:lang" contains a display name for the user. The standard "xml:lang"
language attribute can also be present to indicate the language of language attribute can also be present to indicate the language of
the display-name. the display-name.
The optional attribute "cascaded-focus" contains a conference URI
(different from the main conference URI) for users that are connected
to the main conference as a result of focus cascading. In accordance
with the SIP conferencing framework [9], this defined package allows
for representation of peer-to-peer (i.e. "flat") focus cascading
only. The actual cascading graph is not explicitly expressed in this
package because most applications do not care about the actual
topology of the cascaded focuses as long as the information about
their participants is available. In addition, an advanced application
can construct the graph by subscribing to both this package and the
Dialog Package [10] of the involved focuses and correlating the
required information.
4.1.1.1 User Statuses 4.1.1.1 User Statuses
Two optional status elements are defined: activity-status and history Three optional status elements are defined: status, joining-mode, and
status. "Activity-status" provides information about user's current disconnection-reason.
level of participation in the conference. "History-status", if
present, provides information about the way the user joined or left
the conference. Additional optional indication "is-on-dial-out-list"
completes the information about the user membership in the
conference.
The following statuses are defined for the activity-status element: o "status": provides information about user's current level of
participation in the conference.
o "joining-mode": if present, provides information about the way the
user joined the conference.
o "disconnection-reason": if present, provides information about the
way the user left the conference.
The following statuses are defined for the "status" element:
connected: The user is a participant in the conference. Depending on connected: The user is a participant in the conference. Depending on
the media policies, he/she can send and receive media to and from the media policies, he/she can send and receive media to and from
other participants. other participants.
disconnected: The user is not a participant in the conference and no disconnected: The user is not a participant in the conference and no
active dialog exists between the user and the focus. active dialog exists between the user and the focus.
on-hold: Active SIP dialog exists between a user and a focus, but on-hold: Active SIP dialog exists between a user and a focus, but
user is "on-hold" for this conference. As an example, the user has user is "on-hold" for this conference, i.e. neither he/she is
asked to join the conference using SIP, but his/her participation "hearing" the conference mix, nor is his/her media being mixed in
is pending based on moderator approval. In the meantime he/she is the conference. As an example, the user has asked to join the
hearing music-on-hold or some other kind of related content. conference using SIP, but his/her participation is pending based
on moderator approval. In the meantime he/she is hearing
music-on-hold or some other kind of related content.
The following statuses are defined for the history-status element: muted-by-focus: Active SIP dialog exists between a user and a focus
and the user can "listen" to the conference, but user's media is
not being mixed into the conference.
The following statuses are defined for the "joining-mode" element:
dialed-in: The user dialed into the conference, i.e. sent INVITE to dialed-in: The user dialed into the conference, i.e. sent INVITE to
the focus, which resulted in successful dialog establishment. the focus, which resulted in successful dialog establishment.
dialed-out: The focus has brought the user into the conference by dialed-out: The focus has brought the user into the conference by
sending a successful INVITE to the user. sending a successful INVITE to the user.
focus-owner: The user is the focus itself for this conference.
The following statuses are defined for the disconnection-reason
element:
departed: The user sent a BYE, thus leaving the conference. departed: The user sent a BYE, thus leaving the conference.
booted: The user was sent a BYE by the focus, booting him/her out of booted: The user was sent a BYE by the focus, booting him/her out of
the conference. the conference. Alternatively, the user tried to dial into to
conference without success because was rejected by the focus
according to local policy decisions.
failed: The server tried to bring the user into the conference, but failed: The server tried to bring the user into the conference, but
its attempt to contact the specific user resulted in a non-200 its attempt to contact the specific user resulted in a non-200
class final response. class final response. Alternatively, the user tried to dial into
the conference without success due to technical reasons.
4.1.1.2 Media Stream Information 4.1.1.2 Media Stream Information
Each user has zero or more "media-stream" sub-elements. Each user has zero or more "media-stream" sub-elements.
Each "media-stream" element indicates the media stream that the user Each "media-stream" element indicates the media stream that the user
is currently connected to. Here, "connected to" implies that a user is currently connected to. Here, "connected to" implies that a user
has a media line in their SDP [10]. With this definition, a user is has a media line in their SDP [12]. With this definition, a user is
connected to a media stream even if they are not sending any media. connected to a media stream even if they are not sending any media.
The "media-stream" element has a mandatory "media-type" attribute The "media-stream" element has a mandatory "media-type" attribute
which identifies the media type (e.g. audio, video, message and which identifies the media type (e.g. audio, video, message and
application) and MUST have one of the values registered for "media" application) and MUST have one of the values registered for "media"
of SDP [10]. of SDP [12].
The "media-stream" element has also an optional "proto" sub-element, The "media-stream" element has also an optional "proto" sub-element,
which MUST has the value registered for "proto" of SDP [10]). which MUST has the value registered for "proto" of SDP [12]).
An optional "ssrc" sub-element, if present, carries the value of SSRC An optional "ssrc" sub-element, if present, carries the value of SSRC
(RTP/RTCP [8]) as generated by the user for the stream it sends. (RTP/RTCP [8]) as generated by the user for the stream it sends.
When an RTP mixer generates a CSRC list according to RTP/RTCP [8], it When an RTP mixer generates a CSRC list according to RTP/RTCP [8], it
inserts a list of the SSRC identifiers of the sources that inserts a list of the SSRC identifiers of the sources that
contributed to the generation of a particular packet into the RTP contributed to the generation of a particular packet into the RTP
header of that packet. "An example application is audio conferencing header of that packet. "An example application is audio conferencing
where a mixer indicates all the talkers whose speech was combined to where a mixer indicates all the talkers whose speech was combined to
produce the outgoing packet, allowing the receiver to indicate the produce the outgoing packet, allowing the receiver to indicate the
current talker, even though all the audio packets contain the same current talker, even though all the audio packets contain the same
SSRC identifier (that of the mixer)." SSRC identifier (that of the mixer)."
4.1.2 Sidebar 4.1.2 Sidebar
The sidebar element has one attribute - "entity" that indicates the The sidebar element has one attribute - "entity" that indicates the
URI which identifiers the sidebar. A sidebar has zero or more users URI which identifiers the sidebar. A sidebar has zero or more users
that are of type "user-type" as the users of the main conference are. that are of type "user-type" as the users of the main conference are.
4.1.3 Additional Conference Identifiers
In addition to the Conference URI present in the "entity" attribute,
a conference MAY have additional URIs of various types. Connecting to
these URIs will result in joining to the same conference.
4.1.4 Policy URIs
A policy URI specifies where and how a certain policy pertaining to
the conference can be accessed. The actual policy name and usage is
deduced from the URI schema name.
An example for the "policy-uri" usage is inclusion of the URI of the
CPCP [11]. A subscriber to the Conference package can use the Policy
URI to access and modify the conference policy.
4.2 Constructing Coherent State 4.2 Constructing Coherent State
The conference information subscriber maintains a table for the list The conference information subscriber maintains a table for the list
of users in the conference. The table contains a row for each user. of users in the conference. The table contains a row for each user.
Each row is indexed by a URI, present in the "uri" attribute of the Each row is indexed by a URI, present in the "uri" attribute of the
"user" element. The contents of each row contain the state of that "user" element. The contents of each row contain the state of that
user as conveyed in the document. user as conveyed in the document.
The table is associated with a version number. The version number The table is associated with a version number. The version number
MUST be initialized with the value of the "version" attribute from MUST be initialized with the value of the "version" attribute from
skipping to change at page 11, line 44 skipping to change at page 13, line 7
This import brings in the XML language attribute xml:lang This import brings in the XML language attribute xml:lang
--> -->
<xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd" /> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/03/xml.xsd" />
<xs:element name="conference-info"> <xs:element name="conference-info">
<xs:complexType> <xs:complexType>
<xs:sequence> <xs:sequence>
<xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="sidebar" type="sidebar-type" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="sidebar" type="sidebar-type" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="conf-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
<xs:element name="policy-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence> </xs:sequence>
<xs:attribute name="version" type="xs:nonNegativeInteger" use="required" /> <xs:attribute name="version" type="xs:nonNegativeInteger" use="required" />
<xs:attribute name="state" use="required"> <xs:attribute name="state" use="required">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="full" /> <xs:enumeration value="full" />
<xs:enumeration value="partial" /> <xs:enumeration value="partial" />
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
skipping to change at page 12, line 15 skipping to change at page 13, line 23
<xs:attribute name="state" use="required"> <xs:attribute name="state" use="required">
<xs:simpleType> <xs:simpleType>
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="full" /> <xs:enumeration value="full" />
<xs:enumeration value="partial" /> <xs:enumeration value="partial" />
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
</xs:attribute> </xs:attribute>
<xs:attribute name="entity" type="xs:anyURI" use="required" /> <xs:attribute name="entity" type="xs:anyURI" use="required" />
<xs:attribute name="recording" type="tns:recording-type" use="optional" />
<xs:anyAttribute />
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
<xs:complexType name="user-type"> <xs:complexType name="user-type">
<xs:sequence> <xs:sequence>
<xs:element name="activity-status" type="tns:activity-status-type" minOccurs="0" /> <xs:element name="status" type="tns:status-type" minOccurs="0" />
<xs:element name="history-status" type="tns:history-status-type" minOccurs="0" /> <xs:element name="joining-mode" type="tns:joining-mode-type" minOccurs="0" />
<xs:element name="is-on-dial-out-list" type="xs:boolean" minOccurs="0" /> <xs:element name="disconnection-reason" type="tns:disconnection-reason-type" minOccurs="0" />
<xs:element name="media-stream" type="tns:media-stream-type" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="media-stream" type="tns:media-stream-type" minOccurs="0" maxOccurs="unbounded" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence> </xs:sequence>
<xs:attribute name="uri" type="xs:anyURI" use="required" /> <xs:attribute name="uri" type="xs:anyURI" use="required" />
<xs:attribute name="display-name" type="xs:string" use="optional" /> <xs:attribute name="display-name" type="xs:string" use="optional" />
<xs:attribute ref="xml:lang" use="optional" /> <xs:attribute ref="xml:lang" use="optional" />
<xs:attribute name="cascaded-focus" type="xs:anyURI" use="optional" />
<xs:anyAttribute />
</xs:complexType> </xs:complexType>
<xs:complexType name="sidebar-type"> <xs:complexType name="sidebar-type">
<xs:sequence> <xs:sequence>
<xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence> </xs:sequence>
<xs:attribute name="entity" type="xs:anyURI" use="required" /> <xs:attribute name="entity" type="xs:anyURI" use="required" />
skipping to change at page 13, line 4 skipping to change at page 14, line 15
<xs:attribute name="entity" type="xs:anyURI" use="required" /> <xs:attribute name="entity" type="xs:anyURI" use="required" />
</xs:complexType> </xs:complexType>
<xs:complexType name="media-stream-type"> <xs:complexType name="media-stream-type">
<xs:sequence> <xs:sequence>
<xs:element name="proto" type="xs:string" minOccurs="0" /> <xs:element name="proto" type="xs:string" minOccurs="0" />
<xs:element name="ssrc" type="xs:nonNegativeInteger" minOccurs="0" /> <xs:element name="ssrc" type="xs:nonNegativeInteger" minOccurs="0" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence> </xs:sequence>
<xs:attribute name="media" type="xs:string" use="required" /> <xs:attribute name="media" type="xs:string" use="required" />
</xs:complexType> </xs:complexType>
<xs:simpleType name="activity-status-type"> <xs:simpleType name="status-type">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="connected" /> <xs:enumeration value="connected" />
<xs:enumeration value="disconnected" /> <xs:enumeration value="disconnected" />
<xs:enumeration value="on-hold" /> <xs:enumeration value="on-hold" />
<xs:enumeration value="muted-by-focus" />
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="history-status-type"> <xs:simpleType name="joining-mode-type">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="dialed-in" /> <xs:enumeration value="dialed-in" />
<xs:enumeration value="dialed-out" /> <xs:enumeration value="dialed-out" />
<xs:enumeration value="focus-owner" />
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="disconnection-reason-type">
<xs:restriction base="xs:string">
<xs:enumeration value="departed" /> <xs:enumeration value="departed" />
<xs:enumeration value="booted" /> <xs:enumeration value="booted" />
<xs:enumeration value="failed" /> <xs:enumeration value="failed" />
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:simpleType name="recording-type">
<xs:restriction base="xs:string">
<xs:enumeration value="on" />
<xs:enumeration value="off" />
</xs:restriction>
</xs:simpleType>
</xs:schema> </xs:schema>
4.4 Example 4.4 Example
The following is an example conference information document: The following is an example conference information document:
<conference-info version="0" state="full" entity="sip:conf233@example.com"> <conference-info version="0" state="full" entity="sip:conf233@example.com" recording="on">
<user uri="sip:bob@example.com" display-name="Bob Jones"> <user uri="sip:bob@example.com" display-name="Bob Jones">
<activity-status>connected</activity-status> <status>connected</status>
<history-status>dialed-in</history-status> <joining-mode>dialed-in</joining-mode>
<media-stream media-type="audio" <media-stream media-type="audio">
<proto> RTP/AVP <proto> <proto> RTP/AVP </proto>
<ssrc> 583398 <ssrc> <ssrc> 583398 </ssrc>
</media-stream> </media-stream>
</user> </user>
<user uri="sip:barbara@example.com" display-name="Barbara Jones"> <user uri="sip:barbara@example.com" display-name="Barbara Jones">
<activity-status>on-hold</activity-status> <status>on-hold</status>
</user> </user>
<user uri="sip:bill@example.com" display-name="Bill Minelli"> <user uri="sip:bill@example.com" display-name="Bill Minelli">
<activity-status>on-hold</activity-status> <status>on-hold</status>
</user> </user>
<sidebar entity="sip:conf233.1@example.com"> <sidebar entity="sip:conf233.1@example.com">
<user>uri="sip:barbara@example.com"</user> <user uri="sip:barbara@example.com">
<user>uri="sip:bill@example.com"</user> <user uri="sip:bill@example.com">
</sidebar> </sidebar>
<conf-uri>tel:+18005671234</conf-uri>
<conf-uri>h323:conf545@example.com</conf-uri>
</conference-info> </conference-info>
This document describes a conference with three users, two of which This conference currently has three users, two of which are in a
are in a sidebar conversation. sidebar conversation. The conference is being recorded. There are
additional means to join the conference either by phone using tel URI
[14] or by H.323 protocol using h323 URL [13].
5. Security Considerations 5. Security Considerations
Subscriptions to conference state can reveal very sensitive Subscriptions to conference state can reveal very sensitive
information. For this reason, the document recommends authentication information. For this reason, the document recommends authentication
and authorization, and provides guidelines on sensible authorization and authorization, and provides guidelines on sensible authorization
policies. policies.
Since the data in notifications is sensitive as well, end-to-end SIP Since the data in notifications is sensitive as well, end-to-end SIP
encryption mechanisms using S/MIME SHOULD be used to protect it. encryption mechanisms using S/MIME SHOULD be used to protect it.
skipping to change at page 19, line 7 skipping to change at page 20, line 7
URI: please assign. URI: please assign.
Registrant Contact: IETF, SIPPING Working Group Registrant Contact: IETF, SIPPING Working Group
(sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net). (sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net).
XML: The XML can be found as the sole content of Section 4.3. XML: The XML can be found as the sole content of Section 4.3.
7. Acknowledgements 7. Acknowledgements
The authors would like to thank Dan Petrie and Sean Olson for their The authors would like to thank Dan Petrie, Sean Olson, and Alan
comments. Johnston for their comments.
8. Changes since -01 8. Changes since -02
o State "muted-by-focus" is added to user's status.
o Optional conference attribute "recording" is added.
o Policy URI placeholder (i.e. element "policy-uri") is created.
o Example∆s syntax is corrected.
o Optional attribute "cascaded-focus" URI per user is added.
o Optional additional conference identifiers (i.e. element
"conf-uri") are added.
o In order to cover all possible cases, participant's status is
expressed using three optional statuses: "status", "joining-mode"
and "disconnection-reason". That is instead of "activity-status",
"history-status" and "is-on-dial-out-list".
9. Changes since -01
o Package parameters are removed. Decision about performing o Package parameters are removed. Decision about performing
"recursive" membership algorithm is perceived as a focus local "recursive" membership algorithm is perceived as a focus local
policy. policy.
o General information (i.e. pointers to additional available o General information (i.e. pointers to additional available
services) is removed. The defined XML schema can be extended in services) is removed. The defined XML schema can be extended in
future to include those when XCON work matures. future to include those when XCON work matures.
o Dialog information is removed. It can be obtained by direct o Dialog information is removed. It can be obtained by direct
skipping to change at page 22, line 9 skipping to change at page 24, line 9
3023, January 2001. 3023, January 2001.
[8] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, [8] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", RFC "RTP: A Transport Protocol for Real-Time Applications", RFC
3550, July 2003. 3550, July 2003.
Informative References Informative References
[9] Rosenberg, J., "A Framework for Conferencing with the Session [9] Rosenberg, J., "A Framework for Conferencing with the Session
Initiation Protocol", Initiation Protocol",
draft-ietf-sipping-conferencing-framework-00 (work in draft-ietf-sipping-conferencing-framework-01 (work in
progress), May 2003. progress), October 2003.
[10] Handley, M. and V. Jacobson, "SDP: Session Description [10] Rosenberg, J. and H. Schulzrinne, "An INVITE Inititiated Dialog
Event Package for the Session Initiation Protocol (SIP)",
draft-ietf-sipping-dialog-package-03 (work in progress),
October 2003.
[11] Koskelainen, P., "Requirements for Conference Policy Control
Protocol", draft-ietf-xcon-cpcp-reqs-02 (work in progress),
February 2004.
[12] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998. Protocol", RFC 2327, April 1998.
[13] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
Registration", RFC 3508, April 2003.
[14] Schulzrinne, H., "The tel URI for Telephone Numbers",
draft-ietf-iptel-tel-rfc2806bis-03 (work in progress), February
2004.
Authors' Addresses Authors' Addresses
Jonathan Rosenberg Jonathan Rosenberg
dynamicsoft dynamicsoft
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany, NJ 07054 Parsippany, NJ 07054
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
EMail: jdrosen@dynamicsoft.com EMail: jdrosen@dynamicsoft.com
skipping to change at page 23, line 29 skipping to change at page 26, line 29
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/