RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction
In plain English — editorial summary, not part of the RFC
This document describes modifications to the Session Initiation Protocol (SIP) to address problems that have been identified with the SIP non-INVITE transaction. These modifications reduce the probability of messages losing the race condition inherent in the non-INVITE transaction and reduce useless network traffic. They also improve the robustness of SIP networks when elements stop responding. These changes update behavior defined in RFC 3261. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4320
- Published
- January 2006
- Authors
- R. Sparks
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 3261
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 2006
- RFC 4313Requirements for Distributed Control of Automatic Speech Recognition (ASR), Speaker Identification/Speaker Verification (SI/SV), and Text-to-Speech (TTS) ResourcesCurrent
December 2005
- RFC 4298RTP Payload Format for BroadVoice Speech CodecsCurrent
December 2005
- RFC 4348Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio CodecUpdated
January 2006
- RFC 4351Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio StreamCurrent
January 2006
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4353A Framework for Conferencing with the Session Initiation Protocol (SIP)Current
February 2006
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
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?