view Side-By-Side changes

Internet-Draft                                               dynamicsoft
Expires: January 16, April 25, 2005                                   H. Schulzrinne
                                                     Columbia University
                                                           O. Levin, Ed.
                                                   Microsoft Corporation
                                                           July 18,
                                                        October 25, 2004



    A Session Initiation Protocol (SIP) Event Package for Conference
                                 State
                draft-ietf-sipping-conference-package-05
                draft-ietf-sipping-conference-package-06


Status of this Memo


   This document is an Internet-Draft and is subject to all provisions
   of section 3 of RFC 3667.  By submitting this Internet-Draft, each
   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 become aware will be disclosed, in accordance with
   RFC 3668.


   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.


   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."


   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
   http://www.ietf.org/shadow.html.


   This Internet-Draft will expire on January 16, April 25, 2005.


Copyright Notice


   Copyright (C) The Internet Society (2004).  All Rights Reserved.


Abstract


   This document defines a conference event package for the Session
   Initiation Protocol (SIP) Events framework, along with a data format
   used in notifications for this package.  The conference package




Rosenberg, et al.        Expires January 16, April 25, 2005                 [Page 1]
Internet-Draft             Conference Package                  July               October 2004



   allows users to subscribe to a conference URI.  Notifications are
   sent about changes in the membership of this conference and
   optionally about changes in the state of additional conference
   components.


Table of Contents


   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4  5
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  5  6
   3.  Conference Event Package . . . . . . . . . . . . . . . . . . .  6  7
     3.1   Event Package Name . . . . . . . . . . . . . . . . . . . .  6  7
     3.2   SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . .  6  7
     3.3   Subscription Duration  . . . . . . . . . . . . . . . . . .  6  7
     3.4   NOTIFY Bodies  . . . . . . . . . . . . . . . . . . . . . .  7  8
     3.5   Notifier Processing of SUBSCRIBE Requests  . . . . . . . .  7  8
     3.6   Notifier Generation of NOTIFY Requests . . . . . . . . . .  7  8
     3.7   Subscriber Processing of NOTIFY Requests . . . . . . . . .  8  9
     3.8   Handling of Forked Requests  . . . . . . . . . . . . . . .  8  9
     3.9   Rate of Notifications  . . . . . . . . . . . . . . . . . .  8  9
     3.10  State Agents . . . . . . . . . . . . . . . . . . . . . . .  8  9
   4.  Conference Data Format . Model  . . . . . . . . . . . . . . . . . . . 10
     4.1   Conference Information . . . 11
   5.  Constructing Coherent State  . . . . . . . . . . . . . . . 10
       4.1.1   User Element . . 12
   6.  Conference Data  . . . . . . . . . . . . . . . . . . . 10
         4.1.1.1   User Attributes . . . . 14
     6.1   Conference Information . . . . . . . . . . . . . 11
         4.1.1.2   User Status Elements . . . . . 14
       6.1.1   Conference Type  . . . . . . . . . . 12
         4.1.1.3   Media Information . . . . . . . . . 14
         6.1.1.1   conference-description of
                   conference-description-type  . . . . . . . 13
           4.1.1.3.1   Media Attributes . . . . 14
         6.1.1.2   host-info of host-type . . . . . . . . . . . 13
           4.1.1.3.2   Media Elements . . . 14
         6.1.1.3   conference-state of conference-state-type  . . . . 15
         6.1.1.4   user of user-type  . . . . . . . . . 14
         4.1.1.4   User Role . . . . . . . 15
         6.1.1.5   sidebars-by-ref of uris-type . . . . . . . . . . . 15
         6.1.1.6   sidebar-by-val of conference-type  . . 14
       4.1.2   Sidebar Element . . . . . . 15
       6.1.2   Conference Description Type  . . . . . . . . . . . . . 15
       4.1.3   Additional Conference Identifiers
         6.1.2.1   display-text of string type  . . . . . . . . . . . 15
       4.1.4   Policy URIs
         6.1.2.2   subject of string type . . . . . . . . . . . . . . 15
         6.1.2.3   free-text of string type . . . . . . . . 15
       4.1.5   Recording . . . . . 15
         6.1.2.4   keywords of keywords-type  . . . . . . . . . . . . 16
         6.1.2.5   web-page of anyURI type  . . . . . 15
       4.1.6   Streaming . . . . . . . . 16
         6.1.2.6   conf-uris of uris-type . . . . . . . . . . . . . . 16
     4.2   Constructing Coherent State  .
         6.1.2.7   service-uris of uris-type  . . . . . . . . . . . . 16
         6.1.2.8   maximum-user-count of user-count-type  . . 16
       4.2.1   The Algorithm . . . . 16
         6.1.2.9   available-media of conference-medias-type  . . . . 16
       6.1.3   Host Type  . . . . . . . . . . . . 17
     4.3   Schema . . . . . . . . . . 16
         6.1.3.1   display-text of string type  . . . . . . . . . . . 16
         6.1.3.2   web-page of anyURI type  . . . . . 18
     4.4   Example . . . . . . . . 17
         6.1.3.3   uris of uris-type  . . . . . . . . . . . . . . . . 17
       6.1.4   Conference State Type  . 21
   5.  Security Considerations . . . . . . . . . . . . . . . 17
         6.1.4.1   user-count of user-count-type  . . . . 23
   6.  IANA Considerations . . . . . . 17




Rosenberg, et al.        Expires April 25, 2005                 [Page 2]
Internet-Draft             Conference Package               October 2004



         6.1.4.2   security-level of security-level-type  . . . . . . 17
         6.1.4.3   active of Boolean type . . . . . . . . . 24
     6.1   conference Event Package Registration . . . . . 17
         6.1.4.4   locked of Boolean type . . . . . 24
     6.2   application/conference-info+xml MIME Registration . . . . 24
     6.3   URN Sub-Namespace Registration for
           urn:ietf:params:xml:ns:conference-info . . . . . 17
         6.1.4.5   recording of uris-type . . . . . 24
     6.4   XML Schema Registration . . . . . . . . . 17
         6.1.4.6   active-media of conference-medias-type . . . . . . 18
       6.1.5   User Type  . . 25
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . 18
         6.1.5.1   display-text of string type  . . . 26
   8.  Changes History . . . . . . . . 18
         6.1.5.2   associated-aors of anyURI type . . . . . . . . . . 18
         6.1.5.3   roles of user-roles-type . . . . . 27
     8.1   Changes since -04 . . . . . . . . 18
         6.1.5.4   language of language type  . . . . . . . . . . . . 27




Rosenberg, et al.       Expires January 16, 2005                [Page 2]
Internet-Draft             Conference Package                  July 2004



     8.2   Changes since -03 19
         6.1.5.5   cascaded-focus of anyURI type  . . . . . . . . . . 19
         6.1.5.6   endpoint of endpoint-type  . . . . . . . . . . 27
     8.3   Changes since -02 . . 19
       6.1.6   Endpoint Type  . . . . . . . . . . . . . . . . . . 27
     8.4   Changes since -01 . . 19
         6.1.6.1   display-text of string type  . . . . . . . . . . . 20
         6.1.6.2   referred of execution-type . . . . . . . 28
   9.  References . . . . . 20
         6.1.6.3   state of endpoint-state-type . . . . . . . . . . . 20
         6.1.6.4   joining-method of joining-type . . . . . . . . . . 29
   9.1   Normative References 21
         6.1.6.5   joining-info of execution-type . . . . . . . . . . 21
         6.1.6.6   disconnection-method of disconnection-type . . . . 22
         6.1.6.7   disconnection-info of disconnection-type . . . . . 22
         6.1.6.8   whispering-to of uris-type . 29
   9.2   Informative References . . . . . . . . . . . 22
         6.1.6.9   media of media-type  . . . . . . . . 29
       Authors' Addresses . . . . . . . 22
       6.1.7   Media Type . . . . . . . . . . . . . . . 30
       Intellectual Property and Copyright Statements . . . . . . . 23
         6.1.7.1   display-text of string type  . 32












































Rosenberg, et al.       Expires January 16, 2005                [Page 3]
Internet-Draft             Conference Package                  July 2004



1.  Introduction


   The Session Initiation Protocol (SIP) [6] Events framework Events
   Framework [7] defines general mechanisms for subscribing to, and
   receiving notifications of, events within SIP networks.  It
   introduces the notion . . . . . . . . . . 23
         6.1.7.2   proto of a package, which is a specific
   "instantiation" string type . . . . . . . . . . . . . . . 23
         6.1.7.3   ssrc of the events framework for a well-defined set string type  . . . . . . . . . . . . . . . 23
         6.1.7.4   label of
   events.  Here, we define an event package for SIP conferences.  This
   package provides the conference notification service as outlined in
   the SIP conferencing framework [14].  As described there,
   subscriptions to a conference URI are routed to the focus that is
   handling the conference.  It acts as the notifier, and provides
   clients with updates on conference state.


   The information provided by this package is comprised string type . . . . . . . . . . . . . . . 24
         6.1.7.5   state of conference
   identifier(s), conference participants (optionally with their
   statuses and media description), conference sidebars, conference
   policy URIs, etc.


































Rosenberg, et al.       Expires January 16, 2005                [Page 4]
Internet-Draft             Conference Package                  July 2004



2.  Terminology


   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", media-state-type  . . . . . . . . . . . . 24
         6.1.7.6   snd-status of media-state-type . . . . . . . . . . 24
         6.1.7.7   rcv-status state of media-state-type . . . . . . . 24
         6.1.7.8   call of call-type  . . . . . . . . . . . . . . . . 24
   7.  Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
   8.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
     8.1   Basic Example  . . . . . . . . . . . . . . . . . . . . . . 33
     8.2   Rich Example . . . . . . . . . . . . . . . . . . . . . . . 35
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 40
   10.   IANA Considerations  . . . . . . . . . . . . . . . . . . . . 41
     10.1  conference Event Package Registration  . . . . . . . . . . 41
     10.2  application/conference-info+xml MIME Registration  . . . . 41
     10.3  URN Sub-Namespace Registration for
           urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 41
     10.4  XML Schema Registration  . . . . . . . . . . . . . . . . . 42
   11.   Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43
   12.   Changes History  . . . . . . . . . . . . . . . . . . . . . . 44
     12.1  Changes since -05  . . . . . . . . . . . . . . . . . . . . 44
     12.2  Changes since -04  . . . . . . . . . . . . . . . . . . . . 44
     12.3  Changes since -03  . . . . . . . . . . . . . . . . . . . . 44
     12.4  Changes since -02  . . . . . . . . . . . . . . . . . . . . 44




Rosenberg, et al.        Expires April 25, 2005                 [Page 3]
Internet-Draft             Conference Package               October 2004



     12.5  Changes since -01  . . . . . . . . . . . . . . . . . . . . 45
   13.   References . . . . . . . . . . . . . . . . . . . . . . . . . 46
   13.1  Normative References . . . . . . . . . . . . . . . . . . . . 46
   13.2  Informative References . . . . . . . . . . . . . . . . . . . 46
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 47
       Intellectual Property and Copyright Statements . . . . . . . . 49














































Rosenberg, et al.        Expires April 25, 2005                 [Page 4]
Internet-Draft             Conference Package               October 2004



1.  Introduction


   The Session Initiation Protocol (SIP) [6] Events framework Events
   Framework [7] defines general mechanisms for subscribing to, and
   receiving notifications of, events within SIP networks.  It
   introduces the notion of a package, which is a specific
   "instantiation" of the events framework for a well-defined set of
   events.  Here, we define an event package for SIP conferences.  This
   package provides the conference notification service as outlined in
   the SIP conferencing framework [15].  As described there,
   subscriptions to a conference URI are routed to the focus that is
   handling the conference.  It acts as the notifier, and provides
   clients with updates on conference state.


   The information provided by this package is comprised of conference
   identifier(s), conference participants (optionally with their
   statuses and media description), conference sidebars, conference
   service URIs, etc.


































Rosenberg, et al.        Expires April 25, 2005                 [Page 5]
Internet-Draft             Conference Package               October 2004



2.  Terminology


   In this document, the key words "MUST", "MUST NOT", "REQUIRED",
   "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
   and "OPTIONAL" "OPTIONAL" are to be interpreted as described in RFC 2119 [2] and
   indicate requirement levels for compliant implementations.














































Rosenberg, et al.        Expires April 25, 2005                 [Page 6]
Internet-Draft             Conference Package               October 2004



3.  Conference Event Package


   The conference event package allows a user to subscribe to a
   conference.  In SIP, conferences are represented by URIs.  These URIs
   route to a SIP user agent, called a focus, that is responsible for
   ensuring that all users in the conference can communicate with each
   other, as described in Conferencing Framework [15].  The focus has
   sufficient information about the state of the conference to inform
   subscribers about it.


   It is possible a participant in the conference may in fact be another
   focus.  In order to provide a more complete participant list, the
   focus MAY subscribe to the conference package of the other focus to
   discover the participant list in the cascaded conference.  This
   information can then be included in notifications by using of the
   "cascaded-focus" element as specified by this package.


   This section provides the details for defining a SIP Events package,
   as specified by RFC 3265 [7].


3.1  Event Package Name


   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
   [7].


3.2  SUBSCRIBE Bodies


   A SUBSCRIBE for a conference package MAY contain a body.  This body
   defines a filter to apply to the subscription.  Filter documents are
   not specified in this document, and at the time of writing, are
   expected to be the subject of future standardization activity.


   A SUBSCRIBE for a conference package MAY be sent without a body.
   This implies the default subscription filtering policy.  The default
   policy is:
   o  Notifications are generated every time there is any change in the
      state of the conference.
   o  Notifications do not normally contain full state; rather, they
      only indicate the state that has changed.  The exception is a
      NOTIFY sent in response to a SUBSCRIBE.  These NOTIFYs contain the
      full state of the information requested by the subscriber.


3.3  Subscription Duration


   The default expiration time for a subscription to be interpreted as described in a conference is one
   hour.  Once the conference ends, all subscriptions to that particular
   conference are terminated, with a reason of "noresource" RFC 2119 [2] and
   indicate requirement levels for compliant implementations. 3265




Rosenberg, et al.        Expires January 16, April 25, 2005                 [Page 5] 7]
Internet-Draft             Conference Package                  July               October 2004



3.  Conference Event Package


   The conference event package allows a user to subscribe to a
   conference.  In SIP, conferences are represented by URIs.  These URIs
   route to a SIP user agent, called a focus, that is responsible for
   ensuring that all users in the conference can communicate with each
   other, as



   [7].


3.4  NOTIFY Bodies


   As described in Conferencing Framework [14].  The focus has
   sufficient information about RFC 3265 [7], the NOTIFY message will contain bodies
   that describe the state of the conference to inform
   subscribers about it.


   It subscribed resource.  This body is possible in
   a participant format listed in the conference may in fact be another
   focus.  In order to provide Accept header field of the SUBSCRIBE, or a more complete participant list,
   package-specific default if the
   focus MAY subscribe to Accept header field was omitted from
   the SUBSCRIBE.


   In this event package, the body of the notification contains a
   conference package information document.  This document describes the state
   of a conference.  All subscribers and notifiers MUST support the
   "application/conference-info+xml" data format described in Section 6.
   The subscribe request MAY contain an Accept header field.  If no such
   header field is present, it has a default value of
   "application/conference-info+xml".  If the header field is present,
   it MUST include "application/conference-info+xml", and MAY include
   any other focus to
   discover types.


   Of course, the participant list in notifications generated by the cascaded conference.  This
   information can then server MUST be included in notifications by using one
   of the
   "cascaded-focus" attribute as specified by this package.


   This section provides the details for defining a SIP Events package,
   as formats specified by RFC 3265 [7].


3.1  Event Package Name


   The name of this event package is "conference".  This package name is
   carried in the Event and Allow-Events header, as defined Accept header field in RFC 3265
   [7].


3.2 the SUBSCRIBE Bodies


   A
   request.


3.5  Notifier Processing of SUBSCRIBE for a Requests


   The conference package MAY contain a body.  This body
   defines a filter to apply to the subscription.  Filter documents are
   not specified in this document, information contains very sensitive information.
   Therefore, all subscriptions SHOULD be authenticated and then
   authorized before approval.  Authorization policy is at the time
   discretion of writing, are
   expected to be the subject of future standardization activity.


   A SUBSCRIBE for administrator, as always.  However, a conference package MAY few
   recommendations can be sent without a body.
   This implies the default subscription filtering policy.  The default
   policy is:
   o  Notifications are generated every time there made.


   It is any change RECOMMENDED that all users in the
      state of conference be allowed to
   subscribe to the conference.
   o


3.6  Notifier Generation of NOTIFY Requests


   Notifications do not normally contain full state; rather, they
      only indicate MUST be generated for the conference state that has changed.  The exception is a
      NOTIFY sent in response to when a SUBSCRIBE.  These NOTIFYs contain the
      full state of the information requested by the subscriber.


3.3  Subscription Duration


   The default expiration time for new
   participant joins (i.e.  gets "connected" to) or a subscription participant leaves
   (i.e.  gets "disconnected" from) the conference.


   Subject to a conference is one
   hour.  Once local focus policy, additional changes in participants'
   status, changes in their media types, and other optional information
   MAY be reported by the conference ends, all subscriptions focus.


   Changes in sidebar rosters SHOULD be reported by the focus to that particular
   conference are terminated, with a reason of "noresource" RFC 3265 their
   participants and MAY be reported to others, subject to local policy.





Rosenberg, et al.        Expires January 16, April 25, 2005                 [Page 6] 8]
Internet-Draft             Conference Package                  July               October 2004



   [7].


3.4  NOTIFY Bodies


   As described



   Changes in RFC 3265 [7], conference identifiers and service URIs SHOULD be reported
   by the NOTIFY message will contain bodies
   that describe focus to the Conference package subscribers.


   Changes in other conference state of information MAY be reported by the subscribed resource.  This body is in
   focus to the Conference package subscribers.


3.7  Subscriber Processing of NOTIFY Requests


   The SIP Events framework expects packages to specify how a format listed subscriber
   processes NOTIFY requests in any package specific ways, and in
   particular, how it uses the Accept header field NOTIFY requests to construct a coherent
   view of the SUBSCRIBE, or a
   package-specific default if state of the Accept header field was omitted from subscribed resource.


   Typically, the SUBSCRIBE.


   In this event package, NOTIFY for the body conference package will only contain
   information about those users whose state in the conference has
   changed.  To construct a coherent view of the notification contains total state of all
   users, a subscriber to the conference package will need to combine
   NOTIFYs received over time.


   Notifications within this package can convey partial information;
   that is, they can indicate information document.  This document describes about a subset of the state
   of a conference.  All subscribers and notifiers MUST support
   associated with the
   "application/conference-info+xml" data format described subscription.  This means that an explicit
   algorithm needs to be defined in Section 4. order to construct coherent and
   consistent state.  The subscribe request MAY contain an Accept header field.  If no such
   header field is present, it has a default value details of "application/
   conference-info+xml".  If this mechanism are specific to the header field is present, it MUST
   include "application/conference-info+xml", and MAY include any other
   types capable
   particular document type.  See Section 5 for information on
   constructing coherent information from an
   application/conference-info+xml document.


3.8  Handling of representing dialog state.


   Of course, Forked Requests


   By their nature, the notifications generated conferences supported by the server this package are
   centralized.  Therefore, SUBSCRIBE requests for a conference should
   not generally fork.  Users of this package MUST be in one NOT install more than
   a single subscription as a result of the formats specified in the Accept header field in the a single SUBSCRIBE request.


3.5  Notifier Processing


3.9  Rate of SUBSCRIBE Requests


   The conference information contains very sensitive information.
   Therefore, all subscriptions SHOULD be authenticated and then
   authorized before approval.  Authorization policy Notifications


   For reasons of congestion control, it is at important that the
   discretion rate of the administrator, as always.  However,
   notifications not become excessive.  As a few
   recommendations can be made.


   It result, it is RECOMMENDED
   that all users in the conference be allowed to
   subscribe to the conference.


3.6  Notifier Generation of NOTIFY Requests


   Notifications SHOULD be generated server not generate notifications for the conference whenever there a single subscriber at
   a rate faster than once every 5 seconds.


3.10  State Agents


   Conference state is a change ideally maintained in the state element in any of which the information delivered to
   conference resides.  Therefore, the
   subscriber.


   The changes generally occur when a new participant joins (i.e.  gets
   "connected" to) or a participant leaves (i.e.  gets "disconnected"
   from) elements that maintain the conference.


   Subject
   conference are the ones best suited to a local focus policy, additional changes in participant's
   status, changes in its media types, and other optional media
   attributes MAY be reported by handle subscriptions to it.
   Therefore, the focus. usage of state agents is NOT RECOMMENDED for this




Rosenberg, et al.        Expires January 16, April 25, 2005                 [Page 7] 9]
Internet-Draft             Conference Package                  July               October 2004



   Changes in sidebar rosters



   package.



















































Rosenberg, et al.        Expires April 25, 2005                [Page 10]
Internet-Draft             Conference Package               October 2004



4.  Conference Data Model


   Conference information is an XML document that MUST be well-formed
   and SHOULD be reported valid.  Dialog information documents MUST be based on
   XML 1.0 and MUST be encoded using UTF-8.  This specification makes
   use of XML namespaces for identifying dialog information documents
   and document fragments.  The namespace URI for elements defined by
   this specification is a URN [3], using the focus to their
   participants namespace identifier
   'ietf' defined by [4] and MAY be reported to others, subject to local policy.


   Changes extended by [1].  This URN is:


   The conference information is described by a hierarchal XML structure
   with the root element "conference-info".  The root element is the
   only element in the schema that carries meaningful version number for
   all the elements in the document.  The whole conference identifiers information
   is associated with this version number.


   All sub-elements in the "conference-info" hierarchal XML structure
   can be classified in two groups: those that carry relatively small
   amount of data and policy URIs SHOULD be reported
   by those that can potentially carry a lot of data.
   During partial notifications, the focus to light elements are updated as
   atomic pieces of data.  On the conference participants.


3.7  Subscriber Processing other hand, elements that can carry a
   substantial amount of NOTIFY Requests


   The SIP Events framework expects packages data have the general "state" attribute
   attached to specify how a subscriber
   processes NOTIFY requests them.  That is in any package specific ways, and order to support partial notifications
   for their content.


   A "state" attribute of a child element in
   particular, how it uses the NOTIFY requests document MUST adhere to construct a coherent
   view
   its parent "state".  It means that if the parent's "state" is "full",
   the state of its children MUST be "full".  If the parent's "state" is
   "partial", the state of its children MAY be either "partial", "full",
   or "deleted".


   For elements with the subscribed resource.


   Typically, optional "state" attribute, if the NOTIFY for attribute is
   omitted from the conference package will only contain
   information about those users whose state in notification for the conference has
   changed.  To construct a coherent view of element, it means that the total
   reported element's state of all
   users, is "full".


   All sub-elements, with possible multiple appearances under a subscriber common
   parent, have keys defined to them in order to uniquely identify each
   element among others of the conference same type in the partial notification
   event.













Rosenberg, et al.        Expires April 25, 2005                [Page 11]
Internet-Draft             Conference Package               October 2004



5.  Constructing Coherent State


   A Conference package will need to combine
   NOTIFYs received over time.


   Notifications within this subscriber MUST initialize the "version"
   attribute from the "conference-info" element with the value in the
   first document received.


   The conference package can convey partial information;
   that is, they can indicate information about subscriber locally maintains a subset of local element
   for each element in the state
   associated schema and a table for each element with the subscription.  This means that an explicit
   algorithm needs to be defined
   key(s) in order to construct coherent the schema and
   consistent state.  The details indexed by these key(s).


   Each time a new NOTIFY is received, the value of this mechanism the local version
   number and the "version" attribute in the new received document are specific to
   compared.  If the
   particular value in the new document type.  See Section 4.2 for information on
   constructing coherent information from an application/
   conference-info+xml document.


3.8  Handling of Forked Requests


   By their nature, is one higher than the conferences supported
   local version number, the local version number is increased by this package are
   centralized.  Therefore, SUBSCRIBE requests for a conference should
   not generally fork.  Users of this package MUST NOT install one,
   and the document is processed.  If the value in the document is more
   than
   a single subscription as a result of a single SUBSCRIBE request.


3.9  Rate of Notifications


   For reasons of congestion control, it one higher than the local version number, the local version
   number is important that set to the rate of
   notifications not become excessive.  As a result, it value in the new document, the document is RECOMMENDED
   that
   processed, and the server not subscriber SHOULD generate notifications for a single subscriber at refresh request to
   trigger a rate faster than once every 5 seconds.


3.10  State Agents


   Conference full state is ideally maintained in notification.  If the element value in which the
   conference resides.  Therefore, the elements that maintain the
   conference are document is
   less than the ones best suited to handle subscriptions to it.
   Therefore, local version, the usage of state agents is NOT RECOMMENDED for this




Rosenberg, et al.       Expires January 16, 2005                [Page 8]
Internet-Draft             Conference Package                  July 2004



   package.



















































Rosenberg, et al.       Expires January 16, 2005                [Page 9]
Internet-Draft             Conference Package                  July 2004



4.  Conference Data Format


   Conference information is an XML document that MUST be well-formed
   and SHOULD be valid.  Dialog information documents MUST be based on
   XML 1.0 and MUST be encoded using UTF-8.  This specification makes
   use of XML namespaces for identifying dialog information documents
   and document fragments.  The namespace URI for elements defined by
   this specification is a URN [3], using discarded without
   processing.


   Further processing of the namespace identifier
   'ietf' defined by [4] and extended by [1].  This URN is:



   urn:ietf:params:xml:ns:conference-info


   A conference information document begins with depends on
   whether it contains full or partial state.  If it contains full
   state, indicated by the root element tag
   "conference-info".


4.1  Conference Information


   Conference information begins with value of the top level element
   "conference-info".  This element has three mandatory attributes:
   version: This mandatory "state" attribute allows in the recipient of conference
      information documents to properly order them.  Versions start at 0
   "conference-info" element, the whole local content is flushed and increment
   repopulated from the document.  If it contains "deleted" state,
   indicated by one for each new document sent to a subscriber.
      Versions are scoped within a subscription.  Versions MUST be
      represented using a 32 bit integer.
   state: This mandatory the value of the "state" attribute indicates whether in the document
      contains
   "conference-info" element, it means that the full conference information, or whether it contains
      only ceased to
   exist and the information that has changed since subscriber SHOULD terminate the SUBSCRIBE dialog.


   If the previous document
      (partial).
   entity: This mandatory attribute contains partial state, as indicated by the conference URI that
      identifies value of
   the conference being described "state" attribute in the document.


   The "conference-info" element has zero or more "user" sub-elements
   which contain information on the users in element, the conference.  This document
   is
   followed by zero or more "sidebar" sub-elements which contain
   information on used to update the sidebars local content as described below.


   Starting from outer elements in the conference.  This is followed by
   zero or more "conf-uri" sub-elements which contain information on
   additional URIs that received document,


   1.  If the conference can be accessed by.  This is
   followed by zero or more "policy-uri" sub-elements which contain
   information on additional URIs that parent element contains "full" state, the conference policies can be
   accessed by.  This whole local
   element content is followed by "recording" flushed and "streaming" repopulated from the document.


   2.  Otherwise, if the parent element contains "deleted" state, the
   whole element MUST be removed from the local content.


   3.  Otherwise, if the parent element contains "partial" state:


   3.1 For elements describing recording and streaming statuses of with keys, the
   conference.


4.1.1  User Element subscriber compares the keys received
   in the update with the keys in the local tables.





Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 10] 12]
Internet-Draft             Conference Package                  July               October 2004



4.1.1.1  User Attributes


   The user



   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 has one mandatory attribute, "uri" that indicates information from the URI for update.


   3.1.2 Otherwise, if a key of the user same value does exist, for each
   sub-element in the conference.  This is a logical
   identifier, which corresponds to the authenticated identity of row the
   participant.  The "uri" attribute MUST be unique algorithm is applied from step 2.2.


   3.2 For each atomic element received in the user schema, the element
   list because it is used as
   replaced with the key in partial notifications about
   users' state.


   If a conference participant has more than new information as a single signaling dialog
   associated whole.  Also, for each
   non-atomic element received in the schema with either no "state"
   attribute included or the conference, state attribute is set to "full", the conference focus MAY present
   element is replaced with the
   user's aggregated new information (e.g.  the statuses) and display all
   its media streams under as a single user element.


   Note, whole.


   3.2.1 If an element, which doesnĘt have key(s), is updated or created
   such that its content is empty, that the optional element "instance" of "media" (see below) MAY be used in this case to specify removed from the actual signaling dialog for
   local content at any time.


   3.3 For each
   media stream.


   An anonymous participant in a conference SHOULD be represented by an
   anonymous URI generated by non-atomic element with the focus.  For multiple anonymous
   participants, state attribute set to
   "partial", the focus must ensure that each anonymous URI algorithm is
   unique.  The guidelines for generating anonymous URIs in RFC 3323 [8]
   should be followed.  For example,


   "Anonymous1" <sip:anonymous1@anonymous.invalid>


    could be used for a participant requesting privacy.


   The optional attribute "display-name" contains applied recursively starting from step 3.


































Rosenberg, et al.        Expires April 25, 2005                [Page 13]
Internet-Draft             Conference Package               October 2004



6.  Conference Data



   urn:ietf:params:xml:ns:conference-info


   A conference information document begins with the root element tag
   "conference-info".


6.1  Conference Information


   A conference instance is defined as a display name for top level element
   "conference-info" of a type "conference-type".  Sections below
   describe the
   user. complex types composing the hierarchal
   "conference-type".  The standard "xml:lang" language full XML schema is defined in Section 7.


6.1.1  Conference Type


   This type has the following attributes:


   version: This mandatory attribute can also be present
   to indicate allows the language recipient of the display-name.


   The optional conference
      information documents to properly order them.  Versions start at 0
      and increment by one for each new document sent to a subscriber.
      Versions are scoped within a subscription.  Versions MUST be
      represented using a 32 bit integer.


   entity: This mandatory attribute "cascaded-focus" contains a conference URI
   (different from the main conference URI) for users URI that are connected
   to
      identifies the main conference as a result of focus cascading.  In accordance
   with the SIP conferencing framework [14], this package allows for
   representation of peer-to-peer (i.e.  "flat") focus cascading only.
   The actual cascading graph can not be deduced from the information
   provided being described in the package alone.  Advanced applications can construct document.


   state: This mandatory attribute indicates whether the graph by subscribing to both this package and document
      contains the Dialog Package
   [15] of whole conference information ("full"), only the cascaded foci and correlating
      information that has changed since the relevant information.


   If previous document
      ("partial"), or the main conference "state" is "full", ceased to exist ("deleted").  For
      more details see Section 5.


   This type defines an extendable sequence of the state following optional
   child elements:


6.1.1.1  conference-description of its user(s)
   MUST "full".  If conference-description-type


   This element contains conference information that is derived from
   system conference policies, is set before the main conference "state" activation,
   and is "partial", rarely changed during the state conference lifetime.


6.1.1.2  host-info of its user(s) MAY be either "partial" or "full". host-type


   This element contains information about the entity that hosts the
   conference.  This information is set before the conference
   activation, and is rarely changed during the conference lifetime,




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 11] 14]
Internet-Draft             Conference Package                  July               October 2004



4.1.1.2  User Status Elements


   Three optional status elements are defined: status, joining-mode, and
   disconnection-reason.
   o  "status": provides information about user's current level



   unless the whole conference is moved to be hosted by another entity.


6.1.1.3  conference-state of
      participation in conference-state-type


   This element contains the conference.
   o  "joining-mode": if present, provides dynamic information about the way current state
   of the focus.


6.1.1.4  user joined of user-type


   This element contains the conference.
   o  "disconnection-reason": if present, provides information about the
      way the user left a participant in the
   conference.  The following statuses are defined for element of the "status" element:
   connected: The user is a user-type can have unbounded number
   of appearance in the conference-type for each participant in the
   conference.  Depending on


6.1.1.5  sidebars-by-ref of uris-type


   This element provides a pointer to sidebar information through
   sidebar URIs.  The recipient of the media policies, he/she information can send and receive media then subscribe to and
   sidebar information independently from
      other participants.
   disconnected: The user is not the main Conference package
   subscription.


6.1.1.6  sidebar-by-val of conference-type


   This element provides sidebar information as a participant in part of the conference and no
      active dialog exists between main
   Conference package information.


6.1.2  Conference Description Type


   This element contains the user and "state" attribute which can contain the focus.
   on-hold: Active SIP dialog exists between a user and a focus, but
      user is "on-hold" for this conference, i.e.  neither he/she is
      "hearing"
   values "full", "partial", or deleted".


   This type defines an extendable sequence of the conference mix, nor is his/her media being mixed in following optional
   child elements:


6.1.2.1  display-text of string type


   This element contains text information about the conference.  As an example,


6.1.2.2  subject of string type


   This element contains information about the user has asked to join subject of a conference.


6.1.2.3  free-text of string type


   This element contains free form text about the conference.







Rosenberg, et al.        Expires April 25, 2005                [Page 15]
Internet-Draft             Conference Package               October 2004



6.1.2.4  keywords of keywords-type


   This element contains a list of keywords which describe the
   conference using SIP, but his/her participation is pending based
      on moderator approval.  In the meantime he/she is hearing
      music-on-hold or some other kind topic.


6.1.2.5  web-page of related content.
   muted-via-focus: Active SIP dialog exists between anyURI type


   This element contains a user and URI of a focus
      and the user can "listen" web page that contains information
   related to the conference, but user's media is
      not being mixed into the conference.  Note that sometimes a subset


6.1.2.6  conf-uris of user media streams uris-type


   This element contains information about additional conference URIs
   that this conference can be muted by focus (such as poor quality
      video) while others (such as voice or IM) accessed by.  Examples of such URIs
   include h323: [14] and tel: [13] URIs.


6.1.2.7  service-uris of uris-type


   This element contains the service-related URIs.  These URIs can still be active.  In
      this case, it is RECOMMENDED that the "aggregated" user
      connectivity "status" reflects
   used to manipulate the status conference policies or state, for example.


6.1.2.8  maximum-user-count of user-count-type


   This element contains a count of the mostly active
      media.
   blocked: User is denied from ever participating maximum number of users
   permitted in this the conference.
   pending: User is not yet  The count can be specified for all
   participants in total (using the session, but it is anticipated that
      he/she will join in sub-element with value "any") or
   count the near future.
   calling: User is being called users by their roles in the focus.
   ringing: An PSTN ALERTING or SIP 180 Ringing was returned for the
      outbound call, user is being alerted.
   dialing-in: User is dialing into conference.


6.1.2.9  available-media of conference-medias-type


   This element contains information about the conference, not yet media types available in
   a conference.  The "entry" sub-element MUST be a value registered for
   "proto" of SDP [12].


6.1.3  Host Type


   This element contains the
      roster (probably being authenticated).
   disconnecting: Focus is in "state" attribute which can contain the process of disconnecting user (either
      DISCONNECT
   values "full", "partial", or BYE was sent to deleted".


   This type defines an extendable sequence of the user's device).
   removed: following optional
   child elements:


6.1.3.1  display-text of string type


   This status is used to remove element contains display text information about the user from the roster using
      partial notifications mechanism.


   Note that hosting
   the defined transient states (e.g., calling, ringing, etc.)
   could generate a lot of notifications.  Implementations MAY choose
   not to generate notifications on these to all participants if it will conference.






Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 12] 16]
Internet-Draft             Conference Package                  July               October 2004



   generate too much traffic.


   The following statuses are defined for



6.1.3.2  web-page of anyURI type


   This element contains a web page URI about the "joining-mode" element:
   dialed-in: The user dialed into hosting the conference, i.e.  sent INVITE
   conference.


6.1.3.3  uris of uris-type


   The "entity" sub-element contains additional URIs relating to the focus,
   user hosting the conference.


6.1.4  Conference State Type


   This element contains the "state" attribute which resulted can contain the
   values "full", "partial", or deleted".


   This type defines an extendable sequence of the following optional
   child elements.


6.1.4.1  user-count of user-count-type


   This element contains a count of the current number of users in successful dialog establishment.
   dialed-out: the
   conference.  The focus has brought count can be specified for all participants in total
   (using the user into sub-element with value "any") or count the conference users by
      sending a successful INVITE their
   roles in the conference.


6.1.4.2  security-level of security-level-type


   This element contains information about the conference security
   level.  The values can be "none", "low", "medium", or "high".


6.1.4.3  active of Boolean type


   This element contains information about whether the conference is
   currently active or not.


6.1.4.4  locked of Boolean type


   This element contains information about whether the conference is
   currently locked.  In this context, locked means that the conference
   roster can not be added to (although participants may leave or be
   removed from the conference).


6.1.4.5  recording of uris-type


   The "entry" sub-element contains URIs related to the user.
   focus-owner: The user is recording of the focus for this
   conference.






Rosenberg, et al.        Expires April 25, 2005                [Page 17]
Internet-Draft             Conference Package               October 2004



6.1.4.6  active-media of conference-medias-type


   This status element contains information about the media types currently
   active in the conference which is used only when a participant UA acts as a conference focus.


   The subset of those listed in the
   "available-media" element.


6.1.5  User Type


   This type has the following statuses are defined attributes:


   entity: The mandatory attribute contains the URI for the disconnection-reason
   element:
   departed: The user sent a BYE, thus leaving in the
      conference.
   booted: The user was sent  This is a BYE by logical identifier, which corresponds to
      the focus, booting him/her out authenticated identity of the conference.  Alternatively, the user tried to dial into to
      conference without success because was rejected by the focus
      according to local policy decisions.
   failed: participant.  The server tried to bring "entity"
      attribute MUST be unique in the user into the conference, but
      its attempt to contact element list because it is
      used as the specific user resulted key in partial notifications about users' state.  An
      anonymous participant in a non-200
      class final response.  Alternatively, the user tried to dial into
      the conference without success due to technical reasons.


4.1.1.3  Media Information


   Each user has zero or more "media" sub-elements.


   Each "media" element indicates SHOULD be represented by an
      anonymous URI generated by the media that focus.  For multiple anonymous
      participants, the user is currently
   connected to.  Here, "connected to" implies focus must ensure that a user has a media
   line in his/her SDP [12] document(s).  With this definition, a user
   is connected to a media stream even if he/she each anonymous URI is not sending any
   media.


4.1.1.3.1  Media Attributes
      unique.  The "media" element has guidelines for generating anonymous URIs in RFC 3323
      [8] should be followed.  For example,


   "Anonymous1" <sip:anonymous1@anonymous.invalid>


       could be used for a participant requesting privacy.


   state: This mandatory "media-type" attribute which
   identifies indicates whether the media document
      contains the whole conference information ("full"), only the
      information that has changed since the previous document
      ("partial"), or the conference ceased to exist ("deleted").


   This type (e.g.  audio, video, message and
   application) and MUST have one defines an extendable sequence of the values registered for "media"
   of SDP [12].


   The following optional "id" attribute serves as a unique reference to a "media"
   child elements.


6.1.5.1  display-text of string type


   This element within contains the "user" element.  It MUST be included display text for each
   "media" the user.


6.1.5.2  associated-aors of anyURI type


   This element for all notifications if contains associated URIs of the focus uses "partial"
   user notifications for user.  Usually this conference.  Otherwise, the  "id"
   attribute MAY
   information will be omitted.


   If the user "state" is "full", manually provided by a system administrator
   showing the state logical association between signaling entities otherwise
   independent.


6.1.5.3  roles of its "media" element(s)
   MUST be "full".  If the user "state" is "partial", user-roles-type


   This element contains the state roles of its
   "media" element(s) MAY be either "partial" or "full". the user.





Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 13] 18]
Internet-Draft             Conference Package                  July               October 2004



4.1.1.3.2  Media Elements



6.1.5.4  language of language type


   This element contains the language used by the user.


6.1.5.5  cascaded-focus of anyURI type


   This element contains a conference URI (different from the main
   conference URI) for users that are connected to the main conference
   as a result of focus cascading.  In accordance with the SIP
   conferencing framework [15], this package allows for representation
   of peer-to-peer (i.e.  "flat") focus cascading only.  The "media" actual
   cascading graph can not be deduced from the information provided in
   the package alone.  Advanced applications can construct the graph by
   subscribing to both this package and the Dialog Package [16] of the
   cascaded foci and correlating the relevant information.


6.1.5.6  endpoint of endpoint-type


   This element has also contains information about an optional "proto" sub-element, which
   MUST has endpoint of the value registered for "proto" user.  The
   element of SDP [12].


   An optional "ssrc" sub-element, if present, carries the value endpoint-type can have unbounded number of SSRC
   (defined appearance
   in RTP/RTCP [10]) as generated by the user user-type for each endpoint of the stream it
   sends.


   When an RTP mixer generates user participating in the
   conference.  In a CSRC list according to RTP/RTCP [10],
   it inserts case when authentication is performed per endpoint
   (rather than per user) in a list of the SSRC identifiers system, a focus can be not aware of the sources that
   contributed to
   logical association among endpoints being used by the generation of a particular packet into same user.  In
   this case the RTP
   header of that packet.  "An example application is audio conferencing
   where a mixer indicates all focus MAY present the talkers whose speech was combined endpoints as belonging to
   produce the outgoing packet, allowing
   separate users in the receiver conference schema.


   In a different case, due to indicate privacy concerns for a user the
   current talker, even though all focus may
   want to shield the audio packets contain information about multiple endpoints from the same
   SSRC identifier (that
   recipients of the mixer)."


   An optional "info" sub-element, if present, carries a human readable
   description for this stream populated by Conference document.  To do so the focus.  The value of
   this element corresponds to focus MAY
   aggregate the multiple endpoint information media attribute "i" in
   SDP [12].


   An optional "label" sub-element, if present, carries into a unique
   identifier for this stream among all streams in the conference and is
   assigned by the focus.  The value of this single endpoint
   element corresponds to under this user.


6.1.6  Endpoint Type


   This type has the
   "label" media attribute in SDP [12] and defined in [18].


   An optional "instance" sub-element, if present, carries a URI, which
   MUST uniquely identify following attributes:


   entity: The mandatory attribute contains the signaling dialog being used endpoint URI for
   establishing of this media stream. the
      user in the conference.  In SIP, for example, values of SIP terms, this is the Contact URI or GRUU [17] can
      GRUU.  The "entity" attribute MUST be used for this purpose.  It unique in the endpoint
      element list because it is
   RECOMMENDED to include used as the "instance" information for every user that
   has more than key in partial
      notifications about users' endpoints.  An anonymous participant in
      a single dialog associated with the conference.  This
   element conference SHOULD NOT be included for represented by an anonymous participant.


   An optional "status" sub-element, if present, is used to remove
   "media" elements during partial notifications.


   Optional "snd-status" and "rcv-status" sub-elements, if present,
   describe URI generated
      by the status of media streams in focus.  For multiple anonymous participants, the focus must
      ensure that each direction.


4.1.1.4  User Role anonymous URI is unique.  The optional "role" element conveys the role of the user in the
   conference, e.g.  participant, presenter, panelist, host, etc.
   User's role MAY change dynamically in the course of the conference.
   Also, a user MAY have more than a single role guidelines for
      generating anonymous URIs in one time. RFC 3323 [8] should be followed.






Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 14] 19]
Internet-Draft             Conference Package                  July               October 2004




   state: This document does not define fixed values for mandatory attribute indicates whether the "role" element,
   instead it is expected that conferencing applications will define
   custom-fit roles by templates.


4.1.2  Sidebar Element


   The sidebar element is of the general "conference-type" and MAY use
   all
      contains the attributes and elements defined by it.  Typically, whole endpoint information ("full"), only the
   "entity", which uniquely identifies the sidebar, and the "user"
   elements will be useful to present to
      information that has changed since the majority of previous document
      ("partial"), or the
   participants in endpoint has been deleted from the conference.


   The "conference-type" mandatory attributes MUST be included for each
   sidebar.


   The value conference
      ("deleted").


   This type defines an extendable sequence of the "version" attribute is meaningless following optional
   child elements.


6.1.6.1  display-text of string type


   This element contains the display text for "sidebar"
   elements and MUST be ignored because it is always overruled by the
   "version" attribute endpoint.


6.1.6.2  referred of execution-type


   This element contains the main "conference-info".


   If URI of the user who's action resulted in
   this endpoint being brought into the main conference "state" is "full", (e.g.  the user
   identified by this URI sent a REFER to the focus).


6.1.6.3  state of its sidebar(s)
   MUST be "full".  If the main conference "state" is "partial", endpoint-state-type


   This element contains the state of its sidebar(s) MAY be either "full" or "partial".


   The "entity" URI attribute MUST be unique among the sidebar
   identifiers of endpoint, and can assume the same conference.  Attribute "entity"
   following values:


   connected: The endpoint is used as
   the key for "sidebar" elements in partial notifications for
   "conference-info".


4.1.3  Additional Conference Identifiers


   In addition to the Conference URI present in the "entity" attribute, a conference MAY have additional URIs of various types.  Connecting
   to these URIs will result participant in joining to the same conference.


4.1.4  Policy URIs


   A policy URI specifies where
      Depending on the media policies, he/she can send and how a certain policy pertaining receive media
      to and from other participants.


   disconnected: The endpoint is not a participant in the conference can be accessed.  The actual policy name and usage is
   deduced from
      no active dialog exists between the URI schema name.


   An example endpoint and the focus.


   on-hold: Active SIP dialog exists between an endpoint and a focus,
      but endpoint is "on-hold" for this conference, i.e.  neither
      he/she is "hearing" the "policy-uri" usage conference mix, nor is inclusion of his/her media being
      mixed in the URI of conference.  As an example, the
   CPCP [16].  A subscriber endpoint has asked to
      join the conference using SIP, but his/her participation is
      pending based on moderator approval.  In the meantime he/she is
      hearing music-on-hold or some other kind of related content.


   muted-via-focus: Active SIP dialog exists between an endpoint and a
      focus and the Conference package endpoint can use the Policy
   URI "listen" to access and modify the conference policy.


4.1.5  Recording


   In many cases, legal regulations require conference providers to
   announce to conference, but
      endpoint's media is not being mixed into the participants conference.  Note
      that sometimes a specific conference subset of endpoint media streams can be muted by
      focus (such as poor quality video) while others (such as voice or
      IM) can still be active.  In this case, it is being RECOMMENDED that the
      "aggregated" endpoint connectivity "status" reflects the status of
      the mostly active media.




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 15] 20]
Internet-Draft             Conference Package                  July               October 2004



   recorded.


   In addition




   pending: Endpoint is not yet in the session, but it is anticipated
      that he/she will join in the near future.


   alerting: A PSTN ALERTING or SIP 180 Ringing was returned for the
      outbound call, endpoint is being alerted.


   dialing-in: Endpoint is dialing into the conference, not yet in the
      roster (probably being authenticated).


   dialing-out: Focus has dialed out to connect the recording "status" information, endpoint to the "recording"
   element MAY include
      conference, but the URIs specifying endpoint is not yet in the location and roster (probably
      being authenticated).


   disconnecting: Focus is in the format process of disconnecting endpoint
      (either DISCONNECT or BYE was sent to the recorded data.  Typically, the recorded data becomes available
   after endpoint's device).


   Note that the conference ends.  Multiple URIs can be provided, for
   example, specifying different content types.  For Web-Page embedded
   media, defined transient states (e.g., disconnecting,
   alerting, etc.) could generate a plain HTTP URI lot of notifications.
   Implementations MAY be provided.


4.1.6  Streaming


   The "streaming" element, choose not to generate notifications on these to
   all participants if present, specifies whether it will generate too much traffic.


6.1.6.4  joining-method of joining-type


   This element contains method by which the conference
   output is being streamed (to general public, for example), endpoint joined the
   conference, and can assume the following values:


   dialed-in: The endpoint dialed into the conference, i.e.  sent INVITE
      to the focus, which resulted in what
   streaming format, and at what (e.g.  multicast) addresses it can be
   listened at.  RTSP [11] is an example of such streaming protocol.


4.2  Constructing Coherent State successful dialog establishment.


   dialed-out: The focus has brought the endpoint into the conference information is described by
      sending a hierarchal XML structure
   with successful INVITE to the root element "conference-info". endpoint.


   focus-owner: The root element endpoint is the focus for this conference.  This
      status is used only when a participant UA acts as a conference
      focus.


6.1.6.5  joining-info of execution-type


   This element in contains information about how the schema endpoint joined and
   can contain the following sub-elements:


   when: This element contains the date and time that carries meaningful version number for
   all the elements in endpoint
      joined the document.  The whole conference information
   is associated with this version number.


   The version number MUST be initialized with conference.








Rosenberg, et al.        Expires April 25, 2005                [Page 21]
Internet-Draft             Conference Package               October 2004



   reason: This element contains the value of reason the
   "version" attribute from endpoint joined the "conference-info"
      conference.


   by: This element in the first
   document received.  Each time a new document is received, contains the value URI of the local version number, and entity who caused the "version" attribute in
      endpoint to join the new
   document, are compared.  If conference.


6.1.6.6  disconnection-method of disconnection-type


   This element contains method by which the value in endpoint departed the new document is one
   higher than
   conference, and can assume the local version number, following values:


   departed: The endpoint sent a BYE, thus leaving the local version number is
   increased conference.


   booted: The endpoint was sent a BYE by one, and the document is processed.  If the value in focus, booting him/her out
      of the
   document is more than one higher than conference.  Alternatively, the local version number, endpoint tried to dial into
      to conference without success because was rejected by the focus
      according to local version number is set policy decisions.


   failed: The server tried to bring the value in the new document, the
   document is processed, and endpoint into the subscriber SHOULD generate a refresh
   request conference,
      but its attempt to trigger a full state notification.  If contact the value specific endpoint resulted in a
      non-200 class final response.  Alternatively, the
   document is less than the local version, endpoint tried
      to dial into the document is discarded conference without processing.


   Further processing success due to technical
      reasons.


6.1.6.7  disconnection-info of disconnection-type


   This element contains information about the endpoint's departure from
   the conference information document depends on
   whether it contains full or partial state.  If it and can contain the following sub-elements:


   when: This element contains full
   state, indicated by the value of date and time that the "state" attribute in endpoint
      departed the
   "conference-info" element, conference.


   reason: This element contains the whole local content is flushed and
   repopulated from reason the document.


   If endpoint departed the document
      conference.


   by: This element contains partial state, as indicated by the value URI of the "state" attribute in the "conference-info" element, entity who caused the document
   is used
      endpoint to update depart the local content as described below.





Rosenberg, et al.       Expires January 16, 2005               [Page 16]
Internet-Draft             Conference Package                  July 2004



   All sub-elements conference.


6.1.6.8  whispering-to of uris-type


   If an endpoint is participating in a whisper session with other
   entities, the "conference-info" hierarchal XML structure
   can URIs of these other entities MAY be classified contained in two groups: those that carry relatively small
   amount this
   element.


6.1.6.9  media of data and those that can potentially carry media-type


   This element contains information about a lot media stream of data.
   During partial notifications, the light elements are updated as
   atomic pieces this
   endpoint.  The element of data.  On the other hand, elements that media-type can carry a
   substantial amount of data have the general "state" attribute
   attached to them.  That is in order to support partial notifications
   for their content.


   A "state" attribute have unbounded number of a child element




Rosenberg, et al.        Expires April 25, 2005                [Page 22]
Internet-Draft             Conference Package               October 2004



   appearance in the document MUST adhere to
   its parent "state".  It means that if the parent's "state" is "full",
   the state endpoint-type for each media stream of its children MUST be "full".  If the parent's "state"
   endpoint.  Note that it is
   "partial", the state of its children possible that media streams listed under a
   common endpoint MAY be either "partial" or
   "full".


   For elements with optional "state" attribute, if established by separate signaling means and
   consequently belong to different signaling "calls".


6.1.7  Media Type


   This type has the following attributes:


   entity: The mandatory attribute is not
   included for an element, it means that the element's state a unique identifier of a media
      stream on a per endpoint basis.  This attribute is "full".


   For used as a parent element with "state", its sub-elements with possible
   multiple appearances under the parent have keys that uniquely key
      to identify each element among others in media streams which may be added and deleted on a
      dynamic basis during the same list.


4.2.1  The Algorithm conference.  The conference package subscriber locally maintains a local element
   for each value of this element in
      SHOULD correspond to the schema and a table for each "element with
   key(s)" "mid" value in the schema.  The tables are indexed by the key(s) SDP document as
      defined in schema for the element.


   Starting from outer elements Grouping of Media Lines in the received document,


   1.  If SDP [9].


   state: This mandatory attribute indicates whether the parent element
      contains full state, the element is
   replaced with whole media information ("full"), only the new
      information as a whole.


   2.  Otherwise, if that has changed since the parent previous document
      ("partial"), or the media element has been deleted from the
      conference document ("deleted").


   This type defines an extendable sequence of the following optional
   child elements.


6.1.7.1  display-text of string type


   This element contains partial state,


   2.1 For elements with keys, the subscriber compares the keys received
   in display text for the update with media stream.


6.1.7.2  proto of string type


   This element contains the keys in media type for the local tables.


   2.1.1 If media stream.  The value
   of this element MUST be a key doesn't exist value registered for "proto" of SDP [12].


6.1.7.3  ssrc of string type


   The "ssrc" element carries the value of SSRC (defined in RTP/RTCP
   [10]) as generated by the local table, endpoint for the stream it sends.  When an
   RTP mixer generates a row is added, and
   its content is set CSRC list according to RTP/RTCP [10], it
   inserts a list of the element information from SSRC identifiers of the update.


   2.1.2 Otherwise, if sources that
   contributed to the generation of a key particular packet into the RTP
   header of that packet.  "An example application is audio conferencing
   where a mixer indicates all the same value does exist, for each
   sub-element in talkers whose speech was combined to
   produce the row outgoing packet, allowing the algorithm is applied from step 2.2.


   2.2 For each atomic element received in receiver to indicate the schema,
   current talker, even though all the element is
   replaced with audio packets contain the new information as a whole.  Also, for each
   non-atomic element received in same
   SSRC identifier (that of the schema with either no "state" mixer)."






Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 17] 23]
Internet-Draft             Conference Package                  July               October 2004



6.1.7.4  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 "label" media attribute included in
   SDP [12] and defined in [19].


6.1.7.5  state of media-state-type


   The element "state" contains the state of the media stream and can
   have the values "active", "inactive", or "muted".


6.1.7.6  snd-status of media-state-type


   The element "state" contains the state attribute is set to "full", of the
   element is replaced with sending media stream
   (from the new information as a whole.


   2.2.1 If perspective of the updated endpoint) and can have the values
   "active", "inactive", or created "muted".


6.1.7.7  rcv-status state of media-state-type


   The element carries "state" contains the "removed" status,
   that element SHOULD be removed from state of the local content.  If receiving media stream
   (from the
   element is updated perspective of the endpoint) and can have the values
   "active", "inactive", or created, such that it is empty, that "muted".


6.1.7.8  call of call-type


   The "call" element
   MAY be removed from contains the local content at any time.


   2.3 For each non-atomic element with "sip" sub-element which contains the state attribute set to
   "partial",
   SIP dialog identifier of the algorithm is applied recursively starting from step 2.


4.3 endpoint's dialog with the focus.  The
   "sip" element includes sub-elements "display-text", "call-id",
   "to-tag", "from-tag"






















Rosenberg, et al.        Expires April 25, 2005                [Page 24]
Internet-Draft             Conference Package               October 2004



7.  Schema




   <?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">
   <!--
    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" />


        <!--
          CONFERENCE  ELEMENT
        -->
        <xs:element name="conference-info" type="tns:conference-type"/> type="conference-type"/>
        <!--
          CONFERENCE TYPE
        -->
        <xs:complexType name="conference-type">
                <xs:sequence>
                        <xs:element name="conference-description" type="conference-description-type" minOccurs="0"/>
                        <xs:element name="host-info" type="host-type" minOccurs="0"/>
                        <xs:element name="conference-state" type="conference-state-type" minOccurs="0"/>
                        <xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="sidebars-by-ref" type="uris-type" minOccurs="0"/>
                        <xs:element name="sidebar-by-val" type="conference-type" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="entity" type="xs:anyURI" use="required"/>
                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:attribute name="version" type="xs:string" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
        STATE TYPE
        -->
        <xs:simpleType name="state-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="full" /> value="full"/>
                        <xs:enumeration value="partial" /> value="partial"/>
                        <xs:enumeration value="deleted"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
          CONFERENCE DESCRIPTION TYPE
        -->
        <xs:complexType name="conference-type"> name="conference-description-type">
                <xs:sequence>




Rosenberg, et al.        Expires April 25, 2005                [Page 25]
Internet-Draft             Conference Package               October 2004



                        <xs:element name="user" type="user-type" minOccurs="0" maxOccurs="unbounded" /> name="display-text" type="xs:string" minOccurs="0"/>
                        <xs:element name="sidebar" type="conference-type" name="subject" 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="web-page" type="xs:anyURI" 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="maximum-user-count" type="user-count-type" minOccurs="0"/>
                        <xs:element name="available-media" type="conference-medias-type" minOccurs="0"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded" /> maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          HOST TYPE
        -->
        <xs:complexType name="host-type">
                <xs:sequence>
                        <xs:element name="display-text" type="xs:string" minOccurs="0"/>
                        <xs:element name="web-page" type="xs:anyURI" minOccurs="0"/>
                        <xs:element name="uris" type="uris-type" minOccurs="0"/>
                        <xs:element name="conf-ids" type="conf-ids-type" name="extended" type="extended-type" minOccurs="0" maxOccurs="1" /> maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          CONFERENCE STATE TYPE -->
        <xs:complexType name="conference-state-type">
                <xs:sequence>
                        <xs:element name="user-count" type="user-count-type" minOccurs="0"/>
                        <xs:element name="security-level" type="security-level-type" minOccurs="0"/>
                        <xs:element name="active" type="xs:boolean" minOccurs="0"/>
                        <xs:element name="policy-ids" type="policy-ids-type" minOccurs="0" maxOccurs="1" /> name="locked" type="xs:boolean" minOccurs="0"/>
                        <xs:element name="recording" type="recording-type" minOccurs="0" maxOccurs="1" /> type="uris-type" minOccurs="0"/>
                        <xs:element name="streaming" type="streaming-type" minOccurs="0" maxOccurs="1" />
     <xs:any processContents="lax" name="active-media" type="conference-medias-type" minOccurs="0"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded" /> maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="version" type="xs:nonNegativeInteger" use="required"/>
     <xs:attribute name="state"   type="tns:state-type"        use="required"/>
     <xs:attribute name="entity"  type="xs:anyURI"             use="required"/>
     <xs:anyAttribute /> type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          CONFERENCE MEDIAS TYPE
        -->
        <xs:complexType name="conference-medias-type">
                <xs:sequence>
                        <xs:element name="entry" type="conference-media-type" maxOccurs="unbounded"/>




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 18] 26]
Internet-Draft             Conference Package                  July               October 2004



                </xs:sequence>
                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          CONFERENCE MEDIA TYPE
        -->
        <xs:complexType name="conf-ids-type"> name="conference-media-type">
                <xs:sequence>
                        <xs:element name="conf-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
     <xs:any processContents="lax" name="proto" type="xs:string"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded" /> maxOccurs="unbounded"/>
                </xs:sequence>


    <xs:anyAttribute />
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          CONFERENCE URIs TYPE
        -->
        <xs:complexType name="policy-ids-type"> name="uris-type">
                <xs:sequence>
                        <xs:element name="policy-uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
     <xs:any processContents="lax" minOccurs="0" maxOccurs="unbounded" /> name="entry" type="uri-type" maxOccurs="unbounded"/>
                </xs:sequence>


    <xs:anyAttribute />


                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          CONFERENCE URI TYPE
        -->
        <xs:complexType name="recording-type"> name="uri-type">
                <xs:sequence>
                        <xs:element name="uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
     <xs:any processContents="lax" type="xs:anyURI"/>
                        <xs:element name="label" type="xs:string" minOccurs="0"/>
                        <xs:element name="modified" type="execution-type" minOccurs="0"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded" /> maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          USER COUNT TYPE
        -->
        <xs:complexType name="user-count-type">
                <xs:sequence>
                        <xs:element name="entry" type="count-type" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="status" type=="stream-status-type" use="required"/>
    <xs:anyAttribute /> name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--




Rosenberg, et al.        Expires April 25, 2005                [Page 27]
Internet-Draft             Conference Package               October 2004



          COUNT TYPE
        -->
        <xs:complexType name="streaming-type"> name="count-type">
                <xs:sequence>
                        <xs:element name="uri" type="xs:anyURI" minOccurs="0" maxOccurs="unbounded" />
     <xs:any processContents="lax" name="role" type="user-role-type"/>
                        <xs:element name="count" type="xs:nonNegativeInteger"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded" /> maxOccurs="unbounded"/>
                </xs:sequence>


    <xs:attribute name="status" type="stream-status-type" use="required"/>
    <xs:anyAttribute />
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          SECURITY LEVEL TYPE
        -->
        <xs:simpleType name="security-level-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="none"/>
                        <xs:enumeration value="low"/>
                        <xs:enumeration value="medium"/>
                        <xs:enumeration value="high"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
          KEWORDS TYPE
        -->
        <xs:simpleType name="keywords-type">
                <xs:list itemType="xs:string"/>
        </xs:simpleType>
        <!--
          USER TYPE
        -->
        <xs:complexType name="user-type">
                <xs:sequence>
                        <xs:element name="status" type="tns:user-status-type" name="display-text" type="xs:string" minOccurs="0"/>
                        <xs:element name="joining-mode" type="tns:user-joining-mode-type" name="associated-aors" type="uris-type" minOccurs="0"/>
                        <xs:element name="disconnection-reason" type="tns:user-disconnection-reason-type" name="roles" type="user-roles-type" minOccurs="0"/>
                        <xs:element name="media" type="tns:media-type" name="language" type="xs:language" minOccurs="0"/>
                        <xs:element name="cascaded-focus" type="xs:anyURI" minOccurs="0"/>
                        <xs:element name="endpoint" type="endpoint-type" minOccurs="0" maxOccurs="unbounded"/>
                        <xs:element name="role" type="xs:string" name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="entity" type="xs:anyURI"/>
                <xs:attribute name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          USER ROLES TYPE
        -->
        <xs:complexType name="user-roles-type">




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 19] 28]
Internet-Draft             Conference Package                  July               October 2004



     <xs:any processContents="lax" minOccurs="0"



                <xs:sequence>
                        <xs:element name="entry" type="user-role-type" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="uri"          type="xs:anyURI"   use="required"/>
    <xs:attribute name="display-name" type="xs:string" name="state" type="state-type" use="optional"/>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          USER ROLE TYPE
        -->
        <xs:complexType name="user-role-type">
                <xs:choice>
                        <xs:element name="label" type="xs:string"/>
                </xs:choice>
                <xs:attribute ref="xml:lang" name="conf-template" type="xs:string" use="optional"/>
        </xs:complexType>
        <!--
          ENDPOINT TYPE
        -->
        <xs:complexType name="endpoint-type">
                <xs:sequence>
                        <xs:element name="display-text" type="xs:string" minOccurs="0"/>
                        <xs:element name="referred" type="execution-type" minOccurs="0"/>
                        <xs:element name="state" type="endpoint-state-type" minOccurs="0"/>
                        <xs:element name="whispering-to" type="uris-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="disconnection-method" type="disconnection-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="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="cascaded-focus" type="xs:anyURI" use="optional"/> name="entity" type="xs:anyURI"/>
                <xs:attribute name="state" type="tns:state-type" type="state-type" use="optional"/>
    <xs:anyAttribute />
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          ENDPOINT STATE TYPE
        -->
        <xs:simpleType name="user-status-type"> name="endpoint-state-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="connected"/>
     <xs:enumeration value="disconnected"/>
     <xs:enumeration value="on-hold"/> value="pending"/>
                        <xs:enumeration value="muted-via-focus"/> value="dialing-out"/>
                        <xs:enumeration value="blocked"/> value="dialing-in"/>
                        <xs:enumeration value="pending"/> value="alerting"/>
                        <xs:enumeration value="calling"/> value="on-hold"/>
                        <xs:enumeration value="ringing"/> value="connected"/>
                        <xs:enumeration value="dialing-in"/> value="muted-via-focus"/>




Rosenberg, et al.        Expires April 25, 2005                [Page 29]
Internet-Draft             Conference Package               October 2004



                        <xs:enumeration value="disconnecting"/>
                        <xs:enumeration value="removed"/> value="disconnected"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
        JOINING TYPE
        -->
        <xs:simpleType name="user-joining-mode-type"> name="joining-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="dialed-in" /> value="dialed-in"/>


                        <xs:enumeration value="dialed-out" /> value="dialed-out"/>
                        <xs:enumeration value="focus-owner" /> value="focus-owner"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
        DISCONNECTION TYPE
        -->
        <xs:simpleType name="user-disconnection-reason-type"> name="disconnection-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="departed" /> value="departed"/>
                        <xs:enumeration value="booted" /> value="booted"/>
                        <xs:enumeration value="failed" /> value="failed"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
        EXECUTION TYPE
        -->
        <xs:complexType name="execution-type">
                <xs:sequence>
                        <xs:element name="when" type="xs:dateTime" minOccurs="0"/>
                        <xs:element name="reason" type="xs:string" minOccurs="0"/>
                        <xs:element name="by" type="xs:anyURI" minOccurs="0"/>
                </xs:sequence>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          MEDIA TYPE
        -->
        <xs:complexType name="media-type">
                <xs:sequence>
                        <xs:element name="proto" name="display-text" type="xs:string" minOccurs="0"/>




Rosenberg, et al.       Expires January 16, 2005               [Page 20]
Internet-Draft             Conference Package                  July 2004
                        <xs:element name="ssrc"       type="xs:nonNegativeInteger" name="proto" type="xs:string" minOccurs="0"/>
                        <xs:element name="info" name="ssrc" type="xs:string" minOccurs="0"/>
                        <xs:element name="label" type="xs:string" minOccurs="0"/>
                        <xs:element name="instance"   type="xs:anyURI"             minOccurs="0"/>
     <xs:element name="status"     type="tns:media-status-type" name="state" type="media-state-type" minOccurs="0"/>
                        <xs:element name="snd-status" type="tns:stream-status-type" type="media-state-type" minOccurs="0"/>
                        <xs:element name="rcv-status" type="tns:stream-status-type" type="media-state-type" minOccurs="0"/>
     <xs:any processContents="lax"




Rosenberg, et al.        Expires April 25, 2005                [Page 30]
Internet-Draft             Conference Package               October 2004



                        <xs:element name="call" type="call-type" minOccurs="0"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="media" name="entity" type="xs:string" use="required"/>
                <xs:attribute name="id"     type="nonNegativeInteger"    use="optional"/>
     <xs:attribute name="state"  type="tns:state-type" type="state-type" use="optional"/>
     <xs:anyAttribute />
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          MEDIA STATUS TYPE
        -->
        <xs:simpleType name="media-status-type">
    <xs:restriction base="xs:string">
     <xs:enumeration value="removed" />
    </xs:restriction>
   </xs:simpleType>


   <xs:simpleType name="stream-status-type"> name="media-state-type">
                <xs:restriction base="xs:string">
                        <xs:enumeration value="on"/> value="active"/>
                        <xs:enumeration value="off"/> value="inactive"/>
                        <xs:enumeration value="muted" /> value="muted"/>
                </xs:restriction>
        </xs:simpleType>
        <!--
          CALL TYPE
        -->
        <xs:complexType name="call-type">
                <xs:choice>
                        <xs:element name="sip" type="sip-dialog-id-type"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:choice>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          SIP DIALOG ID TYPE
        -->
        <xs:complexType name="sip-dialog-id-type">
                <xs:sequence>
                        <xs:element name="display-text" type="xs:string" minOccurs="0"/>
                        <xs:element name="dialog-id" type="xs:string"/>
                        <xs:element name="from-tag" type="xs:string"/>
                        <xs:element name="to-tag" type="xs:string"/>
                        <xs:element name="extended" type="extended-type" minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:anyAttribute/>
        </xs:complexType>
        <!--
          EXTENDED TYPE
        -->
        <xs:complexType name="extended-type">
                <xs:sequence>
                        <xs:any minOccurs="0" maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="target-namespace" type="xs:string" use="required"/>




Rosenberg, et al.        Expires April 25, 2005                [Page 31]
Internet-Draft             Conference Package               October 2004



        </xs:complexType>
   </xs:schema>




4.4


















































Rosenberg, et al.        Expires April 25, 2005                [Page 32]
Internet-Draft             Conference Package               October 2004



8.  Examples


8.1  Basic Example


   The following is an example conference information document:



   <conference-info entity="sips:conf233@example.com" state="partial" version="5" >
        <!--
        CONFERENCE INFO
        -->
        <conference-description>
                <subject>Agenda: This month's target</subject>
                <service-uris>
                        <entry>
                                <uri>http://salesgroup.example.com/conference-policies/sales-weekly-meeting.xml</uri>
                                <label>CPCP</label>
                        </entry>
                </service-uris>
        </conference-description>
        <!--
          CONFERENCE STATE
        -->
        <conference-state>
                <user-count>
                        <entry>
                                <role>
                                        <label>any</label>
                                </role>
                                <count>33</count>
                        </entry>
                </user-count>
                <active-media>
                        <entry>
                                <proto>audio</proto>
                        </entry>
                </active-media>
        </conference-state>


        <!--
          USER
        -->
        <user entity="sip:bob@example.com" state="full">
                <display-text>Bob Hoskins</display-text>
        <!--
          ENDPOINTS
        -->
                <endpoint entity="sip:bob@pc33.example.com">




Rosenberg, et al.        Expires April 25, 2005                [Page 33]
Internet-Draft             Conference Package               October 2004



                        <display-text>Bob's Laptop</display-text>
                        <state>disconnected</state>
                        <disconnection-method>departed</disconnection-method>
                        <disconnection-info>
                                <when>2005-03-04T20:00:00Z</when>
                                <reason>bad voice quality</reason>
                                <by>sip:mike@example.com</by>
                        </disconnection-info>


        <!--
          MEDIA
        -->
                        <media entity="1">
                                <display-text>main audio</display-text>
                                <proto>audio</proto>
                                <ssrc>432424</ssrc>
                                <label>34567</label>
                                <state>active</state>
                        </media>
                </endpoint>
        </user>


        <!--
          USER
        -->
        <user entity="sip:alice@example.net" state="full">
                        <display-text>Alice</display-text>
        <!--
                        ENDPOINTS
        -->
         <endpoint entity="sip:4kfk4j392jsu@example.net;grid=433kj4j3u">
                        <state>connected</state>
                         <joining-method>dialed-out</joining-method>
                         <joining-info>


                                 <when>2005-03-04T20:00:00Z</when>
                                 <by>sip:mike@example.com</by>
                         </joining-info>
        <!--
          MEDIA
        -->
                         <media entity="1">
                                        <display-text>main audio</display-text>
                                        <proto>audio</proto>
                                        <ssrc>534232</ssrc>
                                        <label>34564</label>
                                        <state>active</state>
                        </media>




Rosenberg, et al.        Expires April 25, 2005                [Page 34]
Internet-Draft             Conference Package               October 2004



                </endpoint>
        </user>
   </conference-info>



8.2  Rich Example


   The following is an example conference information document.  In this
   example of a partial state notification, there are 32 participants in
   a voice conference.  The user Bob has been booted from the conference
   by Mike due to bad voice quality.  Note that there are three sidebars
   in the conference, two are referenced just by their sidebar URI and
   information about the third sidebar is included in this notification.
   Also note that while this conference offers both audio and video
   capabilities, only audio is currently in use.



   <conference-info entity="sips:conf233@example.com" state="partial" version="5" >
        <!--
        CONFERENCE INFO
        -->
        <conference-description>
                <display-text>Weekly Sales Meeting</display-text>
                <subject>Agenda: This month's target</subject>
                <free-text>xyz</free-text>
                <keywords>sales, meeting, weekly</keywords>
                <web-page>http://sharepoint/salesgroup/</web-page>
                <conf-uris>
                        <entry>
                                <uri>tel:+18005671234</uri>
                                <label>TTI Bridge</label>
                        </entry>
                        <entry>
                                <uri>h323:conf545@h323.example.com</uri>
                        </entry>
                </conf-uris>
                <service-uris>
                        <entry>
                                <uri>http://salesgroup.example.com/conference-policies/sales-weekly-meeting.xml</uri>
                                <label>CPCP</label>
                        </entry>
                </service-uris>
                <maximum-user-count>
                        <entry>
                                <role>
                                        <label>any</label>
                                </role>
                                <count>52</count>




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 21] 35]
Internet-Draft             Conference Package                  July               October 2004



   <?xml version="1.0" encoding="utf-8" ?>
   <conference-info version="0" state="full" entity="sip:conf233@example.com">



                        </entry>
                        <entry>
                                <role conf-template="Basic">
                                        <label>participant</label>
                                </role>
                                <count>50</count>
                        </entry>
                </maximum-user-count>
                <available-media>
                        <entry>
                                <proto>audio</proto>
                        </entry>
                        <entry>
                                <proto>video</proto>
                        </entry>
                </available-media>
        </conference-description>
        <!--
          HOST INFO
        -->
        <host-info>
                <display-text>Sales Host</display-text>
                <web-page>http://sharepoint/salesgroup/hosts/</web-page>
                <uris>
                        <entry>
                                <uri>sip:sales@example.com</uri>
                        </entry>
                </uris>
        </host-info>
        <!--
          CONFERENCE STATE
        -->
        <conference-state>
                <user-count>
                        <entry>
                                <role>
                                        <label>any</label>
                                </role>
                                <count>33</count>
                        </entry>
                        <entry>
                                <role conf-template="Basic">
                                        <label>participant</label>
                                </role>
                                <count>32</count>
                        </entry>
                </user-count>
                <security-level>medium</security-level>




Rosenberg, et al.        Expires April 25, 2005                [Page 36]
Internet-Draft             Conference Package               October 2004



                <active>true</active>
                <locked>false</locked>
                <recording>
                        <entry>
                                <uri>http://quicktime.streaming.com/54634/recording.mov</uri>
                                <label>Quicktime</label>
                        </entry>
                        <entry>
                                <uri>http://real.streaming.com/54634/recording.ram</uri>
                        </entry>
                </recording>
                <active-media>
                        <entry>
                                <proto>audio</proto>
                        </entry>
                </active-media>
        </conference-state>


        <!--
          USERS
        -->
        <user uri="sip:bob@example.com" display-name="Bob Jones">
               <status>connected</status>
               <joining-mode>dialed-in</joining-mode> entity="sip:bob@example.com" state="full">
                <display-text>Bob Hoskins</display-text>
                <associated-aors>
                        <entry>
                                <uri>mailto:bob@example.com</uri>
                                <label>email</label>
                        </entry>
                </associated-aors>
                <roles>
                        <entry>
                                <label>participant</label>
                        </entry>
                </roles>
                <language>en</language>
        <!--
          ENDPOINTS
        -->
                <endpoint entity="sip:bob@pc33.example.com">
                        <display-text>Bob's Laptop</display-text>
                        <referred>
                                <when>2005-03-04T20:00:00Z</when>
                                <by>sip:mike@example.com</by>
                        </referred>
                        <state>disconnecting</state>
                        <whispering-to>
                        <entry>
                                <uri>sip:rob@example.com</uri>




Rosenberg, et al.        Expires April 25, 2005                [Page 37]
Internet-Draft             Conference Package               October 2004



                        </entry>
                        <entry>
                                <uri>sip:helen@example.com</uri>
                        </entry>
                        </whispering-to>
                        <joining-method>dialed-out</joining-method>
                        <joining-info>
                                <when>2005-03-04T20:00:00Z</when>
                                <reason>invitation</reason>
                                <by>sip:mike@example.com</by>
                        </joining-info>
                        <disconnection-method>booted</disconnection-method>
                        <disconnection-info>
                                <when>2005-03-04T20:00:00Z</when>
                                <reason>bad voice quality</reason>
                                <by>sip:mike@example.com</by>
                        </disconnection-info>


        <!--
          MEDIA
        -->
                        <media media="audio">
                     <proto>RTP/AVP</proto>
                     <ssrc>583398</ssrc> entity="1" state="full">
                                <display-text>main audio</display-text>
                                <proto>audio</proto>
                                <ssrc>432424</ssrc>
                                <label>34567</label>
                                <state>active</state>
                                <call>
                                        <sip>
                                                <display-text>full info</display-text>
                                                <dialog-id>hsjh8980vhsb78</dialog-id>
                                                <from-tag>vav738dvbs</from-tag>


                                                <to-tag>8954jgjg8432</to-tag>
                                        </sip>
                                </call>
                        </media>


                </endpoint>


        </user>


        <!--
          SIDEBARS BY REFERENCE
        -->
                        <sidebars-by-ref>
                                <entry>
                                        <uri>sips:conf233@example.com; grid=45</uri>




Rosenberg, et al.        Expires April 25, 2005                [Page 38]
Internet-Draft             Conference Package               October 2004



                                        <label>sidebar with Carol</label>
                                </entry>
                                <entry>
                                        <uri>sips:conf233@example.com; grid=21</uri>
                                        <label>private sidebar with Peter</label>
                                </entry>
                        </sidebars-by-ref>
        <!--
          SIDEBARS BY VALUE
        -->
                        <sidebar-by-val entity="sips:conf233@example.com; grid=77" state="partial">
                                <user uri="sip:barbara@example.com" display-name="Barbara Jones">
               <status>on-hold</status>
         </user>
         <user uri="sip:bill@example.com" display-name="Bill Minelli">
               <status>on-hold</status>
         </user>


         <sidebar version="0" state="full" entity="sip:conf233.1@example.com"> entity="sip:bob@example.com" state="partial"></user>
                                <user uri="sip:barbara@example.com" /> entity="sip:mark@example.com" state="partial"></user>
                                <user uri="sip:bill@example.com" />
         </sidebar>


         <conf-ids>
               <conf-uri>tel:+18005671234</conf-uri>
               <conf-uri>h323:conf545@example.com</conf-uri>
         </conf-ids>


         <recording status="on">
               <uri>http://quicktime.streaming.com/54634/recording.mov</uri>
               <uri>http://real.streaming.com/54634/recording.ram</uri>
               <uri>http://windowsmedia.streaming.com/54634/recording.wmv</uri>
               <uri>http://www.streaming.com/54634/recording.html</uri>
         </recording> entity="sip:dan@example.com" state="partial"></user>
                        </sidebar-by-val>


   </conference-info>



   This conference currently has three users, two of which are in a
   sidebar conversation.  The conference is being recorded.  There are
   additional means to join the conference either by phone using tel URI
   [14] or by H.323 protocol using H.323 URL [13].



































Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 22] 39]
Internet-Draft             Conference Package                  July               October 2004



5.



9.  Security Considerations


   Subscriptions to conference state can reveal very sensitive
   information.  For this reason, the document recommends authentication
   and authorization, and provides guidelines on sensible authorization
   policies.


   Since the data in notifications is sensitive as well, end-to-end SIP
   encryption mechanisms using S/MIME SHOULD be used to protect it.


   Since a focus provides participants identity information using this
   event package, participant privacy needs to be taken into account.  A
   focus MUST support requests by participants for privacy.  Privacy can
   be indicated by the conference policy - for every participant or
   select participants.  It can also be indicated in the session
   signaling.  In SIP this can be done using the Privacy header field
   described in RFC 3323 [8].  For a participant requesting privacy, no
   identity information SHOULD be revealed by the focus such as a URI
   (e.g.  the Address of Record, Contact, or GRUU).  For these cases,
   the anonymous URI generation method outlined in section "User
   Element" of this document MUST be followed.































Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 23] 40]
Internet-Draft             Conference Package                  July               October 2004



6.



10.  IANA Considerations


   This document registers a SIP event package, a new MIME type,
   application/conference-info+xml, a new XML namespace, and a new XML
   schema.


6.1


10.1  conference Event Package Registration


   This specification registers an event package, based on the
   registration procedures defined in RFC 3265 [7].  The following is
   the information required for such a registration:
   Package Name: conference
   Package or Template-Package: This is a package.
   Published Document: RFC XXXX (Note to RFC Editor: Please fill in XXXX
      with the RFC number of this specification).
   Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net.


6.2


10.2  application/conference-info+xml MIME Registration
   MIME media type name: application
   MIME subtype name: conference-info+xml
   Mandatory parameters: none
   Optional parameters: Same as charset parameter application/xml as
      specified in RFC 3023 [5].
   Encoding considerations: Same as encoding considerations of
      application/xml as specified in RFC 3023 [5].
   Security considerations: See Section 10 of RFC 3023 [5] and Section 5 9
      of this specification.
   Interoperability considerations: none.
   Published specification: This document.
   Applications which use this media type: This document type has been
      used to support SIP conferencing applications.
   Additional Information:
      Magic Number: None
      File Extension: .cif or .xml
      Macintosh file type code: "TEXT"
   Personal and email address for further information: Jonathan
      Rosenberg, <jdrosen@jdrosen.net>
   Intended usage: COMMON
   Author/Change controller: The IETF.


6.3


10.3  URN Sub-Namespace Registration for
     urn:ietf:params:xml:ns:conference-info


   This section registers a new XML namespace, as per the guidelines in
   [1].







Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 24] 41]
Internet-Draft             Conference Package                  July               October 2004



   URI: The URI for this namespace is
      urn:ietf:params:xml:ns:conference-info.
   Registrant Contact: IETF, SIPPING working group, <sipping@ietf.org>,
      Jonathan Rosenberg <jdrosen@jdrosen.net>.
   XML:




   BEGIN
   <?xml version="1.0"?>
   <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
             "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
   <html xmlns="http://www.w3.org/1999/xhtml">
   <head>
     <meta http-equiv="content-type"
        content="text/html;charset=iso-8859-1"/>
     <title>Conference Information Namespace</title>
   </head
   <body>
     <h1>Namespace for Conference Information</h1>
     <h2>urn:ietf:params:xml:ns:conference-info</h2>
     <p>See <a href="[[[URL of published RFC]]]">RFCXXXX</a>.</p>
   </body>
   </html>
   END




6.4




10.4  XML Schema Registration


   This specification registers a schema, as per the guidelines in in
   [1].
      URI: please assign.
      Registrant Contact: IETF, SIPPING Working Group
      (sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net).
      XML: The XML can be found as the sole content of Section 4.3. 7.
















Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 25] 42]
Internet-Draft             Conference Package                  July               October 2004



7.



11.  Acknowledgements


   The authors would like to thank Dan Petrie, Sean Olson, Alan
   Johnston, and Rohan Mahy for their comments and inputs.
















































Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 26] 43]
Internet-Draft             Conference Package                  July               October 2004



8.



12.  Changes History


8.1


12.1  Changes since -05
   o  General schema clean-up.
   o  Definition of common types being used by multiple elements.
   o  Introduction of an "endpoint" element as a part of hierarchy:
      user/endpoint/media.


12.2  Changes since -04
   o
   o  "Sidebar-type" has been removed.  "Sidebar" conference element is
      defined using the general "conference-type".
   o  "Recording" conference attribute has been replaced with
      "recording" and "streaming" elements within "conference-type".
      New "recording-type" and "streaming-type" have been introduced.
   o  Attribute "state" has been added to "user-type".
   o  Element "media-stream" within "user-type" has been renamed to
      "media".
   o  Element "role" within "user-type" has been introduced.
   o  The following statuses have been added to "user-status-type":
      blocked, pending, calling, ringing, dialing-in, disconnecting,
      removed.
   o  User status "muted-by-focus" has been renamed to
      "muted-via-focus".
   o  Attributes "id" and "state" have been added to "media-type".
   o  Elements "status", "snd-status" and "rcv-status" have been added
      to "media-type".
   o  Element "dialog-id" has been renamed to "instance".
   o  "Constructing Coherent State" section has been updated to include
      user and media partial notifications.


8.2


12.3  Changes since -03
   o  "Constructing Coherent State" section has been updated.
   o  In order to support partial notifications, two placeholders
      "conference-ids" and "policy-ids" (for "conf-uri" and "policy-uri"
      elements, correspondingly) are created.
   o  Discussion and security considerations regarding anonymous
      participation have been added.
   o  Optional elements "dialog-uri", "info" and "label" per media
      stream are added.


8.3


12.4  Changes since -02
   o  State "muted-by-focus" is added to user's status.
   o  Optional conference attribute "recording" is added.
   o  Policy URI placeholder (i.e.  element "policy-uri") is created.
   o  Example's syntax is corrected.
   o  Optional attribute "cascaded-focus" URI per user is added.





Rosenberg, et al.        Expires April 25, 2005                [Page 44]
Internet-Draft             Conference Package               October 2004



   o  Optional additional conference identifiers (i.e.  element
      "conf-uri") are added.
   o  In order to cover all possible cases, participant's status is
      expressed using three optional statuses: "status", "joining-mode"
      and "disconnection-reason".  That is instead of "activity-status",
      "history-status" and "is-on-dial-out-list".





Rosenberg, et al.       Expires January 16, 2005               [Page 27]
Internet-Draft             Conference Package                  July 2004



8.4


12.5  Changes since -01
   o  Package parameters are removed.  Decision about performing
      "recursive" membership algorithm is perceived as a focus local
      policy.
   o  General information (i.e.  pointers to additional available
      services) is removed.  The defined XML schema can be extended in
      future to include those when XCON work matures.
   o  Dialog information is removed.  It can be obtained by direct
      subscription to a dialog package of a participant.
   o  Media stream information is aligned with SDP definitions (media
      and proto) and SSRC attribute is added.
   o  Participant's status is expressed using two optional statuses:
      "activity" and "history".  Optional "is-on-a-dial-out-list"
      indication is added.
   o  Normative references to XCON work are removed.
   o  Optional sidebar rosters are added.





























Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 28] 45]
Internet-Draft             Conference Package                  July               October 2004



9.



13.  References


9.1


13.1  Normative References


   [1]   Mealling, M., "The IETF XML Registry",
         draft-mealling-iana-xmlns-registry-05 (work in progress), June
         2003.


   [2]   Bradner, S., "Key words for use in RFCs to Indicate Requirement
         Levels", BCP 14, RFC 2119, March 1997.


   [3]   Moats, R., "URN Syntax", RFC 2141, May 1997.


   [4]   Moats, R., "A URN Namespace for IETF Documents", RFC 2648,
         August 1999.


   [5]   Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC
         3023, January 2001.


   [6]   Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
         Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:
         Session Initiation Protocol", RFC 3261, June 2002.


   [7]   Roach, A., "Session Initiation Protocol (SIP)-Specific Event
         Notification", RFC 3265, June 2002.


   [8]   Peterson, J., "A Privacy Mechanism for the Session Initiation
         Protocol (SIP)", RFC 3323, November 2002.


   [9]   Camarillo, G., Eriksson, G., Holler, J. and H. Schulzrinne,
         "Grouping of Media Lines in the Session Description Protocol
         (SDP)", RFC 3388, December 2002.


   [10]  Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson,
         "RTP: A Transport Protocol for Real-Time Applications", STD 64,
         RFC 3550, July 2003.


9.2


13.2  Informative References


   [11]  Schulzrinne, H., Rao, A. and R. Lanphier, "Real Time Streaming
         Protocol (RTSP)", RFC 2326, April 1998.


   [12]  Handley, M. and V. Jacobson, "SDP: Session Description
         Protocol", RFC 2327, April 1998.


   [13]  Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
         Registration",  Vaha-Sipila, A., "URLs for Telephone Calls", RFC 3508, 2806, April 2003.
         2000.





Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 29] 46]
Internet-Draft             Conference Package                  July               October 2004



   [14]  Levin, O., "H.323 Uniform Resource Locator (URL) Scheme
         Registration", RFC 3508, April 2003.


   [15]  Rosenberg, J., "A Framework for Conferencing with the Session
         Initiation Protocol",
         draft-ietf-sipping-conferencing-framework-02
         draft-ietf-sipping-conferencing-framework-03 (work in
         progress), June October 2004.


   [15]


   [16]  Rosenberg, J. and H. Schulzrinne, "An INVITE Inititiated Dialog
         Event Package for the Session Initiation  Protocol (SIP)",
         draft-ietf-sipping-dialog-package-04 (work in progress),
         February 2004.


   [16]


   [17]  Koskelainen, P. and H. Khartabil, "Requirements for Conference
         Policy Control Protocol", draft-ietf-xcon-cpcp-reqs-03 draft-ietf-xcon-cpcp-reqs-04 (work in
         progress), April August 2004.


   [17]


   [18]  Rosenberg, J., "Obtaining and Using Globally Routable User
         Agent (UA) URIs (GRUU) in the  Session Initiation Protocol
         (SIP)", draft-ietf-sip-gruu-02 (work in progress), July 2004.


   [18]


   [19]  Levin, O. and G. Camarillo, "The SDP (Session Description
         Protocol) Label Attribute",
         draft-levin-mmusic-sdp-media-label-00
         draft-ietf-mmusic-sdp-media-label-00 (work in progress), July
         September 2004.



Authors' Addresses


   Jonathan Rosenberg
   dynamicsoft
   600 Lanidex Plaza
   Parsippany, NJ  07054
   US


   Phone: +1 973 952-5000
   EMail: jdrosen@dynamicsoft.com
   URI:   http://www.jdrosen.net














Rosenberg, et al.        Expires April 25, 2005                [Page 47]
Internet-Draft             Conference Package               October 2004



   Henning Schulzrinne
   Columbia University
   M/S 0401
   1214 Amsterdam Ave.
   New York, NY  10027
   US


   EMail: schulzrinne@cs.columbia.edu
   URI:   http://www.cs.columbia.edu/~hgs






Rosenberg, et al.       Expires January 16, 2005               [Page 30]
Internet-Draft             Conference Package                  July 2004



   Orit Levin (editor)
   Microsoft Corporation
   One Microsoft Way
   Redmond, WA  98052
   USA


   EMail: oritl@microsoft.com


































Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 31] 48]
Internet-Draft             Conference Package                  July               October 2004



Intellectual Property Statement


   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   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
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.


   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.


   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.



Disclaimer of Validity


   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.



Copyright Statement


   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.



Acknowledgment


   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Rosenberg, et al.        Expires January 16, April 25, 2005                [Page 32] 49] 
----