OSI model

The Open Systems Interconnection model (OSI Systems Interconnection. The standard is usually re-
model) is a conceptual model that characterizes and stan- ferred to as the Open Systems Interconnection Refer-
dardizes the communication functions of a telecommuni- ence Model, the OSI Reference Model, or simply the OSI
cation or computing system without regard to their un- model. It was published in 1984 by both the ISO, as stan-
derlying internal structure and technology. Its goal is the dard ISO 7498, and the renamed CCITT (now called the
interoperability of diverse communication systems with Telecommunications Standardization Sector of the Inter-
standard protocols. The model partitions a communica- national Telecommunication Union or ITU-T) as stan-
tion system into abstraction layers. The original version dard X.200.
of the model dened seven layers. OSI had two major components, an abstract model of net-
A layer serves the layer above it and is served by the working, called the Basic Reference Model or seven-layer
layer below it. For example, a layer that provides error- model, and a set of specic protocols.
free communications across a network provides the path The concept of a seven-layer model was provided by
needed by applications above it, while it calls the next the work of Charles Bachman at Honeywell Informa-
lower layer to send and receive packets that comprise thetion Services. Various aspects of OSI design evolved
contents of that path. Two instances at the same layer are
from experiences with the ARPANET, NPLNET, EIN,
visualized as connected by a horizontal connection in that
CYCLADES network and the work in IFIP WG6.1. The
layer. new design was documented in ISO 7498 and its various
The model is a product of the Open Systems Inter- addenda. In this model, a networking system was divided
connection project at the International Organization for into layers. Within each layer, one or more entities im-
Standardization (ISO), maintained by the identication plement its functionality. Each entity interacted directly
ISO/IEC 7498-1. only with the layer immediately beneath it, and provided
facilities for use by the layer above it.
Protocols enable an entity in one host to interact with a
corresponding entity at the same layer in another host.
Service denitions abstractly described the functionality
provided to an (N)-layer by an (N-1) layer, where N was
one of the seven layers of protocols operating in the local
host.
The OSI standards documents are available from the ITU-
T as the X.200-series of recommendations.[1] Some of
the protocol specications were also available as part of
the ITU-T X series. The equivalent ISO and ISO/IEC
standards for the OSI model were available from ISO, but
Communication in the OSI-Model (example with layers 3 to 5)
only some of them without fees.[2]

1 History 2 Description of OSI layers

In the late 1970s, one project was administered by the In- The recommendation X.200 describes seven layers, la-
ternational Organization for Standardization (ISO), while beled 1 to 7. Layer 1 is the lowest layer in this model.
another was undertaken by the International Telegraph At each level N, two entities at the communicating de-
and Telephone Consultative Committee, or CCITT (the vices (layer N peers) exchange protocol data units (PDUs)
abbreviation is from the French version of the name). by means of a layer N protocol. Each PDU contains a
These two international standards bodies each developed payload, called the service data unit (SDU), along with
a document that dened similar networking models. protocol-related headers and/or footers.
In 1983, these two documents were merged to form a Data processing by two communicating OSI-compatible
standard called The Basic Reference Model for Open devices is done as such:

1
2 2 DESCRIPTION OF OSI LAYERS

1. The data to be transmitted is composed at the top- 2.2 Layer 2: Data Link Layer
most layer of the transmitting device (layer N) into
a protocol data unit (PDU). The data link layer provides node-to-node data transfer
a link between two directly connected nodes. It detects
2. The PDU is passed to layer N-1, where it is known and possibly corrects errors that may occur in the physi-
as the service data unit (SDU). cal layer. It, among other things, denes the protocol to
establish and terminate a connection between two phys-
3. At layer N-1 the SDU is concatenated with a header, ically connected devices. It also denes the protocol for
a footer, or both, producing a layer N-1 PDU. It is ow control between them.
then passed to layer N-2.
IEEE 802 divides the data link layer into two sublayers:[6]
4. The process continues until reaching the lowermost
level, from which the data is transmitted to the re- Media Access Control (MAC) layer - responsible for
ceiving device. controlling how devices in a network gain access to
medium and permission to transmit it.
5. At the receiving device the data is passed from
the lowest to the highest layer as a series of SDUs Logical Link Control (LLC) layer - responsible for
while being successively stripped from each layers identifying Network layer protocols and then encap-
header and/or footer, until reaching the topmost sulating them and controls error checking and frame
layer, where the last of the data is consumed. synchronization.

Some orthogonal aspects, such as management and
security, involve all of the layers (See ITU-T X.800
Recommendation[5] ). These services are aimed at im-
proving the CIA triad - condentiality, integrity, and
availability - of the transmitted data. In practice, the
availability of a communication service is determined
by the interaction between network design and network
management protocols. Appropriate choices for both of
these are needed to protect against denial of service.
2.1 Layer 1: Physical Layer
The physical layer denes the electrical and physical spec-
ications of the data connection. It denes the rela-
tionship between a device and a physical transmission
medium (e.g., a copper or ber optical cable, radio fre-
quency). This includes the layout of pins, voltages, line
impedance, cable specications, signal timing and simi-
lar characteristics for connected devices and frequency (5
GHz or 2.4 GHz etc.) for wireless devices. It is respon-
sible for transmission and reception of unstructured raw
data in a physical medium. It may dene transmission
mode as simplex, half duplex, and full duplex. It denes
the network topology as bus, mesh, or ring being some of
the most common.
The physical layer of Parallel SCSI operates in this layer,
as do the physical layers of Ethernet and other local-area
networks, such as Token Ring, FDDI, ITU-T G.hn, and
IEEE 802.11 (Wi-Fi), as well as personal area networks
such as Bluetooth and IEEE 802.15.4.
The physical layer is the layer of low-level networking
equipment, such as some hubs, cabling, and repeaters.
The physical layer is never concerned with protocols or
other such higher-layer items. Examples of hardware in Message delivery at the network layer is not necessarily
this layer are network adapters, repeaters, network hubs, guaranteed to be reliable; a network layer protocol may
modems, and ber media converters. provide reliable message delivery, but it need not do so.
The MAC and LLC layers of IEEE 802 networks such
as 802.3 Ethernet, 802.11 Wi-Fi, and 802.15.4 ZigBee,
operate at the data link layer.
The Point-to-Point Protocol (PPP) is a data link layer that
can operate over several dierent physical layers, such as
synchronous and asynchronous serial lines.
The ITU-T G.hn standard, which provides high-speed
local area networking over existing wires (power lines,
phone lines and coaxial cables), includes a complete data
link layer that provides both error correction and ow
control by means of a selective-repeat sliding-window
protocol.
2.3 Layer 3: Network Layer
The network layer provides the functional and procedu-
ral means of transferring variable length data sequences
(called datagrams) from one node to another connected
to the same network. It translates logical network address
into physical machine address. A network is a medium
to which many nodes can be connected, 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 nd the
way to deliver the message to the destination node, possi-
bly routing it through intermediate nodes. If the message
is too large to be transmitted from one node to another on
the data link layer between those nodes, the network may
implement message delivery by splitting the message into
several fragments at one node, sending the fragments in-
dependently, and reassembling the fragments at another
node. It may, but need not, report delivery errors.
2.5 Layer 5: Session Layer 3

A number of layer-management protocols, a function de- transport packet.

ned in the management annex, ISO 7498/4, belong to
the network layer. These include routing protocols, mul-
ticast group management, network-layer information and
error, and network-layer address assignment. It is the
function of the payload that makes these belong to the
network layer, not the protocol that carries them.[7]
Although not developed under the OSI Reference Model
and not strictly conforming to the OSI denition of the
transport layer, the Transmission Control Protocol (TCP)
and the User Datagram Protocol (UDP) of the Internet
Protocol Suite are commonly categorized as layer-4 pro-
tocols within OSI.

2.4 Layer 4: Transport Layer 2.5 Layer 5: Session Layer

The transport layer provides the functional and procedu- The session layer controls the dialogues (connections) be-
ral means of transferring variable-length data sequences tween computers. It establishes, manages and terminates
from a source to a destination host via one or more net- the connections between the local and remote application.
works, while maintaining the quality of service functions. It provides for full-duplex, half-duplex, or simplex oper-
An example of a transport-layer protocol in the standard ation, and establishes checkpointing, adjournment, ter-
Internet stack is Transmission Control Protocol (TCP), mination, and restart procedures. The OSI model made
usually built on top of the Internet Protocol (IP). this layer responsible for graceful close of sessions, which
is a property of the Transmission Control Protocol, and
The transport layer controls the reliability of a given link
also for session checkpointing and recovery, which is not
through ow control, segmentation/desegmentation, and
usually used in the Internet Protocol Suite. The session
error control. Some protocols are state- and connection-
layer is commonly implemented explicitly in application
oriented. This means that the transport layer can keep
environments that use remote procedure calls.
track of the segments and retransmit those that fail. The
transport layer also provides the acknowledgement of the
successful data transmission and sends the next data if 2.6 Layer 6: Presentation Layer
no errors occurred. The transport layer creates packets
out of the message received from the application layer. The presentation layer establishes context between
Packetizing is a process of dividing the long message into application-layer entities, in which the application-layer
smaller messages. entities may use dierent syntax and semantics if the pre-
OSI denes ve classes of connection-mode transport sentation service provides a mapping between them. If a
protocols ranging from class 0 (which is also known as mapping is available, presentation service data units are
TP0 and provides the fewest features) to class 4 (TP4, encapsulated into session protocol data units, and passed
designed for less reliable networks, similar to the Inter- down the protocol stack.
net). Class 0 contains no error recovery, and was designed This layer provides independence from data representa-
for use on network layers that provide error-free connec- tion (e.g., encryption) by translating between application
tions. Class 4 is closest to TCP, although TCP contains and network formats. The presentation layer transforms
functions, such as the graceful close, which OSI assigns data into the form that the application accepts. This layer
to the session layer. Also, all OSI TP connection-mode formats and encrypts data to be sent across a network. It
protocol classes provide expedited data and preservation is sometimes called the syntax layer.[9]
of record boundaries. Detailed characteristics of TP0-4
classes are shown in the following table:[8] The original presentation structure used the Basic Encod-
ing Rules of Abstract Syntax Notation One (ASN.1), with
An easy way to visualize the transport layer is to com- capabilities such as converting an EBCDIC-coded text
pare it with a post oce, which deals with the dispatch le to an ASCII-coded le, or serialization of objects and
and classication of mail and parcels sent. Do remember, other data structures from and to XML.
however, that a post oce manages the outer envelope of
mail. Higher layers may have the equivalent of double
envelopes, such as cryptographic presentation services 2.7 Layer 7: Application Layer
that can be read by the addressee only. Roughly speak-
ing, tunneling protocols operate at the transport layer, The application layer is the OSI layer closest to the end
such as carrying non-IP protocols such as IBM's SNA or user, which means both the OSI application layer and the
Novell's IPX over an IP network, or end-to-end encryp- user interact directly with the software application. This
tion with IPsec. While Generic Routing Encapsulation layer interacts with software applications that implement
(GRE) might seem to be a network-layer protocol, if the a communicating component. Such application programs
encapsulation of the payload takes place only at endpoint, fall outside the scope of the OSI model. Application-
GRE becomes closer to a transport protocol that uses IP layer functions typically include identifying communica-
headers but contains complete frames or packets to de- tion partners, determining resource availability, and syn-
liver to an endpoint. L2TP carries PPP frames inside chronizing communication. When identifying commu-
4 6 COMPARISON WITH TCP/IP MODEL

nication partners, the application layer determines the state information from the PHY layer, network
identity and availability of communication partners for throughput can be signicantly improved and en-
an application with data to transmit. When determining ergy waste can be avoided.[10]
resource availability, the application layer must decide
whether sucient network resources for the requested
communication exist. In synchronizing communication, 4 Interfaces
all communication between applications requires cooper-
ation that is managed by the application layer. This layer
Neither the OSI Reference Model nor OSI protocols
supports application and end-user processes. Communi-
specify any programming interfaces, other than delib-
cation partners are identied, quality of service is identi-
erately abstract service specications. Protocol speci-
ed, user authentication and privacy are considered, and
cations precisely dene the interfaces between dierent
any constraints on data syntax are identied. Everything
computers, but the software interfaces inside computers,
at this layer is application-specic.
known as network sockets are implementation-specic.
For example, Microsoft Windows' Winsock, and Unix's
3 Cross-layer functions Berkeley sockets and System V Transport Layer Inter-
face, are interfaces between applications (layer 5 and
above) and the transport (layer 4). NDIS and ODI are
Cross-layer functions are services that are not tied to a interfaces between the media (layer 2) and the network
given layer, but may aect more than one layer. Examples protocol (layer 3).
include the following:
Interface standards, except for the physical layer to me-
dia, are approximate implementations of OSI service
Security service (telecommunication)[5] as dened
specications.
by ITU-T X.800 recommendation.

Management functions, i.e. functions that permit to

congure, instantiate, monitor, terminate the com- 5 Examples
munications of two or more entities: there is a spe-
cic application-layer protocol, common manage-
ment information protocol (CMIP) and its corre- 6 Comparison with TCP/IP model
sponding service, common management informa-
tion service (CMIS), they need to interact with every The design of protocols in the TCP/IP model of the In-
layer in order to deal with their instances. ternet does not concern itself with strict hierarchical en-
capsulation and layering.[16] RFC 3439 contains a sec-
Multiprotocol Label Switching (MPLS) operates at tion entitled Layering considered harmful".[17] TCP/IP
an OSI-model layer that is generally considered to lie does recognize four broad layers of functionality which
between traditional denitions of layer 2 (data link are derived from the operating scope of their contained
layer) and layer 3 (network layer), and thus is often protocols: the scope of the software application; the end-
referred to as a layer-2.5 protocol. It was designed to-end transport connection; the internetworking range;
to provide a unied data-carrying service for both and the scope of the direct links to other nodes on the
circuit-based clients and packet-switching clients local network.[18]
which provide a datagram-based service model. It
can be used to carry many dierent kinds of traf- Despite using a dierent concept for layering than the
c, including IP packets, as well as native ATM, OSI model, these layers are often compared with the OSI
SONET, and Ethernet frames. layering scheme in the following way:

ARP is used to translate IPv4 addresses (OSI layer
3) into Ethernet MAC addresses (OSI layer 2).
Domain Name Service is an Application Layer ser-
vice which is used to look up the IP address of a
given domain name. Once a reply is received from
the DNS server, it is then possible to form a Layer
3 connection to the third-party host.
Cross MAC and PHY Scheduling is essential in
wireless networks because of the time varying na-
ture of wireless channels. By scheduling packet
transmission only in favorable channel conditions,
which requires the MAC layer to obtain channel
The Internet application layer includes the OSI ap-
plication layer, presentation layer, and most of the
session layer.
Its end-to-end transport layer includes the graceful
close function of the OSI session layer as well as the
OSI transport layer.
The internetworking layer (Internet layer) is a subset
of the OSI network layer.
The link layer includes the OSI data link layer and
sometimes the physical layers, as well as some pro-
tocols of the OSIs network layer.
 5

These comparisons are based on the original seven-layer [9] Grigonis, Richard (2000). Computer telephony- ency-
protocol model as dened in ISO 7498, rather than re- clopaedia. CMP. p. 331. ISBN 9781578200450.
nements in such things as the internal organization of
[10] G. Miao; G. Song (2014). Energy and spectrum ecient
the network layer document. wireless network design. Cambridge University Press.
The presumably strict layering of the OSI model as it ISBN 1107039886.
is usually described does not present contradictions in
[11] ITU-T Recommendation Q.1400 (03/1993)], Architec-
TCP/IP, as it is permissible that protocol usage does not
ture framework for the development of signaling and
follow the hierarchy implied in a layered model. Such ex- OA&M protocols using OSI concepts". ITU. pp. 4, 7.
amples exist in some routing protocols (e.g., OSPF), or
in the description of tunneling protocols, which provide [12] ITU Rec. X.227 (ISO 8650), X.217 (ISO 8649).
a link layer for an application, although the tunnel host
[13] X.700 series of recommendations from the ITU-T (in par-
protocol might well be a transport or even an application- ticular X.711) and ISO 9596.
layer protocol in its own right.
[14] Internetworking Technology Handbook - Internetwork-
ing Basics [Internetworking]". Cisco. 15 January 2014.
7 See also Retrieved 14 August 2015.

[15] 3GPP specication: 36.300. 3gpp.org. Retrieved 14

Hierarchical internetworking model August 2015.

Management plane [16] RFC 3439

Layer 8 [17] RFC 3439 - Some Internet Architectural Guidelines and

Philosophy. ietf.org. Retrieved 14 August 2015.
Protocol stack
[18] Walter Goralski. The Illustrated Network: How TCP/IP
Service layer Works in a Modern Network (PDF). Morgan Kaufmann.
p. 26. ISBN 978-0123745415.
WAP protocol suite
List of information technology acronyms
IBM Systems Network Architecture
9 External links
Internet protocol suite Microsoft Knowledge Base: The OSI Models Seven
Layers Dened and Functions Explained

ISO/IEC standard 7498-1:1994 (PDF document in-

8 References side ZIP archive) (requires HTTP cookies in order
to accept licence agreement)
[1] ITU-T X-Series Recommendations

[2] Publicly Available Standards. Standards.iso.org. 2010-

07-30. Retrieved 2010-09-11.
[3] The OSI Models Seven Layers Dened and Functions
Explained. Microsoft Support. Retrieved 2014-12-28.
[4] RFC 4253
[5] ITU-T Recommendataion X.800 (03/91), Security archi-
tecture for Open Systems Interconnection for CCITT appli-
cations". ITU. Retrieved 14 August 2015.
[6] 5.2 RM description for end stations. IEEE Std 802-
2014, IEEE Standard for Local and Metropolitan Area
Networks: Overview and Architecture. ieee.
[7] International Organization for Standardization (1989-11-
15). ISO/IEC 7498-4:1989 -- Information technology --
Open Systems Interconnection -- Basic Reference Model:
Naming and addressing. ISO Standards Maintenance
Portal. ISO Central Secretariat. Retrieved 2015-08-17.
ITU-T X.200 (the same contents as from ISO)
The ISO OSI Reference Model , Beluga graph of
data units and groups of layers
Zimmermann, Hubert (April 1980). OSI Refer-
ence Model The ISO Model of Architecture
for Open Systems Interconnection. IEEE Trans-
actions on Communications. 28 (4): 425432.
doi:10.1109/TCOM.1980.1094702. CiteSeerX:
10.1.1.136.9497.
Cisco Systems Internetworking Technology Hand-
book
Osi Model : 7 Layer Of The Network Communica-
tion

[8] ITU-T Recommendation X.224 (11/1995) ISO/IEC

8073, Open Systems Interconnection - Protocol for provid-
ing the connection-mode transport service". ITU.
6 10 TEXT AND IMAGE SOURCES, CONTRIBUTORS, AND LICENSES

10 Text and image sources, contributors, and licenses

10.1 Text
OSI model Source: https://en.wikipedia.org/wiki/OSI_model?oldid=740931280 Contributors: Damian Yerrick, AxelBoldt, Bryan Derk-
sen, The Anome, Stephen Gilbert, Manning Bartlett, Amillar, Andre Engels, Gsl, Aldie, Nate Silva, M~enwiki, William Avery, Davi-
dLevinson, Heron, B4hand, Edward, PhilipMW, Michael Hardy, Chris-martin, MartinHarper, Todd, Looxix~enwiki, Mkweise, Ahoerste-
meier, Haakon, Ronz, Nanshu, Glenn, Bogdangiusca, Netsnipe, IMSoP, Evercat, EdH, JidGom, Mulad, Markb, Emperorbma, Fuzheado,
Atreyu42, Markhurd, Tpbradbury, Grendelkhan, Jnc, Ed g2s, Rnbc, Nickshanks, Joy, Fvw, Johnleemk, Finlay McWalter, Phil Boswell,
Robbot, TomPhil, Friedo, Fredrik, Dumbledad, RedWolf, Postdlf, Wjhonson, Rfc1394, Puckly, Rursus, 75th Trombone, Hadal, David
Edgar, Rsduhamel, Filemon, David Gerard, Enochlau, Giftlite, Graeme Bartlett, DavidCary, Cokoli, Jpta~enwiki, Inkling, Tom harrison,
Lupin, Herbee, 0x6D667061, Everyking, CyborgTosser, Itpastorn, EJDyksen, Mboverload, AlistairMcMillan, Alvestrand, Tagishsimon,
Dave2, Gadum, Pamri, Mendel, Inversetime, Ravikiran r, Eldiablo~enwiki, Sridev, Parakalo~enwiki, Tooki, Kramerino, Lazarus666, Pa-
parodo, Jcw69, Slrobertson, Kevin Rector, Trevor MacInnis, Moxfyre, Safety Cap, EagleOne, DmitryKo, Gazpacho, Mike Rosoft, Venu62,
Hes Nikke, Hgerstung, RossPatterson, Discospinster, Rich Farmbrough, Rhobite, DavidBarak, Lulu of the Lotus-Eaters, Demitsu, Paul Au-
gust, Techtoucian, BACbKA, Kaszeta, CanisRufus, Charm, MBisanz, Lankiveil, Bletch, GarethGilson, Sietse Snel, RoyBoy, Triona, Causa
sui, Rlaager, Bobo192, MarkWahl, Smalljim, John Vandenberg, Dreish, Che090572, AtomicDragon, Elipongo, Mikel Ward, Giraedata,
SpeedyGonsales, Chirag, Nk, Bdamokos, Wrs1864, Helix84, Krellis, Nsaa, Mdd, Wayfarer, Ogress, Alansohn, Gary, Ghostalker, Snow-
Fire, Guy Harris, Free Bear, Lectonar, OSUKid7, Caesura, Snowolf, Simon, Wtmitchell, Rebroad, Wtshymanski, Rick Sidwell, Cburnett,
Stephan Leeds, Suruena, RainbowOfLight, Drat, Mikeo, Pethr, H2g2bob, MIT Trekkie, Pytom, Cxxl, Richwales, Beelaj, Mahanga, Ott,
Feezo, Stemonitis, OwenX, Woohookitty, Camw, LOL, Blueskies238, Ilario, Robert K S, Hdante, Kgrr, Cbustapeck, Eyreland, Prashan-
thns, Andybryant, Palica, Marudubshinki, Kesla, Runis57, Jannetta, Chupon, Jetekus, Josh Parris, Casey Abell, Ketiltrout, Dpark, John-
blade, Jake Wartenberg, Kinu, Inkhorn, CraSH, TAS, Tangotango, SMC, Vegaswikian, Kazrak, BDerrly, ElKevbo, N-Man, Fred Bradstadt,
Syced, Yamamoto Ichiro, Audunv, StuartBrady, FlaBot, Nivix, Ewlyahoocom, Eric Soyke, RobyWayne, Intgr, Fresheneesz, Alphachimp,
Chfalcao, Imnotminkus, Jmorgan, Chobot, Hatch68, Visor, DVdm, JesseGarrett, Bgwhite, Adoniscik, Gwernol, FrankTobia, Roboto de
Ajvol, McGinnis, YurikBot, Albanaco, Borgx, Sceptre, Josef Sbl cz, Joodas, Jonwatson, Bhny, Tyler.szabo, SpuriousQ, Kirill Lokshin,
Joebeone, Grubber, Shell Kinney, CambridgeBayWeather, Eleassar, Pseudomonas, Abarry, Friday, NawlinWiki, ENeville, Grafen, Ra-
zorICE, Nick, Marvin01, Brandon, Moe Epsilon, Kaz219~enwiki, Voidxor, Lomn, Davetrainer, Tony1, PyreneesJIM, Nethgirb, Rjstinyc,
Jessemerriman, Caerwine, MarkBrooks, Wknight94, FF2010, Whitejay251, Lt-wiki-bot, YolanCh, Ageekgal, Closedmouth, Iambk, Fang
Aili, Pb30, Abune, Bariswheel, JoanneB, ThunderBird, Allens, Honeyman, CIreland, Luk, Hiddekel, EJSawyer, Sardanaphalus, SmackBot,
Mmernex, Bonobosarenicer, Irnavash, ThreeDee912, Reedy, KnowledgeOfSelf, Bjelleklang, Brick Thrower, Delldot, Nejko, Jonathanwag-
ner, Gilliam, Psiphiorg, @modi, Djib, Delfeye, Alucard 16, Tree Biting Conspiracy, Stevage, Arroww, Octahedron80, Nbarth, Ctbolt,
Adibob, Thief12, TripleF, Can't sleep, clown will eat me, YamiKaitou, ZachPruckowski, JonHarder, Addshore, Kcordina, Edivorce,
Meepster, SundarBot, Adamantios, UU, Dohzer, Soosed, Apocryphite, Cybercobra, Fullstop, Valenciano, Shadow1, Tompsci, HarisM,
Insineratehymn, Weregerbil, Mwtoews, WoiKiCK, Ged UK, Dino.korah, Umair ahmed123, H34d~enwiki, Kuru, Microchip08, Natara-
juab, Rejax, Martinkop, Adj08, Sir Nicholas de Mimsy-Porpington, Tim Q. Wells, Nux, Goodnightmush, Highpriority, Noahspurrier,
Michael miceli, IronGargoyle, Morten, Vanished user 8ij3r8jwe, MarkSutton, Krampo, Yms, Mr Stephen, Dicklyon, Kim Rubin, Wag-
gers, Lachlancooper, Anonymous anonymous, IReceivedDeathThreats, Ryulong, Wrlee~enwiki, Citicat, Nbhatla, Kvng, Rcannon100, Lee
Carre, Hetar, Iridescent, Penno, Shoeofdeath, Beno1000, Courcelles, Drwarpmind, Tnneid, Danlev, Tawkerbot2, Ouishoebean, Stephen-
Falken, Ryt, The Haunted Angel, Mmdoogie, InvisibleK, Sakurambo, KerryVeenstra, CmdrObot, Ale jrb, Nitecruzr, Scohoust, Lighthead,
Naishadh, Andkore, RobEby, Phatom87, Myheadspinsincircles, Mattalyst, Travelbird, Yuokool12, Maguscrowley, Odie5533, Tawkerbot4,
Mattjgalloway, DumbBOT, Chrislk02, Eazy007, Alaibot, Biblbroks, Scolobb, Omicronpersei8, JodyB, Epbr123, Rohwigan03, Jhilving,
Daniel, N5iln, Hcberkowitz, Amitbhatia76, JMatthews, CynicalMe, Marek69, John254, Tellyaddict, Iviney, Ajo Mama, RichardVeryard,
Kaaveh Ahangar~enwiki, Zachary, Dzubint, Turb0chrg, Qexter, KrakatoaKatie, AntiVandalBot, Majorly, Luna Santin, Fjpanna, Seaphoto,
CDima, BommelDing~enwiki, JeTataMe, Alphachimpbot, Graham.rellinger, Myanw, Gkhan, Caper13, JAnDbot, Niaz, Vmguruprasath,
Dereckson, MER-C, Dcooper, LittleOldMe, Enjoi4586, Ideoplex, Bakilas, VoABot II, Ishikawa Minoru, RoscoMck, Davidjk, James-
BWatson, Mbc362, Tedickey, Ifroggie, Panser Born, Animum, Cyktsui, Dili, Mtd2006, MetsBot, Logictheo, Schumi555, BenLiyanage,
WLU, SineChristoNon, Patstuart, Micahcowan, 0612, S3000, Flowanda, MartinBot, Nolyann, Naohiro19, Rettetast, Charles Edward, Ryan
au, Ore4444, Cputrdoc, Markolinsky, Jschoon4, Smokizzy, RockMFR, J.delanoy, Mange01, Carre, SaxicolousOne, Uncle Dick, Public
Menace, Mr Elmo, Saicome, Dispenser, Katalaveno, DJPohly, Skier Dude, Gurchzilla, Swapcouch, AntiSpamBot, Tarekradi, Kraftlos, Wil-
son.canadian, Jrodor, Lordeaswar, Cometstyles, Inomyabcs, Wily duck, Inwind, S (usurped also), Boikej, Pluyo8989, Mlewis000, Lights,
HamatoKameko, 28bytes, GreYFoXGTi, VolkovBot, Wire323, ABF, Adityagaur 7, Je G., Speaker to Lampposts, Lears Fool, Meta-
classing, Saddy Dumpington, Khat17, Philip Trueman, DoorsAjar, Oshwah, BuickCenturyDriver, DSParillo, GDonato, Dmottl, Chim-
pex, Anna Lincoln, DennyColt, Leafyplant, BwDraco, PDFbot, BotKung, VidGa, Ibenr, Rjgodoy, Aslambasha09, Coriron, Ayengar,
Sunilmalik1107, Spitre8520, Henrikholm, AlleborgoBot, PGWG, Jchristn, CMBJ, LOTRrules, Kbrose, SieBot, Mikemoral, Nubiat-
ech, Scarian, Jauerback, Caltas, Matthew Yeager, Triwbe, Yintan, GlassCobra, Bobdrad, Happysailor, Flyer22 Reborn, EnOreg, Oxy-
moron83, Arunachalammanohar, Tpvibes, Steven Crossin, Wishingtown~enwiki, Patrikor, Rkarlsba, StaticGull, ProPuke, Denisarona,
Troy 07, ClueBot, GorillaWarfare, The Thing That Should Not Be, Postmortemjapan, Think4amit, Lawrence Cohen, Unbuttered Parsnip,
Adrianwn, LizardJr8, Anjola, Pmorkert, Puchiko, Andjohn2000, Pointillist, DragonBot, Excirial, Throttler, Alexbot, Jusdafax, Anon
lynx, Erwinkarim, Fleg31789, NuclearWarfare, Arjayay, Jotterbot, Patch1103, DeltaQuad, Botsjeh, Morel, Isthisthingworking, Muro Bot,
Zoobee79, Thingg, Aitias, 7, Subfrowns, Versus22, Mr.ghlban, Mcnuttj, Rgilchrist, Johnuniq, SoxBot III, Apparition11, Bcherwrmlein,
DumZiBoT, FreshPrinz, XLinkBot, Jovianeye, Tbsdy lives, Logthis, Dgtsyb, Karpouzi, Alexius08, Hellomarius, Jdrrmk, Tranzz, Hexa-
Chord, Bojer~enwiki, Addbot, Mobius R, Willking1979, Akiyukio, 1337 JN, Balajia82, Tcncv, Bzimage.it, Friginator, Syntaxsystem, Dj-
moa, Scientus, Vishnava, CanadianLinuxUser, NjardarBot, Amtanoli, Cst17, MrOllie, The Athlon Duster, Ottosmo, Evillawngnome, Roux,
Doniago, TinyTimZamboni, Lockcole, Tide rolls, OlEnglish, Teles, Zorrobot, MuZemike, David0811, Wireless friend, Another-anomaly,
Dcovell, Peni, , Enduser, Angrysockhop, ZX81, Yobot, WikiDan61, Karelklic, Fraggle81, Cm001, Manishar us, Therumakna,
THEN WHO WAS PHONE?, Brougham96, Gafex, Tempodivalse, AnomieBOT, DemocraticLuntz, Duey111, Naresh jangra, Killiondude,
Jim1138, CraigBox, Kingpin13, Ulric1313, Mikeyh56, RandomAct, Flewis, Materialscientist, RobertEves92, uman, 90 Auto, Citation
bot, ShornAssociates, E2eamon, Roux-HG, Crimsonmargarine, Gasp01, Milind m2255, MauritsBot, Xqbot, Saad ziyad, Capricorn42, Nfr-
Maat, Jerey Mall, DSisyphBot, Shrofami, AbigailAbernathy, Fuzzball24816, Nasa-verve, GrouchoBot, AVBOT, Wizardist, Rsiddharth,
Shirik, Mathonius, Kallaspriit, Mmmeg, Theelmgren, Shadowjams, Joaquin008, Sesu Prime, A.amitkumar, FrescoBot, DrSpice, Oita2001,
802geek, Advancedtelcotv, Itusg15q4user, VS6507, Kyllys, Recognizance, Nisavid, Runtux, Geek2003, Kismalac, Eliezerb, Vk anantha,
Originalharry, DrDOS, AstaBOTh15, Simple Bob, Mojalefa247, I dream of horses, Ajw901, LittleWink, Jonesey95, A412, Calmer Waters,
10.2 Images 7

Rushbugled13, Jschnur, Serols, SpaceFlight89, Isofox, Fumitol, Warrierrakesh, Bmylez, Mohitjoshi999, Merlion444, Mmeerman~enwiki,
Yamike, TobeBot, Ashutosh.mcse, Lotje, Asn1tlv, Dinamik-bot, Nemesis of Reason, Bluest, Mattmill30, Fiable.biz, JV Smithy, Tb-
hotch, Minimac, Brambleclawx, DARTH SIDIOUS 2, Artur Perwenis, Candc4, Ripchip Bot, Lynnallendaly, Conquest ace, Deagle AP,
Rollins83, EmausBot, Sliceofmiami, Stryn, Immunize, Alex3yoyo, Super48paul, Dewritech, Racerx11, Mrankur, RenamedUser01302013,
Peaceray, John Hopley, Sp33dyphil, Tommy2010, Wikipelli, Dcirovic, K6ka, Savh, Mohitsport, F, Josve05a, PaulWIKIJeery, Mkage-
nius, Unkownkid123, A930913, Saintends, Can You Prove That You're Human, Kyerussell, Cs mat3, SporkBot, Monterey Bay, Gz33,
Wingman4l7, Vanished user fois8fhow3iqf9hsrlgkjw4tus, Elfosardo, Praggu, Crasheral, Tarian.liber, Orange Suede Sofa, ChuispastonBot,
Pastore Italy, Kkbairi, SharePointStacy, Neil P. Quinn, DASHBotAV, Raju5134, Petrb, Encaitar, ClueBot NG, MelbourneStar, Jeanjour,
Satellizer, Lord Chamberlain, the Renowned, Chester Markel, Jjenkins5123, Jakuzem, Bchiap, 336, Widr, Scottonsocks, Suyashparth,
Chrkelly, Theopolisme, MerlIwBot, Novusuna, Johnny C. Morse, Kronn8, WNYY98, BG19bot, HMGb, Island Monkey, Northamer-
ica1000, Hallows AG, Palltrast, Mudasir011, Snehasapte, Mark Arsten, Shraddha deshmukh, BJMdeJong, Dmohantyatgmail, Benzband,
Jatinsinha, Avitesh, MrsValdry, CitationCleanerBot, GGShinobi, Roo314159, Falk.H.G., Nathanashleywild, Mahesh Sarmalkar, Translu-
centCloud, Wannabemodel, Winston Chuen-Shih Yang, Nkansahrexford, Jsonheld, Vanished user lt94ma34le12, Zhaofeng Li, Jimw338,
Taruntan, Sfeldner, Gm shamim, RealHandy, Tprz, Dexbot, Webclient101, Iambossatghari, Mitrabarun, Neevan99, Frosty, Payal1234,
, ElgeeC, DBhavsar709, Epicgenius, Davidh63, Immaculate.john95, Franois Robere, Melonkelon, Apurv.11213, DavidLeighEllis,
Thardrain, Comp.arch, Tilopenda, Spyglasses, Congoblast, Ginsuloft, Semsi Paco Virchow, Quenhitran, Jianhui67, Lengeni, Byte1000101,
Abbotn, Antrocent, Claw of Slime, YitzchakF, Tayyabjamil, User26954344524345, Omare83, TerryAlex, Psycho365, Say which?, Jain
Nupoor, Ajit31, Biochembob, TranquilHope, Praks purushot, Candlelighter, Vtor, Superdupernova, Sonicwave32, Lukajohn70, Rishi
Neemkhedia, Sagar22more, Prateek Proo, Neil Schoolman, Virulentvowels, Abcd50000, NgYShung, Krlicmuhamed, Bender the Bot,
GAURAV AWASTHI and Anonymous: 2491

10.2 Images
File:Commons-logo.svg Source: https://upload.wikimedia.org/wikipedia/en/4/4a/Commons-logo.svg License: CC-BY-SA-3.0 Contribu-
tors: ? Original artist: ?
File:Folder_Hexagonal_Icon.svg Source: https://upload.wikimedia.org/wikipedia/en/4/48/Folder_Hexagonal_Icon.svg License: Cc-by-
sa-3.0 Contributors: ? Original artist: ?
File:OSI-model-Communication.svg Source: https://upload.wikimedia.org/wikipedia/commons/4/41/OSI-model-Communication.svg
License: Public domain Contributors: Own work Original artist: Runtux

10.3 Content license

Creative Commons Attribution-Share Alike 3.0