RFC 2250: RTP Payload Format for MPEG1/MPEG2 Video
In plain English — editorial summary, not part of the RFC
This memo describes a packetization scheme for MPEG video and audio streams. [STANDARDS-TRACK] The purpose of this document is to express the general Internet community's expectations of Computer Security Incident Response Teams (CSIRTs). It is not possible to define a set of requirements that would be appropriate for all teams, but it is possible and helpful to list and describe the general set of topics and issues which are of concern and interest to constituent communities. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2250
- Published
- January 1998
- Authors
- D. Hoffman; G. Fernando; V. Goyal; M. Civanlar
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 2038
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2343RTP Payload Format for Bundled MPEGCurrent
May 1998
- RFC 3190RTP Payload Format for 12-bit DAT Audio and 20- and 24-bit Linear Sampled AudioCurrent
January 2002
- RFC 3389Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN)Current
October 2002
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
- RFC 3551RTP Profile for Audio and Video Conferences with Minimal ControlUpdated
July 2003
- RFC 2431RTP Payload Format for BT.656 Video EncodingCurrent
October 1998
- RFC 2435RTP Payload Format for JPEG-compressed VideoCurrent
October 1998
- 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?