draft-ietf-rmcat-wireless-tests-05.txt | draft-ietf-rmcat-wireless-tests-06.txt | |||
---|---|---|---|---|
Network Working Group Z. Sarker | Network Working Group Z. Sarker | |||
Internet-Draft I. Johansson | Internet-Draft I. Johansson | |||
Intended status: Informational Ericsson AB | Intended status: Informational Ericsson AB | |||
Expires: December 23, 2018 X. Zhu | Expires: June 25, 2019 X. Zhu | |||
J. Fu | J. Fu | |||
W. Tan | W. Tan | |||
M. Ramalho | M. Ramalho | |||
Cisco Systems | Cisco Systems | |||
June 21, 2018 | December 22, 2018 | |||
Evaluation Test Cases for Interactive Real-Time Media over Wireless | Evaluation Test Cases for Interactive Real-Time Media over Wireless | |||
Networks | Networks | |||
draft-ietf-rmcat-wireless-tests-05 | draft-ietf-rmcat-wireless-tests-06 | |||
Abstract | Abstract | |||
There is an ongoing effort in IETF RMCAT working group to standardize | The Real-time Transport Protocol (RTP) is used for interactive | |||
rate adaptation algorithm(s) for real-time interactive communication. | multimedia communication applications. These applications are | |||
To ensure seamless and robust user experience, the proposed rate | typically required to implement congestion control. To ensure | |||
adaptation algorithm(s) should work well across all access network | seamless and robust user experience, a well-designed RTP-based | |||
types. This document describes test cases for evaluating | congestion control algorithm should work well across all access | |||
performances of the proposed rate adaptation solutions over LTE and | network types. This document describes test cases for evaluating | |||
Wi-Fi networks. | performances of such congestion control algorithms over LTE and Wi-Fi | |||
networks. | ||||
Status of This Memo | Status of This Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
This Internet-Draft will expire on December 23, 2018. | This Internet-Draft will expire on June 25, 2019. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | |||
skipping to change at page 2, line 42 ¶ | skipping to change at page 2, line 42 ¶ | |||
4.1.4. Expected behavior . . . . . . . . . . . . . . . . . . 14 | 4.1.4. Expected behavior . . . . . . . . . . . . . . . . . . 14 | |||
4.2. Bottleneck in Wi-Fi Network . . . . . . . . . . . . . . . 15 | 4.2. Bottleneck in Wi-Fi Network . . . . . . . . . . . . . . . 15 | |||
4.2.1. Network topology . . . . . . . . . . . . . . . . . . 15 | 4.2.1. Network topology . . . . . . . . . . . . . . . . . . 15 | |||
4.2.2. Test setup . . . . . . . . . . . . . . . . . . . . . 15 | 4.2.2. Test setup . . . . . . . . . . . . . . . . . . . . . 15 | |||
4.2.3. Typical test scenarios . . . . . . . . . . . . . . . 16 | 4.2.3. Typical test scenarios . . . . . . . . . . . . . . . 16 | |||
4.2.4. Expected behavior . . . . . . . . . . . . . . . . . . 17 | 4.2.4. Expected behavior . . . . . . . . . . . . . . . . . . 17 | |||
4.3. Other Potential Test Cases . . . . . . . . . . . . . . . 18 | 4.3. Other Potential Test Cases . . . . . . . . . . . . . . . 18 | |||
4.3.1. EDCA/WMM usage . . . . . . . . . . . . . . . . . . . 18 | 4.3.1. EDCA/WMM usage . . . . . . . . . . . . . . . . . . . 18 | |||
4.3.2. Effects of Legacy 802.11b Devices . . . . . . . . . . 18 | 4.3.2. Effects of Legacy 802.11b Devices . . . . . . . . . . 18 | |||
5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 18 | 5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 18 | |||
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 | 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 | |||
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 | 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 | |||
8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 19 | |||
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
9.1. Normative References . . . . . . . . . . . . . . . . . . 19 | 9.1. Normative References . . . . . . . . . . . . . . . . . . 19 | |||
9.2. Informative References . . . . . . . . . . . . . . . . . 20 | 9.2. Informative References . . . . . . . . . . . . . . . . . 20 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 | |||
1. Introduction | 1. Introduction | |||
Wireless networks (both cellular and Wi-Fi [IEEE802.11] local area | Wireless networks (both cellular and Wi-Fi [IEEE802.11] local area | |||
network) are an integral part of the Internet. Mobile devices | network) are an integral part of the Internet. Mobile devices | |||
connected to the wireless networks generate huge amount of media | connected to the wireless networks generate huge amount of media | |||
traffic in the Internet. Application scenarios range from users | traffic in the Internet. Application scenarios range from users | |||
having a video call in the bus to media consumption by someone | having a video call in the bus to media consumption by someone | |||
sitting on a living room couch. It is well known that the | sitting on a living room couch. It is well known that the | |||
characteristics and technical challenges for offering multimedia | characteristics and technical challenges for offering multimedia | |||
skipping to change at page 18, line 46 ¶ | skipping to change at page 18, line 46 ¶ | |||
cases can be added to evaluate the affects of legancy devices on the | cases can be added to evaluate the affects of legancy devices on the | |||
performance of RMCAT congestion control algorithm. | performance of RMCAT congestion control algorithm. | |||
5. Conclusion | 5. Conclusion | |||
This document defines a collection of test cases that are considered | This document defines a collection of test cases that are considered | |||
important for cellular and Wi-Fi networks. Moreover, this document | important for cellular and Wi-Fi networks. Moreover, this document | |||
also provides a framework for defining additional test cases over | also provides a framework for defining additional test cases over | |||
wireless cellular/Wi-Fi networks. | wireless cellular/Wi-Fi networks. | |||
6. Acknowledgements | 6. IANA Considerations | |||
We would like to thank Tomas Frankkila, Magnus Westerlund, Kristofer | This memo includes no request to IANA. | |||
Sandlund for their valuable comments while writing this draft. | ||||
7. IANA Considerations | 7. Security Considerations | |||
This memo includes no request to IANA. | The security considerations in [I-D.ietf-rmcat-eval-criteria] and the | |||
relevant congestion control algorithms apply. The principles for | ||||
congestion control are described in [RFC2914], and in particular any | ||||
new method MUST implement safeguards to avoid congestion collapse of | ||||
the Internet. | ||||
8. Security Considerations | The evaluation of the test cases are intended to be run in a | |||
controlled lab environment. Hence, the applications, simulators and | ||||
network nodes ought to be well-behaved and should not impact the | ||||
desired results. It is important to take appropriate caution to | ||||
avoid leaking non-responsive traffic from unproven congestion | ||||
avoidance techniques onto the open Internet. | ||||
Security issues have not been discussed in this memo. | 8. Acknowledgements | |||
We would like to thank Tomas Frankkila, Magnus Westerlund, Kristofer | ||||
Sandlund for their valuable comments while writing this draft. | ||||
9. References | 9. References | |||
9.1. Normative References | 9.1. Normative References | |||
[Deployment] | [Deployment] | |||
TS 25.814, 3GPP., "Physical layer aspects for evolved | TS 25.814, 3GPP., "Physical layer aspects for evolved | |||
Universal Terrestrial Radio Access (UTRA)", October 2006, | Universal Terrestrial Radio Access (UTRA)", October 2006, | |||
<http://www.3gpp.org/ftp/specs/ | <http://www.3gpp.org/ftp/specs/ | |||
archive/25_series/25.814/25814-710.zip>. | archive/25_series/25.814/25814-710.zip>. | |||
skipping to change at page 19, line 43 ¶ | skipping to change at page 20, line 8 ¶ | |||
[HO-UMTS-3GPP] | [HO-UMTS-3GPP] | |||
TS 25.331, 3GPP., "Radio Resource Control (RRC); Protocol | TS 25.331, 3GPP., "Radio Resource Control (RRC); Protocol | |||
specification", December 2011, | specification", December 2011, | |||
<http://www.3gpp.org/ftp/specs/ | <http://www.3gpp.org/ftp/specs/ | |||
archive/25_series/25.331/25331-990.zip>. | archive/25_series/25.331/25331-990.zip>. | |||
[I-D.ietf-rmcat-eval-criteria] | [I-D.ietf-rmcat-eval-criteria] | |||
Singh, V., Ott, J., and S. Holmer, "Evaluating Congestion | Singh, V., Ott, J., and S. Holmer, "Evaluating Congestion | |||
Control for Interactive Real-time Media", draft-ietf- | Control for Interactive Real-time Media", draft-ietf- | |||
rmcat-eval-criteria-07 (work in progress), May 2018. | rmcat-eval-criteria-08 (work in progress), November 2018. | |||
[NS3WiFi] "Wi-Fi Channel Model in NS3 Simulator", | [NS3WiFi] "Wi-Fi Channel Model in NS3 Simulator", | |||
<https://www.nsnam.org/doxygen/ | <https://www.nsnam.org/doxygen/ | |||
classns3_1_1_yans_wifi_channel.html>. | classns3_1_1_yans_wifi_channel.html>. | |||
[QoS-3GPP] | [QoS-3GPP] | |||
TS 23.203, 3GPP., "Policy and charging control | TS 23.203, 3GPP., "Policy and charging control | |||
architecture", June 2011, <http://www.3gpp.org/ftp/specs/ | architecture", June 2011, <http://www.3gpp.org/ftp/specs/ | |||
archive/23_series/23.203/23203-990.zip>. | archive/23_series/23.203/23203-990.zip>. | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, | Requirement Levels", BCP 14, RFC 2119, | |||
DOI 10.17487/RFC2119, March 1997, | DOI 10.17487/RFC2119, March 1997, | |||
<https://www.rfc-editor.org/info/rfc2119>. | <https://www.rfc-editor.org/info/rfc2119>. | |||
[RFC2914] Floyd, S., "Congestion Control Principles", BCP 41, | ||||
RFC 2914, DOI 10.17487/RFC2914, September 2000, | ||||
<https://www.rfc-editor.org/info/rfc2914>. | ||||
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
9.2. Informative References | 9.2. Informative References | |||
[I-D.ietf-rmcat-cc-requirements] | [I-D.ietf-rmcat-cc-requirements] | |||
Jesup, R. and Z. Sarker, "Congestion Control Requirements | Jesup, R. and Z. Sarker, "Congestion Control Requirements | |||
for Interactive Real-Time Media", draft-ietf-rmcat-cc- | for Interactive Real-Time Media", draft-ietf-rmcat-cc- | |||
requirements-09 (work in progress), December 2014. | requirements-09 (work in progress), December 2014. | |||
[I-D.ietf-rmcat-eval-test] | [I-D.ietf-rmcat-eval-test] | |||
Sarker, Z., Singh, V., Zhu, X., and M. Ramalho, "Test | Sarker, Z., Singh, V., Zhu, X., and M. Ramalho, "Test | |||
Cases for Evaluating RMCAT Proposals", draft-ietf-rmcat- | Cases for Evaluating RMCAT Proposals", draft-ietf-rmcat- | |||
eval-test-06 (work in progress), June 2018. | eval-test-08 (work in progress), November 2018. | |||
[IEEE802.11] | [IEEE802.11] | |||
"Standard for Information technology--Telecommunications | "Standard for Information technology--Telecommunications | |||
and information exchange between systems Local and | and information exchange between systems Local and | |||
metropolitan area networks--Specific requirements Part 11: | metropolitan area networks--Specific requirements Part 11: | |||
Wireless LAN Medium Access Control (MAC) and Physical | Wireless LAN Medium Access Control (MAC) and Physical | |||
Layer (PHY) Specifications", 2012. | Layer (PHY) Specifications", 2012. | |||
[LTE-simulator] | [LTE-simulator] | |||
"NS-3, A discrete-Event Network Simulator", | "NS-3, A discrete-Event Network Simulator", | |||
End of changes. 16 change blocks. | ||||
24 lines changed or deleted | 40 lines changed or added | |||
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |