Browse Prior Art Database

RTP Payload Format for JPEG-compressed Video (RFC2435)

IP.com Disclosure Number: IPCOM000003013D
Original Publication Date: 1998-Oct-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 27 page(s) / 33K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Berc: AUTHOR [+4]

Related Documents

10.17487/RFC2435: DOI

Abstract

This memo describes the RTP payload format for JPEG video streams. [STANDARDS-TRACK]

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group L. Berc Request for Comments: 2435 Digital Equipment Corporation Obsoletes: 2035 W. Fenner Category: Standards Track Xerox PARC R. Frederick Xerox PARC S. McCanne Lawrence Berkeley Laboratory P. Stewart Xerox PARC October 1998

RTP Payload Format for JPEG-compressed Video

Status of this Memo

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.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

Abstract

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 a product of the Audio-Video Transport working group within the Internet Engineering Task Force. Comments are solicited and should be addressed to the working group’s mailing list at rem- conf@es.net and/or the author(s).

Changes from RFC 2035

Most of this memo is identical to RFC 2035. The changes made to the protocol are summarized in Appendix D.

Berc, et. al. Standards Track [Page 1]

RFC 2435 RTP Payload Format for JPEG October 1998

Key Words

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [9].

1. Introduction

The Joint Photographic Experts Group (JPEG) standard [1,2,3] defines a family of compression algorithms for continuous-tone, still images. This still image compression standard can be applied to video by compressing each frame of video as an independent still image and transmitting them in series. Video coded in this fashion is often called Motion-JPEG.

We first give an overview of JPEG and then describe the specific subset of JPEG that is supported in RTP and the mechanism by which JPEG frames are carried as RTP payloads.

The JPEG standard defines four modes of operation: the sequential DCT mode, the progressive DCT mode, the lossless mode, and the hierarchical mode. Depending on the mode, the image is represented in one or more passes. Each pass (called a frame in the JPEG standard) is further broken down into one or more scans. Within each scan, there are one to four components, which represent the three components of a color signal (e.g., "red, green, and blue", or a luminance signal and two chrominance signals). These components can be encoded as separate scans or interleaved into a single scan.

Each frame and scan is preceded with a header containing optional definitions for compression parameters like quantization tables and Huffman coding tables. The headers and optional parameters are identified with "markers" and comprise a marker segment; each scan appears a...

Processing...
Loading...