draft-ietf-sipping-conference-package-07.txt   draft-ietf-sipping-conference-package-08.txt 
SIPPING J. Rosenberg SIPPING J. Rosenberg
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Expires: May 28, 2005 H. Schulzrinne Expires: June 6, 2005 H. Schulzrinne
Columbia University Columbia University
O. Levin, Ed. O. Levin, Ed.
Microsoft Corporation Microsoft Corporation
November 27, 2004 December 6, 2004
A Session Initiation Protocol (SIP) Event Package for Conference A Session Initiation Protocol (SIP) Event Package for Conference
State State
draft-ietf-sipping-conference-package-07 draft-ietf-sipping-conference-package-08
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of section 3 of RFC 3667. By submitting this Internet-Draft, each of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with which he or she become aware will be disclosed, in accordance with
RFC 3668. RFC 3668.
skipping to change at page 1, line 40 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 28, 2005. This Internet-Draft will expire on June 6, 2005.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2004).
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 . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Conference Event Package . . . . . . . . . . . . . . . . . . . 6 3. Conference Event Package . . . . . . . . . . . . . . . . . . . 4
3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 6 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5
3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 6 3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5
3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 6 3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5
3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 7 3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 5
3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 7 3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6
3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 7 3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6
3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 8 3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 6
3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 8 3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7
3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 8 3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7
3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 8 3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7
4. Conference Document . . . . . . . . . . . . . . . . . . . . . 10 4. Conference Document . . . . . . . . . . . . . . . . . . . . . 7
4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.1 Format . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 10 4.2 Namespace . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 10 4.3 Versioning . . . . . . . . . . . . . . . . . . . . . . . . 8
4.4 State and Partial Notifications . . . . . . . . . . . . . 10 4.4 State and Partial Notifications . . . . . . . . . . . . . 8
4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 11 4.5 Element Keys . . . . . . . . . . . . . . . . . . . . . . . 8
4.6 Constructing Coherent State Procedure . . . . . . . . . . 11 4.6 Constructing Coherent State Procedure . . . . . . . . . . 9
5. Conference Data . . . . . . . . . . . . . . . . . . . . . . . 13 5. Conference Data . . . . . . . . . . . . . . . . . . . . . . . 10
5.1 conference-type . . . . . . . . . . . . . . . . . . . . . 13 5.1 conference-type . . . . . . . . . . . . . . . . . . . . . 10
5.1.1 conference-description of 5.1.1 conference-description of
conference-description-type . . . . . . . . . . . . . 13 conference-description-type . . . . . . . . . . . . . 11
5.1.2 host-info of host-type . . . . . . . . . . . . . . . . 13 5.1.2 host-info of host-type . . . . . . . . . . . . . . . . 11
5.1.3 conference-state of conference-state-type . . . . . . 14 5.1.3 conference-state of conference-state-type . . . . . . 11
5.1.4 users of users-type . . . . . . . . . . . . . . . . . 14 5.1.4 users of users-type . . . . . . . . . . . . . . . . . 11
5.1.5 sidebars-by-ref of uris-type . . . . . . . . . . . . . 14 5.1.5 sidebars-by-ref of uris-type . . . . . . . . . . . . . 11
5.1.6 sidebar-by-val of conference-type . . . . . . . . . . 14 5.1.6 sidebar-by-val of conference-type . . . . . . . . . . 11
5.2 conference-description-type . . . . . . . . . . . . . . . 14 5.2 conference-description-type . . . . . . . . . . . . . . . 12
5.2.1 display-text of string type . . . . . . . . . . . . . 14 5.2.1 display-text of string type . . . . . . . . . . . . . 12
5.2.2 subject of string type . . . . . . . . . . . . . . . . 14 5.2.2 subject of string type . . . . . . . . . . . . . . . . 12
5.2.3 free-text of string type . . . . . . . . . . . . . . . 14 5.2.3 free-text of string type . . . . . . . . . . . . . . . 12
5.2.4 keywords of keywords-type . . . . . . . . . . . . . . 14 5.2.4 keywords of keywords-type . . . . . . . . . . . . . . 12
5.2.5 conf-uris of uris-type . . . . . . . . . . . . . . . . 15 5.2.5 conf-uris of uris-type . . . . . . . . . . . . . . . . 12
5.2.6 service-uris of uris-type . . . . . . . . . . . . . . 15 5.2.6 service-uris of uris-type . . . . . . . . . . . . . . 13
5.2.7 maximum-user-count of user-count-type . . . . . . . . 15 5.2.7 maximum-user-count of user-count-type . . . . . . . . 13
5.2.8 available-media of conference-medias-type . . . . . . 15 5.2.8 available-media of conference-medias-type . . . . . . 13
5.3 host-type . . . . . . . . . . . . . . . . . . . . . . . . 15 5.3 host-type . . . . . . . . . . . . . . . . . . . . . . . . 13
5.3.1 display-text of string type . . . . . . . . . . . . . 15 5.3.1 display-text of string type . . . . . . . . . . . . . 14
5.3.2 web-page of anyURI type . . . . . . . . . . . . . . . 16 5.3.2 web-page of anyURI type . . . . . . . . . . . . . . . 14
5.3.3 uris of uris-type . . . . . . . . . . . . . . . . . . 16 5.3.3 uris of uris-type . . . . . . . . . . . . . . . . . . 14
5.4 conference-state-type . . . . . . . . . . . . . . . . . . 16 5.4 conference-state-type . . . . . . . . . . . . . . . . . . 14
5.4.1 user-count of user-count-type . . . . . . . . . . . . 16 5.4.1 user-count of user-count-type . . . . . . . . . . . . 14
5.4.2 active of Boolean type . . . . . . . . . . . . . . . . 16 5.4.2 active of Boolean type . . . . . . . . . . . . . . . . 14
5.4.3 locked of Boolean type . . . . . . . . . . . . . . . . 16 5.4.3 locked of Boolean type . . . . . . . . . . . . . . . . 14
5.4.4 recording of uris-type . . . . . . . . . . . . . . . . 16 5.4.4 active-media of conference-medias-type . . . . . . . . 14
5.4.5 active-media of conference-medias-type . . . . . . . . 17 5.5 user-type . . . . . . . . . . . . . . . . . . . . . . . . 15
5.5 user-type . . . . . . . . . . . . . . . . . . . . . . . . 17 5.5.1 display-text of string type . . . . . . . . . . . . . 15
5.5.1 display-text of string type . . . . . . . . . . . . . 17 5.5.2 associated-aors of anyURI type . . . . . . . . . . . . 15
5.5.2 associated-aors of anyURI type . . . . . . . . . . . . 17 5.5.3 roles of user-roles-type . . . . . . . . . . . . . . . 15
5.5.3 roles of user-roles-type . . . . . . . . . . . . . . . 17 5.5.4 language of language type . . . . . . . . . . . . . . 15
5.5.4 language of language type . . . . . . . . . . . . . . 18 5.5.5 cascaded-focus of anyURI type . . . . . . . . . . . . 16
5.5.5 cascaded-focus of anyURI type . . . . . . . . . . . . 18 5.5.6 endpoint of endpoint-type . . . . . . . . . . . . . . 16
5.5.6 endpoint of endpoint-type . . . . . . . . . . . . . . 18 5.6 endpoint-type . . . . . . . . . . . . . . . . . . . . . . 16
5.6 endpoint-type . . . . . . . . . . . . . . . . . . . . . . 18 5.6.1 display-text of string type . . . . . . . . . . . . . 17
5.6.1 display-text of string type . . . . . . . . . . . . . 19 5.6.2 referred of execution-type . . . . . . . . . . . . . . 17
5.6.2 referred of execution-type . . . . . . . . . . . . . . 19 5.6.3 status of endpoint-status-type . . . . . . . . . . . . 17
5.6.3 status of endpoint-status-type . . . . . . . . . . . . 19 5.6.4 joining-method of joining-type . . . . . . . . . . . . 18
5.6.4 joining-method of joining-type . . . . . . . . . . . . 20 5.6.5 joining-info of execution-type . . . . . . . . . . . . 19
5.6.5 joining-info of execution-type . . . . . . . . . . . . 21 5.6.6 disconnection-method of disconnection-type . . . . . . 19
5.6.6 disconnection-method of disconnection-type . . . . . . 21 5.6.7 disconnection-info of execution-type . . . . . . . . . 19
5.6.7 disconnection-info of execution-type . . . . . . . . . 21 5.6.8 media of media-type . . . . . . . . . . . . . . . . . 20
5.6.8 media of media-type . . . . . . . . . . . . . . . . . 22 5.7 media-type . . . . . . . . . . . . . . . . . . . . . . . . 20
5.7 media-type . . . . . . . . . . . . . . . . . . . . . . . . 22 5.7.1 display-text of string type . . . . . . . . . . . . . 20
5.7.1 display-text of string type . . . . . . . . . . . . . 22 5.7.2 proto of string type . . . . . . . . . . . . . . . . . 20
5.7.2 proto of string type . . . . . . . . . . . . . . . . . 22 5.7.3 src-id of string type . . . . . . . . . . . . . . . . 20
5.7.3 src-id of string type . . . . . . . . . . . . . . . . 22 5.7.4 label of string type . . . . . . . . . . . . . . . . . 21
5.7.4 label of string type . . . . . . . . . . . . . . . . . 23 5.7.5 status of media-status-type . . . . . . . . . . . . . 21
5.7.5 status of media-status-type . . . . . . . . . . . . . 23 5.7.6 call of call-type . . . . . . . . . . . . . . . . . . 21
5.7.6 call of call-type . . . . . . . . . . . . . . . . . . 23 6. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6. XML Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 7.1 Basic Example . . . . . . . . . . . . . . . . . . . . . . 29
7.1 Basic Example . . . . . . . . . . . . . . . . . . . . . . 32 7.2 Rich Example . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Rich Example . . . . . . . . . . . . . . . . . . . . . . . 34 8. Security Considerations . . . . . . . . . . . . . . . . . . . 36
8. Security Considerations . . . . . . . . . . . . . . . . . . . 39 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 40 9.1 conference Event Package Registration . . . . . . . . . . 36
9.1 conference Event Package Registration . . . . . . . . . . 40 9.2 application/conference-info+xml MIME Registration . . . . 36
9.2 application/conference-info+xml MIME Registration . . . . 40
9.3 URN Sub-Namespace Registration for 9.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 40 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 37
9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 41 9.4 XML Schema Registration . . . . . . . . . . . . . . . . . 38
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 42 9.5 URI Purposes Sub-registry Establishment . . . . . . . . . 38
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 39
11.1 Normative References . . . . . . . . . . . . . . . . . . . . 43 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 39
11.2 Informative References . . . . . . . . . . . . . . . . . . . 43 11.1 Normative References . . . . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 44 11.2 Informative References . . . . . . . . . . . . . . . . . . . 40
Intellectual Property and Copyright Statements . . . . . . . . 46 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 41
Intellectual Property and Copyright Statements . . . . . . . . 43
1. Introduction 1. Introduction
The Session Initiation Protocol (SIP) [6] Events framework Events The Session Initiation Protocol (SIP) [7] Events framework Events
Framework [7] defines general mechanisms for subscribing to, and Framework [8] defines general mechanisms for subscribing to, and
receiving notifications of, events within SIP networks. It receiving notifications of, events within SIP networks. It
introduces the notion of a package, which is a specific introduces the notion of a package, which is a specific
"instantiation" of the events framework for a well-defined set of "instantiation" of the events framework for a well-defined set of
events. Here, we define an event package for SIP conferences. This events. Here, we define an event package for SIP conferences. This
package provides the conference notification service as outlined in package provides the conference notification service as outlined in
the SIP conferencing framework [16]. As described there, the SIP conferencing framework [18]. As described there,
subscriptions to a conference URI are routed to the focus that is subscriptions to a conference URI are routed to the focus that is
handling the conference. It acts as the notifier, and provides handling the conference. It acts as the 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
skipping to change at page 6, line 11 skipping to change at page 4, line 37
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations. indicate requirement levels for compliant implementations.
3. Conference Event Package 3. Conference Event Package
The conference event package allows a user to subscribe to a The conference event package allows a user to subscribe to a
conference. In SIP, conferences are represented by URIs. These URIs conference. In SIP, conferences are represented by URIs. These URIs
route to a SIP user agent, called a focus, that is responsible for route to a SIP user agent, called a focus, that is responsible for
ensuring that all users in the conference can communicate with each ensuring that all users in the conference can communicate with each
other, as described in Conferencing Framework [16]. 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 a participant in the conference may in fact be another
focus. In order to provide a more complete participant list, the focus. In order to provide a more complete participant list, the
focus MAY subscribe to the conference package of the other focus to focus MAY subscribe to the conference package of the other focus to
discover the participant list in the cascaded conference. This discover the participant list in the cascaded conference. This
information can then be included in notifications by using of the information can then be included in notifications by 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 Events package, This section provides the details for defining a SIP-specific event
as specified by RFC 3265 [7]. 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
[7]. [8].
3.2 SUBSCRIBE Bodies 3.2 SUBSCRIBE Bodies
A SUBSCRIBE for a conference package MAY contain a body. This body A SUBSCRIBE for a conference package MAY contain a body. This body
defines a filter to apply to the subscription. Filter documents are defines a filter to apply to the subscription. Filter documents are
not specified in this document, and at the time of writing, are not specified in this document, and at the time of writing, are
expected to be the subject of future standardization activity. expected to be the subject of future standardization activity.
A SUBSCRIBE for a conference package MAY be sent without a body. A SUBSCRIBE for a conference package MAY be sent without a body.
This implies the default subscription filtering policy. The default This implies the default subscription filtering policy. The default
skipping to change at page 7, line 4 skipping to change at page 5, line 33
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" RFC 3265
[7]. [8].
3.4 NOTIFY Bodies 3.4 NOTIFY Bodies
As described in RFC 3265 [7], 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
conference information document. This document describes the state conference information document. This document describes the state
of a conference. All subscribers and notifiers MUST support the of a conference. All subscribers and notifiers MUST support the
"application/conference-info+xml" data format described in Section 5. "application/conference-info+xml" data format described in Section 5.
The subscribe request MAY contain an Accept header field. If no such The subscribe request MAY contain an Accept header field. If no such
skipping to change at page 10, line 11 skipping to change at page 7, line 40
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 SHOULD be valid. It MUST be based on Extensible Markup Language
(XML) 1.0 and MUST be encoded using UTF-8 [11]. (XML) 1.0 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 [4] and [2], using the namespace identifier 'ietf' defined by [5] and
extended by RFC 3688 [12]. 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.
skipping to change at page 11, line 25 skipping to change at page 9, line 8
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>, <user>, and <endpoint> use as the key
'entity' 'entity'
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 o Sub-element <entry> of uris-type contained in elements <conf-uris>
<conf-uris>, <service-uris>, and <recording> uses as the key and <service-uris> uses as the key <uri>
<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-medias-type use as the key <proto>
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 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>
skipping to change at page 15, line 13 skipping to change at page 12, line 39
search engines to better classify the conference. search engines to better classify the conference.
5.2.5 conf-uris of uris-type 5.2.5 conf-uris of uris-type
This element contains a set of <entry> sub-elements - each containing This element contains a set of <entry> sub-elements - each containing
the information about an additional conference URI that this the information about an additional conference URI that this
conference can be accessed by. The value of the URI is included in conference can be accessed by. The value of the URI is included in
the <uri> sub-element and its description MAY be included in the the <uri> sub-element and its description MAY be included in the
<display-text> sub-element. <display-text> sub-element.
Examples of such URIs include h323: [15] and tel: [14] URIs. The purpose of the URI SHOULD be included in the <purpose>
sub-element. The currently defined <purpose> values to be used with
the <conf-uris> are:
participation: Indicates that dialing into this URI will bring the
party into the conference
streaming: Indicates that "listening" to this URI will provide the
conference live content
Future extensions to this schema may define new values and register
them with IANA under the registry established by this specification.
Examples of such URIs include sip: / sips: [7], h323: [17], and tel:
[16] URIs.
5.2.6 service-uris of uris-type 5.2.6 service-uris of uris-type
This element contains a set of <entry> sub-elements - each containing This element contains a set of <entry> sub-elements - each containing
the URI to be used in order to access different services available the URI to be used in order to access different services available
for the particular conference. The value of the URI is included in for the particular conference. The value of the URI is included in
the <uri> sub-element and its description MAY be included in the the <uri> sub-element and its description MAY be included in the
<display-text> sub-element. The purpose of the URI SHOULD be <display-text> sub-element.
included in the <purpose> sub-element. The only currently defined
<purpose> value is "web-page" which indicates a web page that The purpose of the URI SHOULD be included in the <purpose>
contains additional information about the conference. Future sub-element. The currently defined <purpose> values to be used with
extensions to this schema may define new values and establish an IANA the <service-uris> are:
registry for the new values.
web-page: Indicates the web page containing the additional
information about the conference
recording: Indicates the link at which the recorded conference
context can be retrieved
event: Indicates the URI to which the subscription to the conference
event package needs to be performed
Future extensions to this schema may define new values and register
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 is used to specify the maximum number of users permitted
in the conference. The number SHOULD be provided for all in the conference. The number SHOULD be provided for all
participants in total by populating the <role> sub-element with value participants in total by populating the <role> sub-element with value
"any". Additionally counters for users with certain roles in the "any". Additionally counters for users with certain roles in the
conference MAY be separately provided. conference MAY be separately provided.
5.2.8 available-media of conference-medias-type 5.2.8 available-media of conference-medias-type
skipping to change at page 16, line 46 skipping to change at page 14, line 50
and its conference URI reserved and published. Still, the conference and its conference URI reserved and published. Still, the conference
will not be "active" till its actual start time. will not be "active" till its actual start time.
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 recording of uris-type 5.4.4 active-media of conference-medias-type
The <entry> sub-element contains URIs related to the recording of the
conference.
5.4.5 active-media of conference-medias-type
This element contains information about the media types currently This element contains information about the media types currently
active in the conference, which is a subset of those listed in the active in the conference, which is a subset of those listed in the
<available-media> element. <available-media> element.
5.5 user-type 5.5 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
participants, the focus must ensure that each anonymous URI is participants, the focus must ensure that each anonymous URI is
unique. The guidelines for generating anonymous URIs in RFC 3323 unique. The guidelines for generating anonymous URIs in RFC 3323
[8] should be followed. For example, [9] should be followed. For example,
"Anonymous1" <sip:anonymous1@anonymous.invalid> "Anonymous1" <sip:anonymous1@anonymous.invalid>
could be used for a participant requesting privacy. could be used for a participant requesting privacy.
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").
skipping to change at page 18, line 16 skipping to change at page 16, line 12
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.5.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 [16], 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 [17] of the subscribing to both this package and the Dialog Package [19] of the
cascaded foci and correlating the relevant information. cascaded foci and correlating the relevant information.
5.5.6 endpoint of endpoint-type 5.5.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 user. The
element of the endpoint-type can have unbounded number of appearance element of the endpoint-type can have unbounded number of appearance
in the user-type for each endpoint of the user participating in the in the user-type for each endpoint of the user participating in the
conference. In a case when authentication is performed per endpoint 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 (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 logical association among endpoints being used by the same user. In
skipping to change at page 18, line 52 skipping to change at page 16, line 48
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 [8] should be guidelines for generating anonymous URIs in RFC 3323 [9] should be
followed. followed.
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.
skipping to change at page 21, line 46 skipping to change at page 19, line 46
5.6.7 disconnection-info of execution-type 5.6.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.
reason: This element contains the reason the endpoint departed the reason: This element contains the reason the endpoint departed the
conference. When known, it is RECOMMENDED to include the numeric conference. When known and meaningful, it is RECOMMENDED to
reason followed by the descriptive text as conveyed/reported by include the information as conveyed/reported by the call signaling
the call signaling. in the format defined by RFC 3326 [10]. For example,
<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.6.8 media of media-type
This element contains information about a media stream of this This element contains information about a media stream of this
endpoint. The element of the media-type can have unbounded number of endpoint. The element of the media-type can have an unbounded number
appearance 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 it is possible that media streams listed under a
common endpoint MAY be established by separate signaling means and common endpoint MAY be established by separate signaling means and
consequently belong to different signaling "calls". consequently belong to different signaling "calls".
5.7 media-type 5.7 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 a unique identifier of a media stream on a per
endpoint basis. This attribute is used as a key to identify media endpoint basis. This attribute is used as a key to identify media
streams which may be added and deleted on a dynamic basis during streams which may be added and deleted on a dynamic basis during
the conference. If the SDP "mid" (as defined in Grouping of Media the conference. If the SDP "mid" (as defined in Grouping of Media
Lines in the SDP [9]) is used for establishing the media stream, Lines in the SDP [11]) is used for establishing the media stream,
the 'id' SHOULD contain the same "mid" value, otherwise the the 'id' SHOULD contain the same "mid" value, otherwise the
notification service MUST generate an 'id' value which is unique notification service MUST generate an 'id' value which is unique
in the endpoint context. 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").
skipping to change at page 22, line 52 skipping to change at page 21, line 4
5.7.2 proto of string type 5.7.2 proto 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 "proto" 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.3 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 [10] the actual source of the media. For example, for the RTP/RTCP [12]
media streams the value MUST contain the SSRC value generated by the media 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 [10], 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
perform an SSRC to user mapping and identify "a current speaker".
5.7.4 label of string type 5.7.4 label of string type
The element <label> carries a unique identifier for this stream among The element <label> carries a unique identifier for this stream among
all streams in the conference and is assigned by the focus. The all streams in the conference and is assigned by the focus. The
value of this element corresponds to the SDP "label" media attribute value of this element corresponds to the SDP "label" media attribute
defined in [19]. defined in [21].
5.7.5 status of media-status-type 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".
skipping to change at page 25, line 22 skipping to change at page 23, line 18
<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-medias-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>
<xs:element name="display-text" type="xs:string" minOccurs="0"/> <xs:element name="display-text" type="xs:string" minOccurs="0"/>
<xs:element name="web-page" type="xs:anyURI" minOccurs="0"/> <xs:element name="web-page" type="xs:anyURI" minOccurs="0"/>
<xs:element name="uris" type="uris-type" minOccurs="0"/> <xs:element name="uris" type="uris-type" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/> <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="state" type="state-type" use="optional" default="full"/> <xs:attribute name="state" type="state-type" use="optional" default="full"/>
<xs:anyAttribute namespace="##other"/> <xs:anyAttribute namespace="##other"/>
</xs:complexType> </xs:complexType>
<!-- <!--
CONFERENCE STATE TYPE CONFERENCE STATE TYPE
--> -->
<xs:complexType name="conference-state-type"> <xs:complexType name="conference-state-type">
<xs:sequence> <xs:sequence>
<xs:element name="user-count" type="user-count-type" minOccurs="0"/> <xs:element name="user-count" type="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="recording" type="uris-type" minOccurs="0"/>
<xs:element name="active-media" type="conference-medias-type" minOccurs="0"/> <xs:element name="active-media" type="conference-medias-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 MEDIAS TYPE
--> -->
<xs:complexType name="conference-medias-type"> <xs:complexType name="conference-medias-type">
<xs:sequence> <xs:sequence>
skipping to change at page 34, line 32 skipping to change at page 32, line 24
--> -->
<conference-description> <conference-description>
<display-text>Weekly Sales Meeting</display-text> <display-text>Weekly Sales Meeting</display-text>
<subject>Agenda: This month's goals</subject> <subject>Agenda: This month's goals</subject>
<free-text>We will start strict on time</free-text> <free-text>We will start strict on time</free-text>
<keywords>sales, meeting, weekly</keywords> <keywords>sales, meeting, weekly</keywords>
<conf-uris> <conf-uris>
<entry> <entry>
<uri>tel:+18005671234</uri> <uri>tel:+18005671234</uri>
<display-text>TTI Bridge</display-text> <display-text>TTI Bridge</display-text>
<purpose>participation</purpose>
</entry> </entry>
<entry> <entry>
<uri>h323:conf545@h323.example.com</uri> <uri>h323:conf545@h323.example.com</uri>
<purpose>participation</purpose>
</entry> </entry>
<entry>
<uri>http://real.streaming.com/54634/live.ram</uri>
<purpose>streaming</purpose>
</entry>
</conf-uris> </conf-uris>
<service-uris> <service-uris>
<entry> <entry>
<uri>http://sharepoint/salesgroup/</uri> <uri>http://sharepoint/salesgroup/</uri>
<purpose>web-page</purpose> <purpose>web-page</purpose>
</entry> </entry>
<entry>
<uri>http://quicktime.com/54634/recording.mov</uri>
<display-text>Quicktime</display-text>
<purpose>recording</purpose>
</entry>
</service-uris> </service-uris>
<maximum-user-count> <maximum-user-count>
<entry> <entry>
<role>any</role> <role>any</role>
<count>52</count> <count>52</count>
</entry> </entry>
<entry> <entry>
<role>participant</role> <role>participant</role>
<count>50</count> <count>50</count>
</entry> </entry>
skipping to change at page 35, line 46 skipping to change at page 33, line 50
<count>33</count> <count>33</count>
</entry> </entry>
<entry> <entry>
<role>participant</role> <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>
<recording>
<entry>
<uri>http://quicktime.streaming.com/54634/recording.mov</uri>
<display-text>Quicktime</display-text>
</entry>
<entry>
<uri>http://real.streaming.com/54634/recording.ram</uri>
</entry>
</recording>
<active-media> <active-media>
<entry> <entry>
<proto>audio</proto> <proto>audio</proto>
</entry> </entry>
</active-media> </active-media>
</conference-state> </conference-state>
<!-- <!--
USERS USERS
--> -->
skipping to change at page 39, line 21 skipping to change at page 36, line 22
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 participants 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 [8]. 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.5
of this document MUST be followed. of this document MUST be followed.
9. IANA Considerations 9. IANA Considerations
This document registers a SIP event package, a new MIME type, This document registers a SIP event package, a new MIME type,
application/conference-info+xml, a new XML namespace, and a new XML application/conference-info+xml, a new XML namespace, and a new XML
schema. schema.
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 [7]. 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).
Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net. Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net.
9.2 application/conference-info+xml MIME Registration 9.2 application/conference-info+xml MIME Registration
MIME media type name: application MIME media type name: application
MIME subtype name: conference-info+xml MIME subtype name: conference-info+xml
Mandatory parameters: none Mandatory parameters: none
Optional parameters: Same as charset parameter application/xml as Optional parameters: Same as charset parameter application/xml as
specified in RFC 3023 [5]. specified in RFC 3023 [6]
Encoding considerations: Same as encoding considerations of Encoding considerations: Same as encoding considerations of
application/xml as specified in RFC 3023 [5]. application/xml as specified in RFC 3023 [6]
Security considerations: See Section 10 of RFC 3023 [5] and Section 8 Security considerations: See Section 10 of RFC 3023 [6] and Section 8
of this specification. of this specification
Interoperability considerations: none. Interoperability considerations: none
Published specification: This document. Published specification: This document
Applications which use this media type: This document type has been Applications which use this media type: This document type has been
used to support SIP conferencing applications. used to support SIP conferencing applications
Additional Information: Additional Information:
Magic Number: None Magic Number: None
File Extension: .cif or .xml File Extension: .cif or .xml
Macintosh file type code: "TEXT" Macintosh file type code: "TEXT"
Personal and email address for further information: Jonathan Personal and email address for further information: Jonathan
Rosenberg, <jdrosen@jdrosen.net> Rosenberg, <jdrosen@jdrosen.net>
Intended usage: COMMON Intended usage: COMMON
Author/Change controller: The IETF. Author/Change controller: The IETF
9.3 URN Sub-Namespace Registration for 9.3 URN Sub-Namespace Registration for
urn:ietf:params:xml:ns:conference-info urn:ietf:params:xml:ns:conference-info
This section registers a new XML namespace, as per the guidelines in This section registers a new XML namespace, as per the guidelines in
RFC 3688 [12]. RFC 3688 [14].
URI: The URI for this namespace is URI: The URI for this namespace is
urn:ietf:params:xml:ns:conference-info. urn:ietf:params:xml:ns:conference-info
Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>, Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>,
Jonathan Rosenberg <jdrosen@jdrosen.net>. Jonathan Rosenberg <jdrosen@jdrosen.net>
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
skipping to change at page 41, line 32 skipping to change at page 38, line 11
<h1>Namespace for Conference Information</h1> <h1>Namespace for Conference Information</h1>
<h2>urn:ietf:params:xml:ns:conference-info</h2> <h2>urn:ietf:params:xml:ns:conference-info</h2>
<p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p> <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
</body> </body>
</html> </html>
END END
9.4 XML Schema Registration 9.4 XML Schema Registration
This specification registers a schema, as per the guidelines in RFC This specification registers a schema, as per the guidelines in RFC
3688 [12]. 3688 [14].
URI: please assign. URI: please assign
Registrant Contact: IETF, SIPPING Working Group Registrant Contact: IETF, SIPPING Working Group
(sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net). (sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net)
XML: The XML can be found as the sole content of Section 6. XML: The XML can be found as the sole content of Section 6
9.5 URI Purposes Sub-registry Establishment
This document instructs the IANA to create a new sub-registry "URI
purposes" under the already existing registry:
http://www.iana.org/assignments/sip-parameters.
The purpose of a URI is an XML element, encoded in the conference
event package [RFC XXXX - substitute with the number assigned to this
draft]. The value of the <purpose> element indicates the intended
usage of the URI in the context of the conference event package and
is defined in sections Section 5.2.5 and Section 5.2.6 of this
specification.
This sub-registry is defined as a table that contains the following
three columns:
Value: The token under registration
Description: A descriptive text defining the intended usage of the
URI
Document: A reference to the document defining the registration
This specification instructs IANA to create the table with the
initial content as defined below:
Value Description Document
------- ---------------------------------- ----------
participation The URI can be used to join the [RFC XXXX]
conference
streaming The URI can be used to access the [RFC XXXX]
streamed conference data
event The URI can be used to subscribe [RFC XXXX]
to the conference event package
recording The URI can be used to access the [RFC XXXX]
recorded conference data
web-page The URI can be used to access a [RFC XXXX]
web page that contains additional
information of the conference
New values of the "URI purposes" are registered by the IANA when a
specification becomes available and according to the definition of
RFC 2434 [9]. The IANA Considerations section of the specification
MUST include the following information:
Value: The value of the <purpose> element to be registered
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, and Miguel Garcia for their
comments and inputs. 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] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, [4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 2434, October
1998.
[5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
August 1999. August 1999.
[5] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC [6] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC
3023, January 2001. 3023, January 2001.
[6] 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.
[7] 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.
[8] 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.
[9] Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne, [10] Schulzrinne, H., Oran, D. and G. Camarillo, "The Reason Header
Field for the Session Initiation Protocol (SIP)", RFC 3326,
December 2002.
[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.
[10] 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.
[11] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD [13] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD
63, RFC 3629, November 2003. 63, RFC 3629, November 2003.
[12] 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
[13] 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.
[14] Vaha-Sipila, A., "URLs for Telephone Calls", RFC 2806, April [16] Schulzrinne, H., "The tel URI for Telephone Numbers", RFC 3966,
2000. December 2004.
[15] 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.
[16] 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 draft-ietf-sipping-conferencing-framework-03 (work in
progress), October 2004. progress), October 2004.
[17] 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), draft-ietf-sipping-dialog-package-05 (work in progress),
November 2004. November 2004.
[18] 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)", draft-ietf-sip-gruu-02 (work in progress), July 2004.
[19] 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), draft-ietf-mmusic-sdp-media-label-00 (work in progress),
September 2004. September 2004.
Authors' Addresses Authors' Addresses
Jonathan Rosenberg Jonathan Rosenberg
Cisco Systems Cisco Systems
600 Lanidex Plaza 600 Lanidex Plaza
Parsippany, NJ 07054 Parsippany, NJ 07054
 End of changes. 

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