RFC 2959: Real-Time Transport Protocol Management Information Base
In plain English — editorial summary, not part of the RFC
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2959
- Published
- October 2000
- Authors
- M. Baugher; B. Strahm; I. Suconick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3016RTP Payload Format for MPEG-4 Audio/Visual StreamsObsoleted
November 2000
- RFC 3047RTP Payload Format for ITU-T Recommendation G.722.1Obsoleted
January 2001
- RFC 2762Sampling of the Group Membership in RTPCurrent
February 2000
- RFC 3189RTP Payload Format for DV (IEC 61834) VideoObsoleted
January 2002
- RFC 3190RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled AudioCurrent
January 2002
- RFC 3267Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio CodecsObsoleted
July 2002
- RFC 3389Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)Current
October 2002
- RFC 2508Compressing IP/UDP/RTP Headers for Low-Speed Serial LinksCurrent
February 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?