[Back to Lecture Notes page]
- 802.3 CSMA/CD,
- 802.4 Token Bus, and
- 802.5 Token Ring
The name Ethernet comes from "luminiferous ether", which physicists used to think is a substance by electromagnetic radiation is transmitted through. Ethernet was actually a standard by Xerox, DEC and Intel, which 802.3 was based on. 802.3 actually contains a whole lot more than what the original Ethernet specifications had. These days, the term Ethernet usually refers to IEEE 802.3.
The original standard defines a 10Mps. Today, Ethernets can support 1Mbps or 100Mps.
Base band refers to digital signals, and broadband refers to analog signals
We also use the category names for the special cables they use (eg. 10Base-T cables). The first number refers to the data rate in Mbps. The last character (5, 2, 1, T or F) either indicates the maximum length of the cables in hundreds of metres (so 500, 200 or 100 meters – using coaxial cables) or the type of cable, twisted pair or fiber optics.
Figure 4-18 textbook p278
With most Network Interface Cards (NIC) these days, you will see two types of plugs – one is the BNC T-junction which is like a cylinder, and the other is for RJ45 connectors which looks like telephone jacks. The RJ45 connectors are for twisted pair wires to hubs.
802.3 doesn't use normal binary representation for signaling. the problem is that if we have eg. 0 volts for bit 0, and 1 volt for bit 1, we won't be able to tell when a line is idle (0 volts) and when it is transmitting bit 0 (also 0 volts). Having two non-zero voltages for 0 and 1 (eg 1 volt for bit 0, and 2 volts for bit 1) is not a solution either since we end up with a continuously high DC (direct current) voltage value.
Figure 4-20 p280
In Manchester Encoding, we represent 0 as a change from a low voltage (-0.85 volts) to a high voltage (+0.85 volts) during a certain time interval. We represent 1 as a change from a high voltage (+0.85 volts) to a low voltage (-0.85 volts). Both changes results in a DC value of 0 volts, which is ideal.
Note that this is a physical layer specification. It deals with using the voltage of a line to represent 0's and 1's. IEEE 802 specifications include physical layer issues as well as DLL services.
Figure 4-21 p281
Frames with the broadcast address goes to all stations on the LAN. Frames with multicast addresses goes to only a group of stations in the LAN. One station can belong to different multicast groups.
This is to prevent the whole frame from being sent out before the station manages to detect a collision.
- If station detects a collision, it selects randomly whether to back off 0 (ie, retransmit immediately) or 1 time slot.
- On the second time, if it again detects a collision, it selects randomly to back off 0, 1, 2, or 3 time slots.
- On the third time, if it again detects a collision, it selects randomly to back off 0, 1, 2, 3, 4 5, 6, or 7 time slots.
- On the nth iteration, it selects between 0-2n -1 time slots to back off.
- This keeps goes, until the maximum of reaches 1023 time slots. Then it keeps selecting between 0-1023 time slots to back off every time there is a collision.
- Although extremely unlikely, it is possible that a station can wait forever to send a frame.
Figure 4-23 p285
Figure 4-24 p286 shows an example switch.
In this example, we have a switch with 4 plug-in cards- the vertical slots. Each plug-in card contains connectors to one particular type of NIC (eg. one plug-in card might be for 10Base-T, another plug-in card for 100Base-T). So different stations with different NICs will connect up to the appropriate plug-in card on this switch.
When a switch gets a frame from one particular connector on one particular plug-in card. It determines whether the frame is meant for another connector on the same card. If it is, it sends it out on that connector. If not, it sends (switches) it to another plug-in card through a high-speed backplane (not shown in the figure - the backplane connects all the plug-in cards in the switch).
In normal 802.3 set-up, all stations contend during a certain contention period - we refer to this as having one collision domain. In a switch, we can restrict the contention to only stations connected to one plug-in card (in which case we say that each plug-in card has its own collision domain), or the plug-in card can buffer up all incoming frames to transmit later (in which case EACH STATION has it's own collision domain, which means NO COLLISIONS HAPPEN).
- Worst-case delay is unbounded
Although highly unlikely, it is possible based on the binary exponential back-off algorithm that a station will wait infinitely long to send a frame
- No mechanism for priority
We can't specify which frames are more important, and should therefore be transmitted first when a channel is seized.
Very important for time-critical frames like those containing voice or video.
Figure 4-26 Tanenbaum textbook p289
Since the network is a broadcast network, every station receive all frames, including the token frames. So the token passing doesn't have to follow the physical layout of the stations. Eg. in figure 4-25, we can have an arbitrary logical ring order of 11, 20, 13, 17, 7.
Each station has a fixed time to transmit all frames - this ensures that there is a limit to the worst-delay for all stations.
If not all the frames of a station are transmitted during that fixed time, it will have to leave it for the next time the token comes around. The use of priority field ensures that the more important frames are guaranteed to be sent first.
See Figure 4-27 p290.
Figure 4-28 p293
Note here that unlike the analog carrier sense protocols we discussed in CSMA/CD and 802.3 and 802.4 (where every station detects the bits AT THE SAME TIME), in Token Ring the bits are passed from one ring interface to the next. Any particular bit would be only located at one particular station at any single time.
The first bit of a token must not have come back to the same interface before it transmit out the last bit.
Must also consider when the network starts to lose machines (eg. workstations with interfaces being switched off at the end of the day), there will be less 1-bit delays.
Figure 4-29 p295
Can use relays to test the performance of individual stations, to find faulty stations or line segments.
This philosophy of having a central station, which so much of the network depends on, is completely different to 802.4. The 802.4 guards very heavily against crashes, and so will not depend on a particular station. This approach is mainly due to the fact that 802.4 was designed for computers controlling factory production lines, where a crash can incur very heavy damages and costs.
Having this LLC means that the protocols on the network layer can use any of the 802 protocols in the same way.
Figure 4-33 p304
[Back to Lecture Notes page]