Data-Link Layer
TCP/IP is a modular protocol suite. The protocols used to implement it are implemented on different hardware platforms. Each layer has its own terminology and data structure. TCP/IP can be implemented on top of virtually any link-layer technology. Virtual private networks and networking tunnels are examples of virtual link layers. A good understanding of how each layer interacts with each other is essential for effective network communication. The Internet layer of TCP/IP Protocol Link layers and their protocols will improve your understanding of the protocol suite[4].
The Data-Link Layer is the lowest layer in the OSI model of the network stack. It is responsible for addressing. Every device on a network has a unique identifier called a hardware address or MAC address. The data-link layer protocols make sure that only data intended for a particular machine gets to that device. In addition, it handles errors that occur at lower levels of the network stack. The data-link layer uses a cyclic redundancy check to verify that data has been received by the right node.
The Data-Link Layer protocols communicate with the physical layer through a wire or transceiver. There may be multiple interfaces for an information system, and each interface is assigned a specific physical layer. The Data-Link Layer protocol converts the signal into digital data. It also controls the physical interface of the device. This layer allows computers to communicate with one another. It’s important to note that the physical interface is one of the lowest layers[3].
The Data-Link Layer in TCP/IP is responsible for encapsulating and delivering network traffic. It also uses MAC addresses to identify the source and destination of data packets. Its transceiver drives network signals, and encodes bits in frames. When it’s time to send and receive data, the Data-Link Layer is responsible for sending and receiving data packets at the right speeds.The Data-Link Layer in TCP/IP protocol links all the different layers together. The Data-Link layer creates frames and adds MAC addresses. This information is required for all kinds of frames, including those that use Ethernet. If you’re using a Token Ring network, Ethernet format packets won’t be understood. That’s why the Data-Link Layer is essential.
The protocol set for the link layer is defined in RFC 1122 and RFC 1123. These standards classify the protocols that operate on the link layer as local area network protocols and IEEE 802 networks. They also describe the framing protocol. However, the role of these protocols varies, depending on how they are used and where they are used. Here are some examples of how they are used.
The Protocols of the Link Layer
A data link is an additional layer of the Internet protocol stack. It is responsible for gathering sets of bits and passing them as packets. This layer also ensures that these packets reach their destinations on time. Errors introduced during physical layer transmission are handled by the data link layer. Consequently, there are many advantages to using a data link. Here are some of the benefits of using a data link[10]
The Data Link layer provides reliability and tools for making and maintaining data link connections. It transforms data bits into frames and handles errors while transmitting them. It provides an interface for the Network Layer, which is the third layer in the OSI reference model. Depending on the protocol, different fields are used. Here are the general types of frame header information. Once you’re familiar with these types of packets, you’re ready to build your own data link network [4].
Different implementations of Data Link layer protocols use different methods for media access control. Different layers are responsible for balancing media access control and network overhead. For example, in the Ethernet protocol, a node may share a frame with another node. This balancing is crucial for data transmission, and it is the basis for Ethernet. In a network with multiple nodes, there will be more than one Data Link layer, and each one will have its own unique media access control protocols[7]
This article will discuss the differences between the TCP/IP model and the OSI model for encapsulating network-layer protocols. Encapsulation encloses data before it is sent over a network and decapsulates it after it is received. The difference between encapsulation and decapsulation lies in how information is added to data. Protocol information is added to data before it is sent over a network, referred to as headers, and removed from it at the destination. [5]
The Data link layer receives a frame from a transmitting device and converts it to a digital signal called a Protocol Data Unit (PDU). This process is called de-encapsulation, where additional information is removed from the sending computer. After the data is de-encapsulated, it is sent from the receiving computer to the upper layer. The Physical layer then de-encapsulates the frames and hands them off to the Data link layer[9]
In theory, local network encapsulates network layer protocols. However, the concept of encapsulation in local networks will remain the same. Although the protocols will be different, the basic underlying concept remains unchanged. The main reason for the difference is that local network encapsulates network-layer protocols. If your network supports local network, you can easily use it[2].
Data Link layer is a Connecting Layer
A common problem associated with a wireless network is packet loss, so protocols in the link layer must detect and correct these errors to ensure the reliability of data transmission. For example, an error can be detected by noting that a transmitting station has occupied a particular channel, but is not able to receive the transmitted data. In such a case, the transmitter will notify the receiver and re-send the message. As a result, the delivery time may vary, due to the extra delay to detect lost data [3].
The protocols of the link layer also have the task of dealing with retransmissions. These retransmissions are necessary to maintain reliability, but add a considerable delay to the delivery, which may be unacceptable for applications that need to play back content. Loss-tolerant applications can adapt to this situation and handle the unreliable media streams without incurring any loss[8]
The data link layer controls access to the medium, divides Bitdatenstroms into blocks, and adds checksums to channel coding. The receiver uses these messages to detect and correct bad blocks. The uppermost sublayer specifies the control mechanisms used for data exchange. This layer can also specify the number of nodes that can access the media, and at what time.
Data Link layer protocols describe the techniques for exchanging frames on and off local media. Various methods are used for different types of media. For example, if a network is composed of many different types of media, the protocols used to control access to those media will need to differ. The protocols of the link layer define how different types of media are shared by different nodes and how these nodes can control access to the media[1].
The protocol used in the data link layer is called media access control. It specifies the methods of data exchange and determines which stations can access media. It also provides information on the number of people allowed to access media at any one time. In addition, it specifies the protocols used for flow control and error notification. Generally, the protocols of the link layer operate within the scope of local network for media access control[6]
The data-oriented methods of media access control are based on the logical topology of the network. Non-shared media access protocols do not require control prior to placing frames onto the media. As the protocols of the link layer do not record the turn-of-access of each device, they tend to be less robust. Furthermore, they don’t scale well under heavy media use. They further diminish throughput as the number of nodes increases [2].
References
[1]S. Zeadally, A. Das and N. Sklavos, “Cryptographic technologies and protocol standards for Internet of Things”, Internet of Things, vol. 14, p. 100075, 2021. Available: 10.1016/j.iot.2019.100075.
[2]J. Rut and M. Bartoszuk, “Visualization techniques for production processes using the communication TCP/IP protocol,” Mechanik, no. 11, pp. 1732–1733, 2016.
[3]K. Zheng, “Enabling “Protocol Routing”: Revisiting Transport Layer Protocol Design in Internet Communications”, IEEE Internet Computing, vol. 21, no. 6, pp. 52-57, 2017. Available: 10.1109/mic.2017.4180845.
[4]”Acknowledgment to Reviewers of Future Internet in 2020″, Future Internet, vol. 13, no. 2, p. 28, 2021. Available: 10.3390/fi13020028.
[5]H. Ishii, “ISDN user-network interface management protocol,” IEEE Network, vol. 3, no. 5, pp. 12–16, Sep. 1989, doi: 10.1109/65.35995.
[6]“Acknowledgement to Reviewers of Future Internet in 2018,” Future Internet, vol. 11, no. 1, p. 14, Jan. 2019, doi: 10.3390/fi11010014.
[7]W. Jiang, “Internet traffic matrix prediction with convolutional LSTM neural network,” Internet Technology Letters, Sep. 2021, doi: 10.1002/itl2.322.
[8]K. S. Reddy, M. Balaraju, and Ramananaik, “Development of new optimal cloud computing mechanism for data exchange based on link selectivity, link reliability and data exchange efficiency,” International Journal of Engineering & Technology, vol. 7, no. 1.2, p. 199, Dec. 2017, doi: 10.14419/ijet.v7i1.2.9066.
[9]“Analytical Review of Error Control in Data Link Layer,” International Journal of Advances in Scientific Research and Engineering, 2018, doi: 10.7324/ijasre.2018.32674.
[10]S. Khosroazad, A. Abedi, and N. Neda, “Achieving maximum bit rate in a cognitive radio network with physical layer network coding,” International Journal of Communication Systems, vol. 31, no. 10, p. e3558, Apr. 2018, doi: 10.1002/dac.3558.