RFC 6141: Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC6141
- Published
- March 2011
- Authors
- G. Camarillo; C. Holmberg; Y. Gao
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 26
- Also known as
- —
- Updates:
- RFC 3261
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5432Quality of Service (QoS) Mechanism Selection in the Session Description Protocol (SDP)Current
March 2009
- RFC 6122Extensible Messaging and Presence Protocol (XMPP): Address FormatObsoleted
March 2011
- RFC 6121Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and PresenceCurrent
March 2011
- RFC 6120Extensible Messaging and Presence Protocol (XMPP): CoreUpdated
March 2011
- RFC 6190RTP Payload Format for Scalable Video CodingCurrent
May 2011
- RFC 6086Session Initiation Protocol (SIP) INFO Method and Package FrameworkCurrent
January 2011
- RFC 6197Location-to-Service Translation (LoST) Service List Boundary ExtensionCurrent
April 2011
- RFC 6216Example Call Flows Using Session Initiation Protocol (SIP) Security MechanismsCurrent
April 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?