RFC 6633: Deprecation of ICMP Source Quench Messages
In plain English — editorial summary, not part of the RFC
This document formally deprecates the use of ICMP Source Quench messages by transport protocols, formally updating RFC 792, RFC 1122, and RFC 1812. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6633
- Published
- May 2012
- Authors
- F. Gont
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 8084Network Transport Circuit BreakersCurrent
March 2017
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 6679Explicit Congestion Notification (ECN) for RTP over UDPUpdated
August 2012
- RFC 7560Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) FeedbackCurrent
August 2015
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?