SIP Configuration Issues: IETF 57, SIPPING Rohan Mahy much content from: Jonathan Rosenberg

Problem We have a potential conflict between the XCAP change package (a SIMPLE WG item) and SIP configuration framework (a SIPPING WG item). Event: sip-config versus Event: xcap-change Would be good to have a consistent way to do change notification regardless of which protocol.

Config framework and xcap XCAP fits in as a piece of the config framework Configuration Retrieval Change Notification Configuration Upload Differences in many details

Similarities HTTP GET/POST for retrieval SUBSCRIBE for finding about changes Don’t include configuration in SIP – fetch it with HTTP

Differences URI used in SUBSCRIBE Content of NOTIFY Config generation Xcap says it’s the username Config-fw says its sipuaconfig Content of NOTIFY Xcap says its the changes – full state notify is just the version Config-fw says its an indirect reference to the content in all cases Config generation Xcap has no notion of this Config-fw uses User Agent header to ID the device and create a profile Profile naming Xcap: client knows the data it needs to get Config-fw: server tells the client the URI to get

Questions Should we unify these things? Are they the same problem? Do they have the same requirements for a solution?

Proposed Solution Merge or Reorganize these two drafts Need an author with some cycles—Dan should have more cycles than in the past What should the new document look like? Comments?