MAC Control Frames
Additional functionality easily integrated
Currently only
Always 64 bytes
| 8 bytes | 6 |
| 6 | 2 | 2 | 44 |
| 4 |
| |
|
|
|
|
|
|
|
|
|
|
| |
| preamble | DA |
| SA | 8808h |
| FCS |
| |||
|
|
|
|
|
|
|
|
|
|
| |
| ........... | Defines function of control frame |
|
| |||||||
| control parameter data (always filled up to 44 bytes) |
|
| ||||||||
|
|
|
|
|
|
|
|
|
|
|
|
(C) Herbert Haas | 2005/03/11 |
|
|
|
|
|
| 9 | |||
|
|
|
|
|
|
|
|
|
|
|
|
Different data rates between switches (and different performance levels) often lead to congestion conditions, full buffers, and frame drops. Traditional Ethernet flow control was only supported on
A much finer method is to send some dummy frames just before the backoff timer allows sending. This way the other station never comes to send again.
Both methods are considered as ugly and only work on half duplex lines. Therefore the MAC Control frames were specified, allowing for active flow control. Now the receiver sends this special frame, notifying the sender to be silent for N slot times.
The MAC Control frame originates in a new Ethernet
9