Real-time Transport Control Protocol (RTCP) in Overlay Multicast
draft-ott-avtcore-rtcp-overlay-multicast-02
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2012-09-09 (latest revision 2012-03-08) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
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) | ||
https://www.ietf.org/archive/id/draft-ott-avtcore-rtcp-overlay-multicast-02.txt
Abstract
The Real-time Transport Control Protocol(RTCP) is designed to operate along with Real-time Transport Protocol(RTP) in unicast, single- source multicast and any-source multicast environments. With the availability of overlay multicast and Application Layer Multicast(ALM), the suitability of RTCP in such environments need to be analyzed. The applicability of the existing RTCP reporting architectures in overlay multicast and ALM environments are investigated and the new features that may be required are discussed in this document.
Authors
Varun Singh
(varun@comnet.tkk.fi)
Jegadish Devadoss
(jegadish@netlab.tkk.fi)
Joerg Ott
(jo@comnet.tkk.fi)
Igor Curcio
(igor.curcio@nokia.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)