@techreport{watson-sipping-req-history-02,
    number =    {draft-watson-sipping-req-history-02},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-watson-sipping-req-history/02/},
    author =    {Mark Watson and Mary Barnes and Cullen Fluffy Jennings and Jon Peterson},
    title =     {{Generic Request History Capability - Requirements}},
    pagetotal = 13,
    year =      2002,
    month =     jun,
    day =       28,
    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.},
}