RFC 3158: RTP Testing Strategies
In plain English — editorial summary, not part of the RFC
This memo describes a possible testing strategy for RTP (real-time transport protocol) implementations. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3158
- Published
- August 2001
- Authors
- C. Perkins; J. Rosenberg; H. Schulzrinne
- Status
- INFORMATIONAL
- 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 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 2736Guidelines for Writers of RTP Payload Format SpecificationsUpdated
December 1999
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
- RFC 2190RTP Payload Format for H.263 Video StreamsCurrent
September 1997
- RFC 4733RTP Payload for DTMF Digits, Telephony Tones, and Telephony SignalsUpdated
December 2006
- RFC 4734Definition of Events for Modem, Fax, and Text Telephony SignalsCurrent
December 2006
- RFC 3096Requirements for robust IP/UDP/RTP header compressionCurrent
July 2001
- RFC 2723SRL: A Language for Describing Traffic Flows and Specifying Actions for Flow GroupsCurrent
October 1999
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?