Explicit Congestion Notification (ECN) is an extension to the Internet Protocol and to the Transmission Control Protocol and is defined in RFC 3168 (2001). ECN allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that is only used when both endpoints support it and are willing to use it. It is only effective when supported by the underlying network.
Conventionally, TCP/IP networks signal congestion by dropping packets. When ECN is successfully negotiated, an ECN-aware router may set a mark in the IP header instead of dropping a packet in order to signal impending congestion. The receiver of the packet echoes the congestion indication to the sender, which reduces its transmission rate as though it detected a dropped packet.
Rather than responding properly or ignoring the bits, some outdated or buggy network equipment drop packets which have ECN bits set.
| Internet protocols |
|---|
| Application layer |
|
| Transport layer |
|
| Routing protocols * |
|
| Internet layer |
|
| Link layer |
|
| * Not a layer. A routing protocol belongs either to application or network layer. |
Read more about Explicit Congestion Notification: Operation, Effects On Performance, Implementations
Famous quotes containing the words explicit and/or congestion:
“I think “taste” is a social concept and not an artistic one. I’m willing to show good taste, if I can, in somebody else’s living room, but our reading life is too short for a writer to be in any way polite. Since his words enter into another’s brain in silence and intimacy, he should be as honest and explicit as we are with ourselves.”
—John Updike (b. 1932)
“In Western Europe people perish from the congestion and stifling closeness, but with us it is from the spaciousness.... The expanses are so great that the little man hasn’t the resources to orient himself.... This is what I think about Russian suicides.”
—Anton Pavlovich Chekhov (1860–1904)