Requirements for Dialog Correlation in the Session Initiation Protocol (SIP)
draft-loreto-sipping-context-id-requirements-02

Document Type Expired Internet-Draft (individual)
Last updated 2009-03-05
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-loreto-sipping-context-id-requirements-02.txt

Abstract

This document justifies the need and lists the requirements for correlating SIP (Session Initiation Protocol) dialogs. The correlated dialogs may or may not be related to the same multimedia session. Being able to logically correlate multiple SIP dialogs is useful for applications that, for different reasons, need to establish several SIP dialogs to provide a given service. The logical correlation of two SIP dialogs is also useful, for instance, to correlate an incoming with an outgoing dialog at a B2BUA.

Authors

Gonzalo Camarillo (gonzalo.camarillo@ericsson.com)
Salvatore Loreto (Salvatore.Loreto@ericsson.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)