<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sipcore-reinvite" target="https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-reinvite-08">
   <front>
      <title>Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)</title>
      <author initials="G." surname="yang" fullname="Gao yang">
         <organization>ZTE</organization>
      </author>
      <author initials="G." surname="Camarillo" fullname="Gonzalo Camarillo">
         <organization>Ericsson</organization>
      </author>
      <author initials="C." surname="Holmberg" fullname="Christer Holmberg">
         <organization>Ericsson</organization>
      </author>
      <date month="December" day="19" year="2010" />
      <abstract>
	 <t>The procedures for handling SIP re-INVITEs are described in RFC 3261.  Implementation and deployment experience has uncovered a number of issues with the original documentation, and this document provides additional procedures that update the original specification to address those issues.  In particular, this document defines in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE.  Additionally, this document defines further details of procedures related to target-refresh requests. [STANDARDS-TRACK]
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sipcore-reinvite-08" />
   
</reference>
