1 / 6

The PUBLISH Method

The PUBLISH Method. Draft-olson-sip-publish-00. 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. A model for presence composition.

isha
Télécharger la présentation

The PUBLISH Method

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The PUBLISH Method Draft-olson-sip-publish-00 Sean Olson <seanol@microsoft.com>

  2. 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 Sean Olson <seanol@microsoft.com>

  3. 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 Sean Olson <seanol@microsoft.com>

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

  5. Example PUBLISH message PUBLISH sip:presentity@domain.com SIP/2.0 Via: SIP/2.0/UDP pua.domain.com;branch=z9hG4bK652hsge To: <sip:presentity@domain.com> From: <sip:presentity@domain.com>;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: ... <?xml version="1.0" encoding="UTF-8"?> <presence xmlns="urn:ietf:params:xml:ns:cpim-pidf" entity="pres:presentity@domain.com"> <tuple id="mobile-phone"> <status> <basic>closed</basic> </status> </tuple> </presence> Sean Olson <seanol@microsoft.com>

  6. 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? Sean Olson <seanol@microsoft.com>

More Related