RFC 5968 on Guidelines for Extending the RTP Control Protocol (RTCP)

rfc-editor@rfc-editor.org Thu, 16 September 2010 23:07 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 [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8492A3A69F3; Thu, 16 Sep 2010 16:07:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level:
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uP56JKdrZABI; Thu, 16 Sep 2010 16:07:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 3E0E73A69D6; Thu, 16 Sep 2010 16:07:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 979CAE0698; Thu, 16 Sep 2010 16:08:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5968 on Guidelines for Extending the RTP Control Protocol (RTCP)
From: rfc-editor@rfc-editor.org
Message-Id: <20100916230805.979CAE0698@rfc-editor.org>
Date: Thu, 16 Sep 2010 16:08:05 -0700 (PDT)
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: Thu, 16 Sep 2010 23:07:41 -0000

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

        
        RFC 5968

        Title:      Guidelines for Extending the RTP 
                    Control Protocol (RTCP) 
        Author:     J. Ott, C. Perkins
        Status:     Informational
        Stream:     IETF
        Date:       September 2010
        Mailbox:    jo@netlab.tkk.fi, 
                    csp@csperkins.org
        Pages:      17
        Characters: 42541
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-avt-rtcp-guidelines-04.txt

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

The RTP Control Protocol (RTCP) is used along with the Real-time
Transport Protocol (RTP) to provide a control channel between media
senders and receivers.  This allows constructing a feedback loop to
enable application adaptation and monitoring, among other uses.  The
basic reporting mechanisms offered by RTCP are generic, yet quite
powerful and suffice to cover a range of uses.  This document
provides guidelines on extending RTCP if those basic mechanisms prove
insufficient.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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