[rmcat] RFC 8593 on Video Traffic Models for RTP Congestion Control Evaluations
rfc-editor@rfc-editor.org Wed, 15 May 2019 01:35 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB2B1202E5; Tue, 14 May 2019 18:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ETFZOU041wZn; Tue, 14 May 2019 18:35:31 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 223341202B0; Tue, 14 May 2019 18:35:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8B524B81DC2; Tue, 14 May 2019 18:35:18 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rmcat@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190515013518.8B524B81DC2@rfc-editor.org>
Date: Tue, 14 May 2019 18:35:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/EugEQ2y9SQm68NO-pmytv7halug>
Subject: [rmcat] RFC 8593 on Video Traffic Models for RTP Congestion Control Evaluations
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2019 01:35:40 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8593
Title: Video Traffic Models for RTP
Congestion Control Evaluations
Author: X. Zhu,
S. Mena,
Z. Sarker
Status: Informational
Stream: IETF
Date: May 2019
Mailbox: xiaoqzhu@cisco.com,
semena@cisco.com,
Zaheduzzaman.Sarker@ericsson.com
Pages: 19
Characters: 44193
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rmcat-video-traffic-model-07.txt
URL: https://www.rfc-editor.org/info/rfc8593
DOI: 10.17487/RFC8593
This document describes two reference video traffic models for
evaluating RTP congestion control algorithms. The first model
statistically characterizes the behavior of a live video encoder in
response to changing requests on the target video rate. The second
model is trace-driven and emulates the output of actual encoded video
frame sizes from a high-resolution test sequence. Both models are
designed to strike a balance between simplicity, repeatability, and
authenticity in modeling the interactions between a live video
traffic source and the congestion control module. Finally, the
document describes how both approaches can be combined into a hybrid
model.
This document is a product of the RTP Media Congestion Avoidance Techniques 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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