1. 6/3/2015Sean Olson The PUBLISH Method Draft-olson-sip-publish-00

2. Sean Olson 6/3/2015 Overview A general purpose mechanism for publishing event state First application is presence publication Based on model for presence composition Defines new PUBLISH method New PType, PStream, PState Headers

3. Sean Olson 6/3/2015 A model for presence composition Event state is published to a “slot” identified by a token carried in the PType header. The slot identifies the context of the published data Publishing devices are distinguished by a unique identifier carried in the PStream header One or more devices can publish to the same slot Event state is soft-state with an expiration value carried in the PState header

4. Sean Olson 6/3/2015 A model for presence composition Presence Compositor PUA Composite Document Appl PUA Share the same “slot” or PType Differentiated by PStream A third party publishing on behalf of the user using a well-known Ptype (e.g. geoloc)

5. Sean Olson 6/3/2015 Example PUBLISH message PUBLISH sip:presentity@domain.com SIP/2.0 Via: SIP/2.0/UDP pua.domain.com;branch=z9hG4bK652hsge To: From: ;tag=1234wxyz Call-ID: 12345678@pua.domain.com CSeq: 3242 PUBLISH Expires: 3600 Event: presence PType: mobile PStream: f81d4fae-7dec-11d0-a765-00a0c91e6bf6@pua.domain.com Content-Type: application/cpim-pidf+xml Content-Length:... closed

6. Sean Olson 6/3/2015 Open Issues Do we attempt to solve the CPL problem with the same model/mechanism? Is the slot concept the right way to go? Do we need to standardize the PType tokens? Should PType require IANA registration? Replace PState with Expires: header?