RealMedia File Format
draft-heftagaub-rmff-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Rahul Agarwal , Jeff Ayars , Brad Hefta-Gaub , Dale Stammen | ||
| Last updated | 1998-03-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The RealMedia File Format (RMFF) is designed to be a generic container for streaming media data. This data may then be played back locally or streamed over a network using protocols such as RTSP and RTP. The format is data-independent, allowing any data type to be recorded, manipulated and played back. Note: This document is intended to be informational in nature of what the file format in use by RealNetworks' RealServer and RealPlayer implementations. Though we think that there are a lot of important concepts embodied in this specification, and that it may even make the basis of a ''standard'' file format, this is intended to eventually end up as an Informational RFC.
Authors
Rahul Agarwal
Jeff Ayars
Brad Hefta-Gaub
Dale Stammen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)