1 / 4

Draft-stucker-sipping-publish-00.txt

This draft proposes a simple mechanism using SIP for publishing general service data, allowing for easy data object transport within SIP messages, transaction ordering, and mapping between service data repository and SIP addresses. It is easily implementable and extensible to meet varying transport requirements. Not intended to replace other protocols. No IPR claims.

arnolddavid
Download Presentation

Draft-stucker-sipping-publish-00.txt

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. Draft-stucker-sipping-publish-00.txt • Based on requirements set forth in draft-donovan-publish-requirements-00.txt, and draft-lennox-sip-reg-payload-01.txt for a SIP-specific mechanism for publishing general service data. • There are no known IPR claims to any sections of this draft.

  2. Draft-stucker-sipping-publish-00 • Simple mechanism: • Allows the use of SIP itself for transporting simple service data objects, where appropriate. • Strong precedence of services transporting service data in message bodies. • Not intended to replace other protocols ie. HTTP or FTP. • Provides a mechanism for ordering transactions.

  3. Easily extended. • Where transport requirements are more complex, services could define their packages to return a URL for more advanced operations (HTTP, WebDAV, LDAP, etc.). • Provides a mapping between a service data repository and a SIP Address on a per service (and potentially per action) basis. • Easily implemented. Works off of the existing REGISTER message logic.

More Related