Recognize retired Source Quench behavior
05Source Quench was an early congestion signal and is now deprecated.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAMSource Quench Message ↗
RFC 792 · Source Quench MessageEXAMPLE
3 / 3
03
Use the transport’s own congestion control instead of this message.
Use the transport’s own congestion control instead of this message.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 792 · Source QuenchRFC 6633 §§ 3–6
The later specification prohibits host generation and requires transports to ignore received Source Quench messages.
Read the updated RFC section ↗Do not implement the historical slowdown behavior as present-day guidance.
- Do not implement the historical slowdown behavior as present-day guidance.
- RFC 6633 says hosts must not send Source Quench and transport protocols must ignore received messages.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy