Retransmission for Source-Specific Multicast (SSM) Sessions
draft-vancaenegem-avtcore-retransmission-for-ssm-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ali C. Begen , Tom VanCaenegem | ||
Last updated | 2011-05-26 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes RTP retransmission for source-specific multicast (SSM) architectures with unicast feedback. RTP payload format for retransmissions has been defined in RFC 4588, whereas the RTP profile an RTP receiver could use to issue RTP Control Protocol (RTCP) feedback messages and the format of these feedback messages have been defined in RFC 4585. RFC 5760 defines the operation for SSM architectures with unicast feedback. First, we document potential issues that could arise when providing a retransmission service using RTP retransmission (RFC 4588 and RFC 4585) for RFC 5760 architectures based on rules described in the relevant RFCs. We then present solutions that allow to avoid unnecessary feedback suppression, provide enhanced retransmission services and address congestion control for retransmission in an SSM environment. These solutions specify certain rules that apply to the distribution source, feedback target(s), retransmission source(s) and RTP receivers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)