RFC 4411: Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events
In plain English — editorial summary, not part of the RFC
This document proposes an IANA Registration extension to the Session Initiation Protocol (SIP) Reason Header to be included in a BYE Method Request as a result of a session preemption event, either at a user agent (UA), or somewhere in the network involving a reservation-based protocol such as the Resource ReSerVation Protocol (RSVP) or Next Steps in Signaling (NSIS). This document does not attempt to address routers failing in the packet path; instead, it addresses a deliberate tear down of a flow between UAs, and informs the terminated UA(s) with an indication of what occurred. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4411
- Published
- February 2006
- Authors
- J. Polk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4412Communications Resource Priority for the Session Initiation Protocol (SIP)Updated
February 2006
- RFC 5898Connectivity Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
July 2010
- RFC 8101IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk ServiceCurrent
March 2017
- RFC 4414An ENUM Registry Type for the Internet Registry Information Service (IRIS)Current
February 2006
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- RFC 4421RTP Payload Format for Uncompressed Video: Additional Colour Sampling ModesCurrent
February 2006
- RFC 4424Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Extension Audio CodecCurrent
February 2006
- RFC 4425RTP Payload Format for Video Codec 1 (VC-1)Current
February 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?