idnits 2.17.1 draft-ietf-sipping-conference-package-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 27 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 20 instances of too long lines in the document, the longest one being 207 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 15, 2004) is 7366 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3265 (ref. '2') (Obsoleted by RFC 6665) ** Obsolete normative reference: RFC 2141 (ref. '4') (Obsoleted by RFC 8141) ** Downref: Normative reference to an Informational RFC: RFC 2648 (ref. '5') ** Obsolete normative reference: RFC 3023 (ref. '7') (Obsoleted by RFC 7303) == Outdated reference: A later version (-05) exists of draft-ietf-sipping-conferencing-framework-01 == Outdated reference: A later version (-06) exists of draft-ietf-sipping-dialog-package-03 == Outdated reference: A later version (-04) exists of draft-ietf-xcon-cpcp-reqs-02 -- Obsolete informational reference (is this intentional?): RFC 2327 (ref. '12') (Obsoleted by RFC 4566) -- No information found for draft-ietf-iptel-tel-rfc2806bis - is the name correct? Summary: 6 errors (**), 0 flaws (~~), 8 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SIPPING J. Rosenberg 3 Internet-Draft dynamicsoft 4 Expires: August 15, 2004 H. Schulzrinne 5 Columbia University 6 O. Levin, Ed. 7 Microsoft Corporation 8 February 15, 2004 10 A Session Initiation Protocol (SIP) Event Package for Conference 11 State 12 draft-ietf-sipping-conference-package-03 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that other 21 groups may also distribute working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at http:// 29 www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on August 15, 2004. 36 Copyright Notice 38 Copyright (C) The Internet Society (2004). All Rights Reserved. 40 Abstract 42 This document defines a conference event package for the Session 43 Initiation Protocol (SIP) Events framework, along with a data format 44 used in notifications for this package. The conference package allows 45 users to subscribe to a conference URI. Notifications are sent about 46 changes in the membership of this conference, the status of users' 47 participation in the conference, and the sidebars in the conference. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 3 52 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 53 3. Conference Event Package . . . . . . . . . . . . . . . . . 5 54 3.1 Event Package Name . . . . . . . . . . . . . . . . . . . . 5 55 3.2 SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 5 56 3.3 Subscription Duration . . . . . . . . . . . . . . . . . . 5 57 3.4 NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 6 58 3.5 Notifier Processing of SUBSCRIBE Requests . . . . . . . . 6 59 3.6 Notifier Generation of NOTIFY Requests . . . . . . . . . . 6 60 3.7 Subscriber Processing of NOTIFY Requests . . . . . . . . . 7 61 3.8 Handling of Forked Requests . . . . . . . . . . . . . . . 7 62 3.9 Rate of Notifications . . . . . . . . . . . . . . . . . . 7 63 3.10 State Agents . . . . . . . . . . . . . . . . . . . . . . . 7 64 4. Conference Data Format . . . . . . . . . . . . . . . . . . 8 65 4.1 Conference Information . . . . . . . . . . . . . . . . . . 8 66 4.1.1 User Element . . . . . . . . . . . . . . . . . . . . . . . 9 67 4.1.1.1 User Statuses . . . . . . . . . . . . . . . . . . . . . . 9 68 4.1.1.2 Media Stream Information . . . . . . . . . . . . . . . . . 10 69 4.1.2 Sidebar . . . . . . . . . . . . . . . . . . . . . . . . . 11 70 4.1.3 Additional Conference Identifiers . . . . . . . . . . . . 11 71 4.1.4 Policy URIs . . . . . . . . . . . . . . . . . . . . . . . 11 72 4.2 Constructing Coherent State . . . . . . . . . . . . . . . 11 73 4.3 Schema . . . . . . . . . . . . . . . . . . . . . . . . . . 12 74 4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . 15 75 5. Security Considerations . . . . . . . . . . . . . . . . . 16 76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . 17 77 6.1 conference Event Package Registration . . . . . . . . . . 17 78 6.2 application/conference-info+xml MIME Registration . . . . 17 79 6.3 URN Sub-Namespace Registration for 80 urn:ietf:params:xml:ns:conference-info . . . . . . . . . . 18 81 6.4 XML Schema Registration . . . . . . . . . . . . . . . . . 19 82 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . 20 83 8. Changes since -02 . . . . . . . . . . . . . . . . . . . . 21 84 9. Changes since -01 . . . . . . . . . . . . . . . . . . . . 22 85 Normative References . . . . . . . . . . . . . . . . . . . 23 86 Informative References . . . . . . . . . . . . . . . . . . 24 87 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 24 88 Intellectual Property and Copyright Statements . . . . . . 26 90 1. Introduction 92 The Session Initiation Protocol (SIP) [3] Events framework [2] 93 defines general mechanisms for subscribing to, and receiving 94 notifications of, events within SIP networks. It introduces the 95 notion of a package, which is a specific "instantiation" of the 96 events framework for a well-defined set of events. Here, we define an 97 event package for SIP conferences. This package provides the 98 conference notification service as outlined in the SIP conferencing 99 framework [9]. As described there, subscriptions to a conference URI 100 are routed to the focus that is handling the conference. It acts as 101 the notifer, and provides clients with updates on conference state. 103 The information provided by this package is comprised of conference 104 identifier(s), conference participants (optionally with their 105 statuses and media types) and conference sidebars. 107 2. Terminology 109 In this document, the key words "MUST", "MUST NOT", "REQUIRED", 110 "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 111 and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and 112 indicate requirement levels for compliant implementations. 114 3. Conference Event Package 116 The conference event package allows a user to subscribe to a 117 conference. In SIP, conferences are represented by URIs. These URIs 118 route to a SIP user agent, called a focus, that is responsible for 119 ensuring that all users in the conference can communicate with each 120 other [9]. The focus has sufficient information about the state of 121 the conference to inform subscribers about it. 123 It is possible a participant in the conference may in fact be another 124 focus. In order to provide a more complete participant list, the 125 focus MAY subscribe to the conference package of the other focus to 126 discover the participant list in the cascaded conference. This 127 information can then be included in notifications by using of the 128 "cascaded-focus" attribute as specified by this package. 130 This section provides the details for defining a SIP Events package, 131 as specified by [2]. 133 3.1 Event Package Name 135 The name of this event package is "conference". This package name is 136 carried in the Event and Allow-Events header, as defined in [2]. 138 3.2 SUBSCRIBE Bodies 140 A SUBSCRIBE for a conference package MAY contain a body. This body 141 defines a filter to apply to the subscription. Filter documents are 142 not specified in this document, and at the time of writing, are 143 expected to be the subject of future standardization activity. 145 A SUBSCRIBE for a conference package MAY be sent without a body. This 146 implies the default subscription filtering policy. The default policy 147 is: 149 o Notifications are generated every time there is any change in the 150 state of the conference. 152 o Notifications do not normally contain full state; rather, they 153 only indicate the state that has changed. The exception is a 154 NOTIFY sent in response to a SUBSCRIBE. These NOTIFYs contain the 155 full state of the information requested by the subscriber. 157 3.3 Subscription Duration 159 The default expiration time for a subscription to a conference is one 160 hour. Once the conference ends, all subscriptions to that particular 161 conference are terminated, with a reason of "noresource" [2]. 163 3.4 NOTIFY Bodies 165 As described in RFC 3265 [2], the NOTIFY message will contain bodies 166 that describe the state of the subscribed resource. This body is in a 167 format listed in the Accept header field of the SUBSCRIBE, or a 168 package-specific default if the Accept header field was omitted from 169 the SUBSCRIBE. 171 In this event package, the body of the notification contains a 172 conference information document. This document describes the state of 173 a conference. All subscribers and notifiers MUST support the 174 "application/conference-info+xml" data format described in Section 4. 175 The subscribe request MAY contain an Accept header field. If no such 176 header field is present, it has a default value of "application/ 177 conference-info+xml". If the header field is present, it MUST include 178 "application/conference-info+xml", and MAY include any other types 179 capable of representing dialog state. 181 Of course, the notifications generated by the server MUST be in one 182 of the formats specified in the Accept header field in the SUBSCRIBE 183 request. 185 3.5 Notifier Processing of SUBSCRIBE Requests 187 The conference information contains very sensitive information. 188 Therefore, all subscriptions SHOULD be authenticated and then 189 authorized before approval. Authorization policy is at the discretion 190 of the administrator, as always. However, a few recommendations can 191 be made. 193 It is RECOMMENDED that all users in the conference be allowed to 194 subscribe to the conference. 196 3.6 Notifier Generation of NOTIFY Requests 198 Notifications SHOULD be generated for the conference whenever there 199 is a change in the state in any of the information delivered to the 200 subscriber. 202 The changes generally occur when a new participant joins, a 203 participant leaves, or a participant is put on-hold. Subject to a 204 local focus policy, changes in media types and other optional media 205 attributes MAY be reported by the focus. In addition, creation and 206 deletion of sidebars together with their rosters MAY be reported by 207 the focus, subject to its local policy. 209 3.7 Subscriber Processing of NOTIFY Requests 211 The SIP Events framework expects packages to specify how a subscriber 212 processes NOTIFY requests in any package specific ways, and in 213 particular, how it uses the NOTIFY requests to contruct a coherent 214 view of the state of the subscribed resource. 216 Typically, the NOTIFY for the conference package will only contain 217 information about those users whose state in the conference has 218 changed. To construct a coherent view of the total state of all 219 users, a subscriber to the conference package will need to combine 220 NOTIFYs received over time. 222 Notifications within this package can convey partial information; 223 that is, they can indicate information about a subset of the state 224 associated with the subscription. This means that an explicit 225 algorithm needs to be defined in order to construct coherent and 226 consistent state. The details of this mechanism are specific to the 227 particular document type. See Section 4.2 for information on 228 constructing coherent information from an application/ 229 conference-info+xml document. 231 3.8 Handling of Forked Requests 233 By their nature, the conferences supported by this package are 234 centralized. Therefore, SUBSCRIBE requests for a conference should 235 not generally fork. Users of this package MUST NOT install more than 236 a single subscription as a result of a single SUBSCRIBE request. 238 3.9 Rate of Notifications 240 For reasons of congestion control, it is important that the rate of 241 notifications not become excessive. As a result, it is RECOMMENDED 242 that the server not generate notifications for a single subscriber at 243 a rate faster than once every 5 seconds. 245 3.10 State Agents 247 Conference state is ideally maintained in the element in which the 248 conference resides. Therefore, the elements that maintain the 249 conference are the ones best suited to handle subscriptions to it. 250 Therefore, the usage of state agents is NOT RECOMMENDED for this 251 package. 253 4. Conference Data Format 255 Conference information is an XML document that MUST be well-formed 256 and SHOULD be valid. Dialog information documents MUST be based on 257 XML 1.0 and MUST be encoded using UTF-8. This specification makes use 258 of XML namespaces for identifying dialog information documents and 259 document fragments. The namespace URI for elements defined by this 260 specification is a URN [4], using the namespace identifier 'ietf' 261 defined by [5] and extended by [6]. This URN is: 263 urn:ietf:params:xml:ns:conference-info 265 A conference information document begins with the root element tag 266 "conference-info". 268 4.1 Conference Information 270 Conference information begins with the top level element 271 "conference-info". This element has three mandatory and one optional 272 attributes: 274 version: This mandatory attribute allows the recipient of conference 275 information documents to properly order them. Versions start at 0 276 and increment by one for each new document sent to a subscriber. 277 Versions are scoped within a subscription. Versions MUST be 278 represented using a 32 bit integer. 280 state: This mandatory attribute indicates whether the document 281 contains the full conference information, or whether it contains 282 only the information that has changed since the previous document 283 (partial). 285 entity: This mandatory attribute contains the conference URI that 286 identifies the conference being described in the document. 288 recording: This optional attribute indicates whether the conference 289 is being recorded at this moment ("on") or not ("off"). 291 The "conference-info" element has zero or more "user" sub-elements 292 which contain information on the users in the conference. This is 293 followed by zero or more "sidebar" sub-elements which contain 294 information on the sidebars in the conference. This is followed by 295 zero or more "conf-uri" sub-elements which contain information on 296 additional URIs that the conference can be accessed by. This is 297 followed by zero or more "policy-uri" sub-elements which contain 298 information on additional URIs that the conference policies can be 299 accessed by. 301 4.1.1 User Element 303 The user element has one mandatory attribute, "uri" that indicates 304 the URI for the user in the conference. This is a logical identifier, 305 not a machine specific one (i.e., it's taken from the authenticated 306 identity of the participant). The optional attribute "display-name" 307 contains a display name for the user. The standard "xml:lang" 308 language attribute can also be present to indicate the language of 309 the display-name. 311 The optional attribute "cascaded-focus" contains a conference URI 312 (different from the main conference URI) for users that are connected 313 to the main conference as a result of focus cascading. In accordance 314 with the SIP conferencing framework [9], this defined package allows 315 for representation of peer-to-peer (i.e. "flat") focus cascading 316 only. The actual cascading graph is not explicitly expressed in this 317 package because most applications do not care about the actual 318 topology of the cascaded focuses as long as the information about 319 their participants is available. In addition, an advanced application 320 can construct the graph by subscribing to both this package and the 321 Dialog Package [10] of the involved focuses and correlating the 322 required information. 324 4.1.1.1 User Statuses 326 Three optional status elements are defined: status, joining-mode, and 327 disconnection-reason. 329 o "status": provides information about user's current level of 330 participation in the conference. 332 o "joining-mode": if present, provides information about the way the 333 user joined the conference. 335 o "disconnection-reason": if present, provides information about the 336 way the user left the conference. 338 The following statuses are defined for the "status" element: 340 connected: The user is a participant in the conference. Depending on 341 the media policies, he/she can send and receive media to and from 342 other participants. 344 disconnected: The user is not a participant in the conference and no 345 active dialog exists between the user and the focus. 347 on-hold: Active SIP dialog exists between a user and a focus, but 348 user is "on-hold" for this conference, i.e. neither he/she is 349 "hearing" the conference mix, nor is his/her media being mixed in 350 the conference. As an example, the user has asked to join the 351 conference using SIP, but his/her participation is pending based 352 on moderator approval. In the meantime he/she is hearing 353 music-on-hold or some other kind of related content. 355 muted-by-focus: Active SIP dialog exists between a user and a focus 356 and the user can "listen" to the conference, but user's media is 357 not being mixed into the conference. 359 The following statuses are defined for the "joining-mode" element: 361 dialed-in: The user dialed into the conference, i.e. sent INVITE to 362 the focus, which resulted in successful dialog establishment. 364 dialed-out: The focus has brought the user into the conference by 365 sending a successful INVITE to the user. 367 focus-owner: The user is the focus itself for this conference. 369 The following statuses are defined for the disconnection-reason 370 element: 372 departed: The user sent a BYE, thus leaving the conference. 374 booted: The user was sent a BYE by the focus, booting him/her out of 375 the conference. Alternatively, the user tried to dial into to 376 conference without success because was rejected by the focus 377 according to local policy decisions. 379 failed: The server tried to bring the user into the conference, but 380 its attempt to contact the specific user resulted in a non-200 381 class final response. Alternatively, the user tried to dial into 382 the conference without success due to technical reasons. 384 4.1.1.2 Media Stream Information 386 Each user has zero or more "media-stream" sub-elements. 388 Each "media-stream" element indicates the media stream that the user 389 is currently connected to. Here, "connected to" implies that a user 390 has a media line in their SDP [12]. With this definition, a user is 391 connected to a media stream even if they are not sending any media. 393 The "media-stream" element has a mandatory "media-type" attribute 394 which identifies the media type (e.g. audio, video, message and 395 application) and MUST have one of the values registered for "media" 396 of SDP [12]. 398 The "media-stream" element has also an optional "proto" sub-element, 399 which MUST has the value registered for "proto" of SDP [12]). 401 An optional "ssrc" sub-element, if present, carries the value of SSRC 402 (RTP/RTCP [8]) as generated by the user for the stream it sends. 404 When an RTP mixer generates a CSRC list according to RTP/RTCP [8], it 405 inserts a list of the SSRC identifiers of the sources that 406 contributed to the generation of a particular packet into the RTP 407 header of that packet. "An example application is audio conferencing 408 where a mixer indicates all the talkers whose speech was combined to 409 produce the outgoing packet, allowing the receiver to indicate the 410 current talker, even though all the audio packets contain the same 411 SSRC identifier (that of the mixer)." 413 4.1.2 Sidebar 415 The sidebar element has one attribute - "entity" that indicates the 416 URI which identifiers the sidebar. A sidebar has zero or more users 417 that are of type "user-type" as the users of the main conference are. 419 4.1.3 Additional Conference Identifiers 421 In addition to the Conference URI present in the "entity" attribute, 422 a conference MAY have additional URIs of various types. Connecting to 423 these URIs will result in joining to the same conference. 425 4.1.4 Policy URIs 427 A policy URI specifies where and how a certain policy pertaining to 428 the conference can be accessed. The actual policy name and usage is 429 deduced from the URI schema name. 431 An example for the "policy-uri" usage is inclusion of the URI of the 432 CPCP [11]. A subscriber to the Conference package can use the Policy 433 URI to access and modify the conference policy. 435 4.2 Constructing Coherent State 437 The conference information subscriber maintains a table for the list 438 of users in the conference. The table contains a row for each user. 439 Each row is indexed by a URI, present in the "uri" attribute of the 440 "user" element. The contents of each row contain the state of that 441 user as conveyed in the document. 443 The table is associated with a version number. The version number 444 MUST be initialized with the value of the "version" attribute from 445 the "conference-info" element in the first document received. Each 446 time a new document is received, the value of the local version 447 number, and the "version" attribute in the new document, are 448 compared. If the value in the new document is one higher than the 449 local version number, the local version number is increased by one, 450 and the document is processed. If the value in the document is more 451 than one higher than the local version number, the local version 452 number is set to the value in the new document, the document is 453 processed, and the subscriber SHOULD generate a refresh request to 454 trigger a full state notification. If the value in the document is 455 less than the local version, the document is discarded without 456 processing. 458 The processing of the conference information document depends on 459 whether it contains full or partial state. If it contains full state, 460 indicated by the value of the "state" attribute in the 461 "conference-info" element, the contents of the table is flushed. It 462 is repopulated from the document. A new row in the user table is 463 created for each "user" element. If the document contains partial 464 state, as indicated by the value of the "state" attribute in the 465 "conference-info" element, the document is used to update the table. 466 For each "user" element in the document, the subscriber checks to see 467 whether a row exists for that user in the user table. This check is 468 done by comparing the URI in the "uri" attribute of the "user" 469 element with the URI associated with the row. If the user doesn't 470 exist in the table, a row is added, and its state is set to the 471 information from that "user" element. If the user does exist, its 472 state is updated to be the information from that "user" element. If a 473 row is updated or created, such that its state is now disconnected, 474 booted, failed or departed, that entry MAY be removed from the table 475 at any time. 477 4.3 Schema 479 480 481 484 486 488 489 490 491 492 493 494 495 497 498 499 500 501 502 503 504 505 507 508 510 512 513 515 516 517 518 519 520 521 522 524 525 526 527 528 530 532 533 534 535 537 539 540 542 543 544 545 546 547 549 550 552 553 554 555 556 557 558 559 561 562 563 564 565 566 567 569 570 571 572 573 574 575 577 578 579 580 581 582 584 586 4.4 Example 588 The following is an example conference information document: 590 592 593 connected 594 dialed-in 595 596 RTP/AVP 597 583398 598 599 601 602 on-hold 603 605 606 on-hold 607 609 610 611 612 614 tel:+18005671234 615 h323:conf545@example.com 617 619 This conference currently has three users, two of which are in a 620 sidebar conversation. The conference is being recorded. There are 621 additional means to join the conference either by phone using tel URI 622 [14] or by H.323 protocol using h323 URL [13]. 624 5. Security Considerations 626 Subscriptions to conference state can reveal very sensitive 627 information. For this reason, the document recommends authentication 628 and authorization, and provides guidelines on sensible authorization 629 policies. 631 Since the data in notifications is sensitive as well, end-to-end SIP 632 encryption mechanisms using S/MIME SHOULD be used to protect it. 634 6. IANA Considerations 636 This document registers a SIP event package, a new MIME type, 637 application/conference-info+xml, a new XML namespace, and a new XML 638 schema. 640 6.1 conference Event Package Registration 642 This specification registers an event package, based on the 643 registration procedures defined in RFC 3265 [2]. The following is the 644 information required for such a registration: 646 Package Name: conference 648 Package or Template-Package: This is a package. 650 Published Document: RFC XXXX (Note to RFC Editor: Please fill in XXXX 651 with the RFC number of this specification). 653 Person to Contact: Jonathan Rosenberg, jdrosen@jdrosen.net. 655 6.2 application/conference-info+xml MIME Registration 657 MIME media type name: application 659 MIME subtype name: conference-info+xml 661 Mandatory parameters: none 663 Optional parameters: Same as charset parameter application/xml as 664 specified in RFC 3023 [7]. 666 Encoding considerations: Same as encoding considerations of 667 application/xml as specified in RFC 3023 [7]. 669 Security considerations: See Section 10 of RFC 3023 [7] and Section 5 670 of this specification. 672 Interoperability considerations: none. 674 Published specification: This document. 676 Applications which use this media type: This document type has been 677 used to support SIP conferencing applications. 679 Additional Information: 681 Magic Number: None 683 File Extension: .cif or .xml 685 Macintosh file type code: "TEXT" 687 Personal and email address for further information: Jonathan 688 Rosenberg, 690 Intended usage: COMMON 692 Author/Change controller: The IETF. 694 6.3 URN Sub-Namespace Registration for 695 urn:ietf:params:xml:ns:conference-info 697 This section registers a new XML namespace, as per the guidelines in 698 [6]. 700 URI: The URI for this namespace is 701 urn:ietf:params:xml:ns:conference-info. 703 Registrant Contact: IETF, SIPPING working group, , 704 Jonathan Rosenberg . 706 XML: 708 BEGIN 709 710 712 713 714 716 Conference Information Namespace 717 719

Namespace for Conference Information

720

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

721

See RFCXXXX.

722 723 724 END 726 6.4 XML Schema Registration 728 This specification registers a schema, as per the guidelines in in 729 [6]. 731 URI: please assign. 733 Registrant Contact: IETF, SIPPING Working Group 734 (sipping@ietf.org), Jonathan Rosenberg (jdrosen@jdrosen.net). 736 XML: The XML can be found as the sole content of Section 4.3. 738 7. Acknowledgements 740 The authors would like to thank Dan Petrie, Sean Olson, and Alan 741 Johnston for their comments. 743 8. Changes since -02 745 o State "muted-by-focus" is added to user's status. 747 o Optional conference attribute "recording" is added. 749 o Policy URI placeholder (i.e. element "policy-uri") is created. 751 o Example�s syntax is corrected. 753 o Optional attribute "cascaded-focus" URI per user is added. 755 o Optional additional conference identifiers (i.e. element 756 "conf-uri") are added. 758 o In order to cover all possible cases, participant's status is 759 expressed using three optional statuses: "status", "joining-mode" 760 and "disconnection-reason". That is instead of "activity-status", 761 "history-status" and "is-on-dial-out-list". 763 9. Changes since -01 765 o Package parameters are removed. Decision about performing 766 "recursive" membership algorithm is perceived as a focus local 767 policy. 769 o General information (i.e. pointers to additional available 770 services) is removed. The defined XML schema can be extended in 771 future to include those when XCON work matures. 773 o Dialog information is removed. It can be obtained by direct 774 subscription to a dialog package of a participant. 776 o Media stream information is aligned with SDP definitions (media 777 and proto) and SSRC attribute is added. 779 o Participant's status is expressed using two optional statuses: 780 "activity" and "history". Optional "is-on-a-dial-out-list" 781 indication is added. 783 o Normative references to XCON work are removed. 785 o Optional sidebar rosters are added. 787 Normative References 789 [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement 790 Levels", BCP 14, RFC 2119, March 1997. 792 [2] Roach, A., "Session Initiation Protocol (SIP)-Specific Event 793 Notification", RFC 3265, June 2002. 795 [3] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., 796 Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP: 797 Session Initiation Protocol", RFC 3261, June 2002. 799 [4] Moats, R., "URN Syntax", RFC 2141, May 1997. 801 [5] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, 802 August 1999. 804 [6] Mealling, M., "The IETF XML Registry", 805 draft-mealling-iana-xmlns-registry-05 (work in progress), June 806 2003. 808 [7] Murata, M., St. Laurent, S. and D. Kohn, "XML Media Types", RFC 809 3023, January 2001. 811 [8] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, 812 "RTP: A Transport Protocol for Real-Time Applications", RFC 813 3550, July 2003. 815 Informative References 817 [9] Rosenberg, J., "A Framework for Conferencing with the Session 818 Initiation Protocol", 819 draft-ietf-sipping-conferencing-framework-01 (work in 820 progress), October 2003. 822 [10] Rosenberg, J. and H. Schulzrinne, "An INVITE Inititiated Dialog 823 Event Package for the Session Initiation Protocol (SIP)", 824 draft-ietf-sipping-dialog-package-03 (work in progress), 825 October 2003. 827 [11] Koskelainen, P., "Requirements for Conference Policy Control 828 Protocol", draft-ietf-xcon-cpcp-reqs-02 (work in progress), 829 February 2004. 831 [12] Handley, M. and V. Jacobson, "SDP: Session Description 832 Protocol", RFC 2327, April 1998. 834 [13] Levin, O., "H.323 Uniform Resource Locator (URL) Scheme 835 Registration", RFC 3508, April 2003. 837 [14] Schulzrinne, H., "The tel URI for Telephone Numbers", 838 draft-ietf-iptel-tel-rfc2806bis-03 (work in progress), February 839 2004. 841 Authors' Addresses 843 Jonathan Rosenberg 844 dynamicsoft 845 600 Lanidex Plaza 846 Parsippany, NJ 07054 847 US 849 Phone: +1 973 952-5000 850 EMail: jdrosen@dynamicsoft.com 851 URI: http://www.jdrosen.net 852 Henning Schulzrinne 853 Columbia University 854 M/S 0401 855 1214 Amsterdam Ave. 856 New York, NY 10027 857 US 859 EMail: schulzrinne@cs.columbia.edu 860 URI: http://www.cs.columbia.edu/~hgs 862 Orit Levin (editor) 863 Microsoft Corporation 864 One Microsoft Way 865 Redmond, WA 98052 866 USA 868 EMail: oritl@microsoft.com 870 Intellectual Property Statement 872 The IETF takes no position regarding the validity or scope of any 873 intellectual property or other rights that might be claimed to 874 pertain to the implementation or use of the technology described in 875 this document or the extent to which any license under such rights 876 might or might not be available; neither does it represent that it 877 has made any effort to identify any such rights. Information on the 878 IETF's procedures with respect to rights in standards-track and 879 standards-related documentation can be found in BCP-11. Copies of 880 claims of rights made available for publication and any assurances of 881 licenses to be made available, or the result of an attempt made to 882 obtain a general license or permission for the use of such 883 proprietary rights by implementors or users of this specification can 884 be obtained from the IETF Secretariat. 886 The IETF invites any interested party to bring to its attention any 887 copyrights, patents or patent applications, or other proprietary 888 rights which may cover technology that may be required to practice 889 this standard. Please address the information to the IETF Executive 890 Director. 892 Full Copyright Statement 894 Copyright (C) The Internet Society (2004). All Rights Reserved. 896 This document and translations of it may be copied and furnished to 897 others, and derivative works that comment on or otherwise explain it 898 or assist in its implementation may be prepared, copied, published 899 and distributed, in whole or in part, without restriction of any 900 kind, provided that the above copyright notice and this paragraph are 901 included on all such copies and derivative works. However, this 902 document itself may not be modified in any way, such as by removing 903 the copyright notice or references to the Internet Society or other 904 Internet organizations, except as needed for the purpose of 905 developing Internet standards in which case the procedures for 906 copyrights defined in the Internet Standards process must be 907 followed, or as required to translate it into languages other than 908 English. 910 The limited permissions granted above are perpetual and will not be 911 revoked by the Internet Society or its successors or assignees. 913 This document and the information contained herein is provided on an 914 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 915 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 916 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 917 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 918 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 920 Acknowledgment 922 Funding for the RFC Editor function is currently provided by the 923 Internet Society.