1 / 7

Correlation of multiple SIP sessions. ( draft-loreto-sipping-context-id-requirements-00.txt )

Investigating a mechanism for state preservation and logical correlation of SIP dialogs. Enhance messaging and historical session concept. Define requirements for including external UA in a conversation.

josephcollins
Download Presentation

Correlation of multiple SIP sessions. ( draft-loreto-sipping-context-id-requirements-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. Gonzalo Camarillo Salvatore Loreto 72th IETF, Dublin, Ireland August 2008 Correlation of multiple SIP sessions.(draft-loreto-sipping-context-id-requirements-00.txt)

  2. Context Id - Motivation We are investigating the opportunity of a mechanism: • to provide a sort of preservation of state across the sessions and across the duration of a call; • to logically correlate an existing SIP dialog, or even multiple SIP transaction sent outside a dialog, with a new SIP dialog The logical Correlation is needed when different SIP signalling can be considered as a part of the same conversation.

  3. Context Id – use cases 1/3 Enhance messaging conversation The idea is to give the possibility to use the mechanism within a MESSAGE for Historical Context. • In this way it would be possible • send a Message • and after a while start an MSRP session that is historically related to that MESSAGE.

  4. Context Id – use cases 2/3 Historical Session concept: correlate the new conversation with a previous one The mechanism would provide SIP with a mechanism for storing state (memory of past sessions after they have completed) and reuse it. In an IM call it would help to store and retrieve the old messages; In Application Interaction using SIP as described in the Tote draft, it would help to retain specific data related to the application I am interacting with.

  5. InviteContext ID Dialog 1 Context Id – use cases 3/3 Including an external UA in a conversation • There are cases when folks may want to use different devices for a single session. • The mechanism would be used to logically correlate an existing SIP dialog with a new SIP dialog. Refer Join header does not work and should not be used in a similar scenario, as "the Join implicitly presumes that the Join recipient will function as a conference mixer."

  6. Context Id – requirements • It MUST be possible to correlate a new application started in a new dialog with another application already existent in a separate dialog. • It MUST be possible to correlate new conversation with a previous one. • The mechanism shall be an End to End value. • The mechanism Id has a defined Time To Live.

  7. Context Id – requirements • The Time To Live of the mechanism shall not be coupled to the life cycle of the application • The mechanism Time To Live is controlled and administered by the application • When the mechanism is not able to correlate an existing dialog, it shall be ignored and handled as a new context.

More Related