SIMPLE Session II - 8th March 2005

MSRP Core - Ben Campbell

- Discuss SDP changes - Review + concerns by MMUSIC on usage

- Compromise solution based on copying address + port to conventional locations

- Now referencing SDP new.

- Added new response codes.

- Other general cleanup issues sorted out in version 10 (security, IANA, editorial)

-From list - Incremental REPORT vs Whole message. Do not add feature for client to set preference at this time.

-From list - Overlapping chunks when failover - WG consensus - its the receivers problem - clarify text.

- Robert Sparks : START WGLC AT THE MIC.

MSRP relay - Cullen

- Explanation of new AUTH processing (shared secret)

- Other major changes covered (SDP, response codes, URI consistent with base draft)

- Remove Stateless relay text to avoid future issues

MSRP Conferences - Miguel Garcia

- Overview of exactly what is in the draft + requirements + proposed extensions.

- Ben Campbell - We need a general solution, not specific MSRP extension - should be XCON work.

- Brian Rosen - take your requirements and input to XCON rather than creating protocol specific solution in SIMPLE.

- Paul - Believes there is a disconnect on the meaning of nickname

- Brian Rosen - nickname - need to get together to agree nickname XCON, SIPPING, SIMPLE, SIP.

- JR - be careful when specifying new identifiers.

- Robert Sparks - way forward - mostly XCON with nicknames discussion needed in SIPPING.

XML Path Operations - Jari Urpalainen

- Start with a short overview

- Changes since last version of the draft

- OPEN Issues and Bugs review - Included proposed solutions (see slide deck)

- JR - concerns about technology. Why is this draft being positioned as a replacement for XCAP?

- Robert Sparks - thinks this draft is anything but simple (as positioned)

- Cullen - Bunch of WG need Diff format for XML + are working on it. We seem to be in the middle ground that describes a general mechanism for single problem area.

- Robert Sparks - FEEDBACK FROM ROOM - Do we want to produce specific XCAP solution OR go outside the WG for a general purpose solution.

- Rohan/JR - if we are going to use XCAP we should produce an XCAP specific solution.

- Robert Sparks - WG specific - proposal is not exactly what we want. Probably need to tack back for XCAP specific and then PIDF OR look at a general mechanism.

- Hisham - HUM - No Conclusion - take to the list.

Policy Capabilities - Jonathan

- Problem Statement - How does a client know which of the auth policies it understands.

- Overview - Quick overview

- Open Issues + should this be adopted as a WG item?

- Robert Sparks - Should we adopt this work?

- HUM - suggests WG adoption.

Prescaps Update - Aki

- Changes discussed form last version.

- Rohan - Priority makes composition difficult.

- Open Issues - no major just a couple of minor. Update schema according to schema workshop design decisions.

Presence Processing Model

- Overview of changes in latest version

- Draft represents bottom half of previous data model

- Issues covered

END of MEETING!!!!!!!!