<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>OSI Model by Nick Griffiths</title>
      <link>https://padlet.com/nickgriffiths141095/osiimodel</link>
      <description>Made with love</description>
      <language>en-us</language>
      <pubDate>2018-10-04 10:52:10 UTC</pubDate>
      <lastBuildDate>2024-05-24 20:04:57 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Layer 5 - Session Layer</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289078673</link>
         <description><![CDATA[<blockquote>The session layer is the fifth layer in the OSI model. It handles all of the connections between the computers. It can control these connections as well as track the dialog (sessions) between the computers.&nbsp;</blockquote><div><br>This layer also establishes the sessions between local and remote applications as well as controlling those connections. The session layer also creates procedures for check-pointing, restarting and termination.&nbsp;<br>&nbsp;</div><div>Sessions are commonly implemented on Web browsers using protocols such as AppleTalk and the Session Control Protocol. The session layer is also responsible for masking potential transport layer failures. The session layer creates a transmission bridge that can provide more efficient long-term transport. <br><br><mark>The functions of the session layer are to set up and manage the communication between two applications. The session layer also helps mask communication failures and manages data synchronisation of multiple session streams.<br>"yeet"</mark></div><div><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-04 12:17:59 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289078673</guid>
      </item>
      <item>
         <title>Layer 1</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079251</link>
         <description><![CDATA[<div>Layer 1 defines electrical and physical specifications for devices/nodes.  The physical layer takes what all the other layers have sent to them<br><br>The physical layer defines the relationship between a device and a cable. <br><br>the physical layer provides bit by bit delivery e.g binary, start stop signalling and flow control, circuit switching, auto negotiation and transmission mode control.<br><br>Binary is the language in which computers and their internal hardware communicates.  The circuits in a computer's processor are made up of billions of transistors which is a tiny switch that is a  some examples of protocols that use the physical layer are digital subscriber line (DSI), USB, Bluetooth, Controller Area Network. <br><br>Some of the major functions and services performed by the physical layer are:</div><ul><li>Bit-by-bit or symbol-by-symbol delivery</li><li>Providing a standardised interface to a physical transmission medium</li><li>Modulation</li><li>Line coding</li><li>Bit synchronisation in synchronous serial communication</li><li>Start-stop signalling and flow control in asynchronous serial communication</li><li>Circuit switching</li><li>Multiplexing</li></ul><div><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/320689505/72385c46f3fc0437f370074548f1e1d6/Figure28_1.png" />
         <pubDate>2018-10-04 12:18:59 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079251</guid>
      </item>
      <item>
         <title>Layer 3 - Network</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079299</link>
         <description><![CDATA[<div>The third layer of the OSI model is the network layer, it is the layer where the switching and routing of packets takes place. Routers and switches are devices that perform packet routing and switching on this layer.<br><br>Packet switching is when a file is broken down into separate packets, and each packet has information such as the destination address, the source address, the total number of packets and the sequence number. After all the packets have been received, they are rearranged to form the original file.<br><br>In Internet Protocol All devices will have an IP address assigned to them for communicating on this layer with IP.<br>There are other types of network layer protocols but they are not commonly used due to the widespread usage of IP<br><br> The network layer also handles addressing packets to the corresponding MAC (Media access control) address, so the packets know what device they are being routed to. <br><br>Overall, the network layer of the OSI model is responsible for routing packets to the right place</div>]]></description>
         <enclosure url="http://ciscocontracting.files.wordpress.com/2010/08/ip-packet3.jpg" />
         <pubDate>2018-10-04 12:19:04 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079299</guid>
      </item>
      <item>
         <title>Layer 2 - Data Link</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079313</link>
         <description><![CDATA[<div>The Data Link Layer is divided into 2 sub-layers, the Logic Link Control sub-layer, and the Media Access Control sub-layer.<br>Logic Link Control<br>The LLC sub-layer's is responsible for the exchange of data between the nodes on a network.&nbsp;<br>Its main function is to manage the data and to make sure it is consistent and accurate, however it is also responsible for error-checking, and it checks each packet sent for errors, and if there is an error, then it asks for the data to be resent.<br>Media Access Control</div><div>On a network, the MAC layer will provide a MAC address for the computer, so that the NIC that the computer has will be recognised specifically - this means that the data will be sent to that MAC address. from the other computer's NIC.&nbsp;</div><div>The MAC layer is responsible for moving data packets from a Network Interface Card (NIC) to another NIC across a channel.<br>Overall<br>Basically the Data Link Layer gets the data and records the MAC address it came from and is going to, then checks for errors and to make sure the data is consistent and accurate, and then it sends it to the network layer.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/320689481/487bc5ddd85afbcb028ad655a67b36fc/data_link_layer.jpg" />
         <pubDate>2018-10-04 12:19:06 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079313</guid>
      </item>
      <item>
         <title>Layer 7 - Application Layer</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079571</link>
         <description><![CDATA[<div>Only layer that interacts directly with the end user<br>The pass of control in the OSI model starts at Layer 7<br>The services which are provided by this layer can consist of:<br>- File transfer<br>- SMTP (Simple mail transfer protocol)<br>- Web chat<br>- Web surfing<br>- Email clients<br>- Network data sharing<br>- Virtual Terminals<br>DHCP - Dynamic Host Configuration Protocol is used to provide an Internet Protocol host with its IP address. (assigns and IP address to each device) <strong><em><mark>According to all known laws of aviation, there is no way a bee should be able to fly. Its wings are too small to get its fat little body off the ground. The bee, of course, flies anyway because bees don't care what humans think is impossible.</mark></em></strong><br>HTTP- This stands for Hypertext Transfer Protocol. This being one of the most important protocols is the foundations of the WWW. HTTP is used as a request-response protocol. The importance comes from the amount of communication it enables between client and server.<br>The application layer relies on the rest of the layers/levels to complete these processes.<br><br>SMTP - Simple Mail Transfer Protocol - the standard for email transmission. It's always used by all mail servers when sending or receiving mail outside their own systems. There are three key command/reply sequences.<br>-MAIL, to establish the return address.<br>-RCPT, the recipient.<br>-DATA, the content of the mail.<br><br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/315582176/41db161711ec894d03da191dc706f9a5/application_layer_326x245.jpg" />
         <pubDate>2018-10-04 12:19:34 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079571</guid>
      </item>
      <item>
         <title>Layer 4 - Transport</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079873</link>
         <description><![CDATA[<div>In the OSI model Layer 4 is&nbsp; known as the Transport Layer, and it's job role is for transferring information/data reliably between two endpoints&nbsp; and this essentially deals and helps with picking up on errors such as deleted or duplicated packets. The required protocol properties is that it's fast, low overhead, does not require acknowledgements, does not resend lost data, delivers data and delivers the date as it arrives.&nbsp;<br><br>It is good for traffic control and processing so there's no crashes. It makes sure the packet is securely transported and makes sure the packet is sent to the correct destination/IP.&nbsp;<br><br>In cases where TCP is being used, packet segments that have been destroyed or lost in transit are re-transmitted to ensure that all of the data reaches the destination in tact so that when the packets are reassembled parts aren't missing.&nbsp;<br><br>The transport layer is also responsible for segmenting data as it is sent out and reassembling it when it is received.<br><br></div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/320689764/9f934b891af737dbd2d04f8db8f3eaed/packtrav_layer_4_1024x555.png" />
         <pubDate>2018-10-04 12:20:13 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079873</guid>
      </item>
      <item>
         <title>Layer 6</title>
         <author></author>
         <link>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079921</link>
         <description><![CDATA[<div><strong><em><mark>The presentation layer</mark></em></strong></div><div><strong><em><mark>It is par</mark></em></strong><strong><mark>t of the hot layer aspect of OSI model that covers applications, presentations and session/transport  layers  etc.</mark></strong></div><div><br></div><div><strong><em><mark>Simple Version:</mark></em></strong></div><div><strong><em><mark>Residing at L</mark></em></strong><strong><mark>ayer 6 of the Open Systems Interconnection (OSI) communications model, the presentation layer ensures that the communications that pass through it are in the appropriate form for the recipient application. In other words, it presents the data in a readable format from an application layer perspective. </mark></strong></div><div><strong><mark><br>Example:<br>For example, a presentation layer program could format a File transfer request in binary code to ensure a successful file transfer. Because binary is the most rudimentary of computing languages, it ensures that the receiving device will be able to decipher and</mark></strong><strong><em><mark> translate it into a format the application layer understands and is expecting. <br></mark></em></strong><strong><mark><br>In areas of security it has  data encryption and decryption: Encryption is needed for security purposes when sending data across networks. <br>Encryption and decryption typically involves the secure sockets layer (SSL) protocol, which has become more popular when used by the presentation layer. </mark></strong></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-04 12:20:19 UTC</pubDate>
         <guid>https://padlet.com/nickgriffiths141095/osiimodel/wish/289079921</guid>
      </item>
   </channel>
</rss>
