RFC 5407: Example Call Flows of Race Conditions in the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document gives example call flows of race conditions in the Session Initiation Protocol (SIP). Race conditions are inherently confusing and difficult to thwart; this document shows the best practices to handle them. The elements in these call flows include SIP User Agents and SIP Proxy Servers. Call flow diagrams and message details are given. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5407
- Published
- December 2008
- Authors
- M. Hasebe; J. Koshiko; Y. Suzuki; T. Yoshikawa; P. Kyzivat
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 60
- Also known as
- BCP147
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5404RTP Payload Format for G.719Current
January 2009
- RFC 5411A Hitchhiker's Guide to the Session Initiation Protocol (SIP)Current
February 2009
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 5391RTP Payload Format for ITU-T Recommendation G.711.1Current
November 2008
- RFC 5390Requirements for Management of Overload in the Session Initiation ProtocolCurrent
December 2008
- RFC 5438Instant Message Disposition Notification (IMDN)Current
February 2009
- RFC 5373Requesting Answering Modes for the Session Initiation Protocol (SIP)Current
November 2008
- RFC 5372Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header RecoveryCurrent
October 2008
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?