RFC 4586 on Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback: Results of the Timing Rule Simulations

rfc-editor@rfc-editor.org Wed, 19 July 2006 18:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GuA-0003Hw-T1; Wed, 19 Jul 2006 14:36:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Gu8-0003Gv-FG; Wed, 19 Jul 2006 14:36:16 -0400
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Gu7-0007nt-39; Wed, 19 Jul 2006 14:36:16 -0400
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k6JI2i06029351; Wed, 19 Jul 2006 11:02:44 -0700
Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k6JI2iQe029350; Wed, 19 Jul 2006 11:02:44 -0700
Date: Wed, 19 Jul 2006 11:02:44 -0700
Message-Id: <200607191802.k6JI2iQe029350@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4586 on Extended RTP Profile for Real-time Transport Control Protocol (RTCP)-Based Feedback: Results of the Timing Rule Simulations
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 4586

        Title:      Extended RTP Profile for Real-time 
                    Transport Control Protocol (RTCP)-Based Feedback: 
                    Results of the Timing Rule Simulations 
        Author:     C. Burmeister, R. Hakenberg,
                    A. Miyazaki, J. Ott,
                    N. Sato, S. Fukunaga
        Status:     Informational
        Date:       July 2006
        Mailbox:    carsten.burmeister@eu.panasonic.com, 
                    rolf.hakenberg@eu.panasonic.com, 
                    miyazaki.akihiro@jp.panasonic.com,  jo@acm.org, 
                    sato652@oki.com,  fukunaga444@oki.com
        Pages:      28
        Characters: 66759
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-burmeister-avt-rtcp-feedback-sim-06.txt

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

This document describes the results achieved when simulating the
timing rules of the Extended RTP Profile for Real-time Transport
Control Protocol (RTCP)-Based Feedback,
denoted AVPF.  Unicast and multicast topologies are considered as
well as several protocol and environment configurations.  The
results show that the timing rules result in better performance
regarding feedback delay and still preserve the well-accepted RTP
rules regarding allowed bit rates for control traffic.  This memo 
provides information for the Internet community.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce