Incomputer networking, thelink layer is the lowestlayer in theInternet protocol suite, the networking architecture of theInternet. The link layer is the group of methods andcommunications protocols confined to the link that a host is physically connected to. The link is the physical and logical network component used to interconnecthosts ornodes in the network, and alink protocol is a suite of methods and standards that operate only between adjacent network nodes of anetwork segment.

Despite the different semantics of layering between theInternet protocol suite andOSI model, the link layer is sometimes described as a combination of the OSI'sdata link layer (layer 2) andphysical layer (layer 1).

The link layer is described inRFC 1122 andRFC 1123. RFC 1122 considers local area network protocols such asEthernet and otherIEEE 802 networks (e.g.Wi-Fi), and framing protocols such asPoint-to-Point Protocol (PPP) to belong to the link layer.

Local area networking standards such asEthernet andIEEE 802.3 specifications use terminology from the seven-layerOSI model rather than the TCP/IP model. The TCP/IP model, in general, does not consider physical specifications; rather, it assumes a working network infrastructure that can deliver media-level frames on the link. Therefore, RFC 1122 and RFC 1123, the definition of the TCP/IP model, do not discuss hardware issues and physicaldata transmission and set no standards for those aspects. Some textbook authors have supported the interpretation that physical data transmission aspects are part of the link layer.^[1][2] Others assumed that physical data transmission standards are not considered communication protocols, and are not part of the TCP/IP model.^[3][4] These authors assume a hardware layer or physical layer below the link layer, and several of them adopt the OSI termdata link layer instead of link layer in a modified description of layering. In the predecessor to the TCP/IP model, theARPAnet Reference Model (RFC 908, 1982), aspects of the link layer are referred to by several poorly defined terms, such asnetwork-access layer,network-access protocol, as well asnetwork layer, while the next higher layer is calledinternetwork layer. In some modern textbooks,network-interface layer,host-to-network layer andnetwork-access layer occur as synonyms either to the link layer or the data link layer, often including the physical layer.

The link layer in the TCP/IP model is a descriptive realm of networking protocols that operate only on the local network segment (link) that a host is connected to. Such protocol packets are not routed to other networks. The link layer includes protocols that manage communication and data framing between devices on the same local network segment, depending on the specific link technology in use.

The core protocols specified by theInternet Engineering Task Force (IETF) in this layer are theAddress Resolution Protocol (ARP), theReverse Address Resolution Protocol (RARP), and theNeighbor Discovery Protocol (NDP), which is a facility delivering similar functionality as ARP forIPv6.

The link layer of the TCP/IP model is often compared directly with the combination of the data link layer and thephysical layer in theOpen Systems Interconnection(OSI) protocol stack. Although they are congruent to some degree in technical coverage of protocols, they are not identical. The link layer in TCP/IP is still wider in scope and, in principle, a different concept and terminology of classification. This may be observed when certain protocols, such as ARP, which is confined to the link layer in the TCP/IP model, are often said to fit between OSI's data link layer and the network layer. In general, direct or strict comparisons should be avoided because the layering in TCP/IP is not a principal design criterion and in general, is considered to be "harmful" (RFC 3439).

Another term sometimes encountered,network access layer, tries to suggest the closeness of this layer to the physical network. However, this use is misleading and non-standard, since the link layer implies functions that are wider in scope than just network access. Important link-layer protocols are used to probe the topology of the local network and discover routers and neighboring hosts, i.e., functions that go well beyond network access.

• R. Coltun; D. Ferguson; J. Moy (July 2008). A. Lindem (ed.).OSPF for IPv6.IETF Network Working Group.doi:10.17487/RFC5340.RFC5340.Proposed Standard. ObsoletesRFC 2740. Updated byRFC 6845,6860,8362,7503 and9454
• R. Braden, ed. (October 1989).Requirements for Internet Hosts -- Communication Layers. Network Working Group.doi:10.17487/RFC1122. STD 3. RFC1122.Internet Standard 3. Updated byRFC 1349,4379,5884,6093,6298,6633,6864,8029 and9293.
• R. Braden, ed. (October 1989).Requirements for Internet Hosts -- Application and Support. Network Working Group.doi:10.17487/RFC1123. STD 3. RFC1123.Internet Standard 3. Updated byRFC 1349,2181,5321,5966 and7766.
• J. Postel;J. Reynolds (February 1988).A Standard for the Transmission of IP Datagrams over IEEE 802 Networks. Network Working Group.doi:10.17487/RFC1042. STD 43. RFC1042.Internet Standard 43. ObsoletesRFC 948.
• C. Hornig (April 1984).A Standard for the Transmission of IP Datagrams over Ethernet Networks. Network Working Group.doi:10.17487/RFC0894. STD 41. RFC894.Internet Standard 41.
• S. J. Leffler; M. J. Karels (April 1984).Trailer Encapsulations. Network Working Group.doi:10.17487/RFC0893.RFC893.Status Unknown.
• David C. Plummer (November 1982).An Ethernet Address Resolution Protocol. Network Working Group.doi:10.17487/RFC0826. STD 37. RFC826.Internet Standard 37. Updated byRFC 5227 and5494.

• Carrier-sense multiple access
• Carrier-sense multiple access with collision detection
• Network interface layer security

Wikiversity has learning resources about Link layer

• IEEE 802 Standards

• Internet Protocol
• Internet Standards
• Link protocols

• Articles with short description
• Short description matches Wikidata