SIPPING Draft Status individualWG itemWGLCIETF LCIESG revRFCed 3g reqscc-transfercall-flowsisup-sip3pccdeaf reqs req historye164overlapnai-reqs reg packagecc-fwsipt aaa reqsconf-models configconf pack * conf reqsdialog pack connection reuse mwi markup/keysnat-scenario qsigservice flows billing stufffax flows content indirect

State of Conferencing Want to adopt a work plan to standardize conferencing Need coherent set of consistent docs Several requirements need to move elsewhere (MMUSIC) Several requirements which may or may not use SIP as a mechanism

Conferencing Scope Tightly-coupled conferences Controlled by a “focus” which has a one-to- one dialog relationship with each “member” Requirements include: –floor control -> MMUSIC –membership control –media layout/presentation -> MMUSIC SIP or non-SIP requirements

Proposed Conferencing Work Plan High-Level Requirements (some deferred) - Levin, et al (Aug 1) Use Cases - Even, Ismail, Zmolek (Aug 1) Framework (start simple and short) - Rosenberg (Aug 1) Mid-Level Requirements - Taylor, Rosen (Sep 1) Examples BCP - TBD Floor Control Reqs (MMUSIC) - Taylor, Rosen, Koskelainen (Aug 1) Media Layout and Presentation Reqs (MMUSIC) - Levin, Even, Zmolek (Sep 1) Update cc-framework to remove most conferencing specific language - Mahy

Message Waiting Issue #1 Should the "media types" concept be replaced entirely with message contexts? –non-backwards compatible change, but better semantic match than what is in the draft now –This would also add extensibility and change control in a single document –The list of valid message-context-classes are: voice-message, fax-message, pager-message, multimedia-message, text-message, and none.

Message Waiting Issue #2 Should the syntax follow SIP instead of the restrictive syntax now in place? –adds explicit whitescape/line folding –use same parser –(The optional message-headers would borrow the "extension-header" syntax from SIP)

Message Waiting Issues #3 If forking or state agents are supported, and the subscriber subscribes to a group alias, how is the specific messaging account specified in the corresponding notifies Peehaps need a “collection” event package template

Connection Reuse