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.
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.
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.