CurrentPROPOSED STANDARDIETF stream

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.

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?

canonical URL: /rfc/2250-rtp-payload-format-for-mpeg1-mpeg2-video