RFC 896: Congestion Control in IP/TCP Internetworks

This memo discusses some aspects of congestion control in IP/TCP Internetworks. It is intended to stimulate thought and further discussion of this topic.…

Read RFC 896 on the RFC Editor

Incoming relationships (28 related RFCs)

Obsoleted by, Normatively referenced by — RFC 7805: Moving Outdated TCP Extensions and TCP-Related Documents to Historic or Informational Status
Normatively referenced by — RFC 3539: Authentication, Authorization and Accounting (AAA) Transport Profile
Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Informatively referenced by — RFC 1122: Requirements for Internet Hosts - Communication Layers
Informatively referenced by — RFC 1812: Requirements for IP Version 4 Routers
Informatively referenced by — RFC 1323: TCP Extensions for High Performance
Informatively referenced by — RFC 1144: Compressing TCP/IP Headers for Low-Speed Serial Links
Informatively referenced by — RFC 9293: Transmission Control Protocol (TCP)
Informatively referenced by — RFC 7567: IETF Recommendations Regarding Active Queue Management
Informatively referenced by — RFC 1072: TCP extensions for long-delay paths
Informatively referenced by — RFC 5044: Marker PDU Aligned Framing for TCP Specification
Informatively referenced by — RFC 3714: IAB Concerns Regarding Congestion Control for Voice Traffic in the Internet
Informatively referenced by — RFC 2525: Known TCP Implementation Problems
Informatively referenced by — RFC 4614: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Informatively referenced by — RFC 4689: Terminology for Benchmarking Network-layer Traffic Control Mechanisms
Informatively referenced by — RFC 1011: Official Internet protocols
Informatively referenced by — RFC 1016: Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID)
Informatively referenced by — RFC 1254: Gateway Congestion Control Survey
Informatively referenced by — RFC 5682: Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
Informatively referenced by — RFC 4138: Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
Informatively referenced by — RFC 4653: Improving the Robustness of TCP to Non-Congestion Events
Informatively referenced by — RFC 7560: Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) Feedback
Informatively referenced by — RFC 4172: iFCP - A Protocol for Internet Fibre Channel Storage Networking
Informatively referenced by — RFC 5290: Comments on the Usefulness of Simple Best-Effort Traffic
Informatively referenced by — RFC 8289: Controlled Delay Active Queue Management
Informatively referenced by — RFC 961: Official ARPA-Internet protocols
Informatively referenced by — RFC 991: Official ARPA-Internet protocols
Informatively referenced by — RFC 2556: OSI connectionless transport services on top of UDP Applicability Statement for Historic Status