Guidelines for Internet Congestion Control at Endpoints
draft-fairhurst-tsvwg-cc-02
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Gorry Fairhurst
|
|
Last updated |
|
2019-07-26
(latest revision 2019-07-05)
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force G. Fairhurst
Internet-Draft University of Aberdeen
Intended status: Standards Track July 26, 2019
Expires: January 27, 2020
Guidelines for Internet Congestion Control at Endpoints
draft-fairhurst-tsvwg-cc-02
Abstract
This document provides guidance on the design of methods to avoid
congestion collapse and to provide congestion control.
Recommendations and requirements on this topic are distributed across
many documents in the RFC series. This therefore seeks to gather and
consolidate these recommendations. This is intended to provide input
to the design of new congestion control methods in protocols, such as
IETF QUIC.
The present document is for discussion and comment by the IETF.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 27, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
Fairhurst Expires January 27, 2020 [Page 1]
Internet-Draft CC Guidelines July 2019
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Principles of Congestion Control . . . . . . . . . . . . . . 3
3.1. A Diversity of Path Characteristics . . . . . . . . . . . 3
3.2. Flow Multiplexing and Congestion . . . . . . . . . . . . 4
3.3. Avoiding Congestion Collapse . . . . . . . . . . . . . . 5
4. Guidelines for Performing Congestion Control . . . . . . . . 6
4.1. Connection Initialization . . . . . . . . . . . . . . . . 6
4.2. Using Path Capacity . . . . . . . . . . . . . . . . . . . 8
4.3. Timers and Retransmission . . . . . . . . . . . . . . . . 9
4.4. Responding to Potential Congestion . . . . . . . . . . . 10
4.5. Using More Capacity . . . . . . . . . . . . . . . . . . . 12
4.6. Network Signals . . . . . . . . . . . . . . . . . . . . . 13
4.7. Protection of Protocol Mechanisms . . . . . . . . . . . . 13
5. IETF Guidelines on Evaluation of Congestion Control . . . . . 13
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
9.1. Normative References . . . . . . . . . . . . . . . . . . 14
9.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Revision Notes . . . . . . . . . . . . . . . . . . . 17
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
The IETF has specified Internet transports (e.g., TCP [ID.ietf-tcpm-
rfc793bis], UDP [RFC0768], UDP-Lite [RFC3828], SCTP [RFC4960], and
DCCP [RFC4340]) as well as protocols layered on top of these
transports (e.g., RTP, QUIC [I-D.ietf-quic-transport], SCTP/UDP
[RFC6951], DCCP/UDP) and transports that work directly over the IP
network layer. These transports are implemented in endpoints
(Internet hosts or routers acting as endpoints) and are designed to
detect and react to network congestion.
Recommendations and requirements on this topic are distributed across
many documents in the RFC series. This document therefore seeks to
gather and consolidate these recommendations. This is intended to
provide input to the design of new congestion control methods in
protocols.
Fairhurst Expires January 27, 2020 [Page 2]
Show full document text