Which Layer Of The Osi Model Is The Data Link Layer? Layer 1 Layer 2 Layer 3 Layer 4
The Open Systems Interconnection model (OSI model) is a conceptual model that describes the universal standard of communication functions of a telecommunications system or computing system, without any regard to the system's underlying internal engineering science and specific protocol suites. Therefore, the objective is the interoperability of all diverse communication systems containing standard communication protocols, through the encapsulation and de-encapsulation of data, for all networked advice.
The model partitions the menstruation of data in a advice organisation into seven abstraction layers, to describe networked communication from the concrete implementation of transmitting $.25 beyond a communications medium to the highest-level representation of data of a distributed application. Each intermediate layer serves a class of functionality to the layer above it and is served by the layer below it. Classes of functionality are realized in all software evolution through all and whatever standardized communication protocols.
Each layer in the OSI model has its own well-defined functions, and the functions of each layer communicate and collaborate with the layers immediately to a higher place and below information technology, unless the layer does not have layers below or above. In either case, each layer of the OSI model has its ain well-defined functions that describe the bones applications for advice of all communication protocols.
The Net protocol suite has a carve up model, the layers of which are mentioned in RFC 1122 and RFC 1123. That model combines the physical and data link layers of the OSI model into a single link layer, and has a unmarried application layer for all protocols in a higher place the transport layer, as opposed to the OSI model's split up application, presentation and session layers of the OSI model.
In comparison, several networking models have sought to create an intellectual framework for clarifying networking concepts and activities,[ citation needed ] simply none have been as successful as the Open Organization Interconnection (OSI) Reference Model in becoming the standard model for discussing, teaching, and learning for the networking procedures in the field of Data engineering science. Including this matter, the model likewise hands allows transparent communication through equivalent exchange of Protocol Information Units (PDU) between two parties, through what is known as Peer-to-Peer Networking (also known as peer-to-peer communication). Equally a upshot, OSI reference model has non simply become an importance slice betwixt non-professionals and professionals, but also in all networking betwixt ane or many parties, due in large function considering of its unremarkably accustomed user-friendly framework.[two]
Advice in the OSI-Model (instance with layers three to 5)
History [edit]
The OSI model started to be developed in the late 1970s to support the emergence of the diverse figurer networking methods, such as the current main method known every bit TCP/IP, that were competing for application in the large national networking efforts in the globe. In the 1980s, the model became a working production of the Open up Systems Interconnection grouping at the International Organisation for Standardization (ISO). While attempting to provide a comprehensive description of networking, the model failed to garner reliance during the design of the Internet, which is reflected in the less prescriptive Internet Protocol Suite, principally sponsored under the auspices of the Net Engineering Job Force (IETF).
In the early- and mid-1970s, networking was largely either authorities-sponsored (NPL network in the United kingdom, ARPANET in the US, CYCLADES in France) or vendor-adult with proprietary standards, such as IBM's Systems Network Architecture and Digital Equipment Corporation's DECnet. Public data networks were only just showtime to sally, and these began to use the 10.25 standard in the late 1970s.[3] [4]
The Experimental Packet Switched System in the United kingdom circa 1973–1975 identified the demand for defining higher level protocols.[3] The UK National Computing Centre publication 'Why Distributed Computing' which came from considerable research into future configurations for figurer systems,[5] resulted in the United kingdom presenting the instance for an international standards committee to cover this surface area at the ISO meeting in Sydney in March 1977.[six]
Beginning in 1977, the International Organization for Standardization (ISO) conducted a program to develop general standards and methods of networking. A similar procedure evolved at the International Telegraph and Telephone Consultative Committee (CCITT, from French: Comité Consultatif International Téléphonique et Télégraphique). Both bodies developed documents that defined similar networking models. The OSI model was first defined in raw form in Washington, DC in February 1978 by Hubert Zimmermann of France and the refined but still typhoon standard was published by the ISO in 1980.[7]
The drafters of the reference model had to fence with many competing priorities and interests. The charge per unit of technological change made it necessary to define standards that new systems could converge to rather than standardizing procedures after the fact; the reverse of the traditional arroyo to developing standards.[8] Although non a standard itself, it was a framework in which futurity standards could exist defined.[9]
In 1983, the CCITT and ISO documents were merged to form The Bones Reference Model for Open up Systems Interconnection, unremarkably referred to as the Open up Systems Interconnection Reference Model, OSI Reference Model, or simply OSI model. It was published in 1984 by both the ISO, as standard ISO 7498, and the renamed CCITT (at present chosen the Telecommunications Standardization Sector of the International Telecommunication Spousal relationship or ITU-T) every bit standard X.200.
OSI had two major components, an abstract model of networking, called the Basic Reference Model or seven-layer model, and a prepare of specific protocols. The OSI reference model was a major advance in the standardisation of network concepts. It promoted the idea of a consequent model of protocol layers, defining interoperability between network devices and software.
The concept of a seven-layer model was provided by the piece of work of Charles Bachman at Honeywell Information Systems.[10] Various aspects of OSI design evolved from experiences with the NPL network, ARPANET, CYCLADES, EIN, and the International Networking Working Group (IFIP WG6.1). In this model, a networking system was divided into layers. Within each layer, one or more than entities implement its functionality. Each entity interacted directly merely with the layer immediately below it and provided facilities for use past the layer above it.
The OSI standards documents are available from the ITU-T equally the X.200-series of recommendations.[eleven] Some of the protocol specifications were also bachelor as part of the ITU-T Ten series. The equivalent ISO and ISO/IEC standards for the OSI model were available from ISO. Not all are free of accuse.[12]
OSI was an manufacture effort, attempting to go industry participants to concur on common network standards to provide multi-vendor interoperability.[13] It was mutual for big networks to support multiple network protocol suites, with many devices unable to interoperate with other devices because of a lack of mutual protocols. For a period in the late 1980s and early 1990s, engineers, organizations and nations became polarized over the issue of which standard, the OSI model or the Cyberspace protocol suite, would result in the best and most robust computer networks.[6] [14] [15] However, while OSI developed its networking standards in the belatedly 1980s,[16] [17] TCP/IP came into widespread use on multi-vendor networks for internetworking.
The OSI model is still used as a reference for didactics and documentation;[xviii] all the same, the OSI protocols originally conceived for the model did not gain popularity. Some engineers contend the OSI reference model is nevertheless relevant to cloud computing.[19] Others say the original OSI model doesn't fit today'southward networking protocols and take suggested instead a simplified approach.[20] [21]
Definitions [edit]
Communication protocols enable an entity in ane host to collaborate with a corresponding entity at the same layer in another host. Service definitions, like the OSI Model, abstractly describe the functionality provided to an (N)-layer by an (Northward-one) layer, where Due north is one of the seven layers of protocols operating in the local host.
At each level Northward, 2 entities at the communicating devices (layer N peers) exchange protocol data units (PDUs) by means of a layer N protocol. Each PDU contains a payload, called the service data unit (SDU), along with protocol-related headers or footers.
Data processing past two communicating OSI-compatible devices proceeds as follows:
- The data to be transmitted is composed at the topmost layer of the transmitting device (layer North) into a protocol information unit (PDU).
- The PDU is passed to layer N-1, where it is known as the service data unit (SDU).
- At layer N-1 the SDU is concatenated with a header, a footer, or both, producing a layer Northward-ane PDU. It is then passed to layer N-ii.
- The process continues until reaching the lowermost level, from which the data is transmitted to the receiving device.
- At the receiving device the data is passed from the lowest to the highest layer as a series of SDUs while being successively stripped from each layer's header or footer until reaching the topmost layer, where the final of the data is consumed.
Standards documents [edit]
The OSI model was divers in ISO/IEC 7498 which consists of the following parts:
- ISO/IEC 7498-1 The Basic Model
- ISO/IEC 7498-2 Security Architecture
- ISO/IEC 7498-three Naming and addressing
- ISO/IEC 7498-four Direction framework
ISO/IEC 7498-1 is also published as ITU-T Recommendation X.200.
Layer architecture [edit]
The recommendation Ten.200 describes seven layers, labelled 1 to 7. Layer 1 is the lowest layer in this model.
| Layer | Protocol data unit (PDU) | Function[22] | ||
|---|---|---|---|---|
| Host layers | vii | Application | Information | High-level APIs, including resource sharing, remote file access |
| 6 | Presentation | Translation of data betwixt a networking service and an awarding; including grapheme encoding, data compression and encryption/decryption | ||
| 5 | Session | Managing communication sessions, i.e., continuous exchange of information in the form of multiple back-and-forth transmissions between two nodes | ||
| 4 | Transport | Segment, Datagram | Reliable transmission of information segments between points on a network, including segmentation, acknowledgement and multiplexing | |
| Media layers | 3 | Network | Parcel | Structuring and managing a multi-node network, including addressing, routing and traffic command |
| 2 | Data link | Frame | Reliable transmission of data frames between two nodes connected by a concrete layer | |
| ane | Physical | Bit, Symbol | Transmission and reception of raw bit streams over a physical medium | |
Layer 1: Physical layer [edit]
The Concrete Layer is responsible for the transmission and reception of unstructured raw data betwixt a device, such as a network interface controller, Ethernet hub, or network switch, and a physical transmission medium. It converts the digital bits into electrical, radio, or optical signals. Layer specifications define characteristics such as voltage levels, the timing of voltage changes, physical data rates, maximum transmission distances, modulation scheme, aqueduct access method and physical connectors. This includes the layout of pins, voltages, line impedance, cable specifications, bespeak timing and frequency for wireless devices. Bit rate control is washed at the physical layer and may define transmission mode as simplex, half duplex, and total duplex. The components of a physical layer tin can be described in terms of a network topology. Physical layer specifications are included in the specifications for the ubiquitous Bluetooth, Ethernet, and USB standards. An example of a less well-known physical layer specification would be for the Tin can standard.
The Concrete Layer also specifies how encoding occurs over a physical point, such as electric voltage or a lite pulse. For example, a 1 flake might exist represented on a copper wire past the transition from a 0-volt to a five-volt signal, whereas a 0 chip might exist represented by the transition from a 5-volt signal to 0-volt signal. As a result, common problems occurring at the Physical Layer are often related to the incorrect media termination, EMI or racket scrambling, and NICs and hubs that are misconfigured or do not work correctly.
Layer 2: Data link layer [edit]
The data link layer provides node-to-node data transfer—a link between two directly continued nodes. It detects and possibly corrects errors that may occur in the concrete layer. It defines the protocol to establish and end a connection betwixt ii physically connected devices. It besides defines the protocol for flow control between them.
IEEE 802 divides the data link layer into two sublayers:[23]
- Medium admission control (MAC) layer – responsible for controlling how devices in a network proceeds admission to a medium and permission to transmit information.
- Logical link command (LLC) layer – responsible for identifying and encapsulating network layer protocols, and controls mistake checking and frame synchronization.
The MAC and LLC layers of IEEE 802 networks such every bit 802.three Ethernet, 802.eleven Wi-Fi, and 802.fifteen.four ZigBee operate at the data link layer.
The Point-to-Indicate Protocol (PPP) is a data link layer protocol that can operate over several unlike physical layers, such as synchronous and asynchronous series lines.
The ITU-T G.hn standard, which provides loftier-speed local area networking over existing wires (ability lines, phone lines and coaxial cables), includes a consummate data link layer that provides both error correction and menstruation control past means of a selective-echo sliding-window protocol.
Security, specifically (authenticated) encryption, at this layer can exist applied with MACSec.
Layer 3: Network layer [edit]
The network layer provides the functional and procedural ways of transferring packets from one node to another connected in "different networks". A network is a medium to which many nodes tin be continued, on which every node has an address and which permits nodes connected to it to transfer messages to other nodes connected to it by merely providing the content of a message and the address of the destination node and letting the network discover the way to evangelize the message to the destination node, possibly routing it through intermediate nodes. If the message is likewise large to be transmitted from i node to another on the information link layer between those nodes, the network may implement message delivery past splitting the bulletin into several fragments at one node, sending the fragments independently, and reassembling the fragments at another node. It may, but does not need to, report delivery errors.
Message delivery at the network layer is not necessarily guaranteed to be reliable; a network layer protocol may provide reliable message delivery, but it need non do so.
A number of layer-direction protocols, a function defined in the management addendum, ISO 7498/4, belong to the network layer. These include routing protocols, multicast group management, network-layer information and error, and network-layer address assignment. Information technology is the function of the payload that makes these vest to the network layer, non the protocol that carries them.[24]
Layer four: Transport layer [edit]
The ship layer provides the functional and procedural means of transferring variable-length data sequences from a source host to a destination host from ane application to some other across a network, while maintaining the quality-of-service functions. Send protocols may be connection-oriented or connectionless.
This may require breaking large protocol data units or long information streams into smaller chunks called "segments", since the network layer imposes a maximum packet size called the maximum manual unit (MTU), which depends on the maximum packet size imposed by all information link layers on the network path betwixt the two hosts. The corporeality of data in a data segment must be small enough to allow for a network-layer header and a send-layer header. For case, for data beingness transferred across an Ethernet, the MTU is 1500 bytes, the minimum size of a TCP header is 20 bytes, and the minimum size of an IPv4 header is 20 bytes, and so the maximum segment size is 1500-(twenty+20) bytes, or 1460 bytes. The process of dividing data into segments is called segmentation; it is an optional function of the transport layer. Some connection-oriented transport protocols, such every bit TCP and the OSI connection-oriented ship protocol (COTP), perform segmentation and reassembly of segments on the receiving side; connectionless send protocols, such as UDP and the OSI connectionless ship protocol (CLTP), usually practise not.
The transport layer as well controls the reliability of a given link betwixt a source and destination host through flow command, error command, and acknowledgments of sequence and beingness. Some protocols are state- and connection-oriented. This means that the transport layer tin can keep track of the segments and retransmit those that fail delivery through the acquittance hand-shake system. The transport layer will also provide the acknowledgement of the successful information manual and sends the next information if no errors occurred.
Reliability, however, is not a strict requirement within the ship layer. Protocols like UDP, for case, are used in applications that are willing to accept some bundle loss, reordering, errors or duplication. Streaming media, existent-fourth dimension multiplayer games and voice over IP (VoIP) are examples of applications in which loss of packets is non normally a fatal problem.
The OSI connection-oriented transport protocol defines v classes of connection-fashion transport protocols ranging from class 0 (which is also known as TP0 and provides the fewest features) to class 4 (TP4, designed for less reliable networks, like to the Internet). Class 0 contains no mistake recovery and was designed for utilise on network layers that provide mistake-gratis connections. Class 4 is closest to TCP, although TCP contains functions, such as the graceful close, which OSI assigns to the session layer. Also, all OSI TP connection-mode protocol classes provide expedited data and preservation of tape boundaries. Detailed characteristics of TP0-4 classes are shown in the post-obit table:[25]
| Feature name | TP0 | TP1 | TP2 | TP3 | TP4 |
|---|---|---|---|---|---|
| Connexion-oriented network | Yep | Aye | Aye | Yes | Yes |
| Connectionless network | No | No | No | No | Yes |
| Concatenation and separation | No | Yes | Yes | Yes | Yes |
| Segmentation and reassembly | Yes | Yes | Yes | Yep | Yes |
| Error recovery | No | Yes | Yes | Yep | Yes |
| Reinitiate connection a | No | Yes | No | Yep | No |
| Multiplexing / demultiplexing over unmarried virtual circuit | No | No | Aye | Yes | Yes |
| Explicit flow control | No | No | Yep | Yes | Yes |
| Retransmission on timeout | No | No | No | No | Yes |
| Reliable transport service | No | Yes | No | Yes | Yes |
| a If an excessive number of PDUs are unacknowledged. | |||||
An easy fashion to visualize the transport layer is to compare it with a mail service role, which deals with the dispatch and nomenclature of mail and parcels sent. A post part inspects only the outer envelope of mail service to determine its delivery. Higher layers may have the equivalent of double envelopes, such as cryptographic presentation services that can exist read by the addressee only. Roughly speaking, tunnelling protocols operate at the transport layer, such equally carrying non-IP protocols such as IBM'south SNA or Novell's IPX over an IP network, or end-to-stop encryption with IPsec. While Generic Routing Encapsulation (GRE) might seem to be a network-layer protocol, if the encapsulation of the payload takes place only at the endpoint, GRE becomes closer to a send protocol that uses IP headers merely contains complete Layer two frames or Layer 3 packets to deliver to the endpoint. L2TP carries PPP frames inside transport segments.
Although not developed under the OSI Reference Model and not strictly befitting to the OSI definition of the transport layer, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) of the Cyberspace Protocol Suite are normally categorized every bit layer-4 protocols within OSI.
Transport Layer Security (TLS) does not strictly fit inside the model either. It contains characteristics of the transport and presentation layers.[26] [27]
Layer v: Session layer [edit]
The Session Layer creates the setup, controls the connections, and ends the teardown, between two or more than computers, which is called a "session". Since DNS and other Proper noun Resolution Protocols operate in this part of the layer, common functions of the Session Layer include user logon (establishment), proper name lookup (management), and user logoff (termination) functions. Including this thing, hallmark protocols are also congenital into about client software, such as FTP Client and NFS Client for Microsoft Networks. Therefore, the Session layer establishes, manages and terminates the connections betwixt the local and remote application. The Session Layer as well provides for full-duplex, half-duplex, or simplex operation, and establishes procedures for checkpointing, suspending, restarting, and terminating a session between two related streams of data, such equally an sound and a video steam in a web-conferencing application. Therefore, The session layer is commonly implemented explicitly in application environments that use remote procedure calls.
Layer 6: Presentation layer [edit]
The Presentation Layer establishes data formatting and data translation into a format specified by the awarding layer during the encapsulation of outgoing letters while being passed down the protocol stack, and possibly reversed during the deencapsulation of incoming messages when being passed up the protocol stack. For this very reason, outgoing messages during encapsulation are converted into a format specified by the awarding layer, while the conversation for incoming messages during deencapsulation are reversed.
The Presentation Layer handles protocol conversion, data encryption, data decryption, data pinch, data decompression, incompatibility of information representation betwixt OSs, and graphic commands. The presentation layer transforms information through the into the course that the application layer accepts, to exist sent beyond a network. Since the presentation layer converts data and graphics into a display format for the Application Layer, the Presentation Layer is sometimes called the syntax layer.[28] For this reason, the Presentation Layer negotiates the transfer of syntax construction through the Basic Encoding Rules of Abstruse Syntax Notation One (ASN.ane), with capabilities such as converting an EBCDIC-coded text file to an ASCII-coded file, or serialization of objects and other data structures from and to XML.[2]
Layer 7: Application layer [edit]
The application layer is the layer of the OSI model that is closest to the end user, which ways both the OSI Awarding Layer and the user interact directly with software awarding that implements a component of communication between the customer and server, such as File Explorer and Microsoft Word. Such awarding programs fall outside the scope of the OSI model unless they are straight integrated into the Application layer through the functions of communication, equally is the case with applications such as Web Browsers and Electronic mail Programs. Other examples of software are Microsoft Network Software for File and Printer Sharing and Unix/Linux Network File Organisation Client for admission to shared file resource.
Application-layer functions typically include file sharing, message handling, and database access, through the about mutual protocols at the application layer, known as HTTP, FTP, SMB/CIFS, TFTP, and SMTP. When identifying communication partners, the application layer determines the identity and availability of communication partners for an awarding with data to transmit. The most important distinction in the application layer is the distinction between the application-entity and the application. For case, a reservation website might have two application-entities: one using HTTP to communicate with its users, and one for a remote database protocol to tape reservations. Neither of these protocols have anything to exercise with reservations. That logic is in the awarding itself. The awarding layer has no means to make up one's mind the availability of resource in the network.[two]
Cantankerous-layer functions [edit]
Cross-layer functions are services that are not tied to a given layer, but may impact more 1 layer.[29] Some orthogonal aspects, such as management and security, involve all of the layers (Meet ITU-T X.800 Recommendation[30]). These services are aimed at improving the CIA triad—confidentiality, integrity, and availability—of the transmitted data. Cross-layer functions are the norm, in exercise, because the availability of a communication service is determined past the interaction betwixt network pattern and network management protocols.
Specific examples of cross-layer functions include the following:
- Security service (telecommunications)[xxx] as defined past ITU-T Ten.800 recommendation.
- Management functions, i.due east. functions that permit to configure, instantiate, monitor, terminate the communications of ii or more than entities: there is a specific application-layer protocol, mutual management information protocol (CMIP) and its respective service, common management data service (CMIS), they need to interact with every layer in order to deal with their instances.
- Multiprotocol Label Switching (MPLS), ATM, and X.25 are 3a protocols. OSI subdivides the Network Layer into three sublayers: 3a) Subnetwork Admission, 3b) Subnetwork Dependent Convergence and 3c) Subnetwork Independent Convergence.[31] It was designed to provide a unified information-carrying service for both excursion-based clients and parcel-switching clients which provide a datagram-based service model. It tin can be used to carry many dissimilar kinds of traffic, including IP packets, besides as native ATM, SONET, and Ethernet frames. Sometimes ane sees reference to a Layer 2.5.
- Cross MAC and PHY Scheduling is essential in wireless networks considering of the time-varying nature of wireless channels. By scheduling packet transmission only in favourable aqueduct weather condition, which requires the MAC layer to obtain channel state information from the PHY layer, network throughput can exist significantly improved and energy waste tin be avoided.[32]
Programming interfaces [edit]
Neither the OSI Reference Model, nor any OSI protocol specifications, outline any programming interfaces, other than deliberately abstract service descriptions. Protocol specifications define a methodology for communication between peers, but the software interfaces are implementation-specific.
For example, the Network Driver Interface Specification (NDIS) and Open Data-Link Interface (ODI) are interfaces between the media (layer ii) and the network protocol (layer 3).
Comparison to other networking suites [edit]
The tabular array below presents a listing of OSI layers, the original OSI protocols, and some approximate modern matches. It is very of import to notation that this correspondence is rough: the OSI model contains idiosyncrasies not establish in later systems such as the IP stack in modern Cyberspace.[21]
| Layer | OSI protocols | TCP/IP protocols | Signaling System vii[33] | AppleTalk | IPX | SNA | UMTS | Miscellaneous examples | |
|---|---|---|---|---|---|---|---|---|---|
| No. | Name | ||||||||
| 7 | Awarding |
|
|
|
|
|
|
| |
| vi | Presentation |
|
|
|
| ||||
| five | Session |
| Sockets (session establishment in TCP / RTP / PPTP) |
|
|
|
| ||
| four | Transport |
|
|
|
|
| |||
| 3 | Network |
|
|
| ATP (TokenTalk / EtherTalk) |
|
|
|
|
| ii | Data link |
|
|
|
| IEEE 802.3 framing Ethernet II framing |
|
|
|
| 1 | Concrete |
| TCP/IP stack does non intendance most the concrete medium, as long as it provides a manner to communicate octets |
|
|
| UMTS air interfaces |
| |
Comparison with TCP/IP model [edit]
The blueprint of protocols in the TCP/IP model of the Internet does not business organization itself with strict hierarchical encapsulation and layering.[38] RFC 3439 contains a section entitled "Layering considered harmful".[39] TCP/IP does recognize four broad layers of functionality which are derived from the operating scope of their contained protocols: the scope of the software application; the host-to-host send path; the internetworking range; and the scope of the direct links to other nodes on the local network.[40]
Despite using a different concept for layering than the OSI model, these layers are often compared with the OSI layering scheme in the following manner:
- The Net application layer maps to the OSI application layer, presentation layer, and most of the session layer.
- The TCP/IP transport layer maps to the graceful close function of the OSI session layer also as the OSI transport layer.
- The cyberspace layer performs functions as those in a subset of the OSI network layer.
- The link layer corresponds to the OSI information link layer and may include similar functions equally the concrete layer, as well as some protocols of the OSI's network layer.
These comparisons are based on the original seven-layer protocol model every bit divers in ISO 7498, rather than refinements in the internal system of the network layer.
The OSI protocol suite that was specified equally role of the OSI project was considered by many as too complicated and inefficient, and to a large extent unimplementable.[41] Taking the "forklift upgrade" approach to networking, it specified eliminating all existing networking protocols and replacing them at all layers of the stack. This fabricated implementation hard and was resisted by many vendors and users with significant investments in other network technologies. In addition, the protocols included so many optional features that many vendors' implementations were not interoperable.[41]
Although the OSI model is ofttimes however referenced, the Internet protocol suite has become the standard for networking. TCP/IP's pragmatic approach to reckoner networking and to contained implementations of simplified protocols made information technology a practical methodology.[41] Some protocols and specifications in the OSI stack remain in use, one instance being IS-IS, which was specified for OSI every bit ISO/IEC 10589:2002 and adapted for Internet utilise with TCP/IP as RFC 1142.
Come across also [edit]
- Mutual Management Information Service (CMIS)
- GOSIP, the (U.S.) Government Open Systems Interconnection Contour
- Hierarchical internetworking model
- Layer 8
- List of data engineering initialisms
- Management aeroplane
- Recursive Internetwork Architecture
- Service layer
Farther reading [edit]
- John Day, "Patterns in Network Architecture: A Return to Fundamentals" (Prentice Hall 2007, ISBN 978-0-13-225242-3)
- Marshall Rose, "The Open up Book" (Prentice-Hall, Englewood Cliffs, 1990)
- David M. Piscitello, A. Lyman Chapin, Open Systems Networking (Addison-Wesley, Reading, 1993)
- Andrew Due south. Tanenbaum, Computer Networks, 4th Edition, (Prentice-Hall, 2002) ISBN 0-xiii-066102-three
- Gary Dickson; Alan Lloyd (July 1992). Open Systems Interconnection/Reckoner Communications Standards and Gossip Explained. Prentice-Hall. ISBN978-0136401117.
References [edit]
- ^ "X.225 : Information technology – Open Systems Interconnection – Connection-oriented Session protocol: Protocol specification". Archived from the original on 1 February 2021. Retrieved 24 November 2021.
- ^ a b c Tomsho, Greg (2016). Guide to Networking Essentials (7th ed.). Cengage. Retrieved iii April 2022.
- ^ a b Davies, Howard; Bressan, Beatrice (26 April 2010). A History of International Inquiry Networking: The People who Made information technology Happen. John Wiley & Sons. pp. 2–3. ISBN978-3-527-32710-2.
- ^ Roberts, Dr. Lawrence G. (November 1978). "The Development of Packet Switching" (PDF). IEEE Invited Newspaper . Retrieved 26 Feb 2022.
- ^ Down, Peter John; Taylor, Frank Edward (1976). Why distributed computing?: An NCC review of potential and feel in the UK. NCC Publications. ISBN9780850121704.
- ^ a b Andrew Fifty. Russell (30 July 2013). "OSI: The Internet That Wasn't". IEEE Spectrum. Vol. l, no. 8.
- ^ "OSI The Net That Wasn't". IEEE Spectrum. March 2017.
- ^ Sunshine, Carl A. (1989). Computer Network Architectures and Protocols. Springer Science & Business Media. p. 35. ISBN978-1-4613-0809-6.
- ^ Hasman, A. (1995). Education and Training in Health Informatics in Europe: Country of the Art, Guidelines, Applications. IOS Press. p. 251. ISBN978-90-5199-234-ii.
- ^ J. A. N. Lee. "Computer Pioneers by J. A. Due north. Lee". IEEE Computer Social club.
- ^ "ITU-T X-Series Recommendations".
- ^ "Publicly Available Standards". Standards.iso.org. 30 July 2010. Retrieved eleven September 2010.
- ^ Russell, Andrew L. (28 April 2014). Open Standards and the Digital Age: History, Credo, and Networks. Cambridge University Printing. ISBN978-1-139-91661-5.
- ^ Russell, Andrew L. "Crude Consensus and Running Code' and the Internet-OSI Standards War" (PDF). IEEE Annals of the History of Computing.
- ^ "Standards Wars" (PDF). 2006.
- ^ Inc, IDG Network World (15 February 1988). Network World. IDG Network Earth Inc.
- ^ Inc, IDG Network Globe (10 Oct 1988). Network Earth. IDG Network Earth Inc.
- ^ Shaw, Keith (22 October 2018). "The OSI model explained: How to sympathise (and recollect) the seven layer network model". Network Earth . Retrieved 16 May 2020.
- ^ "An OSI Model for Cloud". Cisco Blogs. 24 February 2017. Retrieved xvi May 2020.
- ^ Taylor, Steve; Metzler, Jim (23 September 2008). "Why information technology's time to allow the OSI model die". Network World . Retrieved xvi May 2020.
- ^ a b Crawford, JB (27 March 2021). "The actual OSI model".
- ^ "Windows Network Compages and the OSI Model". Microsoft Documentation . Retrieved 24 June 2020.
- ^ "5.two RM description for end stations". IEEE Std 802-2014, IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture . ieee. doi:10.1109/IEEESTD.2014.6847097. ISBN978-0-7381-9219-two.
- ^ International Organization for Standardization (15 November 1989). "ISO/IEC 7498-4:1989 -- Information engineering -- Open Systems Interconnection -- Basic Reference Model: Naming and addressing". ISO Standards Maintenance Portal. ISO Central Secretariat. Retrieved 17 Baronial 2015.
- ^ "ITU-T Recommendation 10.224 (xi/1995) ISO/IEC 8073, Open up Systems Interconnection - Protocol for providing the connection-mode ship service". ITU.
- ^ Hooper, Howard (2012). CCNP Security VPN 642-648 Official Cert Guide (2 ed.). Cisco Printing. p. 22. ISBN9780132966382.
- ^ Spott, Andrew; Leek, Tom; et al. "What layer is TLS?". Data Security Stack Substitution.
- ^ Grigonis, Richard (2000). Figurer telephony- encyclopaedia. CMP. p. 331. ISBN9781578200450.
- ^ Mao, Stephen (thirteen Nov 2009). "Chapter 8: Fundamentals of communication networks". In Wyglinski, Alexander; Nekovee, Maziar; Hou, Thomas (eds.). Cognitive Radio Communications and Networks: Principles and Do. Elsevier. p. 201. ISBN978-0-08-087932-1.
- ^ a b "ITU-T Recommendation X.800 (03/91), Security architecture for Open Systems Interconnection for CCITT applications". ITU. Retrieved xiv August 2015.
- ^ Hegering, Heinz-Gerd (24 August 1999). Integrated management of networked systems : concepts, architectures, and their operational application. Morgan Kaufmann. p. 54. ISBN978-1558605718.
- ^ Miao, Guowang; Song, Guocong (2014). Energy and spectrum efficient wireless network pattern. Cambridge Academy Press. ISBN978-1107039889.
- ^ "ITU-T Recommendation Q.1400 (03/1993)], Compages framework for the development of signaling and OA&Thou protocols using OSI concepts". ITU. pp. 4, vii.
- ^ ITU Rec. 10.227 (ISO 8650), X.217 (ISO 8649).
- ^ X.700 series of recommendations from the ITU-T (in item 10.711) and ISO 9596.
- ^ a b "Internetworking Applied science Handbook - Internetworking Basics [Internetworking]". Cisco. 15 January 2014. Retrieved 14 August 2015.
- ^ "3GPP specification: 36.300". 3gpp.org . Retrieved 14 August 2015.
- ^ RFC 3439
- ^ "RFC 3439 - Some Internet Architectural Guidelines and Philosophy". ietf.org . Retrieved 14 August 2015.
- ^ Walter Goralski (2009). The Illustrated Network: How TCP/IP Works in a Modern Network (PDF). Morgan Kaufmann. p. 26. ISBN978-0123745415.
- ^ a b c Andrew S. Tanenbaum, Computer Networks, § i.4.four.
External links [edit]
 | Wikimedia Commons has media related to OSI model. |
- Microsoft Cognition Base: The OSI Model'southward Vii Layers Defined and Functions Explained
- ISO/IEC standard 7498-1:1994 (PDF document inside Nada archive) (requires HTTP cookies in order to accept licence agreement)
- ITU-T X.200 (the same contents equally from ISO)
- "Information Change Architectures and Flow Charts powered by Google App Engine". infchg.appspot.com. The ISO OSI Reference Model, Beluga graph of data units and groups of layers. Archived from the original on 26 May 2012.
{{cite web}}: CS1 maint: others (link) - Zimmermann, Hubert (Apr 1980). "OSI Reference Model — The ISO Model of Architecture for Open Systems Interconnection". IEEE Transactions on Communications. 28 (4): 425–432. CiteSeerX10.1.1.136.9497. doi:10.1109/TCOM.1980.1094702. S2CID 16013989.
- Cisco Systems Internetworking Technology Handbook
- What is the OSI Model – 7 Layers of OSI Model Explained
- Guide to Networking Essentials, 7th Edition - Cengage
Which Layer Of The Osi Model Is The Data Link Layer? Layer 1 Layer 2 Layer 3 Layer 4,
Source: https://en.wikipedia.org/wiki/OSI_model
Posted by: smithequilad.blogspot.com
0 Response to "Which Layer Of The Osi Model Is The Data Link Layer? Layer 1 Layer 2 Layer 3 Layer 4"
Post a Comment