Support for non-compund RTCP in RTCP AVPF profile, opportunities and consequences
draft-johansson-avt-rtcp-avpf-non-compound-02

Document Type Replaced Internet-Draft (individual)
Last updated 2008-07-11 (latest revision 2007-07-03)
Replaced by draft-ietf-avt-rtcp-non-compound
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 Replaced by draft-ietf-avt-rtcp-non-compound
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-johansson-avt-rtcp-avpf-non-compound-02.txt

Abstract

This memo discusses benefits and issues that arise when allowing RTCP packets to be transmitted as non-compound packets, i.e. not follow the rules of RFC 3550. Based on that analysis this memo proposes changes to the rules to allow feedback messages to be sent as non- compound RTCP packets when using the RTP AVPF profile (RFC 4585) under certain conditions.

Authors

Ingemar Johansson (ingemar.s.johansson@ericsson.com)
Magnus Westerlund (magnus.westerlund@ericsson.com)

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