rfc8867v3.txt		rfc8867.txt
	Internet Engineering Task Force (IETF) Z. Sarker		Internet Engineering Task Force (IETF) Z. Sarker
	Request for Comments: 8867 Ericsson AB		Request for Comments: 8867 Ericsson AB
	Category: Informational V. Singh		Category: Informational V. Singh
	ISSN: 2070-1721 callstats.io		ISSN: 2070-1721 callstats.io
	X. Zhu		X. Zhu
	Cisco Systems		Cisco Systems
	M. Ramalho		M. Ramalho
	AcousticComms		AcousticComms
	July 2020		January 2021
	Test Cases for Evaluating Congestion Control for Interactive Real-Time		Test Cases for Evaluating Congestion Control for Interactive Real-Time
	Media		Media
	Abstract		Abstract
	The Real-time Transport Protocol (RTP) is used to transmit media in		The Real-time Transport Protocol (RTP) is used to transmit media in
	multimedia telephony applications. These applications are typically		multimedia telephony applications. These applications are typically
	required to implement congestion control. This document describes		required to implement congestion control. This document describes
	the test cases to be used in the performance evaluation of such		the test cases to be used in the performance evaluation of such
	skipping to change at line 41 ¶		skipping to change at line 41 ¶
	Internet Engineering Steering Group (IESG). Not all documents		Internet Engineering Steering Group (IESG). Not all documents
	approved by the IESG are candidates for any level of Internet		approved by the IESG are candidates for any level of Internet
	Standard; see Section 2 of RFC 7841.		Standard; see Section 2 of RFC 7841.
	Information about the current status of this document, any errata,		Information about the current status of this document, any errata,
	and how to provide feedback on it may be obtained at		and how to provide feedback on it may be obtained at
	https://www.rfc-editor.org/info/rfc8867.		https://www.rfc-editor.org/info/rfc8867.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2021 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at line 481 ¶		skipping to change at line 481 ¶
	two endpoints varies over time. This test is designed to measure the		two endpoints varies over time. This test is designed to measure the
	responsiveness of the candidate algorithm. This test tries to		responsiveness of the candidate algorithm. This test tries to
	address the requirements in [RFC8836], which requires the algorithm		address the requirements in [RFC8836], which requires the algorithm
	to adapt the flow(s) and provide lower end-to-end latency when there		to adapt the flow(s) and provide lower end-to-end latency when there
	exists:		exists:
	* an intermediate bottleneck		* an intermediate bottleneck
	* change in available capacity (e.g., due to interface change,		* change in available capacity (e.g., due to interface change,
	routing change, abrupt arrival/departure of background non-		routing change, abrupt arrival/departure of background non-
	adaptive traffic).		adaptive traffic)
	* maximum media bit rate is greater than link capacity. In this		* maximum media bit rate is greater than link capacity. In this
	case, when the application tries to ramp up to its maximum bit		case, when the application tries to ramp up to its maximum bit
	rate, since the link capacity is limited to a lower value, the		rate, since the link capacity is limited to a lower value, the
	congestion control scheme is expected to stabilize the sending bit		congestion control scheme is expected to stabilize the sending bit
	rate close to the available bottleneck capacity.		rate close to the available bottleneck capacity.
	It should be noted that the exact variation in available capacity due		It should be noted that the exact variation in available capacity due
	to any of the above depends on the underlying technologies. Hence,		to any of the above depends on the underlying technologies. Hence,
	we describe a set of known factors, which may be extended to devise a		we describe a set of known factors, which may be extended to devise a
	skipping to change at line 847 ¶		skipping to change at line 847 ¶
	Application-related:		Application-related:
	Media Source:		Media Source:
	Media type: Video		Media type: Video
	Media direction: forward		Media direction: forward
	Number of media sources: three (3)		Number of media sources: three (3)
	Media timeline: new media flows are added sequentially,		Media timeline: New media flows are added sequentially,
	at short time intervals. See the test-specific setup		at short time intervals. See the test-specific setup
	below.		below.
	Media type: Audio		Media type: Audio
	Media direction: forward		Media direction: forward
	Number of media sources: three (3)		Number of media sources: three (3)
	Media timeline: new media flows are added sequentially,		Media timeline: New media flows are added sequentially,
	at short time intervals. See the test-specific setup		at short time intervals. See the test-specific setup
	below.		below.
	Competing traffic:		Competing traffic:
	Number of sources: zero (0)		Number of sources: zero (0)
	Test-specific information: Table 5 defines the media timeline for		Test-specific information: Table 5 defines the media timeline for
	both media types.		both media types.
	skipping to change at line 936 ¶		skipping to change at line 936 ¶
	Application-related:		Application-related:
	Media source:		Media source:
	Media type: Video		Media type: Video
	Media direction: forward		Media direction: forward
	Number of media sources: five (5)		Number of media sources: five (5)
	Media timeline: new media flows are added sequentially,		Media timeline: New media flows are added sequentially,
	at short time intervals. See the test-specific setup		at short time intervals. See the test-specific setup
	below.		below.
	Media type: Audio		Media type: Audio
	Media direction: forward		Media direction: forward
	Number of media sources: five (5)		Number of media sources: five (5)
	Media timeline: New media flows are added sequentially,		Media timeline: New media flows are added sequentially,
	skipping to change at line 1473 ¶		skipping to change at line 1473 ¶
	for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August		for RTP over UDP", RFC 6679, DOI 10.17487/RFC6679, August
	2012, <https://www.rfc-editor.org/info/rfc6679>.		2012, <https://www.rfc-editor.org/info/rfc6679>.
	[RFC8593] Zhu, X., Mena, S., and Z. Sarker, "Video Traffic Models		[RFC8593] Zhu, X., Mena, S., and Z. Sarker, "Video Traffic Models
	for RTP Congestion Control Evaluations", RFC 8593,		for RTP Congestion Control Evaluations", RFC 8593,
	DOI 10.17487/RFC8593, May 2019,		DOI 10.17487/RFC8593, May 2019,
	<https://www.rfc-editor.org/info/rfc8593>.		<https://www.rfc-editor.org/info/rfc8593>.
	[RFC8836] Jesup, R. and Z. Sarker, Ed., "Congestion Control		[RFC8836] Jesup, R. and Z. Sarker, Ed., "Congestion Control
	Requirements for Interactive Real-Time Media", RFC 8836,		Requirements for Interactive Real-Time Media", RFC 8836,
	DOI 10.17487/RFC8836, July 2020,		DOI 10.17487/RFC8836, January 2021,
	<https://www.rfc-editor.org/info/rfc8836>.		<https://www.rfc-editor.org/info/rfc8836>.
	[RFC8868] Singh, V., Ott, J., and S. Holmer, "Evaluating Congestion		[RFC8868] Singh, V., Ott, J., and S. Holmer, "Evaluating Congestion
	Control for Interactive Real-time Media", RFC 8868,		Control for Interactive Real-Time Media", RFC 8868,
	DOI 10.17487/RFC8868, July 2020,		DOI 10.17487/RFC8868, January 2021,
	<https://www.rfc-editor.org/info/rfc8868>.		<https://www.rfc-editor.org/info/rfc8868>.
	[RFC8869] Sarker, Z., Zhu, X., and J. Fu, "Evaluation Test Cases for		[RFC8869] Sarker, Z., Zhu, X., and J. Fu, "Evaluation Test Cases for
	Interactive Real-Time Media over Wireless Networks",		Interactive Real-Time Media over Wireless Networks",
	RFC 8869, DOI 10.17487/RFC8869, July 2020,		RFC 8869, DOI 10.17487/RFC8869, January 2021,
	<https://www.rfc-editor.org/info/rfc8869>.		<https://www.rfc-editor.org/info/rfc8869>.
	10.2. Informative References		10.2. Informative References
	[HEVC-seq] HEVC, "Test Sequences",		[HEVC-seq] HEVC, "Test Sequences",
	<http://www.netlab.tkk.fi/~varun/test_sequences/>.		<http://www.netlab.tkk.fi/~varun/test_sequences/>.
	[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41,		[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41,
	RFC 2914, DOI 10.17487/RFC2914, September 2000,		RFC 2914, DOI 10.17487/RFC2914, September 2000,
	<https://www.rfc-editor.org/info/rfc2914>.		<https://www.rfc-editor.org/info/rfc2914>.
End of changes. 9 change blocks.
	10 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/