Generic Request History Capability - Requirements
draft-watson-sipping-req-history-02

Document Type Expired Internet-Draft (individual)
Last updated 2002-06-28
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized 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-watson-sipping-req-history-02.txt

Abstract

Many services that SIP is anticipated to support require the ability to determine why and how the call arrived at a specific application. Examples of such services include (but are not limited to) sessions initiated to call centers via 'click to talk' SIP URLs on a web page, 'call history/logging' style services within intelligent 'call management' software for SIP UAs and calls to voicemail servers and call centers. While SIP implicitly provides the redirect/retarget capabilities that enable calls to be routed to chosen applications, there is currently no standard mechanism within SIP for communicating the history of such a request. This 'request history' information allows the receiving application to determine hints about how and why the call arrived at the application/user. This draft discusses the motivations in support of a mechanism which records the 'request history' and proposes detailed requirements for such a generic 'request history' capability.

Authors

Mark Watson (mark@digitalfountain.com)
Mary Barnes (mary.ietf.barnes@gmail.com)
Cullen Jennings (fluffy@cisco.com)
Jon Peterson (jon.peterson@neustar.biz)

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