RTP Control Protocol (RTCP) Port for Multicast Sessions
draft-begen-avt-rtcp-port-for-ssm-01

 
Document Type Replaced Internet-Draft (individual)
Last updated 2010-08-04 (latest revision 2010-04-04)
Replaced by draft-ietf-avt-rtcp-port-for-ssm
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-avt-rtcp-port-for-ssm
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-begen-avt-rtcp-port-for-ssm-01.txt

Abstract

The Session Description Protocol (SDP) has an attribute that allows RTP applications to specify an address and a port associated with the RTP Control Protocol (RTCP) traffic. In RTP-based source-specific multicast (SSM) sessions, the same attribute is used to designate the address and the RTCP port of the Feedback Target in the SDP description. However, the RTCP port associated with the SSM session itself cannot be specified by the same attribute to avoid ambiguity, and thus, is required to be derived from the "m=" line of the media description. Similarly, in any-source multicast (ASM) sessions, there is no explicit way to specify the destination RTCP port. Deriving the RTCP port from the "m=" line imposes an unnecessary restriction. This document removes this restriction by introducing a new SDP attribute.

Authors

Ali Begen (abegen@cisco.com)

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