draft-ietf-sipping-conference-package-08.txt   draft-ietf-sipping-conference-package-09.txt 
SIPPING J. Rosenberg SIPPING J. Rosenberg
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: June 6, 2005 H. Schulzrinne Expires: August 24, 2005 H. Schulzrinne
Columbia University Columbia University
O. Levin, Ed. O. Levin, Ed.
Microsoft Corporation Microsoft Corporation
December 6, 2004 February 20, 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-08 draft-ietf-sipping-conference-package-09
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.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
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 June 6, 2005. This Internet-Draft will expire on August 24, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Conference Event Package . . . . . . . . . . . . . . . . . . . 4 3. Conference Event Package . . . . . . . . . . . . . . . . . . 5
3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5
3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5 3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 6
3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5 3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 6
3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 5 3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 6
3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6 3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 7
3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6 3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 7
3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 6 3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 7
3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7 3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 8
3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7 3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 8
3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7 3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . 8
4. Conference Document . . . . . . . . . . . . . . . . . . . . . 7 4. Conference Document . . . . . . . . . . . . . . . . . . . . 8
4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 7 4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 7 4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 8 4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4 State and Partial Notifications . . . . . . . . . . . . . 8 4.4 State and Partial Notifications . . . . . . . . . . . . . 9
4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 8 4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 9
4.6 Constructing Coherent State Procedure . . . . . . . . . . 9 4.6 Constructing Coherent State Procedure . . . . . . . . . . 10
5. Conference Data . . . . . . . . . . . . . . . . . . . . . . . 10 5. Conference Data . . . . . . . . . . . . . . . . . . . . . . 11
5.1 conference-type . . . . . . . . . . . . . . . . . . . . . 10 5.1 conference-type . . . . . . . . . . . . . . . . . . . . . 11
5.1.1 conference-description of 5.1.1 conference-description of
conference-description-type . . . . . . . . . . . . . 11 conference-description-type . . . . . . . . . . . . . 12
5.1.2 host-info of host-type . . . . . . . . . . . . . . . . 11 5.1.2 host-info of host-type . . . . . . . . . . . . . . . . 12
5.1.3 conference-state of conference-state-type . . . . . . 11 5.1.3 conference-state of conference-state-type . . . . . . 12
5.1.4 users of users-type . . . . . . . . . . . . . . . . . 11 5.1.4 users of users-type . . . . . . . . . . . . . . . . . 12
5.1.5 sidebars-by-ref of uris-type . . . . . . . . . . . . . 11 5.1.5 sidebars-by-ref of uris-type . . . . . . . . . . . . . 12
5.1.6 sidebar-by-val of conference-type . . . . . . . . . . 11 5.1.6 sidebar-by-val of conference-type . . . . . . . . . . 12
5.2 conference-description-type . . . . . . . . . . . . . . . 12 5.2 conference-description-type . . . . . . . . . . . . . . . 13
5.2.1 display-text of string type . . . . . . . . . . . . . 12 5.2.1 display-text of string type . . . . . . . . . . . . . 13
5.2.2 subject of string type . . . . . . . . . . . . . . . . 12 5.2.2 subject of string type . . . . . . . . . . . . . . . . 13
5.2.3 free-text of string type . . . . . . . . . . . . . . . 12 5.2.3 free-text of string type . . . . . . . . . . . . . . . 13
5.2.4 keywords of keywords-type . . . . . . . . . . . . . . 12 5.2.4 keywords of keywords-type . . . . . . . . . . . . . . 13
5.2.5 conf-uris of uris-type . . . . . . . . . . . . . . . . 12 5.2.5 conf-uris of uris-type . . . . . . . . . . . . . . . . 13
5.2.6 service-uris of uris-type . . . . . . . . . . . . . . 13 5.2.6 service-uris of uris-type . . . . . . . . . . . . . . 14
5.2.7 maximum-user-count of user-count-type . . . . . . . . 13 5.2.7 maximum-user-count of user-count-type . . . . . . . . 14
5.2.8 available-media of conference-medias-type . . . . . . 13 5.2.8 available-media of conference-media-type . . . . . . . 14
5.3 host-type . . . . . . . . . . . . . . . . . . . . . . . . 13 5.3 host-type . . . . . . . . . . . . . . . . . . . . . . . . 14
5.3.1 display-text of string type . . . . . . . . . . . . . 14 5.3.1 display-text of string type . . . . . . . . . . . . . 15
5.3.2 web-page of anyURI type . . . . . . . . . . . . . . . 14 5.3.2 web-page of anyURI type . . . . . . . . . . . . . . . 15
5.3.3 uris of uris-type . . . . . . . . . . . . . . . . . . 14 5.3.3 uris of uris-type . . . . . . . . . . . . . . . . . . 15
5.4 conference-state-type . . . . . . . . . . . . . . . . . . 14 5.4 conference-state-type . . . . . . . . . . . . . . . . . . 15
5.4.1 user-count of user-count-type . . . . . . . . . . . . 14 5.4.1 user-count of user-count-type . . . . . . . . . . . . 15
5.4.2 active of Boolean type . . . . . . . . . . . . . . . . 14 5.4.2 active of Boolean type . . . . . . . . . . . . . . . . 15
5.4.3 locked of Boolean type . . . . . . . . . . . . . . . . 14 5.4.3 locked of Boolean type . . . . . . . . . . . . . . . . 15
5.4.4 active-media of conference-medias-type . . . . . . . . 14 5.4.4 active-media of conference-media-type . . . . . . . . 15
5.5 user-type . . . . . . . . . . . . . . . . . . . . . . . . 15 5.5 conference-media-type . . . . . . . . . . . . . . . . . . 16
5.5.1 display-text of string type . . . . . . . . . . . . . 15 5.5.1 conference-medium-type . . . . . . . . . . . . . . . . 16
5.5.2 associated-aors of anyURI type . . . . . . . . . . . . 15 5.5.1.1 display-text of string type . . . . . . . . . . . 16
5.5.3 roles of user-roles-type . . . . . . . . . . . . . . . 15 5.5.1.2 type of string type . . . . . . . . . . . . . . . 16
5.5.4 language of language type . . . . . . . . . . . . . . 15 5.5.1.3 label of string type . . . . . . . . . . . . . . . 17
5.5.5 cascaded-focus of anyURI type . . . . . . . . . . . . 16 5.6 user-type . . . . . . . . . . . . . . . . . . . . . . . . 17
5.5.6 endpoint of endpoint-type . . . . . . . . . . . . . . 16
5.6 endpoint-type . . . . . . . . . . . . . . . . . . . . . . 16
5.6.1 display-text of string type . . . . . . . . . . . . . 17 5.6.1 display-text of string type . . . . . . . . . . . . . 17
5.6.2 referred of execution-type . . . . . . . . . . . . . . 17 5.6.2 associated-aors of anyURI type . . . . . . . . . . . . 17
5.6.3 status of endpoint-status-type . . . . . . . . . . . . 17 5.6.3 roles of user-roles-type . . . . . . . . . . . . . . . 17
5.6.4 joining-method of joining-type . . . . . . . . . . . . 18 5.6.4 language of language type . . . . . . . . . . . . . . 18
5.6.5 joining-info of execution-type . . . . . . . . . . . . 19 5.6.5 cascaded-focus of anyURI type . . . . . . . . . . . . 18
5.6.6 disconnection-method of disconnection-type . . . . . . 19 5.6.6 endpoint of endpoint-type . . . . . . . . . . . . . . 18
5.6.7 disconnection-info of execution-type . . . . . . . . . 19 5.7 endpoint-type . . . . . . . . . . . . . . . . . . . . . . 19
5.6.8 media of media-type . . . . . . . . . . . . . . . . . 20 5.7.1 display-text of string type . . . . . . . . . . . . . 19
5.7 media-type . . . . . . . . . . . . . . . . . . . . . . . . 20 5.7.2 referred of execution-type . . . . . . . . . . . . . . 19
5.7.1 display-text of string type . . . . . . . . . . . . . 20 5.7.3 status of endpoint-status-type . . . . . . . . . . . . 20
5.7.2 proto of string type . . . . . . . . . . . . . . . . . 20 5.7.4 joining-method of joining-type . . . . . . . . . . . . 21
5.7.3 src-id of string type . . . . . . . . . . . . . . . . 20 5.7.5 joining-info of execution-type . . . . . . . . . . . . 21
5.7.4 label of string type . . . . . . . . . . . . . . . . . 21 5.7.6 disconnection-method of disconnection-type . . . . . . 21
5.7.5 status of media-status-type . . . . . . . . . . . . . 21 5.7.7 disconnection-info of execution-type . . . . . . . . . 22
5.7.6 call of call-type . . . . . . . . . . . . . . . . . . 21 5.7.8 media of media-type . . . . . . . . . . . . . . . . . 22
6. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 22 5.7.9 call-info of call-type . . . . . . . . . . . . . . . . 22
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 5.7.10 media-type . . . . . . . . . . . . . . . . . . . . . 23
7.1 Basic Example . . . . . . . . . . . . . . . . . . . . . . 29 5.7.10.1 display-text of string type . . . . . . . . . . 23
7.2 Rich Example . . . . . . . . . . . . . . . . . . . . . . . 31 5.7.10.2 type of string type . . . . . . . . . . . . . . 23
8. Security Considerations . . . . . . . . . . . . . . . . . . . 36 5.7.10.3 label of string type . . . . . . . . . . . . . . 23
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 5.7.10.4 src-id of string type . . . . . . . . . . . . . 24
9.1 conference Event Package Registration . . . . . . . . . . 36 5.7.10.5 status of media-status-type . . . . . . . . . . 24
9.2 application/conference-info+xml MIME Registration . . . . 36 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 . . . . . . . . . . 37 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 39
9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 38 9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 40
9.5 URI Purposes Sub-registry Establishment . . . . . . . . . 38 9.5 URI Purposes Sub-registry Establishment . . . . . . . . . 40
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 41
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 39 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 41
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 39 11.1 Normative References . . . . . . . . . . . . . . . . . . 41
11.2 Informative References . . . . . . . . . . . . . . . . . . . 40 11.2 Informative References . . . . . . . . . . . . . . . . . 42
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 41 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 43
Intellectual Property and Copyright Statements . . . . . . . . 43 Intellectual Property and Copyright Statements . . . . . . . 45
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [7] Events framework Events The Session Initiation Protocol (SIP) [7]Events Framework [8] defines
Framework [8] defines general mechanisms for subscribing to, and general mechanisms for subscribing to, and receiving notifications
receiving notifications of, events within SIP networks. It of, events within SIP networks. It introduces the notion of a
introduces the notion of a package, which is a specific package, which is a specific "instantiation" of the events framework
"instantiation" of the events framework for a well-defined set of for a well-defined set of events. Here, we define an event package
events. Here, we define an event package for SIP conferences. This for SIP conferences. This package provides the conference
package provides the conference notification service as outlined in notification service as outlined in the SIP conferencing framework
the SIP conferencing framework [18]. As described there, [18]. As described there, subscriptions to a conference URI are
subscriptions to a conference URI are routed to the focus that is routed to the focus that is handling the conference. It acts as the
handling the conference. It acts as the notifier, and provides notifier, and provides clients with updates on conference state.
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
In this document, the key words "MUST", "MUST NOT", "REQUIRED", In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
skipping to change at page 4, line 41 skipping to change at page 5, line 40
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 [18]. 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 a participant in the conference may in fact be another It is possible that a participant in the conference may in fact be
focus. In order to provide a more complete participant list, the another focus. In order to provide a more complete participant list,
focus MAY subscribe to the conference package of the other focus to the focus MAY subscribe to the conference package of the other focus
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 [8].
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
skipping to change at page 5, line 32 skipping to change at page 6, line 28
state of the conference. state of the conference.
o Notifications do not normally contain full state; rather, they o Notifications do not normally contain full state; rather, they
only indicate the state that has changed. The exception is a only indicate the state that has changed. The exception is a
NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the
full state of the information requested by the subscriber. full state of the information requested by the subscriber.
3.3 Subscription Duration 3.3 Subscription Duration
The default expiration time for a subscription to a conference is one The default expiration time for a subscription to a conference is one
hour. Once the conference ends, all subscriptions to that particular hour. Once the conference ends, all subscriptions to that particular
conference are terminated, with a reason of "noresource" RFC 3265 conference are terminated, with a reason of "noresource" as defined
[8]. in RFC 3265 [8].
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 [8], 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
skipping to change at page 6, line 18 skipping to change at page 7, line 14
3.5 Notifier Processing of SUBSCRIBE Requests 3.5 Notifier Processing of SUBSCRIBE Requests
The conference information contains very sensitive information. The conference information contains very sensitive information.
Therefore, all subscriptions SHOULD be authenticated and then Therefore, all subscriptions SHOULD be authenticated and then
authorized before approval. Authorization policy is at the authorized before approval. Authorization policy is at the
discretion of the administrator, as always. However, a few discretion of the administrator, as always. However, a few
recommendations can be made. recommendations can be made.
It is RECOMMENDED that all users in the conference be allowed to It is RECOMMENDED that all users in the conference be allowed to
subscribe to the conference. subscribe to the conference event package.
3.6 Notifier Generation of NOTIFY Requests 3.6 Notifier Generation of NOTIFY Requests
Notifications MUST be generated for the conference state when a new Notifications SHOULD be generated for the conference state when a new
participant joins (i.e. gets "connected" to) or a participant leaves participant joins (i.e. gets "connected" to) or a participant leaves
(i.e. gets "disconnected" from) the conference. (i.e. gets "disconnected" from) the conference.
Subject to a local focus policy, additional changes in participants' Subject to a local focus policy, additional changes in participants'
status, changes in their media types, and other optional information status, changes in their media types, and other optional information
MAY be reported by the focus. MAY be reported by the focus.
Changes in sidebar rosters SHOULD be reported by the focus to their Changes in sidebar rosters SHOULD be reported by the focus to their
participants and MAY be reported to others, subject to local policy. participants and MAY be reported to others, subject to local policy.
skipping to change at page 7, line 23 skipping to change at page 8, line 19
By their nature, the conferences supported by this package are By their nature, the conferences supported by this package are
centralized. Therefore, SUBSCRIBE requests for a conference should centralized. Therefore, SUBSCRIBE requests for a conference should
not generally fork. Users of this package MUST NOT install more than not generally fork. Users of this package MUST NOT install more than
a single subscription as a result of a single SUBSCRIBE request. a single subscription as a result of a single SUBSCRIBE request.
3.9 Rate of Notifications 3.9 Rate of Notifications
For reasons of congestion control, it is important that the rate of For reasons of congestion control, it is important that the rate of
notifications not become excessive. As a result, it is RECOMMENDED notifications not become excessive. As a result, it is RECOMMENDED
that the server not generate notifications for a single subscriber at that the server doesn't generate notifications for a single
a rate faster than once every 5 seconds. subscriber at a rate faster than once every 5 seconds.
3.10 State Agents 3.10 State Agents
Conference state is ideally maintained in the element in which the Conference state is ideally maintained in the element in which the
conference resides. Therefore, the elements that maintain the conference resides. Therefore, the elements that maintain the
conference are the ones best suited to handle subscriptions to it. conference are the ones best suited to handle subscriptions to it.
Therefore, the usage of state agents is NOT RECOMMENDED for this Therefore, the usage of state agents is NOT RECOMMENDED for this
package. package.
4. Conference 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 SHOULD be valid. It MUST be based on Extensible Markup Language and valid. It MUST be based on Extensible Markup Language (XML) 1.0
(XML) 1.0 and MUST be encoded using UTF-8 [13]. and MUST be encoded using UTF-8 [13].
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 [5] and
extended by RFC 3688 [14]. This URN is: extended by RFC 3688 [14]. 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 optional '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 State and Partial Notifications
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: those that carry relatively small
amount of data and those that can potentially carry a lot of data. amount of data and those that can potentially carry a lot of data.
During partial notifications, the light elements are updated as During partial notifications, the light elements are updated as
atomic pieces of data. On the other hand, elements that can carry a atomic pieces of data. On the other hand, elements that can carry a
substantial amount of data have the general 'state' attribute substantial amount of data have the general 'state' attribute
skipping to change at page 9, line 5 skipping to change at page 9, line 48
In a partial notification event it must be possible to uniquely In a partial notification event it must be possible to uniquely
identify each sub-element among others of the same type under a identify each sub-element among others of the same type under a
common parent element. In order to achieve this property, all common parent element. In order to achieve this property, all
sub-elements, with possible multiple appearances under a common sub-elements, with possible multiple appearances under a common
parent (which has the attribute 'state') have keys defined to them. 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 the elements with their keys as defined by this
specification: specification:
o Elements <conference-info>, <user>, and <endpoint> use as the key o Elements <conference-info> and <user> use as the key 'entity'
'entity' o Element <endpoint> uses as the key 'entity' and optionally
'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 Sub-element <entry> of uris-type contained in elements <conf-uris>
and <service-uris> uses as the key <uri> and <service-uris> uses as the key <uri>
o Elements <available-media> and <active-media> of o Elements <available-media> and <active-media> of
conference-medias-type use as the key <proto> conference-media-type use as the key 'id'
o Elements <maximum-user-count> and <user-count> of count-type use o Elements <maximum-user-count> and <user-count> of count-type use
as the key <role> as the key 'role'
o Element <role> of user-roles-type uses as the key <entry>
o Sub-element <entry> of conference-type contained in element o Sub-element <entry> of conference-type contained in element
<sidebars-by-val> uses as the key 'entity' <sidebars-by-val> uses as the key 'entity'
o Elements <associated-uris> and <sidebars-by-ref> of uris-type use o Elements <associated-uris> and <sidebars-by-ref> of uris-type use
as the key <uri> as the key <uri>
4.6 Constructing Coherent State Procedure 4.6 Constructing Coherent State Procedure
A Conference package subscriber MUST initialize the 'version' A conference package subscriber locally maintains a local version
attribute from the <conference-info> element with the value in the number, a local element for each element in the schema, and a table
first document received. for each element with key(s) in the schema.
The conference package subscriber locally maintains a local element For first time a NOTIFY with a "full" document is received (as
for each element in the schema and a table for each element with indicated by the value of the 'state' attribute in the
key(s) in the schema and indexed by these key(s). <conference-info> element), the conference package subscriber MUST
set the local 'version' number to the value of the 'version'
attribute from the received <conference-info> and populate local data
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 less than the document are compared. If the value in the document is equal or less
local version, the document is discarded without processing. If the than the local version, the document is discarded without processing.
value in the document is higher than the local version number, the
local version number is set to the value in the new document and the
document is processed. If the value in the received document is more
than one higher than the previous local version number and the
document contained a partial state, the subscriber SHOULD generate a
refresh request to trigger a full state notification.
Further processing of the conference information depends on the state Otherwise, if the received NOTIFY contains a "full" or "deleted"
contained in the received conference document and indicated by the state, the conference package subscriber MUST set the local 'version'
value of the 'state' attribute in the <conference-info> element. If number to the value of the 'version' attribute from the received
it contains "full" state, the whole local content is flushed and <conference-info> and replace the local information with the received
repopulated from the document. If it contains "deleted" state, it document. Receiving "deleted" state means that the conference ceased
means that the conference ceased to exist and the subscriber SHOULD to exist and the subscriber SHOULD terminate the subscription by
terminate the subscription by sending the SUBSCRIBE with Expires = 0. sending the SUBSCRIBE with Expires = 0.
If the document contains "partial" state, the document is used to Otherwise (i.e. if the received NOTIFY contains "partial" state), if
update the local content as described below. the 'version' number in the received document is more than one number
higher than the previous local version number, the subscriber MUST
generate a refresh request to trigger a full state notification. If
the 'version' number in the document is one higher than the local
version number, the local version number is increased by one and the
document is used to update the local content as described below.
Starting from outer elements in the received document, For each sub-element of the <conference-info> element in the received
1. If the parent element contains "full" state, the whole local document,
element content is flushed and repopulated from the document. 1. If the element contains "full" state, the whole local element
content is flushed and repopulated from the document.
2. Otherwise, if the parent element contains "deleted" state, the 2. Otherwise, if the element contains "deleted" state, the whole
whole element MUST be removed from the local content. element MUST be removed from the local content.
3. Otherwise, if the parent 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.
3.1.1 If a key does not exist in the local table, a row is added, and 3.1.1 If a key does not exist in the local table, a row is added, and
its content is set to the element information from the update. its content is set to the element information from the update.
3.1.2 Otherwise, if a key of the same value does exist, for each 3.1.2 Otherwise, if a key of the same value does exist, for each
sub-element in the row the algorithm is applied from step 2.2. sub-element in the row the algorithm is applied from step 3.2.
3.2 For each atomic element received in the schema, the element is 3.2 For each atomic element received in the schema, the element is
replaced with the new information as a whole. Also, for each replaced with the new information as a whole. Also, for each
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 3. "partial", the algorithm is applied recursively starting from step
3.1.
5. Conference Data 5. Conference Data
A conference information document begins with the root element tag A conference information document begins with the root element tag
<conference-info> of conference-type. Sections below describe the <conference-info> of conference-type. Sections below describe the
complex types composing the hierarchal conference-type. The full XML complex types composing the hierarchal conference-type. The full XML
schema is defined in Section 6. schema is defined in Section 6.
5.1 conference-type 5.1 conference-type
skipping to change at page 11, line 7 skipping to change at page 12, line 7
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 details 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. included when used in the root <conference-info> element. Version
Versions start at 0 and increment by one for each new document number is a 32 bit monotonically increasing integer scoped within
sent to a subscriber. Versions are scoped within a subscription. a subscription. A server MUST increment the version number by one
Versions are represented using a 32 bit integer. for each new partial notification being sent to a subscriber.
The conference-type defines an extendable sequence of child elements. The conference-type defines an extendable sequence of child elements.
A "full" conference document MUST at least include the following A "full" conference document MUST at least include the following
sub-elements: <conference-description>, <conference-state>, and sub-elements: <conference-description>, <conference-state>, and
<users>. <users>.
The child elements are described in details below: The child elements are described in details below:
5.1.1 conference-description of conference-description-type 5.1.1 conference-description of conference-description-type
skipping to change at page 13, line 31 skipping to change at page 14, line 31
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
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.7 maximum-user-count of user-count-type
This element is used to specify the maximum number of users permitted This element, if used, specifies the maximum number of users
in the conference. The number SHOULD be provided for all permitted in the conference and SHOULD include the counter for all
participants in total by populating the <role> sub-element with value participants in the conference in total by populating the attribute
"any". Additionally counters for users with certain roles in the 'role' with value "any". Counters for users with specific roles MAY
conference MAY be separately provided. be additionally provided.
5.2.8 available-media of conference-medias-type 5.2.8 available-media of conference-media-type
This element contains information about the media types available in This element contains information about the media streams with their
the conference. The <entry> sub-element MUST contain one of the types available to the participants in the conference. The entries
values registered for "proto" of SDP [3] and its later revision(s). in the <available-media> container are of conference-medium-type and
are indexed by attribute 'id'.
5.3 host-type 5.3 host-type
This type defines the 'state' attribute which can contain the values This type defines the 'state' attribute which can contain the values
"full", "partial", or "deleted". "full", "partial", or "deleted".
This type defines an extendable sequence of the following child This type defines an extendable sequence of the following child
elements: elements:
5.3.1 display-text of string type 5.3.1 display-text of string type
skipping to change at page 14, line 39 skipping to change at page 15, line 39
This element is used to specify the current number of users in the This element is used to specify the current number of users in the
conference. The number SHOULD be provided for all participants in conference. The number SHOULD be provided for all participants in
total by populating the <role> sub-element with value "any". total by populating the <role> sub-element with value "any".
Additionally counters for users with certain roles in the conference Additionally counters for users with certain roles in the conference
MAY be separately provided. MAY be separately provided.
5.4.2 active of Boolean type 5.4.2 active of Boolean type
This element says whether the conference is currently active or not. This element says whether the conference is currently active or not.
For example, a conference can be scheduled for a certain start time A conference is active if dialing into one of the <conf-uris> results
and its conference URI reserved and published. Still, the conference in successful establishment of a call signaling session between the
will not be "active" till its actual start time. dialed user and the conference focus.
5.4.3 locked of Boolean type 5.4.3 locked of Boolean type
This element contains information about whether the conference is This element contains information about whether the conference is
currently locked. In this context, "locked" means that the currently locked. In this context, "locked" means that the
conference roster can not be added to (although participants may conference roster can not be added to (although participants may
leave or be removed from the conference). leave or be removed from the conference).
5.4.4 active-media of conference-medias-type 5.4.4 active-media of conference-media-type
This element contains information about the media types currently This element contains information about the media streams being
active in the conference, which is a subset of those listed in the currently active in the conference, which is a subset of those listed
<available-media> element. in the <available-media> container. The entries in the
<active-media> container are of conference-medium-type and are
indexed by attribute 'id'.
5.5 user-type Note, that correlation between media streams in both containers is
achieved by matching the values of <label> sub-elements element
regardless the position of each media entry (i.e. its 'id' value) in
the container.
5.5 conference-media-type
This type defines a sequence of <entry> child elements, each of
conference-medium-type.
This type defines the 'state' attribute which can contain the values
"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
elements.
5.5.1 conference-medium-type
This type defines the 'id' attribute, which is the media stream
identifier being generated by the notification server such as its
value is unique among all entries in the parent container. This
attribute is the key to identify media streams in the container.
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
elements.
5.5.1.1 display-text of string type
This element contains the display text for the media stream.
5.5.1.2 type of string type
This element contains the media type of the media stream. The value
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
The element <label> carries a unique identifier for this stream among
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
This type defines the following attributes: This type defines the following attributes:
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 authenticated identity of the participant. The 'entity'
attribute MUST be unique in the user element list because it is attribute MUST be unique in the user element list because it is
used as the key in partial notifications about users' state. An used as the key in partial notifications about users' state. An
anonymous participant in a conference SHOULD be represented by an anonymous participant in a conference SHOULD be represented by an
anonymous URI generated by the focus. For multiple anonymous anonymous URI generated by the focus. For multiple anonymous
skipping to change at page 15, line 34 skipping to change at page 17, line 39
could be used for a participant requesting privacy. could be used for a participant requesting privacy.
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"). conference ceased to exist ("deleted").
This type defines an extendable sequence of the following child This type defines an extendable sequence of the following child
elements. elements.
5.5.1 display-text of string type 5.6.1 display-text of string type
This element contains the display text for the user. This element contains the display text for the user.
5.5.2 associated-aors of anyURI type 5.6.2 associated-aors of anyURI type
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.5.3 roles of user-roles-type 5.6.3 roles of user-roles-type
This element contains the roles of the user. This element contains the roles of the user.
5.5.4 language of language type 5.6.4 language of language type
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.5.5 cascaded-focus of anyURI type 5.6.5 cascaded-focus of anyURI type
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 [18], 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 the subscribing to both this package and the Dialog Package [19] of each
cascaded foci and correlating the relevant information. cascaded focus and correlating the relevant information.
5.5.6 endpoint of endpoint-type 5.6.6 endpoint of endpoint-type
This element contains information about an endpoint of the user. The This element contains information about an endpoint of the parent
element of the endpoint-type can have unbounded number of appearance <user>. The <endpoint> element can have unbounded number of
in the user-type for each endpoint of the user participating in the appearances for each user participating in the conference.
conference. In a case when authentication is performed per endpoint
(rather than per user) in a system, a focus can be not aware of the
logical association among endpoints being used by the same user. In
this case the focus MAY present the endpoints as belonging to
separate users in the conference schema.
In a different case, due to privacy concerns for a user, the focus The first mandatory key 'entity' of an <endpoint> specifies one of
may want to shield the information about multiple endpoints from the the user devices. Potentially, each device can establish multiple
recipients of the Conference document. To do so the focus MAY call signaling sessions with the conference focus simultaneously.
aggregate the multiple endpoint information into a single endpoint The secondary optional key 'call-id' can be included by the
element under this user. notification server in order to provide status information for each
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.
5.6 endpoint-type In a conferencing system where authentication is performed per
endpoint (rather than per user), a focus is not necessarily aware of
the logical association of multiple endpoints under a common user.
In this case, the focus would arrange the endpoints as belonging to
separate users in the conference document. Note, that typically in
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
focus may choose to shield the information about the participant's
multiple endpoints from the third-party subscribers. To do so, the
focus MAY aggregate the multiple endpoints' information into a single
<endpoint> element under the participant's <user>. Note, that in
this case the notification server can still include the secondary
'call-id' key and provide the information for each call signaling
session individually.
5.7 endpoint-type
This type defines the following attributes: This type defines the following attributes:
entity: The attribute contains the endpoint URI for the user in the entity: The attribute contains the endpoint URI for the user in the
conference. In SIP terms, this is the Contact URI or GRUU. The conference. In SIP terms, this is the Contact URI or GRUU. The
'entity' attribute MUST be unique in the endpoint element list 'entity' attribute MUST be unique in the endpoint element list
because it is used as the key in partial notifications about because it is used as the key in partial notifications about
users' endpoints. An endpoint belonging to an anonymous users' endpoints. An endpoint belonging to an anonymous
participant in a conference SHOULD be represented by an anonymous participant in a conference SHOULD be represented by an anonymous
URI generated by the focus. For multiple anonymous endpoints, the URI generated by the focus. For multiple anonymous endpoints, the
focus must ensure that each anonymous URI is unique. The focus must ensure that each anonymous URI is unique. The
guidelines for generating anonymous URIs in RFC 3323 [9] should be guidelines for generating anonymous URIs in RFC 3323 [9] should be
followed. followed.
call-id: This attribute is optional and its usage is a subject to the
server's policy per subscriber. The value of this attribute is a
numeric index, which is unique for each call signaling session of
the parent endpoint. This attribute is used when the server needs
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 deleted from the conference ("deleted").
This type defines an extendable sequence of the following child This type defines an extendable sequence of the following child
elements. elements.
5.6.1 display-text of string type 5.7.1 display-text of string type
This element contains the display text for the endpoint. This element contains the display text for the endpoint.
5.6.2 referred of execution-type 5.7.2 referred of execution-type
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. referred to the conference and SHOULD be expressed in Coordinated
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.6.3 status of endpoint-status-type 5.7.3 status of endpoint-status-type
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.
skipping to change at page 18, line 12 skipping to change at page 20, line 42
pending based on moderator approval. In the meantime he/she is pending based on moderator approval. In the meantime he/she is
hearing music-on-hold or some other kind of related content. 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 SIP dialog exists between an endpoint and a
focus and the endpoint can "listen" to the conference, but 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 mostly 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 endpoint
(either DISCONNECT or BYE was sent to the endpoint). (either DISCONNECT or BYE was sent to the endpoint).
Note that the defined transient statuss (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.6.4 joining-method of joining-type 5.7.4 joining-method of joining-type
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, i.e. sent INVITE
to the focus, which resulted in successful dialog establishment. 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 by
sending a successful INVITE to the endpoint. 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 participants UA acts as a conference status is used only when a participant's UA acts as a conference
focus. focus.
5.6.5 joining-info of execution-type 5.7.5 joining-info of execution-type
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. joined the conference and SHOULD be expressed in Coordinated
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.6.6 disconnection-method of disconnection-type 5.7.6 disconnection-method of disconnection-type
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: The endpoint sent a BYE, thus leaving the conference.
booted: The endpoint was sent a BYE by the focus, booting him/her out booted: The endpoint was sent a BYE by the focus, booting him/her out
of the conference. Alternatively, the endpoint tried to dial into of the conference. Alternatively, the endpoint tried to dial into
to conference without success because was rejected by the focus to conference but was rejected by the focus due to local policy.
according to local policy decisions.
failed: The server tried to bring the endpoint into the conference, failed: The server tried to bring the endpoint into the conference,
but its attempt to contact the specific endpoint resulted in a but its attempt to contact the specific endpoint resulted in a
non-200 class final response. Alternatively, the endpoint tried non-200 class final response. Alternatively, the endpoint tried
to dial into the conference without success due to technical to dial into the conference without success due to technical
reasons. reasons.
5.6.7 disconnection-info of execution-type 5.7.7 disconnection-info of execution-type
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. departed the conference and SHOULD be expressed in Coordinated
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.6.8 media of media-type 5.7.8 media of media-type
This element contains information about a media stream of this This element contains information about a media stream of the
endpoint. The element of the media-type can have an unbounded number endpoint. The element of the media-type can have an unbounded number
of appearances in the endpoint-type for each media stream of the of appearances in the endpoint-type for each media stream of the
endpoint. Note that it is possible that media streams listed under a endpoint. Note, that if the 'call-id' attribute of the endpoint is
common endpoint MAY be established by separate signaling means and not provided by the server, it is possible that the media streams
consequently belong to different signaling "calls". listed under the common endpoint were established by separate
signaling sessions (i.e. belong to different "calls" or "dialogs").
5.7 media-type 5.7.9 call-info of call-type
The <call-info> element MAY be used only if the server chose to
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
information for a call being maintained between the endpoint and the
focus. Note, that privacy policies MUST be consulted before
revealing this information to third-party participants.
The <sip> sub-element contains the SIP dialog identifier of the
endpoint's dialog with the focus. The element includes sub-elements
<display-text>, <call-id>, <to-tag>, <from-tag>.
In future, the <call-info> element can be expanded to include call
signaling protocol information for other protocols besides SIP.
5.7.10 media-type
This type defines the following attributes: This type defines the following attributes:
id: The attribute is a unique identifier of a media stream on a per id: The attribute is the media stream identifier being generated by
endpoint basis. This attribute is used as a key to identify media the notification server such as its value is unique in the
streams which may be added and deleted on a dynamic basis during endpoint context. This attribute is the key to identify media
the conference. If the SDP "mid" (as defined in Grouping of Media streams which can be added and deleted on dynamic basis during the
Lines in the SDP [11]) is used for establishing the media stream, conference and the changes being reported in the conference state
the 'id' SHOULD contain the same "mid" value, otherwise the notifications.
notification service MUST generate an 'id' value which is unique
in the endpoint context.
state: This attribute indicates whether the element contains the state: This attribute indicates whether the element contains the
whole media information ("full"), only the information that has whole media information ("full"), only the information that has
changed since the previous notification ("partial"), or that the changed since the previous notification ("partial"), or that the
media element has been deleted from the conference document media element has been deleted from the conference document
("deleted"). ("deleted").
This type defines an extendable sequence of the following child This type defines an extendable sequence of the following child
elements. elements.
5.7.1 display-text of string type 5.7.10.1 display-text of string type
This element contains the display text for the media stream. This element contains the display text for the media stream.
5.7.2 proto of string type 5.7.10.2 type of string 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 "proto" 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.3 src-id of string type 5.7.10.3 label of string type
The element <label> carries a unique identifier for this stream among
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.7.10.4 src-id of string type
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 the RTP/RTCP [12] the actual source of the media. For example, for RTP/RTCP [12] media
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 [12],
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.4 label of string type 5.7.10.5 status of media-status-type
The element <label> carries a unique identifier for this stream among
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.7.5 status of media-status-type
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.7.6 call of call-type
The <call> element is a general container for providing call
signaling detailed information. Note that privacy policies MUST be
consulted before revealing this information to third-party
participants.
Specifically, the <sip> sub-element contains the SIP dialog
identifier of the endpoint's dialog with the focus. The element
includes sub-elements <display-text>, <call-id>, <to-tag>,
<from-tag>.
In future, the <call> element can be expanded to include other call
signaling protocol identifiers.
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 23, line 15 skipping to change at page 25, line 44
--> -->
<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="user-count-type" minOccurs="0"/>
<xs:element name="available-media" type="conference-medias-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: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>
skipping to change at page 23, line 42 skipping to change at page 26, line 23
<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="user-count-type" 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-medias-type" 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:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
CONFERENCE MEDIAS TYPE CONFERENCE MEDIA TYPE
--> -->
<xs:complexType name="conference-medias-type"> <xs:complexType name="conference-media-type">
<xs:sequence> <xs:sequence>
<xs:element name="entry" type="conference-media-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: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 MEDIUM TYPE
--> -->
<xs:complexType name="conference-media-type"> <xs:complexType name="conference-medium-type">
<xs:sequence> <xs:sequence>
<xs:element name="proto" type="xs:string"/> <xs:element name="display-text" type="xs:string"/>
<xs:element name="type" type="xs:string" minOccurs="0"/>
<xs:element name="label" type="xs:string" 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: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>
<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"/>
skipping to change at page 25, line 27 skipping to change at page 27, line 50
<xs:element name="entry" type="count-type" maxOccurs="unbounded"/> <xs:element name="entry" type="count-type" 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>
<!-- <!--
COUNT TYPE COUNT TYPE
--> -->
<xs:complexType name="count-type"> <xs:complexType name="count-type">
<xs:sequence> <xs:sequence>
<xs:element name="role" type="xs:string"/>
<xs:element name="count" type="xs:nonNegativeInteger"/> <xs:element name="count" type="xs:nonNegativeInteger"/>
<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="role" type="xs:string" use="required"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </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
skipping to change at page 26, line 34 skipping to change at page 29, line 4
<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 ROLES TYPE USER ROLES TYPE
--> -->
<xs:complexType name="user-roles-type"> <xs:complexType name="user-roles-type">
<xs:sequence> <xs:sequence>
<xs:element name="entry" type="xs:string" maxOccurs="unbounded"/> <xs:element name="entry" type="xs:string" 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>
<!-- <!--
ENDPOINT TYPE ENDPOINT TYPE
--> -->
<xs:complexType name="endpoint-type"> <xs:complexType name="endpoint-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="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"/>
skipping to change at page 27, line 6 skipping to change at page 29, line 20
<xs:complexType name="endpoint-type"> <xs:complexType name="endpoint-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="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: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:anyURI"/> <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"/>
skipping to change at page 28, line 18 skipping to change at page 30, line 32
<xs:sequence> <xs:sequence>
<xs:element name="when" type="xs:dateTime" minOccurs="0"/> <xs:element name="when" type="xs:dateTime" minOccurs="0"/>
<xs:element name="reason" type="xs:string" minOccurs="0"/> <xs:element name="reason" type="xs:string" minOccurs="0"/>
<xs:element name="by" type="xs:anyURI" minOccurs="0"/> <xs:element name="by" type="xs:anyURI" minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
MEDIA TYPE
-->
<xs:complexType name="media-type">
<xs:sequence>
<xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="proto" type="xs:string" minOccurs="0"/>
<xs:element name="src-id" 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:element name="call" type="call-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<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:complexType>
<!--
MEDIA STATUS TYPE
-->
<xs:simpleType name="media-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="recvonly"/>
<xs:enumeration value="sendonly"/>
<xs:enumeration value="sendrecv"/>
<xs:enumeration value="inactive"/>
</xs:restriction>
</xs:simpleType>
<!--
CALL TYPE CALL TYPE
--> -->
<xs:complexType name="call-type"> <xs:complexType name="call-type">
<xs:choice> <xs:choice>
<xs:element name="sip" type="sip-dialog-id-type"/> <xs:element name="sip" type="sip-dialog-id-type"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice> </xs:choice>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
skipping to change at page 29, line 29 skipping to change at page 31, line 11
<xs:element name="call-id" type="xs:string"/> <xs:element name="call-id" type="xs:string"/>
<xs:element name="from-tag" type="xs:string"/> <xs:element name="from-tag" type="xs:string"/>
<xs:element name="to-tag" type="xs:string"/> <xs:element name="to-tag" type="xs:string"/>
<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>
<!-- <!--
MEDIA TYPE
-->
<xs:complexType name="media-type">
<xs:sequence>
<xs:element name="display-text" 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="src-id" 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:sequence>
<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:complexType>
<!--
MEDIA STATUS TYPE
-->
<xs:simpleType name="media-status-type">
<xs:restriction base="xs:string">
<xs:enumeration value="recvonly"/>
<xs:enumeration value="sendonly"/>
<xs:enumeration value="sendrecv"/>
<xs:enumeration value="inactive"/>
</xs:restriction>
</xs:simpleType>
<!--
SIDEBARS BY VAL TYPE SIDEBARS BY VAL TYPE
--> -->
<xs:complexType name="sidebars-by-val-type"> <xs:complexType name="sidebars-by-val-type">
<xs:sequence> <xs:sequence>
<xs:element name="entry" type="conference-type" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="entry" type="conference-type" 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>
skipping to change at page 30, line 21 skipping to change at page 32, line 30
<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>
<entry> <entry role="any">
<role>any</role>
<count>33</count> <count>33</count>
</entry> </entry>
</user-count> </user-count>
<active-media> <active-media>
<entry> <entry id="1">
<proto>audio</proto> <display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
</entry> </entry>
</active-media> </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>
skipping to change at page 31, line 8 skipping to change at page 33, line 18
<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>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1"> <media id="1">
<display-text>main audio</display-text> <display-text>main audio</display-text>
<proto>audio</proto> <type>audio</type>
<src-id>432424</src-id>
<label>34567</label> <label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status> <status>sendrecv</status>
</media> </media>
</endpoint> </endpoint>
</user> </user>
<!-- <!--
USER USER
--> -->
<user entity="sip:alice@example.net" state="full"> <user entity="sip:alice@example.net" state="full">
<display-text>Alice</display-text> <display-text>Alice</display-text>
<!-- <!--
ENDPOINTS ENDPOINTS
--> -->
<endpoint entity="sip:4kfk4j392jsu@example.net;grid=433kj4j3u"> <endpoint entity="sip:4kfk4j392jsu@example.net;grid=433kj4j3u" call="1">
<status>connected</status> <status>connected</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>
<by>sip:mike@example.com</by> <by>sip:mike@example.com</by>
</joining-info> </joining-info>
<!-- <!--
MEDIA MEDIA
--> -->
<media id="1"> <media id="1">
<display-text>main audio</display-text> <display-text>main audio</display-text>
<proto>audio</proto> <type>audio</type>
<label>34567</label>
<src-id>534232</src-id> <src-id>534232</src-id>
<label>34564</label>
<status>sendrecv</status> <status>sendrecv</status>
</media> </media>
</endpoint> </endpoint>
</user> </user>
</users> </users>
</conference-info> </conference-info>
7.2 Rich Example 7.2 Rich Example
The following is an example conference information document. In this The following is an example conference information document. In this
example of a partial state notification, there are 32 participants in example of a partial state notification, there are 32 participants in
a voice conference. The user Bob has been booted from the conference a voice conference. The user Bob has been booted from the conference
skipping to change at page 32, line 49 skipping to change at page 35, line 15
<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>
<entry> <entry role="any">
<role>any</role>
<count>52</count> <count>52</count>
</entry> </entry>
<entry> <entry role="participant">
<role>participant</role>
<count>50</count> <count>50</count>
</entry> </entry>
</maximum-user-count> </maximum-user-count>
<available-media> <available-media>
<entry> <entry id="1">
<proto>audio</proto> <display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
</entry> </entry>
<entry> <entry id="2">
<proto>video</proto> <display-text>main video</display-text>
<type>video</type>
<label>34569</label>
</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>
</host-info> </host-info>
<!-- <!--
CONFERENCE STATE CONFERENCE STATE
--> -->
<conference-state> <conference-state>
<user-count> <user-count>
<entry> <entry role="any">
<role>any</role>
<count>33</count> <count>33</count>
</entry> </entry>
<entry> <entry role="participant">
<role>participant</role>
<count>32</count> <count>32</count>
</entry> </entry>
</user-count> </user-count>
<active>true</active> <active>true</active>
<locked>false</locked> <locked>false</locked>
<active-media> <active-media>
<entry> <entry id="1">
<proto>audio</proto> <type>audio</type>
</entry> </entry>
</active-media> </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>
<uri>mailto:bob@example.com</uri> <uri>mailto:bob@example.com</uri>
<display-text>email</display-text> <display-text>email</display-text>
</entry> </entry>
</associated-aors> </associated-aors>
<roles> <roles>
<entry>participant</entry> <entry>participant</entry>
skipping to change at page 34, line 30 skipping to change at page 36, line 41
</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"> <endpoint entity="sip:bob@pc33.example.com" call="1">
<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>
skipping to change at page 34, line 50 skipping to change at page 37, line 13
<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>
<!-- <!--
MEDIA CALL INFO
--> -->
<media id="1" state="full"> <call-info>
<display-text>main audio</display-text>
<proto>audio</proto>
<src-id>432424</src-id>
<label>34567</label>
<status>sendrecv</status>
<call>
<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> </call-info>
<!--
MEDIA
-->
<media id="1" state="full">
<display-text>main audio</display-text>
<type>audio</type>
<label>34567</label>
<src-id>432424</src-id>
<status>sendrecv</status>
</media> </media>
</endpoint> </endpoint>
</user> </user>
</users> </users>
<!-- <!--
SIDEBARS BY REFERENCE SIDEBARS BY REFERENCE
--> -->
<sidebars-by-ref> <sidebars-by-ref>
<entry> <entry>
skipping to change at page 36, line 16 skipping to change at page 38, line 29
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
and authorization, and provides guidelines on sensible authorization and authorization, and provides guidelines on sensible authorization
policies. policies.
Since the data in notifications is sensitive as well, end-to-end SIP Since the data in notifications is sensitive as well, end-to-end SIP
encryption mechanisms using S/MIME SHOULD be used to protect it. encryption mechanisms using S/MIME SHOULD be used to protect it.
Since a focus provides participants identity information using this 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 [9]. 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.5 the anonymous URI generation method outlined in section Section 5.6
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, and a new XML application/conference-info+xml, a new XML namespace, a new XML
schema. schema, and creates a sub-registry "URI purposes" under the
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 [8]. 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).
skipping to change at page 39, line 26 skipping to change at page 41, line 32
recording The URI can be used to access the [RFC XXXX] recording The URI can be used to access the [RFC XXXX]
recorded conference data recorded conference data
web-page The URI can be used to access a [RFC XXXX] web-page The URI can be used to access a [RFC XXXX]
web page that contains additional web page that contains additional
information of the conference information of the conference
New values of the "URI purposes" are registered by the IANA when a New values of the "URI purposes" are registered by the IANA when a
specification becomes available and according to the definition of specification becomes available and according to the definition of
RFC 2434 [9]. The IANA Considerations section of the specification RFC 2434 [4]. The IANA Considerations section of the specification
MUST include the following information: MUST include the following information:
Value: The value of the <purpose> element to be registered Value: The value of the <purpose> element to be registered
Description: A short description of the intended usage of the URI Description: A short description of the intended usage of the URI
10. Acknowledgements 10. Acknowledgements
The authors would like to thank Dan Petrie, Sean Olson, Alan The authors would like to thank Dan Petrie, Sean Olson, Alan
Johnston, Rohan Mahy, Cullen Jennings, and Miguel Garcia for their Johnston, Rohan Mahy, Cullen Jennings, Brian Rosen, Roni Even, and
comments and inputs. Miguel Garcia for their comments and inputs.
11. References 11. References
11.1 Normative References 11.1 Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[2] 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] 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", RFC [6] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types",
3023, January 2001. RFC 3023, January 2001.
[7] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., [7] 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 [8] 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 [9] Peterson, J., "A Privacy Mechanism for the Session Initiation
Protocol (SIP)", RFC 3323, November 2002. Protocol (SIP)", RFC 3323, November 2002.
skipping to change at page 40, line 34 skipping to change at page 42, line 42
December 2002. December 2002.
[11] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne, [11] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne,
"Grouping of Media Lines in the Session Description Protocol "Grouping of Media Lines in the Session Description Protocol
(SDP)", RFC 3388, December 2002. (SDP)", RFC 3388, December 2002.
[12] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, [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", STD [13] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
63, RFC 3629, November 2003. STD 63, RFC 3629, November 2003.
[14] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [14] 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 [15] 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, [16] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,
December 2004. December 2004.
[17] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme [17] 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 [18] Rosenberg, J., "A Framework for Conferencing with the Session
Initiation Protocol", Initiation Protocol",
draft-ietf-sipping-conferencing-framework-03 (work in Internet-Draft draft-ietf-sipping-conferencing-framework-03,
progress), October 2004. October 2004.
[19] Rosenberg, J., "An INVITE Inititiated Dialog Event Package for [19] Rosenberg, J., "An INVITE Inititiated Dialog Event Package for
the Session Initiation Protocol (SIP)", the Session Initiation Protocol (SIP)",
draft-ietf-sipping-dialog-package-05 (work in progress), Internet-Draft draft-ietf-sipping-dialog-package-05, November
November 2004. 2004.
[20] Rosenberg, J., "Obtaining and Using Globally Routable User [20] 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)", draft-ietf-sip-gruu-02 (work in progress), July 2004. (SIP)", Internet-Draft draft-ietf-sip-gruu-02, July 2004.
[21] Levin, O. and G. Camarillo, "The SDP (Session Description [21] Levin, O. and G. Camarillo, "The SDP (Session Description
Protocol) Label Attribute", Protocol) Label Attribute",
draft-ietf-mmusic-sdp-media-label-00 (work in progress), Internet-Draft draft-ietf-mmusic-sdp-media-label-01, January
September 2004. 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
US US
Phone: +1 973 952-5000 Phone: +1 973 952-5000
EMail: jdrosen@cisco.com Email: jdrosen@cisco.com
URI: http://www.jdrosen.net URI: http://www.jdrosen.net
Henning Schulzrinne Henning Schulzrinne
Columbia University Columbia University
M/S 0401 M/S 0401
1214 Amsterdam Ave. 1214 Amsterdam Ave.
New York, NY 10027 New York, NY 10027
US US
EMail: schulzrinne@cs.columbia.edu Email: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs URI: http://www.cs.columbia.edu/~hgs
Orit Levin (editor) Orit Levin (editor)
Microsoft Corporation Microsoft Corporation
One Microsoft Way One Microsoft Way
Redmond, WA 98052 Redmond, WA 98052
US US
EMail: oritl@microsoft.com Email: oritl@microsoft.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
skipping to change at page 43, line 41 skipping to change at page 45, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

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