Must Know As a Network Engineer

OSI Reference Model and IP Set Model

What is OSI Reference Model and IP Set Model

All Network Protocol are categorized by conception of Layers. Layers are mainly used by OSI Reference Model and IP Set Model.

TCP/IP , which is defacto standard in internet , is based on IP Set Model, but the words "Layer" is indicated that it is based on OSI Reference Model.

The current mainstream TCP/IP is based on the IP Set Model, but the word "Layer" conventionally refers to the layer based on the OSI Reference Model. In this way, it is practical that it is an IP Set Model, but the layer that comes up in the conversation often points to the one of the OSI Reference Model.

For example, Layer 2 switch, Layer 3 switch, Layer 4 switch, Layer 7 switch indicate layers of the OSI Reference Model, and obstacles resulting from not being physically connected are called "Layer 1 obstacles".

Specific examples of OSI reference model and IP set model

lThe OSI(Open systems interconnection) Reference Model is a hierarchical model created by ISO and CCITT. However, the current mainstream Communication Technology TCP/IP does not strictly follow this model. That is, data communication currently strictly based on this hierarchical model is a minority. TCP/IP uses a hierarchical model called "IP Set Model" because of ease of implementation.

A comparison between the OSI reference model and the IP set model is shown in the table below.

Layer
OSI Reference Model
IP Set Model
Examples of protocols and standards
7Application LayerApplication Layerhttp, ftp, dns, smtp, pop, imap, snmp
6Presentation Layer
5Session LayerTLS(old SSL)
4Transport LayerTransport Layer
or
Service Layer
tcp, udp
3Network LayerNetwork Layer
or
Routing Layer
ip, icmp, arp, rarp
2Data Link LayerNetwork Access LayerEthernet, FDDI,
Token-Ring, PPP, Frame-Relay, ATM
1Physical LayerPhysical LayerUTP, Optical-Fiber, Wireless,
Coaxial-Cable

The roles of each layer are as follows.

1. Physical Layer

Physical requirements such as cable type and connector shape, and noise reference value for transmission of bit in transmission medium (electricity or light) are defined.

Specific implementations include UTP category 5e / 6 / 6a, optical cable of single-mode and multi-mode, coaxial cable etc.

 

2. Data Link Layer

Define how to communicate directly or between devices connected via Layer 2 equipment (L2 switch etc.). It specifies how to make concrete bit strings and so on. The communication destination at this layer is not limited to the device you want to communicate with, but it may be a data transfer device such as a router or L3 switch.

Ethernet is the most popular implementation, but there are other PPP , PPPoE, ATM, frame relay, etc.

The Network Layer should not change to the destination, but the Data Link Layer can be changed in any number of times without any problem. Rather, the role of the Data Link Layer is to absorb physical changes such as cables.

Though the Data Link Layer can be used depending on the Physical Layer, for example, OM3 type of optical multi-mode corresponds widely from 100 Mbps to 100 Gbps.

3. Network Layer

Determine the communication route to the device you want to communicate (destination IP address for IP). (Route selection by routing etc.)

IP is the de facto standard for implementation.

4. Transport Layer

It manages the communication status between the source device and the device that wishes to communicate. (Error correction, retransmission control, etc.)

TCP/UDP is the de facto standard for implementation. Whether to use TCP or UDP is chosen depending on the protocol of the Application Layer, but in some case, for example NTP or syslog, etc, RFC it is said that "should be used with UDP", software which can be set by TCP Yes.

5. Session Layer

Define the communication procedure between both communication programs on the source device and the device you wish to communicate with. (Communication method, connection / disconnection procedure, recovery procedure in case of abnormality, etc.)

通信元の機器上と通信したい機器上の両通信プログラム間での通信手順を定義します。(通信方式、接続/切断の手順や異常時の回復手順など)

A concrete implementation is TLS (former SSL).

6. Presentation Layer

Perform format conversion of data. (Conversion of character code etc.)

The famous implementation is ASCII mode of FTP. For example html files created on Windows will be [character code Shift-JIS] and [line code CR + LF], but if you upload this to Linux under FTP as ASCII mode, you can see [character code EUC-JP] and [ Code LF] automatically.

有名な実装は、FTPのアスキーモードです。Windowsで作成したhtmlファイルなどは[文字コードShift-JIS]と[改行コードCR+LF]になりますが、これをLinuxにFTPでアスキーモードでアップロードすると、[文字コードEUC-JP]と[改行コードLF]に自動で変換してくれます。

If you do not want this conversion, use binary mode.

For example, you can set as follows for the famous FTP client software "FFFTP".

By clicking "Preferences" in "Options" and clicking "Transfer 1", you can select "transfer mode always" ASCII mode "always" binary mode "" switch by file name ". By default, "Switch by file name" is selected.

7. Application Layer

Define the communication procedure between applications. (Format of http etc.)

For example, when you want to download html files etc on web server, it is job of this layer to use GET command.

コメント

タイトルとURLをコピーしました