RFC 5898: Connectivity Preconditions for Session Description Protocol (SDP) Media Streams
In plain English — editorial summary, not part of the RFC
This document defines a new connectivity precondition for the Session Description Protocol (SDP) precondition framework. A connectivity precondition can be used to delay session establishment or modification until media stream connectivity has been successfully verified. The method of verification may vary depending on the type of transport used for the media. For unreliable datagram transports such as UDP, verification involves probing the stream with data or control packets. For reliable connection-oriented transports such as TCP, verification can be achieved simply by successful connection establishment or by probing the connection with data or control packets, depending on the situation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5898
- Published
- July 2010
- Authors
- F. Andreasen; G. Camarillo; D. Oran; D. Wing
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 6223Indication of Support for Keep-AliveCurrent
April 2011
- RFC 6442Location Conveyance for the Session Initiation ProtocolUpdated
December 2011
- RFC 6446Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate ControlCurrent
January 2012
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 7092A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User AgentsCurrent
December 2013
- RFC 7118The WebSocket Protocol as a Transport for the Session Initiation Protocol (SIP)Current
January 2014
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?