ANONYMOUS wrote In practice the situation is blurred because the PL and DLL are combined in a Media Access Control (MAC) Layer, such as a single Ethernet interface card. If taken too literally - that the PL is just the wire itself, the scene where e...

ANONYMOUS wrote Discarding DATA will result in it, eventually, being re-transmitted, but not for the longest (anticipated) time. During the period of time, we hope that the congestion will 'die' down while the sender waits for the ACK (which will now...

Lecture 2 states " RX Monitors (only detects) transmission errors" as a responsibility of the physical layer. How does the physical layer detect errors? Are detection techniques such as hamming, parity, crc etc not a function of the DLL? Could I als...

When choosing the best candidates for removal via load shedding, why is it that we discard DATA instead of ACKs, as per the lecture notes? Wouldn't it be easier to retransmit just a single bit for an ACK or is it to do with the idea that the ACK is ne...

ANONYMOUS wrote Hello, yes, you are correct. I have corrected the last sentence on each of page 20 and page 21. (There seems to have been some poor cut-and-paste going on there - I wonder for how many years it went un-noticed...?) Thanks.

I think the statement is pointing out that even though an application (a node) is generating bursty traffic. Because this traffic is being fed into the leaky bucket algorithm, it doesn't saturate the network as the leaky bucket only permits a specifi...

Hi, i am hoping to get some clarification on this statement from pg. 20 of Wk. 5 lecture "The leaky bucket algorithm enables an application to generate bursty traffic (high volume, for a short period) without saturating the network". I would've though...