| Number | Files | Title | Authors | Date | More Info | Status |
|---|---|---|---|---|---|---|
| RFC 3819,BCP 89 | ASCII,PDF | Advice for Internet Subnetwork Designers | P. Karn, Ed., C. Bormann, G. Fairhurst, D. Grossman, R. Ludwig, J. Mahdavi, G. Montenegro, J. Touch, L. Wood | July 2004 | Updated byRFC 9599,Errata | Best Current Practice |
| RFC 9599,BCP 89 | ASCII,PDF | Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP | B. Briscoe, J. Kaippallimalil | August 2024 | UpdatesRFC 3819 | Best Current Practice |
This document provides advice to the designers of digital communication equipment, link-layer protocols, and packet-switched local networks (collectively referred to as subnetworks), who wish to support the Internet protocols but may be unfamiliar with the Internet architecture and the implications of their design choices on the performance and efficiency of the Internet. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
The purpose of this document is to guide the design of congestionnotification in any lower-layer or tunnelling protocol thatencapsulates IP. The aim is for explicit congestion signals topropagate consistently from lower-layer protocols into IP. Then, theIP internetwork layer can act as a portability layer to carrycongestion notification from non-IP-aware congested nodes up to thetransport layer (L4). Specifications that follow these guidelines,whether produced by the IETF or other standards bodies, shouldassure interworking among IP-layer and lower-layer congestionnotification mechanisms. This document is included in BCP 89 andupdates the single paragraph of advice to subnetwork designers aboutExplicit Congestion Notification (ECN) in Section 13 of RFC 3819 byreplacing it with a reference to this document.
For the definition ofStatus,seeRFC 2026.
For the definition ofStream, seeRFC 8729.