R&M Data Center Handbook
R&M Data Center Handbook
R&M Data Center Handbook
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
www.datacenter.rdm.com<br />
3.8. Transmission Protocols<br />
In order to be able to transfer information from a transmitter to one or more recipients, the<br />
data must be packed properly for transmission, in accordance with how it is transmitted. This<br />
is the job of transmission protocols in data communication. A connection-oriented protocol<br />
first establishes a connection, then sends the data, has this confirmed and finally ends the<br />
connection when the transmission is finished. By contrast, a connectionless protocol entirely<br />
omits the steps of establishing and ending the connection and confirming the transmission,<br />
which is why such a transmission is less secure but faster. Protocols therefore establish<br />
different rules.<br />
A protocol is an agreement on how a connection, communication and data transfer between two parties must be<br />
executed. Protocols can be implemented via hardware, software, or a combination of the two.<br />
Protocols are divided up into:<br />
• Transport-oriented protocols (OSI layer 1–4) & application-oriented protocols (OSI layer 5–7)<br />
• Routable and non-routable protocols (ability to forward through routers, IP = routable)<br />
• Router protocols (path selection decision for routers, e.g. RIP, OSPF, BGP, IGRP, etc.)<br />
A transmission protocol (also known as a network protocol) is a precise arrangement by which data are exchanged<br />
between computers or processors that are connected to one another via a network (distributed system).<br />
This arrangement consists of a set of rules and formats (syntax) which specifies the communication behavior of<br />
the instances which are communicating in the computers (semantics).<br />
The exchange of messages requires an interaction of different protocols, which assume different tasks. The individual<br />
protocols are organized into layers so as to control the complexity associated with the process. In such an<br />
architecture, each protocol belongs to a specified layer and is responsible for carrying out specific tasks (for<br />
example, checking data for completeness – layer 2). Protocols at higher layers use the services from protocols at<br />
lower layers (e.g. layer 3 relies on the fact that all data arrived in full). The protocols structured in this way together<br />
form a protocol stack (this is currently typically a TCP/IP protocol stack).<br />
3.8.1. Implementation (OSI & TCP/IP, Protocols)<br />
The OSI reference model was drafted starting in 1977 by the International Organization for Standardization as a<br />
basis for developing communication standards, and published in 1984 (ISO 7498). The goal of Open Systems<br />
Interconnection (OSI) is a communication system within heterogeneous networks, especially between different<br />
computer worlds, that is based on basic services supported by applications. These basic services include, for<br />
example, file transfer, the virtual terminal, remote access to files and the exchange of electronic mail. In addition to<br />
the actual application data, these and all other communication applications require additional structural and<br />
procedural information that are specified as OSI protocols.<br />
7- Application Layer<br />
Application<br />
6- Presentation Layer<br />
5- Session Layer<br />
4- Transport Layer<br />
3- Network Layer<br />
2- <strong>Data</strong> Link Layer<br />
1- Physical Layer<br />
Computer<br />
Active components<br />
Passive components<br />
R&M <strong>Data</strong> <strong>Center</strong> <strong>Handbook</strong> V2.0 © 08/2011 Reichle & De-Massari AG Page 95 of 156