datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP
draft-ietf-cuss-sip-uui-reqs-09

RFC
Document Stream: IETF
Last updated: 2012-01-03
Replaces: draft-johnston-cuss-sip-uui-reqs
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (cuss)
Doc Shepherd Follow-up Underway
Document shepherd:Vijay Gurbani
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6567
IANA Action State: No IC 
Responsible AD: Gonzalo Camarillo
IESG Note: Vijay K. Gurbani (vkg@bell-labs.com) is the document shepherd.
Send notices to: cuss-chairs@tools.ietf.org, draft-ietf-cuss-sip-uui-reqs@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-cuss-sip-uui-reqs.

Abstract:
This document introduces the transport of call control User-to-User Information (UUI) using the Session Initiation Protocol (SIP) and develops several requirements for a new SIP mechanism. Some SIP sessions are established by or related to a non-SIP application. This application may have information that needs to be transported between the SIP User Agents during session establishment. In addition to interworking with the Integrated Services Digital Network (ISDN) UUI Service, this extension will also be used for native SIP endpoints requiring application UUI. This document is not an Internet Standards Track specification; it is published for informational purposes.

Authors:
Alan Johnston <alan.b.johnston@gmail.com>
Laura Liess <laura.liess.dt@gmail.com>

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