1. Publish Requirements

2. draft-donovan-publish-requirements-01
Characterizes publish as upload of service data (CPL, Presence Docs)
Starts SIP/other protocol discussion
Lists requirements on extension if SIP is chosen

3. …-publish-requirements-…
Arbitrary content
Explicit binding to a service
Explicit declaration of action
Add, delete, replace, append, merge
extensible
Provide/use Auth/Auth
Establish duration (allow hard state)

4. Draft-stucker-sipping-publish-00
Satisfies –publish-requirements-
Carries content in bodies
DATA Method
Action header
Service header

5. Discord
Little opposition (little disussion) of donovan-publish-requirements-
Little support for stucker-sipping-publish

6. What’s the disconnect?
It is not clear whether it is appropriate to meet these requirements using SIP.
-publish-requirements- proposes requirements on a SIP extension. Should they be generalized?
If you abstract the implementation protocol(s) away, are these the right requirements?

7. If we “publish” using Protocol foo
How do we bind foo-things to sip-things?
How do we ensure the foo infrastucture gets the “publish” to the particular application being used by the associated sip-thing?