[rfc-dist] RFC 3640 on RTP Payload Format for Transport of MPEG-4 Elementary Streams
rfc-editor@rfc-editor.org (rfc-editor@rfc-editor.org) Mon, 01 December 2003 20:20 UTC
From: rfc-editor@rfc-editor.org
Date: Mon, 01 Dec 2003 12:20:05 -0800
Subject: [rfc-dist] RFC 3640 on RTP Payload Format for Transport of MPEG-4 Elementary Streams
Message-ID: <200312012020.hB1KK5s13608@gamma.isi.edu>
--NextPart A new Request for Comments is now available in online RFC libraries. RFC 3640 Title: RTP Payload Format for Transport of MPEG-4 Elementary Streams Author(s): J. van der Meer, D. Mackie, V. Swaminathan, D. Singer, P. Gentric Status: Standards Track Date: November 2003 Mailbox: jan.vandermeer@philips.com, dmackie@apple.com, viswanathan.swaminathan@sun.com, singer@apple.com, philippe.gentric@philips.com Pages: 43 Characters: 102606 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-avt-mpeg4-simple-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3640.txt The Motion Picture Experts Group (MPEG) Committee (ISO/IEC JTC1/SC29 WG11) is a working group in ISO that produced the MPEG-4 standard. MPEG defines tools to compress content such as audio-visual information into elementary streams. This specification defines a simple, but generic RTP payload format for transport of any non-multiplexed MPEG-4 elementary stream. This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <031201121840.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3640 --OtherAccess Content-Type: Message/External-body; name="rfc3640.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <031201121840.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart--
- [rfc-dist] RFC 3640 on RTP Payload Format for Tra… rfc-editor@rfc-editor.org