Parameter value/LAN
Max. collision domain DTE to
DTE
Max. collision domain with repeater Slot time Interframe Gap AttemptLimit BackoffLimit JamSize MaxFrameSize MinFrameSize
BurstLimit
10Base | 100Base | | 1000Base |
| | | |
100 meters | 100 meters for UTP | | 100 meters for UTP |
412 meters for fiber | | 316 meters for fiber |
| |
| | | |
2500 meters | 205 meters | | 200 meters |
| | | |
512 bit times | 512 bit times | | 512 bit times |
9.6us | 0.96us | | 0.096us |
16 | 16 | 16 |
10 | 10 | 10 |
32 bits | 32 bits | | 32 bits |
1518 | 1518 | 1518 |
64 | 64 | 64 |
Not applicable | Not applicable | | 65536 bits |
Table 3-4 Ethernet parameters for half duplex mode
In full-duplex operation mode, both transmitting and receiving frames are processed simultaneously. This doubles the total bandwidth. Full duplex is much easier than half duplex because it does not involve media contention, collision, retransmission schedule, padding bits for short frame. The rest functions follow the specification of IEEE802.3. For example, it must meet the requirement of minimum inter-frame gap between successive frames and frame format the same as that in the half-duplex operation.
Because no collision will happen in full-duplex operation, for sure, there is no mechanism to tell all the involved devices. What will it be if receiving device is busy and a frame is coming at the same time? Can it use “backpressure” to tell the source device? A function flow control is introduced in the full-duplex operation.
Publication date: March, 2007
Revision A1
