The TCP/IP model is a description framework for computer network protocols created in

the 1970s by DARPA, an agency of the United States Department of Defense. It evolved
from ARPANET, which was the world's first wide area network and a predecessor of the
Internet. The TCP/IP Model is sometimes called the Internet Model or the DoD Model.
TCP/IP has four abstraction layers as defined in RFC 1122.

• Application Layer (process-to-process): This is the scope within which

applications create user data and communicate this data to other processes or
applications on another or the same host. The communications partners are often
called peers. This is where the "higher level" protocols such as SMTP, FTP, SSH,
HTTP, etc. operate.

• Transport Layer (host-to-host): The Transport Layer constitutes the networking

regime between two network hosts, either on the local network or on remote
networks separated by routers. The Transport Layer provides a uniform
networking interface that hides the actual topology (layout) of the underlying
network connections. This is where flow-control, error-correction, and connection
protocols exist, such as TCP. This layer deals with opening and maintaining
connections between Internet hosts.

• Internet Layer (internetworking): The Internet Layer has the task of exchanging
datagrams across network boundaries. It is therefore also referred to as the layer
that establishes internetworking, indeed, it defines and establishes the Internet.
This layer defines the addressing and routing structures used for the TCP/IP
protocol suite. The primary protocol in this scope is the Internet Protocol, which
defines IP addresses. Its function in routing is to transport datagrams to the next
IP router that has the connectivity to a network closer to the final data destination.

• Link Layer: This layer defines the networking methods within the scope of the
local network link on which hosts communicate without intervening routers. This
layer describes the protocols used to describe the local network topology and the
interfaces needed to affect transmission of Internet Layer datagrams to next-
neighbor hosts. (cf. the OSI Data Link Layer).
The layers near the top are logically closer to the user application, while those near the
bottom are logically closer to the physical transmission of the data.
Application Layer
From Wikipedia, the free encyclopedia
Jump to: navigation, search
The Internet Protocol Suite (TCP/IP) and the Open Systems Interconnection model (OSI
model) of computer networking each specify a group of protocols and methods identified
by the name Application Layer.
In TCP/IP, the Application Layer contains all protocols and methods that fall into the
realm of process-to-process communications across an Internet Protocol (IP) network.
Application Layer methods use the underlying Transport Layer protocols to establish
host-to-host connections.
In the OSI model, the definition of its Application Layer is narrower in scope, explicitly
distinguishing additional functionality above the Transport Layer at two additional levels,
the Session Layer and the Presentation Layer. OSI specifies strict modular separation of
functionality at these layers and provides protocol implementations for each layer.

Presentation Layer
From Wikipedia, the free encyclopedia
Jump to: navigation, search
The OSI Model
7 Application Layer
6 Presentation Layer
5 Session Layer
4 Transport Layer
3 Network Layer
Data Link Layer

2 • LLC sublayer

ΜΑ Χ σ υ β λ α ψ ε ρ
1 Physical Layer
This box: view · talk · edit
The Presentation Layer is Layer 6 of the seven-layer OSI model of computer
networking and serves as the data translator for the network.[1]HYPERLINK \l
"cite_note-Microsoft_Technet-1"[2] It is sometimes called the syntax layer.[3]
The Presentation Layer is responsible for the delivery and formatting of information to
the application layer for further processing or display.[4] It relieves the application layer
of concern regarding syntactical differences in data representation within the end-user
systems. Note: An example of a presentation service would be the conversion of an
EBCDIC-coded text file to an ASCII-coded file.
The Presentation Layer is the lowest layer at which application programmers consider
data structure and presentation, instead of simply sending data in form of datagrams or
packets between hosts. This layer deals with issues of string representation - whether they
use the Pascal method (an integer length field followed by the specified amount of bytes)
or the C/C++ method (null-terminated strings, i.e. "thisisastring\0"). The idea is that
the application layer should be able to point at the data to be moved, and the Presentation
Layer will deal with the rest.
Serialization of complex data structures into flat byte-strings (using mechanisms such as
TLV or XML) can be thought of as the key functionality of the Presentation Layer.
Encryption is typically done at this level too, although it can be done on the Application,
Session, Transport, or Network Layers; each having its own advantages and
disadvantages.[1] Decryption is also handled at the presentation layer. For example, when
logging off bank account sites the presentation layer will decrypt the data as it is
received.[1] Another example is representing structure, which is normally standardized at
this level, often by using XML. As well as simple pieces of data, like strings, more
complicated things are standardized in this layer. Two common examples are 'objects' in
object-oriented programming, and the exact way that streaming video is transmitted.
In many widely used applications and protocols, no distinction is made between the
presentation and application layers. For example, HTTP, generally regarded as an
application layer protocol, has Presentation Layer aspects such as the ability to identify
character encoding for proper conversion, which is then done in the Application Layer.
Within the service layering semantics of the OSI network architecture, the Presentation
Layer responds to service requests from the Application Layer and issues service requests
to the Session Layer.

Session Layer
From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may
be challenged and removed. (October 2009)
"Layer 5" redirects here. For the political layer sometimes included in the TCP/IP model,
see Layer 8.
The OSI Model
7 Application Layer
6 Presentation Layer
5 Session Layer
4 Transport Layer
3 Network Layer
2 Data Link Layer

• LLC sublayer
 ΜΑ Χ σ υ β λ α ψ ε ρ
1 Physical Layer
This box: view · talk · edit
The Session Layer is Layer 5 of the seven-layer OSI model of computer networking.
The Session Layer provides the mechanism for opening, closing and managing a session
between end-user application processes, i.e. a semi-permanent dialogue. Communication
sessions consist of requests and responses that occur between applications. Session Layer
services are commonly used in application environments that make use of remote
procedure calls (RPCs).
An example of a Session Layer protocol is the OSI protocol suite Session Layer Protocol,
also known as X.225 or ISO 8327. In case of a connection loss this protocol may try to
recover the connection. If a connection is not used for a long period, the Session Layer
Protocol may close it and re-open it. It provides for either full duplex or half-duplex
operation and provides synchronization points in the stream of exchanged messages.[1]
Other examples of Session Layer implementations include Zone Information Protocol
(ZIP) – the AppleTalk protocol that coordinates the name binding process, and Session
Control Protocol (SCP) – the DECnet Phase IV Session Layer protocol.
Within the service layering semantics of the OSI network architecture, the Session Layer
responds to service requests from the Presentation Layer and issues service requests to
the Transport Layer.