A Mechanism for Transporting User to User Call Control Information in SIP
draft-johnston-cuss-sip-uui-01

Document Type Replaced Internet-Draft (individual)
Last updated 2011-11-22 (latest revision 2010-12-14)
Replaced by draft-ietf-cuss-sip-uui
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 Replaced by draft-ietf-cuss-sip-uui
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-johnston-cuss-sip-uui-01.txt

Abstract

There is a need for applications using SIP to exchange User to User Information (UUI) data during session establishment. This information, known as call control UUI, is a small piece of data inserted by an application initiating the session, and utilized by an application accepting the session. This data is opaque to SIP and its function is unrelated to any basic SIP function. Several approaches to transporting call control UUI in SIP have been proposed. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document discusses three mechanisms to meet the requirements defined in the Requirements for SIP Call Control UUI document. A new SIP header field which bests meets these requirements is proposed.

Authors

Alan Johnston (alan.b.johnston@gmail.com)
Joanne McMillen (c.joanne.mcmillen@gmail.com)
James Rafferty (james.rafferty@dialogic.com)

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