Dismiss
There will be a system update on Friday, May 5th, 6 PM ET. You may experience a brief service interruption.
Browse Prior Art Database

RTP Payload Format for H.261 Video Streams (RFC2032)

IP.com Disclosure Number: IPCOM000002586D
Original Publication Date: 1996-Oct-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 10 page(s) / 26K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

T. Turletti: AUTHOR [+2]

Abstract

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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 11% of the total text.

Network Working Group T. Turletti

Request for Comments: 2032 MIT

Category: Standards Track C. Huitema

Bellcore

October 1996

RTP Payload Format for H.261 Video Streams

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.

Table of Contents

1. Abstract ............................................. 1

2. Purpose of this document ............................. 2

3. Structure of the packet stream ....................... 2

3.1 Overview of the ITU-T recommendation H.261 .......... 2

3.2 Considerations for packetization .................... 3

4. Specification of the packetization scheme ............ 4

4.1 Usage of RTP ........................................ 4

4.2 Recommendations for operation with hardware codecs .. 6

5. Packet loss issues ................................... 7

5.1 Use of optional H.261-specific control packets ...... 8

5.2 H.261 control packets definition .................... 9

5.2.1 Full INTRA-frame Request (FIR) packet ............. 9

5.2.2 Negative ACKnowledgements (NACK) packet ........... 9

6. Security Considerations .............................. 10

Authors' Addresses ..................................... 10

Acknowledgements ....................................... 10

References ............................................. 11

1. Abstract

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.

This specification 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 authors.

2. Purpose of this document

The ITU-T recommendation H.261 [6] specifies the encodings used by

ITU-T compliant video-conference codecs. Although these encodings

were originally specified for fixed data rate ISDN circuits,

experiments [3],[8] have shown that they can also be used over

packet-switched networks such as the Internet.

The purpose of this memo is to specify the RTP payload format for

encapsulating H.261 video streams in RTP [1].

3. Structure of the packet stream

3.1. Overview of the ITU-T recommendation H.261

The H.261 coding is organized as a hierarchy of groupings. The video

stream is composed of a sequence of...