<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sipcore-rfc4244bis-callflows" target="https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-rfc4244bis-callflows-08">
   <front>
      <title>Session Initiation Protocol (SIP) History-Info Header Call Flow Examples</title>
      <author initials="M." surname="Barnes" fullname="Mary Barnes">
         </author>
      <author initials="F." surname="Audet" fullname="Francois Audet">
         <organization>Skype</organization>
      </author>
      <author initials="S." surname="Schubert" fullname="Shida Schubert">
         <organization>NTT</organization>
      </author>
      <author initials="H. E." surname="van Elburg" fullname="Hans Erik van Elburg">
         <organization>Detecon International Gmbh</organization>
      </author>
      <author initials="C." surname="Holmberg" fullname="Christer Holmberg">
         <organization>Ericsson</organization>
      </author>
      <date month="November" day="7" year="2013" />
      <abstract>
	 <t>This document describes use cases and documents call flows that require the History-Info header field to capture the Request-URIs as a Session Initiation Protocol (SIP) Request is retargeted.  The use cases are described along with the corresponding call flow diagrams and messaging details.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sipcore-rfc4244bis-callflows-08" />
   
</reference>
