draft-ietf-sipping-conference-package-03.txt   draft-ietf-sipping-conference-package-04.txt 
´╗┐
SIPPING J. Rosenberg SIPPING J. Rosenberg
Internet-Draft dynamicsoft Internet-Draft dynamicsoft
Expires: August 15, 2004 H. Schulzrinne Expires: November 19, 2004 H. Schulzrinne
Columbia University Columbia University
O. Levin, Ed. O. Levin, Ed.
Microsoft Corporation Microsoft Corporation
February 15, 2004 May 21, 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-03 draft-ietf-sipping-conference-package-04
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
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
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
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 August 15, 2004. This Internet-Draft will expire on November 19, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). 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
users to subscribe to a conference URI. Notifications are sent about allows users to subscribe to a conference URI. Notifications are
changes in the membership of this conference, the status of users' sent about changes in the membership of this conference and
participation in the conference, and the sidebars in the conference. optionally about changes in the state of additional conference
components.
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 . . . . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . 7 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 . . . . . . . . . . . . . . . . . . . . 9
4.1 Conference Information . . . . . . . . . . . . . . . . . . 8 4.1 Conference Information . . . . . . . . . . . . . . . . . . 9
4.1.1 User Element . . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1 User Element . . . . . . . . . . . . . . . . . . . . . 9
4.1.1.1 User Statuses . . . . . . . . . . . . . . . . . . . . . . 9 4.1.1.1 User Attributes . . . . . . . . . . . . . . . . . 10
4.1.1.2 Media Stream Information . . . . . . . . . . . . . . . . . 10 4.1.1.2 User Status Elements . . . . . . . . . . . . . . . 10
4.1.2 Sidebar . . . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.1.3 Media Stream Information . . . . . . . . . . . . . 12
4.1.3 Additional Conference Identifiers . . . . . . . . . . . . 11 4.1.2 Sidebar Element . . . . . . . . . . . . . . . . . . . 13
4.1.4 Policy URIs . . . . . . . . . . . . . . . . . . . . . . . 11 4.1.3 Additional Conference Identifiers . . . . . . . . . . 13
4.2 Constructing Coherent State . . . . . . . . . . . . . . . 11 4.1.4 Policy URIs . . . . . . . . . . . . . . . . . . . . . 13
4.3 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 12 4.2 Constructing Coherent State . . . . . . . . . . . . . . . 13
4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.2.1 User and Sidebar Updates . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . 16 4.2.2 Conference and Policy Identifiers Updates . . . . . . 14
6. IANA Considerations . . . . . . . . . . . . . . . . . . . 17 4.3 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 15
6.1 conference Event Package Registration . . . . . . . . . . 17 4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . 17
6.2 application/conference-info+xml MIME Registration . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
6.1 conference Event Package Registration . . . . . . . . . . 20
6.2 application/conference-info+xml MIME Registration . . . . 20
6.3 URN Sub-Namespace Registration for 6.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 18 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 20
6.4 XML Schema Registration . . . . . . . . . . . . . . . . . 19 6.4 XML Schema Registration . . . . . . . . . . . . . . . . . 21
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 20 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 22
8. Changes since -02 . . . . . . . . . . . . . . . . . . . . 21 8. Changes History . . . . . . . . . . . . . . . . . . . . . . . 23
9. Changes since -01 . . . . . . . . . . . . . . . . . . . . 22 8.1 Changes since -03 . . . . . . . . . . . . . . . . . . . . 23
Normative References . . . . . . . . . . . . . . . . . . . 23 8.2 Changes since -02 . . . . . . . . . . . . . . . . . . . . 23
Informative References . . . . . . . . . . . . . . . . . . 24 8.3 Changes since -01 . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . 24 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . 26 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 24
9.2 Informative References . . . . . . . . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 25
Intellectual Property and Copyright Statements . . . . . . . . 27
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [3] Events framework [2] The Session Initiation Protocol (SIP) [6] Events framework Events
defines general mechanisms for subscribing to, and receiving Framework [7] defines general mechanisms for subscribing to, and
notifications of, events within SIP networks. It introduces the receiving notifications of, events within SIP networks. It
notion of a package, which is a specific "instantiation" of the introduces the notion of a package, which is a specific
events framework for a well-defined set of events. Here, we define an "instantiation" of the events framework for a well-defined set of
event package for SIP conferences. This package provides the events. Here, we define an event package for SIP conferences. This
conference notification service as outlined in the SIP conferencing package provides the conference notification service as outlined in
framework [9]. As described there, subscriptions to a conference URI the SIP conferencing framework [13]. As described there,
are routed to the focus that is handling the conference. It acts as subscriptions to a conference URI are routed to the focus that is
the notifer, and provides clients with updates on conference state. handling the conference. It acts as the notifier, 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(s), conference participants (optionally with their identifier(s), conference participants (optionally with their
statuses and media types) and conference sidebars. statuses and media description), conference sidebars, and conference
policy URIs.
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 [2] 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, as described in Conferencing Framework [13]. The focus has
the conference to inform subscribers about it. sufficient information about the state of the conference to inform
subscribers about it.
It is possible a participant in the conference may in fact be another 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. In order to provide a more complete participant list, the
focus MAY subscribe to the conference package of the other focus to focus MAY subscribe to the conference package of the other focus to
discover the participant list in the cascaded conference. This discover the participant list in the cascaded conference. This
information can then be included in notifications by using of the information can then be included in notifications by using of the
"cascaded-focus" attribute as specified by this package. "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 RFC 3265 [7].
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 RFC 3265
[7].
3.2 SUBSCRIBE Bodies 3.2 SUBSCRIBE Bodies
A SUBSCRIBE for a conference 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 conference package MAY be sent without a body. This A SUBSCRIBE for a conference package MAY be sent without a body.
implies the default subscription filtering policy. The default policy This implies the default subscription filtering policy. The default
is: policy 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.
3.3 Subscription Duration 3.3 Subscription Duration
The default expiration time for a subscription to a conference is one The default expiration time for a subscription to a conference is one
hour. Once the conference ends, all subscriptions to that particular hour. Once the conference ends, all subscriptions to that particular
conference are terminated, with a reason of "noresource" [2]. conference are terminated, with a reason of "noresource" RFC 3265
[7].
3.4 NOTIFY Bodies 3.4 NOTIFY Bodies
As described in RFC 3265 [2], the NOTIFY message will contain bodies As described in RFC 3265 [7], the NOTIFY message will contain bodies
that describe the state of the subscribed resource. This body is in a that describe the state of the subscribed resource. This body is in
format listed in the Accept header field of the SUBSCRIBE, or a a format listed in the Accept header field of the SUBSCRIBE, or a
package-specific default if the Accept header field was omitted from package-specific default if the Accept header field was omitted from
the SUBSCRIBE. the SUBSCRIBE.
In this event package, the body of the notification contains a In this event package, the body of the notification contains a
conference information document. This document describes the state of conference information document. This document describes the state
a conference. All subscribers and notifiers MUST support the of a conference. All subscribers and notifiers MUST support the
"application/conference-info+xml" data format described in Section 4. "application/conference-info+xml" data format described in Section 4.
The subscribe request MAY contain an Accept header field. If no such The subscribe request MAY contain an Accept header field. If no such
header field is present, it has a default value of "application/ header field is present, it has a default value of "application/
conference-info+xml". If the header field is present, it MUST include conference-info+xml". If the header field is present, it MUST
"application/conference-info+xml", and MAY include any other types include "application/conference-info+xml", and MAY include any other
capable of representing dialog state. types capable of representing dialog state.
Of course, the notifications generated by the server MUST be in one Of course, the notifications generated by the server MUST be in one
of the formats specified in the Accept header field in the SUBSCRIBE of the formats specified in the Accept header field in the SUBSCRIBE
request. request.
3.5 Notifier Processing of SUBSCRIBE Requests 3.5 Notifier Processing of SUBSCRIBE Requests
The conference information contains very sensitive information. The conference information contains very sensitive information.
Therefore, all subscriptions SHOULD be authenticated and then Therefore, all subscriptions SHOULD be authenticated and then
authorized before approval. Authorization policy is at the discretion authorized before approval. Authorization policy is at the
of the administrator, as always. However, a few recommendations can discretion of the administrator, as always. However, a few
be made. recommendations can be made.
It is RECOMMENDED that all users in the conference be allowed to It is RECOMMENDED that all users in the conference be allowed to
subscribe to the conference. subscribe to the conference.
3.6 Notifier Generation of NOTIFY Requests 3.6 Notifier Generation of NOTIFY Requests
Notifications SHOULD be generated for the conference whenever there Notifications SHOULD be generated for the conference whenever there
is a change in the state in any of the information delivered to the is a change in the state in any of the information delivered to the
subscriber. subscriber.
The changes generally occur when a new participant joins, a The changes generally occur when a new participant joins (i.e. gets
participant leaves, or a participant is put on-hold. Subject to a "connected" to) or a participant leaves (i.e. gets "disconnected"
local focus policy, changes in media types and other optional media from) the conference.
attributes MAY be reported by the focus. In addition, creation and
deletion of sidebars together with their rosters MAY be reported by Subject to a local focus policy, additional changes in participant's
the focus, subject to its local policy. status, changes in its media types, and other optional media
attributes MAY be reported by the focus.
Changes in sidebar rosters SHOULD be reported by the focus to their
participants and MAY be reported to others, subject to local policy.
Changes in conference identifiers and policy URIs SHOULD be reported
by the focus to the conference participants.
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
skipping to change at page 8, line 9 skipping to change at page 9, line 9
Conference state is ideally maintained in the element in which the Conference state is ideally maintained in the element in which the
conference resides. Therefore, the elements that maintain the conference resides. Therefore, the elements that maintain the
conference are the ones best suited to handle subscriptions to it. conference are the ones best suited to handle subscriptions to it.
Therefore, the usage of state agents is NOT RECOMMENDED for this Therefore, the usage of state agents is NOT RECOMMENDED for this
package. package.
4. Conference Data Format 4. Conference Data Format
Conference information is an XML document that MUST be well-formed Conference information is an XML document that MUST be well-formed
and SHOULD be valid. Dialog information documents MUST be based on and SHOULD be valid. Dialog information documents MUST be based on
XML 1.0 and MUST be encoded using UTF-8. This specification makes use XML 1.0 and MUST be encoded using UTF-8. This specification makes
of XML namespaces for identifying dialog information documents and use of XML namespaces for identifying dialog information documents
document fragments. The namespace URI for elements defined by this and document fragments. The namespace URI for elements defined by
specification is a URN [4], using the namespace identifier 'ietf' this specification is a URN [3], using the namespace identifier
defined by [5] and extended by [6]. This URN is: 'ietf' defined by [4] and extended by [1]. 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 and one optional "conference-info". This element has three mandatory and one optional
skipping to change at page 9, line 7 skipping to change at page 10, line 5
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. This is followed by information on the sidebars in the conference. This is followed by
zero or more "conf-uri" sub-elements which contain information on zero or more "conf-uri" sub-elements which contain information on
additional URIs that the conference can be accessed by. This is additional URIs that the conference can be accessed by. This is
followed by zero or more "policy-uri" sub-elements which contain followed by zero or more "policy-uri" sub-elements which contain
information on additional URIs that the conference policies can be information on additional URIs that the conference policies can be
accessed by. accessed by.
4.1.1 User Element 4.1.1 User Element
4.1.1.1 User Attributes
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
not a machine specific one (i.e., it's taken from the authenticated identifier, which corresponds to the authenticated identity of the
identity of the participant). The optional attribute "display-name" participant. The "uri" attribute MUST be unique in the user element
contains a display name for the user. The standard "xml:lang" list because it is used as the key in partial notifications about
language attribute can also be present to indicate the language of users' state.
the display-name.
If a conference participant has more than a single signaling dialog
associated with the conference, the conference focus MAY present the
user's aggregated information (e.g. the statuses) and display all
its media streams under a single user element.
Note, that the optional element "dialog-uri" of "media-stream" (see
below) MAY be used in this case to specify the actual signaling
dialog for each media stream.
An anonymous participant in a conference SHOULD be represented by an
anonymous URI generated by the focus. For multiple anonymous
participants, the focus must ensure that each anonymous URI is
unique. The guidelines for generating anonymous URIs in RFC 3323 [8]
should be followed. For example,
"Anonymous1" <sip:anonymous1@anonymous.invalid>
could be used for a participant requesting privacy.
The optional attribute "display-name" contains a display name for the
user. The standard "xml:lang" language attribute can also be present
to indicate the language of the display-name.
The optional attribute "cascaded-focus" contains a conference URI The optional attribute "cascaded-focus" contains a conference URI
(different from the main conference URI) for users that are connected (different from the main conference URI) for users that are connected
to the main conference as a result of focus cascading. In accordance to the main conference as a result of focus cascading. In accordance
with the SIP conferencing framework [9], this defined package allows with the SIP conferencing framework [13], this package allows for
for representation of peer-to-peer (i.e. "flat") focus cascading representation of peer-to-peer (i.e. "flat") focus cascading only.
only. The actual cascading graph is not explicitly expressed in this The actual cascading graph can not be deduced from the information
package because most applications do not care about the actual provided in the package alone. Advanced applications can construct
topology of the cascaded focuses as long as the information about the graph by subscribing to both this package and the Dialog Package
their participants is available. In addition, an advanced application [14] of the cascaded foci and correlating the relevant information.
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.2 User Status Elements
Three optional status elements are defined: status, joining-mode, and Three optional status elements are defined: status, joining-mode, and
disconnection-reason. disconnection-reason.
o "status": provides information about user's current level of o "status": provides information about user's current level of
participation in the conference. participation in the conference.
o "joining-mode": if present, provides information about the way the o "joining-mode": if present, provides information about the way the
user joined the conference. user joined the conference.
o "disconnection-reason": if present, provides information about the o "disconnection-reason": if present, provides information about the
way the user left the conference. way the user left the conference.
The following statuses are defined for the "status" element: 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, i.e. neither he/she is user is "on-hold" for this conference, i.e. neither he/she is
"hearing" the conference mix, nor is his/her media being mixed in "hearing" the conference mix, nor is his/her media being mixed in
the conference. As an example, the user has asked to join the the conference. As an example, the user has asked to join the
conference using SIP, but his/her participation is pending based conference using SIP, but his/her participation is pending based
on moderator approval. In the meantime he/she is hearing on moderator approval. In the meantime he/she is hearing
music-on-hold or some other kind of related content. music-on-hold or some other kind of related content.
muted-by-focus: Active SIP dialog exists between a user and a focus 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 and the user can "listen" to the conference, but user's media is
not being mixed into the conference. not being mixed into the conference. Note that sometimes a subset
of user media streams can be muted by focus (such as poor quality
video) while others (such as voice or IM) can still be active. In
this case, it is RECOMMENDED that the "aggregated" user
connectivity "status" reflects the status of the active media.
The following statuses are defined for the "joining-mode" element: 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 for this conference. This status
focus-owner: The user is the focus itself for this conference. is used only when a participant UA acts as a conference focus
being identified by its own AOR or GRUU.
The following statuses are defined for the disconnection-reason The following statuses are defined for the disconnection-reason
element: 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. Alternatively, the user tried to dial into to the conference. Alternatively, the user tried to dial into to
conference without success because was rejected by the focus conference without success because was rejected by the focus
according to local policy decisions. 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. Alternatively, the user tried to dial into class final response. Alternatively, the user tried to dial into
the conference without success due to technical reasons. the conference without success due to technical reasons.
4.1.1.2 Media Stream Information 4.1.1.3 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 [12]. With this definition, a user is has a media line in his/her SDP [11] document(s). With this
connected to a media stream even if they are not sending any media. definition, a user is connected to a media stream even if he/she is
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 [12]. of SDP [11].
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 [12]). which MUST has the value registered for "proto" of SDP [11].
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. (defined in RTP/RTCP [10]) 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 [10],
inserts a list of the SSRC identifiers of the sources that it 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 An optional "info" sub-element, if present, carries a human readable
description for this stream populated by the focus. The value of
this element corresponds to the information media attribute "i" in
SDP [11].
The sidebar element has one attribute - "entity" that indicates the An optional "label" sub-element, if present, carries a unique
URI which identifiers the sidebar. A sidebar has zero or more users identifier for this stream among all streams in the conference and is
that are of type "user-type" as the users of the main conference are. assigned by the focus. The value of this element corresponds to the
"label" media attribute in SDP [11] and defined in [17].
An optional "dialog-id" sub-element, if present, carries a URI, which
MUST uniquely identify the signaling dialog being used for
establishing of this media stream. In SIP, for example, values of
Contact URI or GRUU [16] can be used for this purpose. It is
RECOMMENDED to include the "dialog-id" information for every user
that has more than a single dialog associated with the conference.
This element SHOULD NOT be included for an anonymous participant.
4.1.2 Sidebar Element
The sidebar element has one attribute - "entity", which carries the
URI identifying the sidebar. This URI MUST be unique among the
sidebar identifiers of the same conference. Attribute "entity" is
used as the key in partial notifications about sidebars of a
conference.
A sidebar has zero or more users of "user-type".
4.1.3 Additional Conference Identifiers 4.1.3 Additional Conference Identifiers
In addition to the Conference URI present in the "entity" attribute, In addition to the Conference URI present in the "entity" attribute,
a conference MAY have additional URIs of various types. Connecting to a conference MAY have additional URIs of various types. Connecting
these URIs will result in joining to the same conference. to these URIs will result in joining to the same conference.
4.1.4 Policy URIs 4.1.4 Policy URIs
A policy URI specifies where and how a certain policy pertaining to A policy URI specifies where and how a certain policy pertaining to
the conference can be accessed. The actual policy name and usage is the conference can be accessed. The actual policy name and usage is
deduced from the URI schema name. deduced from the URI schema name.
An example for the "policy-uri" usage is inclusion of the URI of the 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 CPCP [15]. A subscriber to the Conference package can use the Policy
URI to access and modify the conference 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 Conference information is associated with a version number. The
of users in the conference. The table contains a row for each user. version number MUST be initialized with the value of the "version"
Each row is indexed by a URI, present in the "uri" attribute of the attribute from the "conference-info" element in the first document
"user" element. The contents of each row contain the state of that received. Each time a new document is received, the value of the
user as conveyed in the document. local version number, and the "version" attribute in the new
document, are compared. If the value in the new document is one
higher than the local version number, the local version number is
increased by one, and the document is processed. If the value in the
document is more than one higher than the local version number, the
local version number is set to the value in the new document, the
document is processed, and the subscriber SHOULD generate a refresh
request to trigger a full state notification. If the value in the
document is less than the local version, the document is discarded
without processing.
The table is associated with a version number. The version number Further processing of the conference information document depends on
MUST be initialized with the value of the "version" attribute from whether it contains full or partial state. If it contains full
the "conference-info" element in the first document received. Each state, indicated by the value of the "state" attribute in the
time a new document is received, the value of the local version "conference-info" element, the whole local content is flushed and
number, and the "version" attribute in the new document, are repopulated from the document.
compared. If the value in the new document is one higher than the
local version number, the local version number is increased by one,
and the document is processed. If the value in the document is more
than one higher than the local version number, the local version
number is set to the value in the new document, the document is
processed, and the subscriber SHOULD generate a refresh request to
trigger a full state notification. If the value in the document is
less than the local version, the document is discarded without
processing.
The processing of the conference information document depends on If the document contains partial state, as indicated by the value of
whether it contains full or partial state. If it contains full state, the "state" attribute in the "conference-info" element, the document
indicated by the value of the "state" attribute in the is used to update the local content as described below.
"conference-info" element, the contents of the table is flushed. It
is repopulated from the document. A new row in the user table is The conference information is described by a means of a root element:
created for each "user" element. If the document contains partial "conference-info", which can be comprised of elements of four main
state, as indicated by the value of the "state" attribute in the types: "user-type", "sidebar-type", "conf-ids-type", and
"conference-info" element, the document is used to update the table. "policy-ids-type". Updates from partial notifications MUST be
For each "user" element in the document, the subscriber checks to see implemented as a set of atomic operations on elements of these types
whether a row exists for that user in the user table. This check is only.
done by comparing the URI in the "uri" attribute of the "user"
element with the URI associated with the row. If the user doesn't 4.2.1 User and Sidebar Updates
exist in the table, a row is added, and its state is set to the
information from that "user" element. If the user does exist, its The conference package subscriber maintains two tables: one for the
state is updated to be the information from that "user" element. If a list of users and another for the list of sidebars in the conference.
row is updated or created, such that its state is now disconnected, Each table contains a row for each user or each sidebar
booted, failed or departed, that entry MAY be removed from the table correspondingly. Each row is indexed by a URI key, present in the
"uri" attribute of the "user" element or in the "entity" attribute of
the "sidebar" element correspondingly. The contents of each row
contain the state of that user or a sidebar as conveyed in the
document.
If the document is an update (i.e. contains partial state), for each
table and for each element (i.e. "user" or "sidebar") the subscriber
compares the keys received in the update with the keys in the local
tables. If a key doesn't exist in the local table, a row is added,
and its content is set to the element information from the update.
If a key of the same value does exist, the row content is replaced
with the received information.
If a row is updated or created such that user's state becomes
"disconnected", that entry MAY be removed from the table at any time.
If a row is updated or created such that a sidebar element doesn't
contain any users, that sidebar element MAY be removed from the table
at any time. at any time.
4.2.2 Conference and Policy Identifiers Updates
In order to support additional conference features, the conference
package subscriber SHOULD locally maintain two additional
informational elements: "conf-ids" and "policy-ids". The content of
each contains a list of URIs for additional conference identifiers or
for policy protocols (correspondingly) applicable to this conference.
If the document is an update (i.e. contains partial state), and one
or both of the elements exist in the update, the element(s) is/are
replaced with the new information as a whole.
If the element is updated or created, such that it is empty, that
element MAY be removed from the local content at any time.
4.3 Schema 4.3 Schema
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:conference-info" xmlns:tns="urn:ietf:params:xml:ns:conference-info" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:ietf:params:xml:ns:conference-info" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:schema targetNamespace="urn:ietf:params:xml:ns:conference-info" xmlns:tns="urn:ietf:params:xml:ns:conference-info" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:ietf:params:xml:ns:conference-info" elementFormDefault="qualified" attributeFormDefault="unqualified">
<!-- <!--
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="conf-ids" type="conf-ids-type" minOccurs="0" maxOccurs="1" />
<xs:element name="policy-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="policy-ids" type="policy-ids-type" minOccurs="0" maxOccurs="1" />
<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>
skipping to change at page 14, line 9 skipping to change at page 16, line 26
<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" />
</xs:complexType> </xs:complexType>
<xs:complexType name="conf-ids-type">
<xs:sequence>
<xs:element name="conf-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:anyAttribute />
</xs:complexType>
<xs:complexType name="policy-ids-type">
<xs:sequence>
<xs:element name="policy-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
<xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" />
</xs:sequence>
<xs:anyAttribute />
</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:element name="info" type="xs:string" minOccurs="0" />
<xs:element name="label" type="xs:string" minOccurs="0" />
<xs:element name="dialog-id" type="xs:anyURI" 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="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" />
skipping to change at page 15, line 26 skipping to change at page 18, line 22
<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">
<status>on-hold</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">
<status>on-hold</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 uri="sip:barbara@example.com">
<user uri="sip:bill@example.com"> <user uri="sip:bill@example.com">
</sidebar> </sidebar>
<conf-ids>
<conf-uri>tel:+18005671234</conf-uri> <conf-uri>tel:+18005671234</conf-uri>
<conf-uri>h323:conf545@example.com</conf-uri> <conf-uri>h323:conf545@example.com</conf-uri>
</conf-ids>
</conference-info> </conference-info>
This conference currently has three users, two of which are in a This conference currently has three users, two of which are in a
sidebar conversation. The conference is being recorded. There are sidebar conversation. The conference is being recorded. There are
additional means to join the conference either by phone using tel URI additional means to join the conference either by phone using tel URI
[14] or by H.323 protocol using h323 URL [13]. [14] or by H.323 protocol using H.323 URL [12].
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.
Since a focus provides participants identity information using this
event package, participant privacy needs to be taken into account. A
focus MUST support requests by participants for privacy. Privacy can
be indicated by the conference policy - for every participant or
select participants. It can also be indicated in the session
signaling. In SIP this can be done using the Privacy header field
described in RFC 3323 [8]. For a participant requesting privacy, no
identity information SHOULD be revealed by the focus such as a URI
(e.g. the Address of Record, Contact, or GRUU). For these cases,
the anonymous URI generation method outlined in section "User
Element" of this document MUST be followed.
6. IANA Considerations 6. IANA Considerations
This document registers a SIP event package, a new MIME type, This document registers a SIP event package, a new MIME type,
application/conference-info+xml, a new XML namespace, and a new XML application/conference-info+xml, a new XML namespace, and a new XML
schema. schema.
6.1 conference Event Package Registration 6.1 conference Event Package Registration
This specification registers an event package, based on the This specification registers an event package, based on the
registration procedures defined in RFC 3265 [2]. The following is the registration procedures defined in RFC 3265 [7]. The following is
information required for such a registration: the information required for such a registration:
Package Name: conference Package Name: conference
Package or Template-Package: This is a package. Package or Template-Package: This is a package.
Published Document: RFC XXXX (Note to RFC Editor: Please fill in XXXX Published Document: RFC XXXX (Note to RFC Editor: Please fill in XXXX
with the RFC number of this specification). with the RFC number of this specification).
Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net. Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net.
6.2 application/conference-info+xml MIME Registration 6.2 application/conference-info+xml MIME Registration
MIME media type name: application MIME media type name: application
MIME subtype name: conference-info+xml MIME subtype name: conference-info+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: Same as charset parameter application/xml as Optional parameters: Same as charset parameter application/xml as
specified in RFC 3023 [7]. specified in RFC 3023 [5].
Encoding considerations: Same as encoding considerations of Encoding considerations: Same as encoding considerations of
application/xml as specified in RFC 3023 [7]. application/xml as specified in RFC 3023 [5].
Security considerations: See Section 10 of RFC 3023 [5] and Section 5
Security considerations: See Section 10 of RFC 3023 [7] and Section 5
of this specification. of this specification.
Interoperability considerations: none. Interoperability considerations: none.
Published specification: This document. Published specification: This document.
Applications which use this media type: This document type has been Applications which use this media type: This document type has been
used to support SIP conferencing applications. used to support SIP conferencing applications.
Additional Information: Additional Information:
Magic Number: None Magic Number: None
File Extension: .cif or .xml File Extension: .cif or .xml
Macintosh file type code: "TEXT" Macintosh file type code: "TEXT"
Personal and email address for further information: Jonathan Personal and email address for further information: Jonathan
Rosenberg, <jdrosen@jdrosen.net> Rosenberg, <jdrosen@jdrosen.net>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: The IETF. Author/Change controller: The IETF.
6.3 URN Sub-Namespace Registration for 6.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info urn:ietf:params:xml:ns:conference-info
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
[6]. [1].
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:conference-info. urn:ietf:params:xml:ns:conference-info.
Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>, Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>,
Jonathan Rosenberg <jdrosen@jdrosen.net>. Jonathan Rosenberg <jdrosen@jdrosen.net>.
XML: XML:
BEGIN BEGIN
<?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"/>
skipping to change at page 19, line 8 skipping to change at page 21, line 32
<h1>Namespace for Conference Information</h1> <h1>Namespace for Conference Information</h1>
<h2>urn:ietf:params:xml:ns:conference-info</h2> <h2>urn:ietf:params:xml:ns:conference-info</h2>
<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p> <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
6.4 XML Schema Registration 6.4 XML Schema Registration
This specification registers a schema, as per the guidelines in in This specification registers a schema, as per the guidelines in in
[6]. [1].
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, Sean Olson, and Alan The authors would like to thank Dan Petrie, Sean Olson, and Alan
Johnston for their comments. Johnston for their comments and inputs.
8. Changes since -02 8. Changes History
o State "muted-by-focus" is added to user's status. 8.1 Changes since -03
o "Constructing Coherent State" section has been updated.
o In order to support partial notifications, two placeholders
"conference-ids" and "policy-ids" (for "conf-uri" and "policy-uri"
elements, correspondingly) are created.
o Discussion and security considerations regarding anonymous
participation have been added.
o Optional elements "dialog-uri", "info" and "label" per media
stream are added.
8.2 Changes since -02
o State "muted-by-focus" is added to user's status.
o Optional conference attribute "recording" is added. o Optional conference attribute "recording" is added.
o Policy URI placeholder (i.e. element "policy-uri") is created. o Policy URI placeholder (i.e. element "policy-uri") is created.
o Example's syntax is corrected.
o ExampleĂs syntax is corrected.
o Optional attribute "cascaded-focus" URI per user is added. o Optional attribute "cascaded-focus" URI per user is added.
o Optional additional conference identifiers (i.e. element o Optional additional conference identifiers (i.e. element
"conf-uri") are added. "conf-uri") are added.
o In order to cover all possible cases, participant's status is o In order to cover all possible cases, participant's status is
expressed using three optional statuses: "status", "joining-mode" expressed using three optional statuses: "status", "joining-mode"
and "disconnection-reason". That is instead of "activity-status", and "disconnection-reason". That is instead of "activity-status",
"history-status" and "is-on-dial-out-list". "history-status" and "is-on-dial-out-list".
9. Changes since -01 8.3 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
subscription to a dialog package of a participant. subscription to a dialog package of a participant.
o Media stream information is aligned with SDP definitions (media o Media stream information is aligned with SDP definitions (media
and proto) and SSRC attribute is added. and proto) and SSRC attribute is added.
o Participant's status is expressed using two optional statuses: o Participant's status is expressed using two optional statuses:
"activity" and "history". Optional "is-on-a-dial-out-list" "activity" and "history". Optional "is-on-a-dial-out-list"
indication is added. indication is added.
o Normative references to XCON work are removed. o Normative references to XCON work are removed.
o Optional sidebar rosters are added. o Optional sidebar rosters are added.
Normative References 9. References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 9.1 Normative References
[1] Mealling, M., "The IETF XML Registry",
draft-mealling-iana-xmlns-registry-05 (work in progress), June
2003.
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [3] Moats, R., "URN Syntax", RFC 2141, May 1997.
Notification", RFC 3265, June 2002.
[3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [4] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999.
[5] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC
3023, January 2001.
[6] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002. Session Initiation Protocol", RFC 3261, June 2002.
[4] Moats, R., "URN Syntax", RFC 2141, May 1997. [7] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002.
[5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999.
[6] Mealling, M., "The IETF XML Registry", [8] Peterson, J., "A Privacy Mechanism for the Session Initiation
draft-mealling-iana-xmlns-registry-05 (work in progress), June Protocol (SIP)", RFC 3323, November 2002.
2003.
[7] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC [9] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne,
3023, January 2001. "Grouping of Media Lines in the Session Description Protocol
(SDP)", RFC 3388, December 2002.
[8] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, [10] 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 9.2 Informative References
[9] Rosenberg, J., "A Framework for Conferencing with the Session [11] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998.
[12] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
Registration", RFC 3508, April 2003.
[13] Rosenberg, J., "A Framework for Conferencing with the Session
Initiation Protocol", Initiation Protocol",
draft-ietf-sipping-conferencing-framework-01 (work in draft-ietf-sipping-conferencing-framework-01 (work in
progress), October 2003. progress), October 2003.
[10] Rosenberg, J. and H. Schulzrinne, "An INVITE Inititiated Dialog [14] Rosenberg, J. and H. Schulzrinne, "An INVITE Inititiated Dialog
Event Package for the Session Initiation Protocol (SIP)", Event Package for the Session Initiation Protocol (SIP)",
draft-ietf-sipping-dialog-package-03 (work in progress), draft-ietf-sipping-dialog-package-04 (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. February 2004.
[12] Handley, M. and V. Jacobson, "SDP: Session Description [15] Koskelainen, P. and H. Khartabil, "Requirements for Conference
Protocol", RFC 2327, April 1998. Policy Control Protocol", draft-ietf-xcon-cpcp-reqs-03 (work in
progress), April 2004.
[13] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
Registration", RFC 3508, April 2003.
[14] Schulzrinne, H., "The tel URI for Telephone Numbers", [16] Rosenberg, J., "Obtaining and Using Globally Routable User
draft-ietf-iptel-tel-rfc2806bis-03 (work in progress), February Agent (UA) URIs (GRUU) in the Session Initiation Protocol
(SIP)", draft-ietf-sip-gruu-01 (work in progress), February
2004. 2004.
[17] Levin, O. and G. Camarillo, "SDP Media Label",
draft-levin-mmusic-sdp-media-label-00 (work in progress),
May 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
 End of changes. 

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