I mentioned two theoretical models, and you can see them here represented in blue. It looks really complicated, but we will break this down into manageable chunks. There are two broad models that we see in use. On the right-hand side, we see the TCP IP model. This is a really old longstanding model that separates networking out into four layers. My advice here is to keep an awareness of this model. This isn't a model that we use professionally day to day. But it's important because as you can see on the TCP IP protocol suite, a lot of those protocols we still have in use day to day. We still have commonly referenced. Things like mail or file transfer, are things that we would still use today. We have some protocols listed, there TCP and UDP that we will talk about a little bit later in the chapter, and some underlying topologies as well. The TCP IP Model separates our networking out into the network interface layer, the Internet layer, the transport layer, and the application layer. The OSI model by comparison has seven layers, and we'll start with the physical layer. This is the actual medium. We're connecting to, we're sending our data across the data link layer, Layer 2 deals with getting our data onto the network. The network layer routing, transporting our data across those networks. The transport layer forming resilient or non-resilient connections with another endpoint. Session layer, Layer 5 the session layer, forming logical sessions, setting them up, managing them, and then tearing them down at the end. The presentation layer is all about getting your data, looking right for the system. Presenting your data in a way that makes sense for the application layer and the presentation layer is all about encoding. Encoding is not the same thing as encryption. Encoding is formatting. We might want an image to be formatted as a JPEG. Interestingly, for us, in terms of security at the presentation layer, this is where we see most of the encryption occurring. After all, encryption is a form of presentation. We're presenting our data in a way that is non-readable or way that is readable. We're presenting this data so that as the data moves up to the application layer, it can be passed on to the application. Just a point of warning here, the application layer is not the application itself. Now as we go through the module, we will go through each of these seven layers in turn. Please don't panic now there's an awful lot to take in on this slide. But what I would say is by the end of the chapter, be familiar with this seven-layer model and be able to reference Layer 2, is the data link, Layer 5, know the layers, be able to correlate that number with what it does, its purpose and its name as well. Layer 5 is the session layer, Layer 6 is the presentation layer, and so on. What we see in the bottom diagram we will discuss on this slide. This is the OSI model. OSI stands for Open Systems Interconnect. It's an open model and it's supported, maintained as an international standard, an ISO. This is commonly referenced as the ISO model. It's a palindrome, reads the same backwards as forwards. Each of the seven layers then provides a specific function. The numbering starts at the bottom and moves upwards. There are different traffic types, addresses, and devices associated with Layers 2, 3, and 4, and I will stress those different traffic types, addresses, and devices as we cover each of those different layers. Now, I think there is a really good way to remember this. There are lots of different mnemonics that you can use to help remember this model. We have starting at the bottom, starting at Layer 1. Please do not tell salespeople anything. As a mnemonic and easy way to remember, please do not throw sausage pizza away. There are endless variations of these. You may know some already. But what I would suggest is find something that works for you in terms of helping you to remember these seven layers. Most networking engineers will be able to tell you one of those mnemonics. Because when you first approach this model, it's typically what you learn. What you see on the right-hand column in the diagram is a process of encapsulation. We can think of this as being similar to Russian dolls. Inside one doll, you find another. Right at the heart, you have the smallest doll. What we do is we take our application data and we add a header, a presentation there. At the session layer, at the transport layer, we encapsulate it at each layer to make the data sensible usable at that layer. This is where we encounter those different traffic types. This is why we have those different traffic types. At Layer 2, we have frames, at Layer 3, we have packets, and at Layer 4 we have segments. Now we'll cover that and as we move through each layer, we'll talk about the traffic that addresses the devices. Again, don't worry about remembering it all right now.