RFC 6128 on RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions

rfc-editor@rfc-editor.org Sat, 12 February 2011 00:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 0E7FD3A6A24; Fri, 11 Feb 2011 16:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.025
X-Spam-Status: No, score=-102.025 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Ym+N8-KYQ08H; Fri, 11 Feb 2011 16:04:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 583F93A6A89; Fri, 11 Feb 2011 16:04:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A72C3E074F; Fri, 11 Feb 2011 16:04:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6128 on RTP Control Protocol (RTCP) Port for Source-Specific Multicast (SSM) Sessions
From: rfc-editor@rfc-editor.org
Message-Id: <20110212000425.A72C3E074F@rfc-editor.org>
Date: Fri, 11 Feb 2011 16:04:25 -0800
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Feb 2011 00:04:10 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6128

        Title:      RTP Control Protocol (RTCP) Port 
                    for Source-Specific Multicast (SSM) Sessions 
        Author:     A. Begen
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2011
        Mailbox:    abegen@cisco.com
        Pages:      6
        Characters: 11544
        Updates:    RFC5760

        I-D Tag:    draft-ietf-avt-rtcp-port-for-ssm-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6128.txt

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.  Deriving the RTCP port from the "m=" line imposes an
unnecessary restriction.  This document removes this restriction by
introducing a new SDP attribute.  [STANDARDS-TRACK]

This document is a product of the Audio/Video Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC