| |
RFC 3168 (rfc3168) - The Addition of Explicit Congestion Notification (ECN |
 | | ECN as an Indication of Persistent Congestion We emphasize that a *single* packet with the CE codepoint set in an IP packet causes the transport layer to respond, in terms of congestion control, as it would to a packet drop. |
 | | When ECN usage is allowed in the outer IP header, the ECT codepoint is set in the outer header for ECN-capable connections and congestion notifications (indicated by the CE codepoint) from such connections are propagated to the inner header at tunnel egress. |
 | | The ECN nonce allows the development of mechanisms for the sender to probabilistically verify that network elements are not erasing the CE codepoint, and that data receivers are properly reporting to the sender the receipt of packets with the CE codepoint set. |
| www.faqs.org /rfcs/rfc3168.html (19407 words) |