<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Networking Reviews</title>
	<atom:link href="https://www.networkingreviews.com/category/osi-layers/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.networkingreviews.com</link>
	<description></description>
	<lastBuildDate>Wed, 04 Jun 2008 15:15:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.1</generator>
	<item>
		<title>TCP/IP Model vs OSI Model</title>
		<link>https://www.networkingreviews.com/tcpip-model-vs-osi-model/</link>
					<comments>https://www.networkingreviews.com/tcpip-model-vs-osi-model/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 15:15:49 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<category><![CDATA[osi model]]></category>
		<category><![CDATA[tcp model]]></category>
		<category><![CDATA[tcpip model]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/?p=82</guid>

					<description><![CDATA[We have talked in other posts about the OSI model, which is the de-facto standard model for describing and implementing IP communication networks. You might be thinking that the OSI model was the original standard created when the first computer networks started to appear, but this is wrong. The TCP/IP model is older than the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>We have talked in other posts about the <strong>OSI model</strong>, which is the de-facto standard model for describing and implementing IP communication networks. You might be thinking that the OSI model was the original standard created when the first computer networks started to appear, but this is wrong. The TCP/IP model is older than the OSI, despite that the OSI is the most well known model today.</p>
<p><span id="more-82"></span></p>
<p>The <strong>TCP/IP model</strong> originated by the U.S Department of Defense in the 1970s. It is very similar to the OSI Model, but with a simpler structure, as shown below:</p>
<p style="text-align: center;"><img fetchpriority="high" decoding="async" style="vertical-align: middle;" src="https://www.networkingreviews.com/images/tcp-model-vs-osi-model.jpg" alt="tcp model compared with osi model" width="450" height="500" /></p>
<p>As you can see from the diagram above, the TCP/IP model matches the OSI up to the Transport Layer. The top three layers of the OSI (Session, Presentation, Application) are represented just by one layer on the TCP/IP model (the Application Layer).</p>
<p>The strength of the TCP/IP model compared to the OSI is that its simpler and is completely aligned with the TCP/IP protocol stack. The weakness of the TCP/IP model compared to the OSI is that its mostly network-centric and does not describe the application interaction in much detail.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/tcpip-model-vs-osi-model/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 7: Application Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-7-application-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-7-application-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 18:05:34 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-7-application-layer/</guid>

					<description><![CDATA[The Application Layer is the one which interacts with the user. A Software application that implements a communicating component, uses the OSI Application Layer to establish the application’s communication. For example a word processor that does not have communications capabilities, would not be concerned with the OSI Application Layer. On the other hand, an application [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The Application Layer is the one which interacts with the user. A Software application that implements a communicating component, uses the OSI Application Layer to establish the application’s communication. For example a word processor that does not have communications capabilities, would not be concerned with the OSI Application Layer. On the other hand, an application with communication capabilities (e.g a Web Browser), has to implement the OSI Application Layer standards.<br />
<span id="more-33"></span></p>
<p><!--adsense--></p>
<p><strong><u>Examples of Layer 7 Applications</u></strong><br />
• Telnet<br />
• FTP<br />
• HTTP<br />
• SMTP<br />
• WWW Browsers<br />
• SNMP</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-7-application-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 6: Presentation Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-6-presentation-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-6-presentation-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 18:03:38 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-6-presentation-layer/</guid>

					<description><![CDATA[The main function of this layer is to define data formats, coding, and conversion functions that are applied to application layer data. These functions ensure that information sent from the application layer of one system would be readable by the application layer of another system. Encryption and compression of Data are also defined as Presentation [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The main function of this layer is to define data formats, coding, and conversion functions that are applied to application layer data. These functions ensure that information sent from the application layer of one system would be readable by the application layer of another system. Encryption and compression of Data are also defined as Presentation layer functions.<span id="more-32"></span></p>
<p><!--adsense--></p>
<p>Some popular implementations of the Presentation Layer are well-known standards such as QuickTime and MPEG, Graphics Interchange Format (GIF), Joint Photographic Experts Group (JPEG), and Tagged Image File Format (TIFF).</p>
<p><strong><u>Examples of Layer 6 Standards</u></strong><br />
• ASCII<br />
• EBCDIC<br />
• TIFF<br />
• GIF<br />
• JPEG<br />
• MPEG<br />
• MIDI</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-6-presentation-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 5: Session Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-5-session-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-5-session-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 17:51:06 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-5-session-layer/</guid>

					<description><![CDATA[The Session Layer starts, controls, and manages communication conversations (sessions). Communication sessions consist of service requests and service responses that occur between applications located in different network devices. These requests and responses are coordinated by protocols implemented at the session layer. The session layer creates ways to imply which flows are part of the same [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The Session Layer starts, controls, and manages communication conversations (sessions). Communication sessions consist of service requests and service responses that occur between applications located in different network devices. These requests and responses are coordinated by protocols implemented at the session layer. The session layer creates ways to imply which flows are part of the same session and which flows must complete before any are considered complete.<span id="more-31"></span></p>
<p><!--adsense--></p>
<p><strong><u>Examples of Layer 5 Specifications and Protocols</u></strong><br />
• RPC<br />
• Session Control Protocol (SCP)<br />
• SQL<br />
• NFS<br />
• NetBios names <!-- InstanceEndEditable --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-5-session-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 4: Transport Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-4-transport-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-4-transport-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 17:50:07 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-4-transport-layer/</guid>

					<description><![CDATA[The Transport Layer (e.g TCP) provides reliable delivery of Data by using error checking, acknowledgments, flow control, and sequence checking. Multiplexing of incoming data for different flows to applications on the same host (for example, TCP ports) is also performed. Flow control in this layer ensures that the transmitting device does not send more data [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The Transport Layer (e.g TCP) provides reliable delivery of Data by using error checking, acknowledgments, flow control, and sequence checking. Multiplexing of incoming data for different flows to applications on the same host (for example, TCP ports) is also performed. Flow control in this layer ensures that the transmitting device does not send more data than the receiving device can process.</p>
<p><!--adsense--></p>
<p><strong><u>Examples of Layer 4 Specifications and Protocols</u></strong><br />
• TCP<br />
• UDP<br />
• SPX<br />
• Port Numbers (e.g 80 for HTTP) <!-- InstanceEndEditable --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-4-transport-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 3: Network Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-3-network-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-3-network-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 17:47:36 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-3-network-layer/</guid>

					<description><![CDATA[This Layer defines logical addressing (e.g IP address) in order to identify each endpoint in a network and provide end-to-end delivery of packets. Think of the Network Layer as the postal service in a country. When you want to send a letter to a friend, you just need to know the destination postal address (e.g [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>This Layer defines logical addressing (e.g IP address) in order to identify each endpoint in a network and provide end-to-end delivery of packets. Think of the Network Layer as the postal service in a country. When you want to send a letter to a friend, you just need to know the destination postal address (e.g destination IP address) and you send the letter. The postal service (e.g the Network Layer) will determine the path to the destination (e.g IP Path Determination) and take care of the delivery (e.g using IP Routing). The two endpoints do not need to know the exact path taken for the delivery of the letter.</p>
<p><!--adsense--></p>
<p>This Layer also encapsulates data into Packets, and defines how to fragment a packet into smaller pieces to accommodate media with smaller Maximum Transmission Units. An IP Router works in this Layer, since it can use the IP address information to route packets.</p>
<p><strong><u>Examples of Layer 3 Specifications and Protocols</u></strong><br />
• IP<br />
• IPX<br />
• AppleTalk <!-- InstanceEndEditable --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-3-network-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 2: Data Link Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-2-data-link-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-2-data-link-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 17:44:48 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/2008/03/05/osi-layer-2-data-link-layer/</guid>

					<description><![CDATA[The Data Link Layer provides error detection and error recovery of the data flowing across the physical network link. The Specifications in this OSI Layer define network and protocol characteristics such as Physical addressing, network topology, error notification, flow control etc. The physical addressing defined in this layer determines how devices are addressed on the [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The Data Link Layer provides error detection and error recovery of the data flowing across the physical network link. The Specifications in this OSI Layer define network and protocol characteristics such as Physical addressing, network topology, error notification, flow control etc. The physical addressing defined in this layer determines how devices are addressed on the data link layer. An example of physical addressing is the MAC address which is hard-coded in all Ethernet Network Interface Cards (NIC). Each Ethernet NIC that exist in the world has a unique MAC address. The Data Link Layer also combines bits into Frames. Each Frame has a Layer 2 Header which includes the Source and Destination MAC addresses among other fields.</p>
<p><!--adsense--></p>
<p><strong><u>Examples of Layer 2 Specifications and Protocols</u></strong><br />
• IEEE 802.3 Ethernet<br />
• HDLC<br />
• Frame Relay<br />
• ATM<br />
• PPP <!-- InstanceEndEditable --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-2-data-link-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OSI Layer 1: Physical Layer</title>
		<link>https://www.networkingreviews.com/osi-layer-1-physical-layer/</link>
					<comments>https://www.networkingreviews.com/osi-layer-1-physical-layer/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Tue, 04 Mar 2008 20:30:11 +0000</pubDate>
				<category><![CDATA[OSI Layers]]></category>
		<guid isPermaLink="false">https://www.networkingreviews.com/blog/2008/03/04/osi-layer-1-physical-layer/</guid>

					<description><![CDATA[The Physical Layer defines the Electrical, Mechanical, and functional specifications of the physical link used to connect the communication device on the network. This layer defines characteristics like voltage levels, data rates, maximum transmission distances, connectors etc. The specifications in this Layer can be categorized as LAN or WAN: LAN Specifications Examples: • Ethernet • [&#8230;]]]></description>
										<content:encoded><![CDATA[<p>The Physical Layer defines the Electrical, Mechanical, and functional specifications of the physical link used to connect the communication device on the network. This layer defines characteristics like voltage levels, data rates, maximum transmission distances, connectors etc.</p>
<p>The specifications in this Layer can be categorized as LAN or WAN:<span id="more-27"></span></p>
<p><!--adsense--></p>
<p><u><strong>LAN Specifications Examples:</strong></u><br />
• Ethernet<br />
• FDDI<br />
• Token Ring</p>
<p><u><strong>WAN Specifications Examples:</strong></u><br />
• V24<br />
• V35<br />
• X21<br />
• EIA/TIA-232 <!-- InstanceEndEditable --></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.networkingreviews.com/osi-layer-1-physical-layer/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
