ObsoletedPROPOSED STANDARDIETF stream

RFC 2032: RTP Payload Format for H.261 Video Streams

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4587.

Current version: RFC 4587RTP Payload Format for H.261 Video Streams

In plain English — editorial summary, not part of the RFC

This memo describes a scheme to packetize an H.261 video stream for transport using the Real-time Transport Protocol, RTP, with any of the underlying protocols that carry RTP. [STANDARDS-TRACK]

Document record

Document ID
RFC2032
Published
October 1996
Authors
T. Turletti; C. Huitema
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
11
Also known as
Obsoleted by:
RFC 4587

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/2032-rtp-payload-format-for-h-261-video-streams