draft-ietf-sipping-conference-package-09.txt   draft-ietf-sipping-conference-package-10.txt 
SIPPING J. Rosenberg SIPPING J. Rosenberg
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: August 24, 2005 H. Schulzrinne Expires: September 26, 2005 H. Schulzrinne
Columbia University Columbia University
O. Levin, Ed. O. Levin, Ed.
Microsoft Corporation Microsoft Corporation
February 20, 2005 March 25, 2005
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-09 draft-ietf-sipping-conference-package-10
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of Section 3 of RFC 3667. By submitting this Internet-Draft, each of Section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 24, 2005. This Internet-Draft will expire on September 26, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2005).
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 used in notifications for this package. The conference package
allows users to subscribe to a conference URI. Notifications are allows users to subscribe to a conference URI. Notifications are
sent about changes in the membership of this conference and sent about changes in the membership of this conference and
optionally about changes in the state of additional conference optionally about changes in the state of additional conference
components. components.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Conference Event Package . . . . . . . . . . . . . . . . . . 5 3. Conference Event Package . . . . . . . . . . . . . . . . . . . 4
3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 4
3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 6 3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5
3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 6 3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5
3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 6 3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 5
3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 7 3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6
3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 7 3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6
3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 7 3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 6
3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 8 3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7
3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 8 3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7
3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . 8 3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7
4. Conference Document . . . . . . . . . . . . . . . . . . . . 8 4. Conference Document . . . . . . . . . . . . . . . . . . . . . 7
4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 8 4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 8 4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 State and Partial Notifications . . . . . . . . . . . . . 9 4.4 Partial Notifications Mechanism . . . . . . . . . . . . . 8
4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 9 4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 9
4.6 Constructing Coherent State Procedure . . . . . . . . . . 10 4.6 Constructing Coherent State Procedure . . . . . . . . . . 9
5. Conference Data . . . . . . . . . . . . . . . . . . . . . . 11 5. Conference Data . . . . . . . . . . . . . . . . . . . . . . . 10
5.1 conference-type . . . . . . . . . . . . . . . . . . . . . 11 5.1 <conference-info> . . . . . . . . . . . . . . . . . . . . 11
5.1.1 conference-description of 5.2 <conference-description> . . . . . . . . . . . . . . . . . 11
conference-description-type . . . . . . . . . . . . . 12 5.2.1 <conf-uris> . . . . . . . . . . . . . . . . . . . . . 12
5.1.2 host-info of host-type . . . . . . . . . . . . . . . . 12 5.2.2 <service-uris> . . . . . . . . . . . . . . . . . . . . 13
5.1.3 conference-state of conference-state-type . . . . . . 12 5.2.3 <maximum-user-count> . . . . . . . . . . . . . . . . . 13
5.1.4 users of users-type . . . . . . . . . . . . . . . . . 12 5.2.4 <available-media> . . . . . . . . . . . . . . . . . . 13
5.1.5 sidebars-by-ref of uris-type . . . . . . . . . . . . . 12 5.3 <host-info> . . . . . . . . . . . . . . . . . . . . . . . 14
5.1.6 sidebar-by-val of conference-type . . . . . . . . . . 12 5.3.1 <display-text> . . . . . . . . . . . . . . . . . . . . 14
5.2 conference-description-type . . . . . . . . . . . . . . . 13 5.3.2 <web-page> . . . . . . . . . . . . . . . . . . . . . . 14
5.2.1 display-text of string type . . . . . . . . . . . . . 13 5.3.3 <uris> . . . . . . . . . . . . . . . . . . . . . . . . 14
5.2.2 subject of string type . . . . . . . . . . . . . . . . 13 5.4 <conference-state> . . . . . . . . . . . . . . . . . . . . 14
5.2.3 free-text of string type . . . . . . . . . . . . . . . 13 5.4.1 <user-count> . . . . . . . . . . . . . . . . . . . . . 14
5.2.4 keywords of keywords-type . . . . . . . . . . . . . . 13 5.4.2 <active> . . . . . . . . . . . . . . . . . . . . . . . 15
5.2.5 conf-uris of uris-type . . . . . . . . . . . . . . . . 13 5.4.3 <locked> . . . . . . . . . . . . . . . . . . . . . . . 15
5.2.6 service-uris of uris-type . . . . . . . . . . . . . . 14 5.5 <users> of <user> . . . . . . . . . . . . . . . . . . . . 15
5.2.7 maximum-user-count of user-count-type . . . . . . . . 14 5.5.1 <display-text> . . . . . . . . . . . . . . . . . . . . 16
5.2.8 available-media of conference-media-type . . . . . . . 14 5.5.2 <associated-aors> . . . . . . . . . . . . . . . . . . 16
5.3 host-type . . . . . . . . . . . . . . . . . . . . . . . . 14 5.5.3 <roles> . . . . . . . . . . . . . . . . . . . . . . . 16
5.3.1 display-text of string type . . . . . . . . . . . . . 15 5.5.4 <language> . . . . . . . . . . . . . . . . . . . . . . 16
5.3.2 web-page of anyURI type . . . . . . . . . . . . . . . 15 5.5.5 <cascaded-focus> . . . . . . . . . . . . . . . . . . . 16
5.3.3 uris of uris-type . . . . . . . . . . . . . . . . . . 15 5.5.6 <endpoint> . . . . . . . . . . . . . . . . . . . . . . 16
5.4 conference-state-type . . . . . . . . . . . . . . . . . . 15 5.6 <endpoint> . . . . . . . . . . . . . . . . . . . . . . . . 17
5.4.1 user-count of user-count-type . . . . . . . . . . . . 15 5.6.1 <display-text> . . . . . . . . . . . . . . . . . . . . 17
5.4.2 active of Boolean type . . . . . . . . . . . . . . . . 15 5.6.2 <referred> . . . . . . . . . . . . . . . . . . . . . . 17
5.4.3 locked of Boolean type . . . . . . . . . . . . . . . . 15 5.6.3 <status> . . . . . . . . . . . . . . . . . . . . . . . 18
5.4.4 active-media of conference-media-type . . . . . . . . 15 5.6.4 <joining-method> . . . . . . . . . . . . . . . . . . . 19
5.5 conference-media-type . . . . . . . . . . . . . . . . . . 16 5.6.5 <joining-info> . . . . . . . . . . . . . . . . . . . . 19
5.5.1 conference-medium-type . . . . . . . . . . . . . . . . 16 5.6.6 <disconnection-method> . . . . . . . . . . . . . . . . 19
5.5.1.1 display-text of string type . . . . . . . . . . . 16 5.6.7 <disconnection-info> . . . . . . . . . . . . . . . . . 20
5.5.1.2 type of string type . . . . . . . . . . . . . . . 16 5.6.8 <media> . . . . . . . . . . . . . . . . . . . . . . . 20
5.5.1.3 label of string type . . . . . . . . . . . . . . . 17 5.6.9 <call-info> . . . . . . . . . . . . . . . . . . . . . 20
5.6 user-type . . . . . . . . . . . . . . . . . . . . . . . . 17 5.7 <media> . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.6.1 display-text of string type . . . . . . . . . . . . . 17 5.7.1 <display-text> . . . . . . . . . . . . . . . . . . . . 21
5.6.2 associated-aors of anyURI type . . . . . . . . . . . . 17 5.7.2 <type> . . . . . . . . . . . . . . . . . . . . . . . . 21
5.6.3 roles of user-roles-type . . . . . . . . . . . . . . . 17 5.7.3 <label> . . . . . . . . . . . . . . . . . . . . . . . 21
5.6.4 language of language type . . . . . . . . . . . . . . 18 5.7.4 <src-id> . . . . . . . . . . . . . . . . . . . . . . . 21
5.6.5 cascaded-focus of anyURI type . . . . . . . . . . . . 18 5.7.5 <status> . . . . . . . . . . . . . . . . . . . . . . . 22
5.6.6 endpoint of endpoint-type . . . . . . . . . . . . . . 18 5.8 <sidebars-by-ref> . . . . . . . . . . . . . . . . . . . . 22
5.7 endpoint-type . . . . . . . . . . . . . . . . . . . . . . 19 5.9 <sidebar-by-val> . . . . . . . . . . . . . . . . . . . . . 22
5.7.1 display-text of string type . . . . . . . . . . . . . 19 6. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.7.2 referred of execution-type . . . . . . . . . . . . . . 19 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.7.3 status of endpoint-status-type . . . . . . . . . . . . 20 7.1 Basic Example . . . . . . . . . . . . . . . . . . . . . . 30
5.7.4 joining-method of joining-type . . . . . . . . . . . . 21 7.2 Rich Example . . . . . . . . . . . . . . . . . . . . . . . 32
5.7.5 joining-info of execution-type . . . . . . . . . . . . 21 8. Security Considerations . . . . . . . . . . . . . . . . . . . 35
5.7.6 disconnection-method of disconnection-type . . . . . . 21 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
5.7.7 disconnection-info of execution-type . . . . . . . . . 22 9.1 conference Event Package Registration . . . . . . . . . . 36
5.7.8 media of media-type . . . . . . . . . . . . . . . . . 22 9.2 application/conference-info+xml MIME Registration . . . . 36
5.7.9 call-info of call-type . . . . . . . . . . . . . . . . 22
5.7.10 media-type . . . . . . . . . . . . . . . . . . . . . 23
5.7.10.1 display-text of string type . . . . . . . . . . 23
5.7.10.2 type of string type . . . . . . . . . . . . . . 23
5.7.10.3 label of string type . . . . . . . . . . . . . . 23
5.7.10.4 src-id of string type . . . . . . . . . . . . . 24
5.7.10.5 status of media-status-type . . . . . . . . . . 24
6. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . 24
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.1 Basic Example . . . . . . . . . . . . . . . . . . . . . . 32
7.2 Rich Example . . . . . . . . . . . . . . . . . . . . . . . 34
8. Security Considerations . . . . . . . . . . . . . . . . . . 38
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . 38
9.1 conference Event Package Registration . . . . . . . . . . 38
9.2 application/conference-info+xml MIME Registration . . . . 39
9.3 URN Sub-Namespace Registration for 9.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 39 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 37
9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 40 9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 38
9.5 URI Purposes Sub-registry Establishment . . . . . . . . . 40 9.5 URI Purposes Sub-registry Establishment . . . . . . . . . 38
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 41 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
11.1 Normative References . . . . . . . . . . . . . . . . . . 41 11.1 Normative References . . . . . . . . . . . . . . . . . . . 39
11.2 Informative References . . . . . . . . . . . . . . . . . 42 11.2 Informative References . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 41
Intellectual Property and Copyright Statements . . . . . . . 45 Intellectual Property and Copyright Statements . . . . . . . . 43
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [7]Events Framework [8] defines The Session Initiation Protocol (SIP) Events Framework [9] defines
general mechanisms for subscribing to, and receiving notifications general mechanisms for subscribing to, and receiving notifications
of, events within SIP networks. It introduces the notion of a of, events within SIP networks. It introduces the notion of a
package, which is a specific "instantiation" of the events framework package, which is a specific "instantiation" of the events framework
for a well-defined set of events. Here, we define an event package for a well-defined set of events. Here, we define an event package
for SIP conferences. This package provides the conference for SIP conferences. This package provides the conference
notification service as outlined in the SIP conferencing framework notification service as outlined in the SIP conferencing framework
[18]. As described there, subscriptions to a conference URI are [19]. As described there, subscriptions to a conference URI are
routed to the focus that is handling the conference. It acts as the routed to the focus that is handling the conference. It acts as the
notifier, and provides clients with updates on conference state. 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 description), conference sidebars, conference statuses and media description), conference sidebars, conference
service URIs, etc. service URIs, etc.
2. Terminology 2. Terminology
skipping to change at page 5, line 36 skipping to change at page 4, line 36
"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, as described in Conferencing Framework [18]. The focus has other, as described in Conferencing Framework [19]. The focus has
sufficient information about the state of the conference to inform sufficient information about the state of the conference to inform
subscribers about it. subscribers about it.
It is possible that a participant in the conference may in fact be It is possible that a participant in the conference may in fact be
another focus. In order to provide a more complete participant list, another focus. In order to provide a more complete participant list,
the focus MAY subscribe to the conference package of the other focus the focus MAY subscribe to the conference package of the other focus
to discover the participant list in the cascaded conference. This to discover the participant list in the cascaded conference. This
information can then be included in notifications by use of the information can then be included in notifications by use of the
<cascaded-focus> element as specified by this package. <cascaded-focus> element as specified by this package.
This section provides the details for defining a SIP-specific event This section provides the details for defining a SIP-specific event
notification package, as specified by RFC 3265 [8]. notification package, as specified by RFC 3265 [9].
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 RFC 3265 carried in the Event and Allow-Events header, as defined in RFC 3265
[8]. [9].
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. A SUBSCRIBE for a conference package MAY be sent without a body.
This implies the default subscription filtering policy. The default This implies the default subscription filtering policy. The default
skipping to change at page 6, line 29 skipping to change at page 5, line 29
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" as defined conference are terminated, with a reason of "noresource" as defined
in RFC 3265 [8]. in RFC 3265 [9].
3.4 NOTIFY Bodies 3.4 NOTIFY Bodies
As described in RFC 3265 [8], the NOTIFY message will contain bodies As described in RFC 3265 [9], the NOTIFY message will contain bodies
that describe the state of the subscribed resource. This body is in that describe the state of the subscribed resource. This body is in
a 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 conference information document. This document describes the state
of 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 5. "application/conference-info+xml" data format described in Section 5.
The subscribe request MAY contain an Accept header field. If no such The subscribe request MAY contain an Accept header field. If no such
skipping to change at page 8, line 36 skipping to change at page 7, line 36
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 Document 4. Conference Document
4.1 Format 4.1 Format
Conference information is an XML document that MUST be well-formed Conference information is an XML document that MUST be well-formed
and valid. It MUST be based on Extensible Markup Language (XML) 1.0 and valid. It MUST be based on Extensible Markup Language (XML) 1.0
and MUST be encoded using UTF-8 [13]. and MUST be encoded using UTF-8 [12].
4.2 Namespace 4.2 Namespace
This specification makes use of XML namespaces for identifying This specification makes use of XML namespaces for identifying
conference information documents and document fragments. The conference information documents and document fragments. The
namespace URI for elements defined by this specification is a URN namespace URI for elements defined by this specification is a URN
[2], using the namespace identifier 'ietf' defined by [5] and [2], using the namespace identifier 'ietf' defined by [6] and
extended by RFC 3688 [14]. This URN is: extended by RFC 3688 [13]. This URN is:
urn:ietf:params:xml:ns:conference-info urn:ietf:params:xml:ns:conference-info
4.3 Versioning 4.3 Versioning
The conference information is described by a hierarchal XML structure The conference information is described by a hierarchal XML structure
with the root element <conference-info>. The root element is the with the root element <conference-info>. The root element is the
only element in the schema that carries meaningful version number for only element in the schema that carries meaningful version number for
all the elements in the document. The whole conference information all the elements in the document. The whole conference information
is associated with this version number. is associated with this version number.
The 'version' attribute MUST be included in the root The 'version' attribute MUST be included in the root
<conference-info> element. <conference-info> element.
4.4 State and Partial Notifications 4.4 Partial Notifications Mechanism
This specification defines a basic partial notifications mechanism by
using a 'state' attribute as described below. This mechanism MUST be
supported by all subscribing clients. Additional general partial
notifications mechanisms can be defined and applied to this package
in the future.
All sub-elements in the <conference-info> hierarchal XML structure All sub-elements in the <conference-info> hierarchal XML structure
can be classified in two groups: those that carry relatively small can be classified in two groups: permissible for partial
amount of data and those that can potentially carry a lot of data. notifications or not. Elements that carry a substantial amount of
During partial notifications, the light elements are updated as data that is subject to frequent changes are permissible for partial
atomic pieces of data. On the other hand, elements that can carry a notifications and have a 'state' attribute attached to them. All
substantial amount of data have the general 'state' attribute future extensions to this schema MUST define which extension elements
attached to them. That is in order to support partial notifications can also use this mechanism. All other elements can be updated as
for their content. atomic pieces of data only.
The 'state' attribute indicates whether the reported information Below is the complete list of elements permissible to use the partial
about the element is "full", "partial" or the element is "deleted" notifications mechanism defined in this specification. (Note that
from the conference state document. The default value of any 'state' future partial notifications mechanisms can potentially be applicable
attribute is "full". to additional elements.)
o Element <conference-info>
o Element <users>
o Element <user>
o Element <endpoint>
o Element <sidebars-by-val>
o Element <sidebars-by-ref>
The 'state' attribute value indicates whether the reported
information about the element is "full", "partial" or the element is
"deleted" from the conference state document. The default value of
any 'state' attribute is "full".
A 'state' attribute of a child element in the document MUST adhere to A 'state' attribute of a child element in the document MUST adhere to
its parent 'state'. It means that if the parent's 'state' is "full", its parent 'state'. It means that if the parent's 'state' is "full",
the state of its children MUST be "full". If the parent's 'state' is the state of its children MUST be "full". If the parent's 'state' is
"partial", the state of its children MAY be either "partial", "full", "partial", the state of its children MAY be either "partial", "full",
or "deleted". or "deleted".
4.5 Element Keys 4.5 Element Keys
The defined XML schema has a property of unique identification among
sub-elements of a common parent, which makes it possible to use the
partial notifications mechanism defined in this document. This
property is achieved by defining a key to each sub-element that can
appear multiple times under the common parent.
In the context of this specification, the element key is the set of In the context of this specification, the element key is the set of
mandatory attributes or sub-elements of the element. The key value mandatory attributes or sub-elements of an element. The key value
MUST be unique for the element among its siblings of the same type. MUST be unique for the element among its siblings of the same type.
In a partial notification event it must be possible to uniquely In the context of this specification, the comparison rules for keys
identify each sub-element among others of the same type under a of type xs:anyURI are byte-by-byte (including all URI parameters that
common parent element. In order to achieve this property, all can be included with the URI).
sub-elements, with possible multiple appearances under a common
parent (which has the attribute 'state') have keys defined to them.
Below is the list of the elements with their keys as defined by this Below is the list of elements (subject to partial notifications of
their parent elements) with their keys as defined by this
specification: specification:
o Elements <conference-info> and <user> use as the key 'entity' o Element <user> uses as the key 'entity'
o Element <endpoint> uses as the key 'entity' and optionally o Element <endpoint> uses as the key 'entity'
'call-id'
o Element <media> uses as the key 'id' o Element <media> uses as the key 'id'
o Sub-element <entry> of uris-type contained in elements <conf-uris> o Element <entry> (child to <sidebars-by-val>) uses as the key
and <service-uris> uses as the key <uri> 'entity'
o Elements <available-media> and <active-media> of o Element <sidebars-by-ref> uses as the key <uri>
conference-media-type use as the key 'id'
o Elements <maximum-user-count> and <user-count> of count-type use
as the key 'role'
o Sub-element <entry> of conference-type contained in element
<sidebars-by-val> uses as the key 'entity'
o Elements <associated-uris> and <sidebars-by-ref> of uris-type use
as the key <uri>
4.6 Constructing Coherent State Procedure 4.6 Constructing Coherent State Procedure
A conference package subscriber locally maintains a local version A conference package subscriber maintains a local version number, a
number, a local element for each element in the schema, and a table local element for each element in the schema, and a table for each
for each element with key(s) in the schema. element with its key as defined above.
For first time a NOTIFY with a "full" document is received (as The first time a NOTIFY with a "full" document is received (as
indicated by the value of the 'state' attribute in the indicated by the value of the 'state' attribute in the
<conference-info> element), the conference package subscriber MUST <conference-info> element), the conference package subscriber MUST
set the local 'version' number to the value of the 'version' set the local 'version' number to the value of the 'version'
attribute from the received <conference-info> and populate local data attribute from the received <conference-info> and populate local data
with the received information. with the received information.
Each time a new NOTIFY is received, the value of the local version Each time a new NOTIFY is received, the value of the local version
number and the value of the 'version' attribute in the new received number and the value of the 'version' attribute in the new received
document are compared. If the value in the document is equal or less document are compared. If the value in the document is equal or less
than the local version, the document is discarded without processing. than the local version, the document is discarded without processing.
skipping to change at page 10, line 45 skipping to change at page 10, line 12
state, the conference package subscriber MUST set the local 'version' state, the conference package subscriber MUST set the local 'version'
number to the value of the 'version' attribute from the received number to the value of the 'version' attribute from the received
<conference-info> and replace the local information with the received <conference-info> and replace the local information with the received
document. Receiving "deleted" state means that the conference ceased document. Receiving "deleted" state means that the conference ceased
to exist and the subscriber SHOULD terminate the subscription by to exist and the subscriber SHOULD terminate the subscription by
sending the SUBSCRIBE with Expires = 0. sending the SUBSCRIBE with Expires = 0.
Otherwise (i.e. if the received NOTIFY contains "partial" state), if Otherwise (i.e. if the received NOTIFY contains "partial" state), if
the 'version' number in the received document is more than one number the 'version' number in the received document is more than one number
higher than the previous local version number, the subscriber MUST higher than the previous local version number, the subscriber MUST
generate a refresh request to trigger a full state notification. If generate a subscription refresh request to trigger a full state
the 'version' number in the document is one higher than the local notification. If the 'version' number in the document is one higher
version number, the local version number is increased by one and the than the local version number, the local version number is updated
document is used to update the local content as described below. accordingly and the document is used to update the local content as
described below.
For each sub-element of the <conference-info> element in the received For each sub-element of the <conference-info> element in the received
document, document,
1. If the element contains "full" state, the whole local element 1. If the element contains "full" state, the whole local element
content is flushed and repopulated from the document. content is flushed and repopulated from the document.
2. Otherwise, if the element contains "deleted" state, the whole 2. Otherwise, if the element contains "deleted" state, the whole
element MUST be removed from the local content. element MUST be removed from the local content.
3. Otherwise, if the element contains "partial" state: 3. Otherwise, if the element contains "partial" state:
3.1 For elements with keys, the subscriber compares the keys received 3.1 For elements with keys, the subscriber compares the keys received
in the update with the keys in the local tables. in the update with the keys in the local tables.
skipping to change at page 11, line 33 skipping to change at page 11, line 5
non-atomic element received in the schema with either no 'state' non-atomic element received in the schema with either no 'state'
attribute included or the state attribute is set to "full", the attribute included or the state attribute is set to "full", the
element is replaced with the new information as a whole. element is replaced with the new information as a whole.
3.3 For each non-atomic element with the state attribute set to 3.3 For each non-atomic element with the state attribute set to
"partial", the algorithm is applied recursively starting from step "partial", the algorithm is applied recursively starting from step
3.1. 3.1.
5. Conference Data 5. Conference Data
A conference information document begins with the root element tag 5.1 <conference-info>
<conference-info> of conference-type. Sections below describe the
complex types composing the hierarchal conference-type. The full XML
schema is defined in Section 6.
5.1 conference-type A conference information document begins with the root element tag
<conference-info> of conference-type.
This type defines the following attributes: The following attributes are defined for <conference-info>:
entity: This attribute contains the conference URI that identifies entity: This attribute contains the conference URI that identifies
the conference being described in the document. the conference being described in the document.
state: This attribute indicates whether the document contains the state: This attribute indicates whether the document contains the
whole conference information ("full"), only the information that whole conference information ("full"), only the information that
has changed since the previous document ("partial"), or the has changed since the previous document ("partial"), or the
conference ceased to exist ("deleted"). For more details see conference ceased to exist ("deleted"). For more detail see
Section 4. Section 4.
version: This attribute allows the recipient of conference version: This attribute allows the recipient of conference
information documents to properly order them and it MUST be information documents to properly order them and it MUST be
included when used in the root <conference-info> element. Version included when used in the root <conference-info> element. Version
number is a 32 bit monotonically increasing integer scoped within number is a 32 bit monotonically increasing integer scoped within
a subscription. A server MUST increment the version number by one a subscription. A server MUST increment the version number by one
for each new partial notification being sent to a subscriber. for each new partial notification being sent to a subscriber.
The conference-type defines an extendable sequence of child elements. The <conference-info> element is comprised of
A "full" conference document MUST at least include the following <conference-description>, <host-info>, <conference-state>, <users>,
sub-elements: <conference-description>, <conference-state>, and <sidebar-by-ref> and <sidebars-by-val> child elements. A "full"
<users>. conference document MUST at least include the
<conference-description> and <users> child elements.
The child elements are described in details below:
5.1.1 conference-description of conference-description-type
This element contains conference information that is derived from
system conference policies, is set before the conference activation,
and is rarely changed during the conference lifetime.
5.1.2 host-info of host-type
This element contains information about the entity that hosts the
conference. This information is set before the conference
activation, and is rarely changed during the conference lifetime,
unless the whole conference is moved to be hosted by another entity.
5.1.3 conference-state of conference-state-type
This element contains the dynamic information about the current state
of the conference.
5.1.4 users of users-type
This element can contain an unbounded number of <user> sub-elements
of user-type each containing the information about a participant in
the conference.
5.1.5 sidebars-by-ref of uris-type
This element contains <entry> sub-elements of uri-type which provide
pointers to sidebar information through sidebar URIs. The recipient
of the information can then subscribe to sidebar information
independently from the main conference package subscription.
5.1.6 sidebar-by-val of conference-type
This element provides sidebar information as a part of the main Following sections describe these elements in detail. The full XML
conference package information. schema is provided in Section 6.
5.2 conference-description-type 5.2 <conference-description>
This type defines the 'state' attribute which can contain the values The <conference-description> element describes the conference as a
"full", "partial", or "deleted". whole.
This type defines an extendable sequence of the following child The child elements <display-text>, <subject>, <free-text>, and
elements: <keywords> are used to describe the conference content:
5.2.1 display-text of string type <display-text>: Contains a text suitable for human consumption and
directory listing
This element contains text description of the conference. <subject>: Contains the subject of the conference
<free-text>: Contains an additional longer description of the
conference
5.2.2 subject of string type <keywords>: Contains a list of comma-separated keywords that can be
used by search engines to better classify the conference
This element contains the subject of the conference. Additional child elements <conf-uris> and <service-uris> are used to
describe the conference-related URIs; <maximum-user-count> and
<available-media> are used to describe the overall characteristics.
5.2.3 free-text of string type This information is typically derived from the system conference
policies, is set before the conference activation, and is rarely
changed during the conference lifetime.
This element contains free form text about the conference. The following sections describe the remaining elements in more
detail. Other sub-elements can extend <conference-description> in
the future.
5.2.4 keywords of keywords-type 5.2.1 <conf-uris>
This element contains a list of words that can be used by automatic This element is a set of <entry> child elements - each containing the
search engines to better classify the conference. URI to be used in order to access the conference by different
signaling means. The value of the URI MUST be unique in the
conference context and is included in the <uri> sub-element.
5.2.5 conf-uris of uris-type Each <entry> can contain additional optional information useful to
the participant when accessing the conference.
This element contains a set of <entry> sub-elements - each containing An <entry> element MAY contain the <display-text> sub-element that
the information about an additional conference URI that this provides a textual description meant for human consumption.
conference can be accessed by. The value of the URI is included in
the <uri> sub-element and its description MAY be included in the
<display-text> sub-element.
The purpose of the URI SHOULD be included in the <purpose> Each <entry> element SHOULD contain a <purpose> sub-element that
sub-element. The currently defined <purpose> values to be used with describes what happens when accessing the URI. The currently defined
the <conf-uris> are: <purpose> values to be used with the <conf-uris> are:
participation: Indicates that dialing into this URI will bring the participation: Accessing a URI with this <purpose> will bring the
party into the conference party into the conference
streaming: Indicates that "listening" to this URI will provide the streaming: Accessing a URI with this <purpose> will commence
conference live content streaming the conference, but not allow active participation
Examples of suitable URI schemes include sip: and sips: [8], h323:
[18], and tel: [17] URIs. The rtsp [14] URI is suitable for
streaming.
Future extensions to this schema may define new values and register Future extensions to this schema may define new values and register
them with IANA under the registry established by this specification. them with IANA under the registry established by this specification.
Examples of such URIs include sip: / sips: [7], h323: [17], and tel: 5.2.2 <service-uris>
[16] URIs.
5.2.6 service-uris of uris-type This element describes auxiliary services available for the
conference. Like <conference-uris>, this element contains a set of
<entry> child elements - each containing the URI to be used in order
to access different services available for the particular conference.
The value of the URI MUST be unique in the conference context and is
included in the <uri> sub-element.
This element contains a set of <entry> sub-elements - each containing An <entry> element MAY contain the <display-text> sub-element that
the URI to be used in order to access different services available provides a textual description meant for user consumption.
for the particular conference. The value of the URI is included in
the <uri> sub-element and its description MAY be included in the
<display-text> sub-element.
The purpose of the URI SHOULD be included in the <purpose> Each <entry> element SHOULD contain a <purpose> sub-element. The
sub-element. The currently defined <purpose> values to be used with currently defined <purpose> values to be used with the <service-uris>
the <service-uris> are: are:
web-page: Indicates the web page containing the additional web-page: Indicates the web page containing the additional
information about the conference information about the conference
recording: Indicates the link at which the recorded conference recording: Indicates the link at which the recorded conference
context can be retrieved context can be retrieved
event: Indicates the URI to which the subscription to the conference event: Indicates the URI to which the subscription to the conference
event package needs to be performed event package needs to be performed. This would typically be the
conference URI of the main conference
Future extensions to this schema may define new values and register Future extensions to this schema may define new values and register
them with IANA under the registry established by this specification. them with IANA under the registry established by this specification.
5.2.7 maximum-user-count of user-count-type 5.2.3 <maximum-user-count>
This element, if used, specifies the maximum number of users This element, if used, specifies the maximum number of users
permitted in the conference and SHOULD include the counter for all permitted in the conference.
participants in the conference in total by populating the attribute
'role' with value "any". Counters for users with specific roles MAY
be additionally provided.
5.2.8 available-media of conference-media-type
This element contains information about the media streams with their
types available to the participants in the conference. The entries
in the <available-media> container are of conference-medium-type and
are indexed by attribute 'id'.
5.3 host-type
This type defines the 'state' attribute which can contain the values
"full", "partial", or "deleted".
This type defines an extendable sequence of the following child
elements:
5.3.1 display-text of string type
This element contains display text information about the entity
hosting the conference.
5.3.2 web-page of anyURI type
This element contains a web page URI about the user hosting the
conference.
5.3.3 uris of uris-type
The <entity> sub-element contains additional URIs pointing to the
conference host.
5.4 conference-state-type
This type defines the 'state' attribute which can contain the values 5.2.4 <available-media>
"full", "partial", or "deleted".
This type defines an extendable sequence of the following child This element contains a sequence of <entry> child elements of
elements. conference-medium-type, each being indexed by the attribute 'label'.
5.4.1 user-count of user-count-type The 'label' attribute is the media stream identifier being assigned
by the conferencing server such as its value is unique in the
<conference-info> context. The value of this attribute MAY
correspond to the SDP "label" media attribute defined in [22].
This element is used to specify the current number of users in the Each <entry> describes a single media stream available to the
conference. The number SHOULD be provided for all participants in participants in the conference and contains the following
total by populating the <role> sub-element with value "any". information:
Additionally counters for users with certain roles in the conference
MAY be separately provided.
5.4.2 active of Boolean type <display-text> This element contains the display text for the media
stream.
This element says whether the conference is currently active or not. <type> This element contains the media type of the media stream. The
A conference is active if dialing into one of the <conf-uris> results value of this element MUST be one of the values registered for
in successful establishment of a call signaling session between the "media" of SDP [3] and its later revision(s).
dialed user and the conference focus.
5.4.3 locked of Boolean type <status> This element indicates the status in both directions of the
media stream and has the values "sendrecv", "sendonly",
"recvonly", or "inactive" as defined in SDP [3] and its later
revision(s). Note that value specifies the direction from the
participant's point of view.
This element contains information about whether the conference is 5.3 <host-info>
currently locked. In this context, "locked" means that the
conference roster can not be added to (although participants may
leave or be removed from the conference).
5.4.4 active-media of conference-media-type This element contains information about the entity hosting the
conference. This information is set before the conference
activation, and is rarely changed during the conference lifetime,
unless the whole conference is moved to be hosted by another entity.
The host information is comprised of the following elements:
This element contains information about the media streams being 5.3.1 <display-text>
currently active in the conference, which is a subset of those listed
in the <available-media> container. The entries in the
<active-media> container are of conference-medium-type and are
indexed by attribute 'id'.
Note, that correlation between media streams in both containers is This element contains display text describing the entity hosting the
achieved by matching the values of <label> sub-elements element conference.
regardless the position of each media entry (i.e. its 'id' value) in
the container.
5.5 conference-media-type 5.3.2 <web-page>
This type defines a sequence of <entry> child elements, each of This element contains a URI of a web page describing either the
conference-medium-type. conference service or the user hosting the conference.
This type defines the 'state' attribute which can contain the values 5.3.3 <uris>
"full", "partial", or "deleted". This attribute indicates whether
the element of conference-media-type contains all existing entries
("full"), only the entries that have changed since the previous
notification ("partial"), or that the included entries have been
deleted from the conference document ("deleted").
This type defines an extendable sequence of the following child This element can contain additional (to the conference URI) URIs
elements. pointing to the conference host.
5.5.1 conference-medium-type 5.4 <conference-state>
This type defines the 'id' attribute, which is the media stream By including this element in the conference document, the server can
identifier being generated by the notification server such as its inform the subscribers about the changes in the overall conference
value is unique among all entries in the parent container. This information. The <conference-state> child elements are described
attribute is the key to identify media streams in the container. below.
Note, that the entries can be added and deleted on dynamic basis
during the conference and the changes being reported in the
conference state notifications.
This type defines an extendable sequence of the following child 5.4.1 <user-count>
elements.
5.5.1.1 display-text of string type This element contains the current number of users in the conference.
This element contains the display text for the media stream. 5.4.2 <active>
5.5.1.2 type of string type This Boolean element says whether the conference is currently active
or not. A conference is active if dialing into one of the
<conf-uris> results in successful establishment of a call signaling
session between the dialed user and the conference focus.
This element contains the media type of the media stream. The value 5.4.3 <locked>
of this element MUST be one of the values registered for "media" of
SDP [3] and its later revision(s).
5.5.1.3 label of string type This Boolean element says whether the conference is currently locked
or not. In this context, "locked" means that the conference roster
can not be added to (although participants may leave or be removed
from the conference).
The element <label> carries a unique identifier for this stream among 5.5 <users> of <user>
all streams in the conference and is assigned by the focus. The
value of this element corresponds to the SDP "label" media attribute
defined in [21].
5.6 user-type The <users> element is a container of <user> child elements, each
describing a single participant in the conference.
This type defines the following attributes: The following attributes are defined for <user> element:
entity: This attribute contains the URI for the user in the entity: This attribute contains the URI for the user in the
conference. This is a logical identifier, which corresponds to conference. This is a logical identifier, which corresponds to
the authenticated identity of the participant. The 'entity' the call signaling authenticated identity of the participant. The
attribute MUST be unique in the user element list because it is 'entity' value MUST be unique among all participants in the
used as the key in partial notifications about users' state. An conference. If for some participants, the focus decides to not
anonymous participant in a conference SHOULD be represented by an revealing this information (due to local policies or security
anonymous URI generated by the focus. For multiple anonymous reasons, for example), the host portion of the user URI MUST use
participants, the focus must ensure that each anonymous URI is the .invalid top level domain (TLD) according to definitions of
unique. The guidelines for generating anonymous URIs in RFC 3323 RFC 2606 [5]. The focus also MUST construct the user portion of
[9] should be followed. For example, the URI such as the URI is unique among all participants of the
same domain. For example,
"Anonymous1" <sip:anonymous1@anonymous.invalid> "Anonymous1" <sip:anonymous1@anonymous.invalid>
could be used for a participant requesting privacy. could be used for a participant requesting privacy in accordance
with the guidelines for generating anonymous URIs of RFC 3323
[15].
state: This attribute indicates whether the document contains the state: This attribute indicates whether the document contains the
whole conference information ("full"), only the information that whole user information ("full"), only the information that has
has changed since the previous document ("partial"), or the changed since the previous document ("partial"), or the user was
conference ceased to exist ("deleted"). removed from the conference ("deleted").
This type defines an extendable sequence of the following child The following child elements are defined for <user> element:
elements.
5.6.1 display-text of string type 5.5.1 <display-text>
This element contains the display text for the user. This element is used to display the user friendly name in the
conference.
5.6.2 associated-aors of anyURI type 5.5.2 <associated-aors>
This element contains associated URIs of the user. Usually this This element contains associated URIs of the user. Usually this
information will be manually provided by a system administrator information will be manually provided by a system administrator
showing the logical association between signaling entities otherwise showing the logical association between signaling entities otherwise
independent. independent.
5.6.3 roles of user-roles-type 5.5.3 <roles>
This element contains the roles of the user. This element is used to display the roles of the user in the
conference.
5.6.4 language of language type 5.5.4 <language>
This element contains the language preference of the user. This This element contains the language preference of the user. This
information can be automatically learned via call signaling or be information can be automatically learned via call signaling or be
manually set per participant. manually set per participant.
5.6.5 cascaded-focus of anyURI type 5.5.5 <cascaded-focus>
This element contains a conference URI (different from the main This element contains a conference URI (different from the main
conference URI) for users that are connected to the main conference conference URI) for users that are connected to the main conference
as a result of focus cascading. In accordance with the SIP as a result of focus cascading. In accordance with the SIP
conferencing framework [18], this package allows for representation conferencing framework [19], this package allows for representation
of peer-to-peer (i.e. "flat") focus cascading only. The actual of peer-to-peer (i.e. "flat") focus cascading only. The actual
cascading graph can not be deduced from the information provided in cascading graph can not be deduced from the information provided in
the package alone. Advanced applications can construct the graph by the package alone. Advanced applications can construct the graph by
subscribing to both this package and the Dialog Package [19] of each subscribing to both this package and the Dialog Package [20] of each
cascaded focus and correlating the relevant information. cascaded focus and correlating the relevant information.
5.6.6 endpoint of endpoint-type 5.5.6 <endpoint>
This element contains information about an endpoint of the parent
<user>. The <endpoint> element can have unbounded number of
appearances for each user participating in the conference.
The first mandatory key 'entity' of an <endpoint> specifies one of By including one or more <endpoint> elements under a parent <user>
the user devices. Potentially, each device can establish multiple element, the server can provide the desired level of details
call signaling sessions with the conference focus simultaneously. (including the state, media streams, and access information) about
The secondary optional key 'call-id' can be included by the the user's devices and signaling sessions taking part in the
notification server in order to provide status information for each conference.
call signaling session of the endpoint individually. Each subscriber
MUST be prepared to receive under a <user> multiple <endpoint>
elements with the same 'entity' value and different 'call-id' values.
In a conferencing system where authentication is performed per In a conferencing system where authentication is performed per
endpoint (rather than per user), a focus is not necessarily aware of endpoint (rather than per user), the focus can be unaware of the
the logical association of multiple endpoints under a common user. logical association of multiple endpoints under a common user. In
In this case, the focus would arrange the endpoints as belonging to this case, each endpoint will appear as a separate <user> with its
separate users in the conference document. Note, that typically in own <endpoint> sub-element(s) in the conference document.
this case, a <user> would contain a single <endpoint> with their
'entity' attributes having the same value.
In a different case, due to privacy concerns for a participant, a In a different case, the focus may choose to shield the information
focus may choose to shield the information about the participant's about the participant's multiple endpoints and signaling sessions
multiple endpoints from the third-party subscribers. To do so, the from other subscribers altogether (due to privacy policies, for
focus MAY aggregate the multiple endpoints' information into a single example). To do so, the focus MAY aggregate the multiple signaling
<endpoint> element under the participant's <user>. Note, that in sessions' information under a single <endpoint> element. Note that
this case the notification server can still include the secondary in this case, the detailed call signaling information (represented by
'call-id' key and provide the information for each call signaling <call-info> sub-element) will not be included.
session individually.
5.7 endpoint-type 5.6 <endpoint>
This type defines the following attributes: This section describes the <endpoint> element in more detail.
entity: The attribute contains the endpoint URI for the user in the The following attributes are defined for <endpoint> element:
conference. In SIP terms, this is the Contact URI or GRUU. The
'entity' attribute MUST be unique in the endpoint element list
because it is used as the key in partial notifications about
users' endpoints. An endpoint belonging to an anonymous
participant in a conference SHOULD be represented by an anonymous
URI generated by the focus. For multiple anonymous endpoints, the
focus must ensure that each anonymous URI is unique. The
guidelines for generating anonymous URIs in RFC 3323 [9] should be
followed.
call-id: This attribute is optional and its usage is a subject to the entity: The server MUST generate the 'entity' key for each <endpoint>
server's policy per subscriber. The value of this attribute is a element included under the parent <user>, such as its value is
numeric index, which is unique for each call signaling session of unique in the user context. In SIP terms, this can be the Contact
the parent endpoint. This attribute is used when the server needs URI, GRUU, etc.
to provide call signaling information for each signaling session
(also known as a call or a dialog) between the endpoint and the
focus individually. If 'call-id' is not included, it means that
the server chose providing call signaling status of the <endpoint>
collectively for (potentially multiple) call signaling sessions
between the endpoint and the conference focus.
state: This attribute indicates whether the element contains the state: This attribute indicates whether the element contains the
whole endpoint information ("full"), only the information that has whole endpoint information ("full"), only the information that has
changed since the previous document ("partial"), or the endpoint changed since the previous document ("partial"), or the endpoint
has been deleted from the conference ("deleted"). has been removed from the conference ("deleted").
This type defines an extendable sequence of the following child The following child elements are defined for <endpoint> element:
elements.
5.7.1 display-text of string type 5.6.1 <display-text>
This element contains the display text for the endpoint. This element contains the display text for the endpoint.
5.7.2 referred of execution-type 5.6.2 <referred>
This element contains information about the user who's action This element contains information about the user who's action
resulted in this endpoint being brought into the conference (e.g. resulted in this endpoint being brought into the conference (e.g.
the SIP user identified by this URI sent a REFER to the focus). It the SIP user identified by this URI sent a REFER to the focus). It
can contain the following sub-elements: can contain the following sub-elements:
when: This element contains the date and time that the endpoint was when: This element contains the date and time that the endpoint was
referred to the conference and SHOULD be expressed in Coordinated referred to the conference and SHOULD be expressed in Coordinated
Universal Time (UTC) format. Universal Time (UTC) format.
reason: This element contains the reason the endpoint was referred to reason: This element contains the reason the endpoint was referred to
the conference. the conference.
by: This element contains the URI of the entity who caused the by: This element contains the URI of the entity who caused the
endpoint to be referred to the conference. endpoint to be referred to the conference.
5.7.3 status of endpoint-status-type 5.6.3 <status>
This element contains the status of the endpoint, and can assume the This element contains the status of the endpoint, and can assume the
following values: following values:
connected: The endpoint is a participant in the conference. connected: The endpoint is a participant in the conference.
Depending on the media policies, he/she can send and receive media Depending on the media policies, he/she can send and receive media
to and from other participants. to and from other participants.
disconnected: The endpoint is not a participant in the conference and disconnected: The endpoint is not a participant in the conference and
no active dialog exists between the endpoint and the focus. no active dialog exists between the endpoint and the focus.
on-hold: Active SIP dialog exists between an endpoint and a focus, on-hold: Active signaling dialog exists between an endpoint and a
but endpoint is "on-hold" for this conference, i.e. neither focus, but endpoint is "on-hold" for this conference, i.e.
he/she is "hearing" the conference mix, nor is his/her media being neither he/she is "hearing" the conference mix, nor is his/her
mixed in the conference. As an example, the endpoint has asked to media being mixed in the conference. As an example, the endpoint
join the conference using SIP, but his/her participation is has asked to join the conference using SIP, but his/her
pending based on moderator approval. In the meantime he/she is participation is pending based on moderator approval. In the
hearing music-on-hold or some other kind of related content. meantime he/she is hearing music-on-hold or some other kind of
related content.
muted-via-focus: Active SIP dialog exists between an endpoint and a muted-via-focus: Active signaling dialog exists between an endpoint
focus and the endpoint can "listen" to the conference, but and a focus and the endpoint can "listen" to the conference, but
endpoint's media is not being mixed into the conference. Note endpoint's media is not being mixed into the conference. Note
that sometimes a subset of endpoint media streams can be muted by that sometimes a subset of endpoint media streams can be muted by
focus (such as poor quality video) while others (such as voice or 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 IM) can still be active. In this case, it is RECOMMENDED that the
"aggregated" endpoint connectivity <status> reflects the status of "aggregated" endpoint connectivity <status> reflects the status of
the most active media. the most active media.
pending: Endpoint is not yet in the session, but it is anticipated pending: Endpoint is not yet in the session, but it is anticipated
that he/she will join in the near future. that he/she will join in the near future.
alerting: A PSTN ALERTING or SIP 180 Ringing was returned for the alerting: A PSTN ALERTING or SIP 180 Ringing was returned for the
outbound call, endpoint is being alerted. outbound call, endpoint is being alerted.
dialing-in: Endpoint is dialing into the conference, not yet in the dialing-in: Endpoint is dialing into the conference, not yet in the
roster (probably being authenticated). roster (probably being authenticated).
dialing-out: Focus has dialed out to connect the endpoint to the dialing-out: Focus has dialed out to connect the endpoint to the
conference, but the endpoint is not yet in the roster (probably conference, but the endpoint is not yet in the roster (probably
being authenticated). being authenticated).
disconnecting: Focus is in the process of disconnecting endpoint disconnecting: Focus is in the process of disconnecting the endpoint
(either DISCONNECT or BYE was sent to the endpoint). (e.g., in SIP a DISCONNECT or BYE was sent to the endpoint).
Note that the defined transient statuses (e.g., disconnecting, Note that the defined transient statuses (e.g., disconnecting,
alerting, etc.) could generate a lot of notifications. alerting, etc.) could generate a lot of notifications.
Implementations MAY choose not to generate notifications on these to Implementations MAY choose not to generate notifications on these to
all participants if it will generate too much traffic. all participants if it will generate too much traffic.
5.7.4 joining-method of joining-type 5.6.4 <joining-method>
This element contains method by which the endpoint joined the This element contains method by which the endpoint joined the
conference, and can assume the following values: conference, and can assume the following values:
dialed-in: The endpoint dialed into the conference, i.e. sent INVITE dialed-in: The endpoint dialed into the conference (e.g., in SIP sent
to the focus, which resulted in successful dialog establishment. INVITE to the focus), which resulted in successful dialog
establishment.
dialed-out: The focus has brought the endpoint into the conference by dialed-out: The focus has brought the endpoint into the conference
sending a successful INVITE to the endpoint. (e.g., in SIP by sending a successful INVITE to the endpoint).
focus-owner: The endpoint is the focus for this conference. This focus-owner: The endpoint is the focus for this conference. This
status is used only when a participant's UA acts as a conference status is used only when a participant's UA acts as a conference
focus. focus.
5.7.5 joining-info of execution-type 5.6.5 <joining-info>
This element contains information about how the endpoint joined and This element contains information about how the endpoint joined and
can contain the following sub-elements: can contain the following sub-elements:
when: This element contains the date and time that the endpoint when: This element contains the date and time that the endpoint
joined the conference and SHOULD be expressed in Coordinated joined the conference and SHOULD be expressed in Coordinated
Universal Time (UTC). Universal Time (UTC).
reason: This element contains the reason the endpoint joined the reason: This element contains the reason the endpoint joined the
conference. conference.
by: This element contains the URI of the entity who caused the by: This element contains the URI of the entity who caused the
endpoint to join the conference. endpoint to join the conference.
5.7.6 disconnection-method of disconnection-type 5.6.6 <disconnection-method>
This element contains method by which the endpoint departed the This element contains method by which the endpoint departed the
conference, and can assume the following values: conference, and can assume the following values:
departed: The endpoint sent a BYE, thus leaving the conference. departed: In SIP, the endpoint sent a BYE, thus leaving the
conference.
booted: The endpoint was sent a BYE by the focus, booting him/her out booted: In SIP, the endpoint was sent a BYE by the focus, booting
of the conference. Alternatively, the endpoint tried to dial into him/her out of the conference. Alternatively, the endpoint tried
to conference but was rejected by the focus due to local policy. to dial into to conference but was rejected by the focus due to
local policy.
failed: The server tried to bring the endpoint into the conference, failed: In SIP, the server tried to bring the endpoint into the
but its attempt to contact the specific endpoint resulted in a conference, but its attempt to contact the specific endpoint
non-200 class final response. Alternatively, the endpoint tried resulted in a non-200 class final response. Alternatively, the
to dial into the conference without success due to technical endpoint tried to dial into the conference without success due to
reasons. technical reasons.
5.7.7 disconnection-info of execution-type 5.6.7 <disconnection-info>
This element contains information about the endpoint's departure from This element contains information about the endpoint's departure from
the conference and can contain the following sub-elements: the conference and can contain the following sub-elements:
when: This element contains the date and time that the endpoint when: This element contains the date and time that the endpoint
departed the conference and SHOULD be expressed in Coordinated departed the conference and SHOULD be expressed in Coordinated
Universal Time (UTC). Universal Time (UTC).
reason: This element contains the reason the endpoint departed the reason: This element contains the reason the endpoint departed the
conference. When known and meaningful, it is RECOMMENDED to conference. When known and meaningful, it is RECOMMENDED to
include the information as conveyed/reported by the call signaling include the information as conveyed/reported by the call signaling
in the format defined by RFC 3326 [10]. For example, in the format defined by RFC 3326 [10]. For example,
<reason>Reason: SIP ;cause=415 ;text="Unsupported Media Type"</reason> <reason>Reason: SIP ;cause=415 ;text="Unsupported Media Type"</reason>
by: This element contains the URI of the entity who caused the by: This element contains the URI of the entity who caused the
endpoint to depart the conference. endpoint to depart the conference.
5.7.8 media of media-type 5.6.8 <media>
This element contains information about a media stream of the This element contains information about a single media stream and is
endpoint. The element of the media-type can have an unbounded number included for each media stream being established between the focus
of appearances in the endpoint-type for each media stream of the and the <endpoint>.
endpoint. Note, that if the 'call-id' attribute of the endpoint is
not provided by the server, it is possible that the media streams
listed under the common endpoint were established by separate
signaling sessions (i.e. belong to different "calls" or "dialogs").
5.7.9 call-info of call-type Note that if the <call-info> sub-element of the endpoint is not
included in the document by the server, it is possible that the media
streams listed under the common <endpoint> were established by
separate signaling sessions.
The <call-info> element MAY be used only if the server chose to 5.6.9 <call-info>
explicitly identify each signaling session between the endpoint and
the focus by including the 'call-id' attribute as the <endpoint>
secondary key.
The <call-info> element is used for providing detailed call signaling The <call-info> element provides detailed call signaling information
information for a call being maintained between the endpoint and the for a call being maintained between the participant and the focus.
focus. Note, that privacy policies MUST be consulted before Privacy policies MUST be consulted before revealing this information
revealing this information to third-party participants. to other participants.
The <sip> sub-element contains the SIP dialog identifier of the The <sip> sub-element contains the SIP dialog identifier of the
endpoint's dialog with the focus. The element includes sub-elements endpoint's dialog with the focus. The element includes sub-elements
<display-text>, <call-id>, <to-tag>, <from-tag>. <display-text>, <call-id>, <to-tag>, <from-tag>.
In future, the <call-info> element can be expanded to include call In future, the <call-info> element can be expanded to include call
signaling protocol information for other protocols besides SIP. signaling protocol information for other protocols besides SIP.
5.7.10 media-type 5.7 <media>
This type defines the following attributes:
id: The attribute is the media stream identifier being generated by This section describes the <media> element in more detail.
the notification server such as its value is unique in the
endpoint context. This attribute is the key to identify media
streams which can be added and deleted on dynamic basis during the
conference and the changes being reported in the conference state
notifications.
state: This attribute indicates whether the element contains the A single 'id' attribute is defined for this element. This is the
whole media information ("full"), only the information that has media stream identifier being generated by the server such as its
changed since the previous notification ("partial"), or that the value is unique in the endpoint context. This attribute is the key
media element has been deleted from the conference document to refer to a particular media stream in the conference document.
("deleted").
This type defines an extendable sequence of the following child The following child elements are defined for <media>:
elements.
5.7.10.1 display-text of string type 5.7.1 <display-text>
This element contains the display text for the media stream. This element contains the display text for the media stream.
5.7.10.2 type of string type 5.7.2 <type>
This element contains the media type for the media stream. The value This element contains the media type for the media stream. The value
of this element MUST be one of the values registered for "media" of of this element MUST be one of the values registered for "media" of
SDP [3] and its later revision(s). SDP [3] and its later revision(s).
5.7.10.3 label of string type 5.7.3 <label>
The element <label> carries a unique identifier for this stream among The <label> element carries a unique identifier for this stream among
all streams in the conference and is assigned by the focus. The all streams in the conference and is assigned by the focus. The
value of this element corresponds to the SDP "label" media attribute value of this element corresponds to the SDP "label" media attribute
defined in [21]. defined in [22].
5.7.10.4 src-id of string type 5.7.4 <src-id>
The <src-id> element, if applicable, carries the information about The <src-id> element, if applicable, carries the information about
the actual source of the media. For example, for RTP/RTCP [12] media the actual source of the media. For example, for RTP/RTCP [11] media
streams, the value MUST contain the SSRC value generated by the streams, the value MUST contain the SSRC value generated by the
endpoint for the stream it sends. endpoint for the stream it sends.
When an RTP mixer generates a CSRC list according to RTP/RTCP [12], When an RTP mixer generates a CSRC list according to RTP/RTCP [11],
it 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. A quote from RFC 3550: "An example header of that packet. A quote from RFC 3550: "An example
application is audio conferencing where a mixer indicates all the application is audio conferencing where a mixer indicates all the
talkers whose speech was combined to produce the outgoing packet, talkers whose speech was combined to produce the outgoing packet,
allowing the receiver to indicate the current talker, even though all allowing the receiver to indicate the current talker, even though all
the audio packets contain the same SSRC identifier (that of the the audio packets contain the same SSRC identifier (that of the
mixer)." mixer)."
If an RTP mixer compliant to the above is used, participants can If an RTP mixer compliant to the above is used, participants can
perform an SSRC to user mapping and identify "a current speaker". perform an SSRC to user mapping and identify "a current speaker".
5.7.10.5 status of media-status-type 5.7.5 <status>
The element <status> indicates the status in both directions of the The element <status> indicates the status in both directions of the
media stream and has the values "sendrecv", "sendonly", "recvonly", media stream and has the values "sendrecv", "sendonly", "recvonly",
or "inactive" as defined in SDP [3] and its later revision(s). Note or "inactive" as defined in SDP [3] and its later revision(s). Note
that value specifies the direction from the participant's point of that value specifies the direction from the participant's point of
view. For example, a muted participant's stream will have the value view. For example, a muted participant's stream will have the value
of "recvonly". of "recvonly".
5.8 <sidebars-by-ref>
This element contains a set of <entry> child elements each containing
a sidebar conference URI. The recipient of the information can then
subscribe to sidebar information independently from the main
conference package subscription.
5.9 <sidebar-by-val>
This element contains a set of <entry> child elements each containing
information about a single sidebar. By using this element of
conference-type, the server can include a full or a partial
description of each sidebar (as a sub-conference) in the body of the
main conference document.
6. XML Schema 6. XML 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" />
<!-- <!--
CONFERENCE ELEMENT CONFERENCE ELEMENT
skipping to change at page 25, line 43 skipping to change at page 23, line 39
CONFERENCE DESCRIPTION TYPE CONFERENCE DESCRIPTION TYPE
--> -->
<xs:complexType name="conference-description-type"> <xs:complexType name="conference-description-type">
<xs:sequence> <xs:sequence>
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="subject" type="xs:string" minOccurs="0"/> <xs:element name="subject" type="xs:string" minOccurs="0"/>
<xs:element name="free-text" type="xs:string" minOccurs="0"/> <xs:element name="free-text" type="xs:string" minOccurs="0"/>
<xs:element name="keywords" type="keywords-type" minOccurs="0"/> <xs:element name="keywords" type="keywords-type" minOccurs="0"/>
<xs:element name="conf-uris" type="uris-type" minOccurs="0"/> <xs:element name="conf-uris" type="uris-type" minOccurs="0"/>
<xs:element name="service-uris" type="uris-type" minOccurs="0"/> <xs:element name="service-uris" type="uris-type" minOccurs="0"/>
<xs:element name="maximum-user-count" type="user-count-type" minOccurs="0"/> <xs:element name="maximum-user-count" type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="available-media" type="conference-media-type" minOccurs="0"/> <xs:element name="available-media" type="conference-media-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
HOST TYPE HOST TYPE
--> -->
<xs:complexType name="host-type"> <xs:complexType name="host-type">
<xs:sequence> <xs:sequence>
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="web-page" type="xs:anyURI" minOccurs="0"/> <xs:element name="web-page" type="xs:anyURI" minOccurs="0"/>
<xs:element name="uris" type="uris-type" minOccurs="0"/> <xs:element name="uris" type="uris-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
CONFERENCE STATE TYPE CONFERENCE STATE TYPE
--> -->
<xs:complexType name="conference-state-type"> <xs:complexType name="conference-state-type">
<xs:sequence> <xs:sequence>
<xs:element name="user-count" type="user-count-type" minOccurs="0"/> <xs:element name="user-count" type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="active" type="xs:boolean" minOccurs="0"/> <xs:element name="active" type="xs:boolean" minOccurs="0"/>
<xs:element name="locked" type="xs:boolean" minOccurs="0"/> <xs:element name="locked" type="xs:boolean" minOccurs="0"/>
<xs:element name="active-media" type="conference-media-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
CONFERENCE MEDIA TYPE CONFERENCE MEDIA TYPE
--> -->
<xs:complexType name="conference-media-type"> <xs:complexType name="conference-media-type">
<xs:sequence> <xs:sequence>
<xs:element name="entry" type="conference-medium-type" maxOccurs="unbounded"/> <xs:element name="entry" type="conference-medium-type" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
CONFERENCE MEDIUM TYPE CONFERENCE MEDIUM TYPE
--> -->
<xs:complexType name="conference-medium-type"> <xs:complexType name="conference-medium-type">
<xs:sequence> <xs:sequence>
<xs:element name="display-text" type="xs:string"/> <xs:element name="display-text" type="xs:string"/>
<xs:element name="type" type="xs:string" minOccurs="0"/> <xs:element name="type" type="xs:string" minOccurs="0"/>
<xs:element name="label" type="xs:string" minOccurs="0"/> <xs:element name="status" type="media-status-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="id" type="xs:nonNegativeInteger" use="required"/> <xs:attribute name="label" type="xs:string" use="required"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
URIs TYPE URIs TYPE
--> -->
<xs:complexType name="uris-type"> <xs:complexType name="uris-type">
<xs:sequence> <xs:sequence>
<xs:element name="entry" type="uri-type" maxOccurs="unbounded"/> <xs:element name="entry" type="uri-type" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
skipping to change at page 27, line 36 skipping to change at page 25, line 37
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="purpose" type="xs:string" minOccurs="0"/> <xs:element name="purpose" type="xs:string" minOccurs="0"/>
<xs:element name="modified" type="execution-type" minOccurs="0"/> <xs:element name="modified" type="execution-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
USER COUNT TYPE
-->
<xs:complexType name="user-count-type">
<xs:sequence>
<xs:element name="entry" type="count-type" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/>
</xs:complexType>
<!--
COUNT TYPE
-->
<xs:complexType name="count-type">
<xs:sequence>
<xs:element name="count" type="xs:nonNegativeInteger"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="role" type="xs:string" use="required"/>
<xs:anyAttribute namespace="##other"/>
</xs:complexType>
<!--
KEWORDS TYPE KEWORDS TYPE
--> -->
<xs:simpleType name="keywords-type"> <xs:simpleType name="keywords-type">
<xs:list itemType="xs:string"/> <xs:list itemType="xs:string"/>
</xs:simpleType> </xs:simpleType>
<!-- <!--
USERS TYPE USERS TYPE
--> -->
<xs:complexType name="users-type"> <xs:complexType name="users-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 namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/> <xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
USER TYPE USER TYPE
--> -->
<xs:complexType name="user-type"> <xs:complexType name="user-type">
<xs:sequence> <xs:sequence>
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="associated-aors" type="uris-type" minOccurs="0"/> <xs:element name="associated-aors" type="uris-type" minOccurs="0"/>
skipping to change at page 29, line 23 skipping to change at page 27, line 14
<xs:element name="referred" type="execution-type" minOccurs="0"/> <xs:element name="referred" type="execution-type" minOccurs="0"/>
<xs:element name="status" type="endpoint-status-type" minOccurs="0"/> <xs:element name="status" type="endpoint-status-type" minOccurs="0"/>
<xs:element name="joining-method" type="joining-type" minOccurs="0"/> <xs:element name="joining-method" type="joining-type" minOccurs="0"/>
<xs:element name="joining-info" type="execution-type" minOccurs="0"/> <xs:element name="joining-info" type="execution-type" minOccurs="0"/>
<xs:element name="disconnection-method" type="disconnection-type" minOccurs="0"/> <xs:element name="disconnection-method" type="disconnection-type" minOccurs="0"/>
<xs:element name="disconnection-info" type="execution-type" minOccurs="0"/> <xs:element name="disconnection-info" type="execution-type" minOccurs="0"/>
<xs:element name="media" type="media-type" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="media" type="media-type" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="call-info" type="call-type" minOccurs="0"/> <xs:element name="call-info" type="call-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="entity" type="xs:string"/>
<xs:attribute name="entity" type="xs:anyURI"/>
<xs:attribute name="call-id" type="xs:string" use="optional"/>
<xs:attribute name="state" type="state-type" use="optional" default="full"/> <xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
ENDPOINT STATUS TYPE ENDPOINT STATUS TYPE
--> -->
<xs:simpleType name="endpoint-status-type"> <xs:simpleType name="endpoint-status-type">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="pending"/> <xs:enumeration value="pending"/>
<xs:enumeration value="dialing-out"/> <xs:enumeration value="dialing-out"/>
<xs:enumeration value="dialing-in"/> <xs:enumeration value="dialing-in"/>
<xs:enumeration value="alerting"/> <xs:enumeration value="alerting"/>
<xs:enumeration value="on-hold"/> <xs:enumeration value="on-hold"/>
skipping to change at page 31, line 23 skipping to change at page 29, line 20
<xs:complexType name="media-type"> <xs:complexType name="media-type">
<xs:sequence> <xs:sequence>
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="type" type="xs:string" minOccurs="0"/> <xs:element name="type" type="xs:string" minOccurs="0"/>
<xs:element name="label" type="xs:string" minOccurs="0"/> <xs:element name="label" type="xs:string" minOccurs="0"/>
<xs:element name="src-id" type="xs:string" minOccurs="0"/> <xs:element name="src-id" type="xs:string" minOccurs="0"/>
<xs:element name="status" type="media-status-type" minOccurs="0"/> <xs:element name="status" type="media-status-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="id" type="xs:string" use="required"/> <xs:attribute name="id" type="xs:string" use="required"/>
<xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
MEDIA STATUS TYPE MEDIA STATUS TYPE
--> -->
<xs:simpleType name="media-status-type"> <xs:simpleType name="media-status-type">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="recvonly"/> <xs:enumeration value="recvonly"/>
<xs:enumeration value="sendonly"/> <xs:enumeration value="sendonly"/>
skipping to change at page 32, line 29 skipping to change at page 30, line 29
<uri> http://sharepoint/salesgroup/</uri> <uri> http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose> <purpose>web-page</purpose>
</entry> </entry>
</service-uris> </service-uris>
</conference-description> </conference-description>
<!-- <!--
CONFERENCE STATE CONFERENCE STATE
--> -->
<conference-state> <conference-state>
<user-count> <user-count>33</user-count>
<entry role="any">
<count>33</count>
</entry>
</user-count>
<active-media>
<entry id="1">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
</entry>
</active-media>
</conference-state> </conference-state>
<users> <users>
<!-- <!--
USER USER
--> -->
<user entity="sip:bob@example.com" state="full"> <user entity="sip:bob@example.com" state="full">
<display-text>Bob Hoskins</display-text> <display-text>Bob Hoskins</display-text>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:bob@pc33.example.com"> <endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text> <display-text>Bob's Laptop</display-text>
<status>disconnected</status> <status>disconnected</status>
skipping to change at page 35, line 11 skipping to change at page 33, line 5
</conf-uris> </conf-uris>
<service-uris> <service-uris>
<entry> <entry>
<uri>http://sharepoint/salesgroup/</uri> <uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose> <purpose>web-page</purpose>
</entry> </entry>
<entry> <entry>
<uri>http://quicktime.com/54634/recording.mov</uri> <uri>http://quicktime.com/54634/recording.mov</uri>
<display-text>Quicktime</display-text> <display-text>Quicktime</display-text>
<purpose>recording</purpose> <purpose>recording</purpose>
</entry> </entry>
</service-uris> </service-uris>
<maximum-user-count> <maximum-user-count>100</maximum-user-count>
<entry role="any">
<count>52</count>
</entry>
<entry role="participant">
<count>50</count>
</entry>
</maximum-user-count>
<available-media> <available-media>
<entry id="1"> <entry label="34567">
<display-text>main audio</display-text> <display-text>main audio</display-text>
<type>audio</type> <type>audio</type>
<label>34567</label> <status>sendrecv</status>
</entry> </entry>
<entry id="2"> <entry label="34569">
<display-text>main video</display-text> <display-text>main video</display-text>
<type>video</type> <type>video</type>
<label>34569</label> <status>inactive</status>
</entry> </entry>
</available-media> </available-media>
</conference-description> </conference-description>
<!-- <!--
HOST INFO HOST INFO
--> -->
<host-info> <host-info>
<display-text>Sales Host</display-text> <display-text>Sales Host</display-text>
<web-page>http://sharepoint/salesgroup/hosts/</web-page> <web-page>http://sharepoint/salesgroup/hosts/</web-page>
<uris> <uris>
<entry> <entry>
<uri>sip:sales@example.com</uri> <uri>sip:sales@example.com</uri>
</entry> </entry>
</uris> </uris>
skipping to change at page 35, line 51 skipping to change at page 33, line 40
<uris> <uris>
<entry> <entry>
<uri>sip:sales@example.com</uri> <uri>sip:sales@example.com</uri>
</entry> </entry>
</uris> </uris>
</host-info> </host-info>
<!-- <!--
CONFERENCE STATE CONFERENCE STATE
--> -->
<conference-state> <conference-state>
<user-count> <user-count>32</user-count>
<entry role="any">
<count>33</count>
</entry>
<entry role="participant">
<count>32</count>
</entry>
</user-count>
<active>true</active> <active>true</active>
<locked>false</locked> <locked>false</locked>
<active-media>
<entry id="1">
<type>audio</type>
</entry>
</active-media>
</conference-state> </conference-state>
<!-- <!--
USERS USERS
--> -->
<users> <users>
<user entity="sip:bob@example.com"> <user entity="sip:bob@example.com">
<display-text>Bob Hoskins</display-text> <display-text>Bob Hoskins</display-text>
<associated-aors> <associated-aors>
<entry> <entry>
skipping to change at page 36, line 41 skipping to change at page 34, line 18
</entry> </entry>
</associated-aors> </associated-aors>
<roles> <roles>
<entry>participant</entry> <entry>participant</entry>
</roles> </roles>
<language>en</language> <language>en</language>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:bob@pc33.example.com" call="1"> <endpoint entity="sip:bob@pc33.example.com">
<display-text>Bob's Laptop</display-text> <display-text>Bob's Laptop</display-text>
<referred> <referred>
<when>2005-03-04T20:00:00Z</when> <when>2005-03-04T20:00:00Z</when>
<reason>expert required</reason> <reason>expert required</reason>
<by>sip:mike@example.com</by> <by>sip:mike@example.com</by>
</referred> </referred>
<status>disconnecting</status> <status>disconnecting</status>
<joining-method>dialed-out</joining-method> <joining-method>dialed-out</joining-method>
<joining-info> <joining-info>
<when>2005-03-04T20:00:00Z</when> <when>2005-03-04T20:00:00Z</when>
<reason>invitation</reason> <reason>invitation</reason>
<by>sip:mike@example.com</by> <by>sip:mike@example.com</by>
</joining-info> </joining-info>
<disconnection-method>booted</disconnection-method> <disconnection-method>booted</disconnection-method>
<disconnection-info> <disconnection-info>
<when>2005-03-04T20:00:00Z</when> <when>2005-03-04T20:00:00Z</when>
<reason>bad voice quality</reason> <reason>bad voice quality</reason>
<by>sip:mike@example.com</by> <by>sip:mike@example.com</by>
</disconnection-info> </disconnection-info>
<!-- <!--
CALL INFO CALL INFO
--> -->
skipping to change at page 37, line 27 skipping to change at page 35, line 6
<sip> <sip>
<display-text>full info</display-text> <display-text>full info</display-text>
<call-id>hsjh8980vhsb78</call-id> <call-id>hsjh8980vhsb78</call-id>
<from-tag>vav738dvbs</from-tag> <from-tag>vav738dvbs</from-tag>
<to-tag>8954jgjg8432</to-tag> <to-tag>8954jgjg8432</to-tag>
</sip> </sip>
</call-info> </call-info>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1" state="full"> <media id="1">
<display-text>main audio</display-text> <display-text>main audio</display-text>
<type>audio</type> <type>audio</type>
<label>34567</label> <label>34567</label>
<src-id>432424</src-id> <src-id>432424</src-id>
<status>sendrecv</status> <status>sendrecv</status>
</media> </media>
</endpoint> </endpoint>
</user> </user>
</users> </users>
<!-- <!--
SIDEBARS BY REFERENCE SIDEBARS BY REFERENCE
--> -->
<sidebars-by-ref> <sidebars-by-ref state="partial">
<entry> <entry>
<uri>sips:conf233@example.com; grid=45</uri> <uri>sips:conf233@example.com; grid=45</uri>
<display-text>sidebar with Carol</display-text> <display-text>sidebar with Carol</display-text>
</entry> </entry>
<entry> <entry>
<uri>sips:conf233@example.com; grid=21</uri> <uri>sips:conf233@example.com; grid=21</uri>
<display-text>private sidebar with Peter</display-text> <display-text>private sidebar with Peter</display-text>
</entry> </entry>
</sidebars-by-ref> </sidebars-by-ref>
<!-- <!--
SIDEBARS BY VALUE SIDEBARS BY VALUE
--> -->
<sidebars-by-val> <sidebars-by-val state="partial">
<entry entity="sips:conf233@example.com; grid=77" state="partial"> <entry entity="sips:conf233@example.com; grid=77" state="partial">
<users> <users>
<user entity="sip:bob@example.com" state="partial"></user> <user entity="sip:bob@example.com"></user>
<user entity="sip:mark@example.com" state="partial"></user> <user entity="sip:mark@example.com"></user>
<user entity="sip:dan@example.com" state="partial"></user> <user entity="sip:dan@example.com"></user>
</users> </users>
</entry> </entry>
</sidebars-by-val> </sidebars-by-val>
</conference-info> </conference-info>
8. Security Considerations 8. 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
skipping to change at page 38, line 35 skipping to change at page 36, line 16
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 participant identity information using this Since a focus provides participant identity information using this
event package, participant privacy needs to be taken into account. A event package, participant privacy needs to be taken into account. A
focus MUST support requests by participants for privacy. Privacy can focus MUST support requests by participants for privacy. Privacy can
be indicated by the conference policy - for every participant or be indicated by the conference policy - for every participant or
select participants. It can also be indicated in the session select participants. It can also be indicated in the session
signaling. In SIP this can be done using the Privacy header field signaling. In SIP this can be done using the Privacy header field
described in RFC 3323 [9]. For a participant requesting privacy, no described in RFC 3323 [15]. For a participant requesting privacy, no
identity information SHOULD be revealed by the focus such as a URI identity information SHOULD be revealed by the focus such as a URI
(e.g. the Address of Record, Contact, or GRUU). For these cases, (e.g. the Address of Record, Contact, or GRUU). For these cases,
the anonymous URI generation method outlined in section Section 5.6 the anonymous URI generation method outlined in section Section 5.5
of this document MUST be followed. of this document MUST be followed.
9. IANA Considerations 9. 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, a new XML application/conference-info+xml, a new XML namespace, a new XML
schema, and creates a sub-registry "URI purposes" under the schema, and creates a sub-registry "URI purposes" under the
existing registry: http://www.iana.org/assignments/sip-parameters. existing registry: http://www.iana.org/assignments/sip-parameters.
9.1 conference Event Package Registration 9.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 [8]. The following is registration procedures defined in RFC 3265 [9]. The following is
the 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.
9.2 application/conference-info+xml MIME Registration 9.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 [6] specified in RFC 3023 [7]
Encoding considerations: Same as encoding considerations of Encoding considerations: Same as encoding considerations of
application/xml as specified in RFC 3023 [6] application/xml as specified in RFC 3023 [7]
Security considerations: See Section 10 of RFC 3023 [6] and Section 8 Security considerations: See Section 10 of RFC 3023 [7] and Section 8
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
9.3 URN Sub-Namespace Registration for 9.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
RFC 3688 [14]. RFC 3688 [13].
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"
skipping to change at page 40, line 26 skipping to change at page 38, line 8
<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
9.4 XML Schema Registration 9.4 XML Schema Registration
This specification registers a schema, as per the guidelines in RFC This specification registers a schema, as per the guidelines in RFC
3688 [14]. 3688 [13].
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 6 XML: The XML can be found as the sole content of Section 6
9.5 URI Purposes Sub-registry Establishment 9.5 URI Purposes Sub-registry Establishment
This document instructs the IANA to create a new sub-registry "URI This document instructs the IANA to create a new sub-registry "URI
purposes" under the already existing registry: purposes" under the already existing registry:
http://www.iana.org/assignments/sip-parameters. http://www.iana.org/assignments/sip-parameters.
The purpose of a URI is an XML element, encoded in the conference The purpose of a URI is an XML element, encoded in the conference
event package [RFC XXXX - substitute with the number assigned to this event package [RFC XXXX - substitute with the number assigned to this
draft]. The value of the <purpose> element indicates the intended draft]. The value of the <purpose> element indicates the intended
usage of the URI in the context of the conference event package and usage of the URI in the context of the conference event package and
is defined in sections Section 5.2.5 and Section 5.2.6 of this is defined in sections Section 5.2.1 and Section 5.2.2 of this
specification. specification.
This sub-registry is defined as a table that contains the following This sub-registry is defined as a table that contains the following
three columns: three columns:
Value: The token under registration Value: The token under registration
Description: A descriptive text defining the intended usage of the Description: A descriptive text defining the intended usage of the
URI URI
Document: A reference to the document defining the registration Document: A reference to the document defining the registration
skipping to change at page 42, line 14 skipping to change at page 40, line 6
[2] Moats, R., "URN Syntax", RFC 2141, May 1997. [2] Moats, R., "URN Syntax", RFC 2141, May 1997.
[3] Handley, M. and V. Jacobson, "SDP: Session Description [3] Handley, M. and V. Jacobson, "SDP: Session Description
Protocol", RFC 2327, April 1998. Protocol", RFC 2327, April 1998.
[4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October Considerations Section in RFCs", BCP 26, RFC 2434, October
1998. 1998.
[5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, [5] Eastlake, D. and A. Panitz, "Reserved Top Level DNS Names",
BCP 32, RFC 2606, June 1999.
[6] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999. August 1999.
[6] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", [7] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types",
RFC 3023, January 2001. RFC 3023, January 2001.
[7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [8] 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.
[8] Roach, A., "Session Initiation Protocol (SIP)-Specific Event [9] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002. Notification", RFC 3265, June 2002.
[9] Peterson, J., "A Privacy Mechanism for the Session Initiation
Protocol (SIP)", RFC 3323, November 2002.
[10] Schulzrinne, H., Oran, D. and G. Camarillo, "The Reason Header [10] Schulzrinne, H., Oran, D. and G. Camarillo, "The Reason Header
Field for the Session Initiation Protocol (SIP)", RFC 3326, Field for the Session Initiation Protocol (SIP)", RFC 3326,
December 2002. December 2002.
[11] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne, [11] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
"Grouping of Media Lines in the Session Description Protocol
(SDP)", RFC 3388, December 2002.
[12] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", STD 64, "RTP: A Transport Protocol for Real-Time Applications", STD 64,
RFC 3550, July 2003. RFC 3550, July 2003.
[13] Yergeau, F., "UTF-8, a transformation format of ISO 10646", [12] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
STD 63, RFC 3629, November 2003. STD 63, RFC 3629, November 2003.
[14] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [13] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
11.2 Informative References 11.2 Informative References
[15] Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming [14] Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming
Protocol (RTSP)", RFC 2326, April 1998. Protocol (RTSP)", RFC 2326, April 1998.
[16] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966, [15] Peterson, J., "A Privacy Mechanism for the Session Initiation
Protocol (SIP)", RFC 3323, November 2002.
[16] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne,
"Grouping of Media Lines in the Session Description Protocol
(SDP)", RFC 3388, December 2002.
[17] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,
December 2004. December 2004.
[17] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme [18] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
Registration", RFC 3508, April 2003. Registration", RFC 3508, April 2003.
[18] Rosenberg, J., "A Framework for Conferencing with the Session [19] Rosenberg, J., "A Framework for Conferencing with the Session
Initiation Protocol", Initiation Protocol",
Internet-Draft draft-ietf-sipping-conferencing-framework-03, Internet-Draft draft-ietf-sipping-conferencing-framework-04,
October 2004. February 2005.
[19] Rosenberg, J., "An INVITE Inititiated Dialog Event Package for [20] Rosenberg, J., "An INVITE Inititiated Dialog Event Package for
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
Internet-Draft draft-ietf-sipping-dialog-package-05, November Internet-Draft draft-ietf-sipping-dialog-package-05, November
2004. 2004.
[20] Rosenberg, J., "Obtaining and Using Globally Routable User [21] Rosenberg, J., "Obtaining and Using Globally Routable User
Agent (UA) URIs (GRUU) in the Session Initiation Protocol Agent (UA) URIs (GRUU) in the Session Initiation Protocol
(SIP)", Internet-Draft draft-ietf-sip-gruu-02, July 2004. (SIP)", Internet-Draft draft-ietf-sip-gruu-03, February 2005.
[21] Levin, O. and G. Camarillo, "The SDP (Session Description [22] Levin, O. and G. Camarillo, "The SDP (Session Description
Protocol) Label Attribute", Protocol) Label Attribute",
Internet-Draft draft-ietf-mmusic-sdp-media-label-01, January Internet-Draft draft-ietf-mmusic-sdp-media-label-01, January
2005. 2005.
Authors' Addresses Authors' Addresses
Jonathan Rosenberg Jonathan Rosenberg
Cisco Systems Cisco Systems
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany, NJ 07054 Parsippany, NJ 07054
 End of changes. 

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