Elevating RTP to Protocol Status
draft-rosenberg-rtpproto-00

Document Type Expired Internet-Draft (individual)
Authors Jonathan Rosenberg  , Henning Schulzrinne  , Bernard Aboba 
Last updated 1998-03-13
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-rosenberg-rtpproto-00.txt

Abstract

This document discusses the issues involved in elevating RTP to the status of protocol, equivalent to TCP or UDP. This will result in all RTP packets being explicitly labeled as such in the packet header. This vastly simplifies the problem of classifying real time streams. Such classification operations are essential for successful deploy- ment of RTP header compression, differentiated services, and traffic isolation. We define the format of the RTP protocol header, and dis- cuss issues of backwards compatibility.

Authors

Jonathan Rosenberg (jdrosen@cisco.com)
Henning Schulzrinne (hgs+geopriv@cs.columbia.edu)
Bernard Aboba (Bernard_Aboba@hotmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)