RFC 2435 on RTP Payload Format for JPEG

RFC Editor <rfc-ed@ISI.EDU> Thu, 15 October 1998 22:55 UTC

Message-Id: <199810152242.PAA20267@tnt.isi.edu>
To: IETF-Announce:;
Subject: RFC 2435 on RTP Payload Format for JPEG
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 15 Oct 1998 15:42:15 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2435:

        Title:	    RTP Payload Format for JPEG-compressed Video
	Author(s):  L. Berc, W. Fenner, R. Frederick, S. McCanne,
		    P. Stewart
	Status:     Proposed Standard
	Date:       October 1998
        Mailbox:    berc@pa.dec.com, fenner@parc.xerox.com, 
		    frederick@parc.xerox.com, mccanne@cs.berkeley.edu,
		    stewart@parc.xerox.com
	Pages:      27
        Characters: 54173
        Obsoletes:  2035
        I-D Tag:    draft-ietf-avt-jpeg-new-02.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2435.txt

This memo describes the RTP payload format for JPEG video streams.
The packet format is optimized for real-time video streams where codec
parameters change rarely from frame to frame.

This document is 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 Alegre Ramos
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.

ftp://ftp.isi.edu/in-notes/rfc2435.txt"><ftp://ftp.isi.edu/in-notes/rfc2435.txt>

RFC 2435 on RTP Payload Format for JPEG RFC Editor