16 ms·
The Actual OSI Model
- hyperman1 6y agoI once implemented a part of RFC1006, a way to use ISO protocols on the internet. It contains gems like: In migrating from the use of TCP/IP to the ISO protocols Whoever wrote that RFC seemed to think of the internet as some temporary stopgap measure until responsible adults found the time to implement a real network protocol. My main takeway was: Thank god the internet won, OSI was some badly specified eldritch horror. RFC1006 was the only spec that seemed more or less readable by a human being.
- unmole 6y agoThe only ISO protocol that seems better designed than its IETF counterpart is IS-IS. Which is why it is still widely used. The spec is still hopelessly unreadable though.
- bombcar 6y ago"ISIS" is an unfortunate name for a Protocol.
- unmole 6y agoIt's pronounced IS-IS. The hyphen is important.
- deleted 6y ago[deleted]
- ASalazarMX 6y ago"ISIS" is an unfortunate name for a Protocol, please change it. Yours truly: Mr. Bombcar
- jcrawfordor 6y agoThis was supposed to be in the article but, I'll be honest, I wrote it over a vacation and stopped and started several times and some things got lost in the shuffle. I find IS-IS particularly interesting because, to summarize somewhat aggressively, TCP/IP first went into use basically without any working gateway protocols. So in early IP networks it was very common to use a full chunk of the OSI layer (IS-IS and CLNP) just to use IS-IS with IP prefixes shoehorned in, as the "IP" gateway protocol. OSPF is basically exactly this but formalized and running IS-IS over IP so you don't need the lower OSI layers. I'm sure there are still some IP networks out there today using the OSI stack for promulgating IP routes, it seems to still be well supported by all the vendors.
- p_l 6y agoBecause IPv4 was a temporary, stopgap solution. That's why it has 32bit addressing, when by late 1980s the need for larger address space for Internet was already well understood (that's partly why OSI does 20bytes for address). The spec is wordy, but CLNS and TP4 differ little from IP and TCP, except for TP4 not having legacy of being a dumb emulated serial port, so it has message framing. Most of verbiage comes from the part that OSI took pains to handle a lot of problems upfront instead of saying "eh, it's temporary, let's go shopping", and writing standards with strict requirements tended to have certain verbiage allowing one to specify in minutiae what was missing from implementation, with no Postel around to promote lax handling. N.B. a pretty serious (and implemented on Cisco and Sun) proposal to fix the already-known addressing problem of IPv4 was TUBA - which is essentially TCP running on top of CLNS.
- HourglassFR 6y agoAgree, the OSI model was what smart people who thought deeply about the issue decided we should do. Unfortunatly the timing was bad and the coherent model emerged just a bit to late. Maybe if the major networking infrastructures had been in Europe a switch could have been a possibility. Americans are very pragmatic: make the stuff work and get on with your life, if problems arise in the future we will fix them. American standards are usually but a formalisation of already accepted practises (and this goes well beyond network stuff), this is why they are so effective and so poorly thought out. I guess it's still better than "ideals" that nobody follows. And of course this is an oversimplification of some sensitivity difference between vast parts of the world, we individuals are but samples on the agregate sociological context that drives this sort of things.
- simiones 6y ago> he OSI model was what smart people who thought deeply about the issue decided we should do. And yet, they came up with 2 layers of stuff that only a limited number of applications actually use (session, presentation), 2 protocols instead of one at layers 2 and 3, a much more complex layer 4 protocol. The application side of network programming would likely be much more difficult if we had used an OSI network instead of TCP/IP.
- ggm 6y ago> RFC1006, Marshall Rose. he's a fantastic coder, and wrote the Open Book and the Simple Book and has done a lot of work in protocols, and IETF standards. I have a lot of time for Marshall. he did a lot of work on MH, the mailsystem I used for years. The Simple book is why we have SNMP and not CMIP (in some ways)
- imwillofficial 6y ago"I have said before that I believe that teaching modern students the OSI model as an approach to networking is a fundamental mistake that makes the concepts less clear rather than more." Oh my Jesus, this, so much this. This was a great, well written article. Even as a network engineer, I learned some things. Never hurts to study the fundamentals.
- centimeter 6y agoI don't really object to the first 4 layers of the OSI model as applied to the current network stack - it's a pretty useful model of the separation-of-concerns between, say, Cat5, ethernet, IP, TCP.
- jnwatson 6y agoThose are indeed 4 layers, but, as the author points out, those don’t map onto the bottom 4 layers of OSI cleanly.
- jcrawfordor 6y agoThe biggest thing I would point out here, which I only mentioned briefly in the article, is the division of layer 2 into the MAC and the LLC "sublayers". This is received wisdom today that is frequently repeated in textbooks and courses, but this whole concept of "sublayers" was invented (and then formalized into standards!) to resolve the OSI model's poor correspondence to many non-OSI technologies like Ethernet II and 802.11*. Not only does the OSI model have "too many" layers, it also has "too few". So this is a major way in which the OSI model is not some "idealized" or "genericized" model like people often claim, but rather an alternative model that is sometimes similar, sometimes different from TCP/IP.
- jnwatson 6y agoIt reminds me of the taxonomy of living things. The 8 levels (Domain, Kingdom, Phylum, ...) are useful at the top, but break down fairly quickly as we've learned how complicated life really is. The last plant I looked up (Wisteria) doesn't really have a useful phylum or class classification, and has 7 non-mappable "clade" groups of which it is a member. They still teach the 8 levels though.
- allending 6y agoFor a useful introduction to network layers, Radia Perlman explains the actual layers and how to think about them pragmatically: https://youtu.be/qXz_RxBFQ20?t=496 https://youtu.be/qXz_RxBFQ20?t=496
- walrus01 6y agoThe part about CSMA reminded me that as an educational model, a lot of what can go right, or wrong with an 802.11(abgn/ac/ax) network is at what we would call layer 2. If you've ever seen an environment that's a CSMA hell of -70 noise floor in 2.4 GHz and devices stomping on each other, or a poorly configured "mesh" network, that's all layer 2. Thinking about things like, how are your design constraints different when dealing with a half duplex/TDD air medium, vs something like a traditional FDD point to point microwave radio? But then as a mental model in order to understand that, it's important to think about the layer 1 of what the wifi radios are doing: Questions such as, why is this Comcast 802.11ac home router running in an 80 MHz channel, stepping on this other device that's also trying to run in the same 80 MHz channel? Why did somebody install a unifi AP with a torus shaped RF pattern vertically on a wall, instead of horizontally on a ceiling as it was intended?
- bombcar 6y agoI wish more devices came with diagrams showing the RF pattern - I honestly have no idea how I’m supposed to orient the antennae on my Mikrotik.
- walrus01 6y agowhat model do you have? If it's an all-in-one router like a HAP AC, it should be horizontal, best coverage would be if it were flat on a wood shelf or similar.
- bombcar 6y agoIt’s one of the ones with adjustable antennae - RB4011iGS+5HacQ2HnD-IN-US - and based on the pictures I have them pointing “up”.
- junon 6y agoAgreed. To take it further, the OS APIs suck for protocol selection too. And router technologies. And basically everything. E.g. in theory your router should work with level 3 and below. This includes the firewall. However, try to implement a new Level 4 protocol and all of a sudden your packets won't route. This was the whole point of this separation - that while UDP and TCP are useful in general cases, there are much better and novel ways to frame packets for e.g. cust infrastructure with different properties and different requirements. But it simply doesn't work. This stuff has driven me nuts for decades. OSI has rarely been helpful aside from just general communication of ideas. It shouldn't be used as any authoritative reference, ESPECIALLY not in classrooms.
- walrus01 6y ago> E.g. in theory your router should work with level 3 and below. If you look at the configuration on a typical small but powerful router (I'll use a Juniper MX204 for an example), of course it's doing things at both layers 2 and 3. It's a useful model to define what is going on with various ethernet switch fabrics, before you try to understand how it's set up at layer 3. At layer 2 you could have a 100GbE interface that carries a vlan trunk going to a 1RU 48-port switch physically adjacent to the mx204, to create local subinterfaces on the router to 10Gbps PNI peers, to downstream colocation/datacenter customers, etc. That's all traditional "layer 2" ethernet stuff. Then your logical subinterfaces themselves are configured as BGP peers, which is of course layer 3. Understanding the model of your theoretical MX204 you've got: layer 1: AC or DC power, cabling, fans, physical mounting, serial console cables also layer 1, but has an impact on how you can configure stuff at layer 2: Does this port have a short reach 100GbE CWDM4 interace in it? Or a longer reach coherent? Maybe this 10GbE port has a 1490/1550 bidi single strand in it? layer 2: Ethernet configuration in all its myriad ways. And also things like P and PE MPLS configuration to carry a layer 2 circuit between places over your layer 3 network. Configuration for ISIS would also go in layer 2. layer 3: bgp, ospf, all the typical "router" stuff.
- comex 6y agoI believe the parent isn’t complaining that routers do things at layers 1-3, but that they also do things at layer 4 (namely, block anything that isn’t TCP or UDP).
- bombcar 6y agoThis makes me feel quite a bit better at never really understanding the OSI mapping - that it doesn’t really map clears things up nicely. Vestiges of the presentation-layer like stuff exist in ntohs() and friends.
- jimmar 6y agoThe quote, "All models are wrong, but some are useful" comes to mind. The OSI model is useful but far from perfect. But you'd be doing students a disservice if you don't teach them about it at a minimum because the OSI model is part of the networking vernacular.
- slaymaker1907 6y agoI think there are good arguments to be made that the OSI model has too many layers to be useful. My favorite description of the IP networking model is that IP is the "narrow waist" of internet protocols. Lower levels can vary and upper levels can vary, but IP remains constant (which is why IPv6 is such a nightmare whereas all the other protocols below and above IP have changed significantly with less effort).
- jcrawfordor 6y agoThe main utility the OSI model has served me is being able to recite it for job interviews. More honestly, though, I think the OSI model can be used very constructively in teaching by contrasting it with IP. IP is simpler and also less feature-rich; you can learn a lot about IP by noticing which aspects of the OSI model were "left out" from IP (putting it that way muddles the timeline but probably also isn't that inaccurate) and how it varies from what was designed at one point as a "complete" protocol set. But this is all a part of my larger philosophy of a "historical approach" to teaching networking. It's not too uncommon for instructors to do this by discussing X.25 and/or ALOHA early on and then comparing/contrasting IP, but for whatever reason it is typical to introduce the OSI model alongside IP without the historical context of what the OSI model is and isn't useful for today.
- walrus01 6y agoI disagree about it not being a useful model for teaching stuff. In particular as a facilities based ISP, you have to care about what the OSI layer 1 is, because ultimately an ISP is built out of real world physical things. The article seems to skip over concerns about layer 1. But if you have no understanding of how things are engineered at layer 1, or of the possible failure modes, all sorts of bad things can happen. Or you'll end up buying the wrong thing, or getting bamboozled by equipment vendors once they realize you're not paying attention to the layer 1. People not understanding layer 1 are how things happen like an ISP sending out somebody to try to install a 10GbE 1310nm/LX circuit to a piece of equipment that was shipped with a multimode SFP+ in it. Engineering of large complex backbone systems encompasses the overlap between layers 1 and 2. For instance all of the optical engineering that goes into a inter-city DWDM system is "layer 1" - but those same DWDM chassis have 10/100GbE short reach layer 2 transport circuits hanging off of them, to connect to your own ISP's or customers' ISPs' network equipment. Then the controller card in your DWDM system is likely running some form of embedded Linux and has a 100BaseTX/1000BaseT interface in it with an IP address in a management network, it can have an snmpd on it that exposes a set of OIDs to poll by network monitoring gear, it runs an sshd on it it, etc. So you've got layer 3 and layer 4/5 stuff going on in that same 10RU DWDM box which needs to be taken into account in your network design. Maybe you have a system somewhere which periodically retrieves a text dump of the entire configuration of the DWDM box, whatever its equivalent of a 'show run' is, and stores it in git? That's all layers 4-7. In the modern all-ethernet world, tons of possible configuration parameters for exactly how the 10 or 100GbE handoffs are set up on each side. And various configuration parameters. Ever encountered somebody who mistakenly ordered a 10GbE WANPHY circuit when it should have been LANPHY, or vice versa? That's an example of why an understanding of the underlying layers of what you're working on is important. Only once you have a good solid grasp of layers 1 and 2 can you begin to properly architect your network at layer 3. One thing that I do try to repeat as often as possible, if helping to train NOC and junior neteng people, is that things get very blurry between how software is set up at layers 4-7. The same piece of software that might be doing things at what the OSI model would call layer 4 may also have a end user GUI/presentation/operator interface that would be defined as layer 7. I do not think that mentally imagining rigid definitions between layers 4-7 is very useful these days. I personally think that as a method of understanding network architecture, the first level of layers 1-3, and 4, are much more useful than the blurry "4-7" model.
- croes 6y agoAnd what is the actual OSI model?
- rtpg 6y agoDoes anyone have book recommendations for like a complete covering of how we get the lower layers working for networking? I believe I understand stuff in isolation but every time I read a full thing I get a lot into “wait but why am I not worrying about packet ordering issues when doing random socket stuff with Python” style existential dilemmas Thinking of something that might be equivalent to “NAND to Tetris” for networks. I want to know how the wires work fully!
- zamadatix 6y agoThe data on the wires really varies too much to cover like a nand2tetris where you can walk through one way to do it from the ground up and call it good. Generally if there is a way to transmit data it's possible and probably your socket could go over it or some combination. Even taking a narrow scope such as "copper cables carrying ethernet" leads to various collision algorithms, encodings, wire counts, and optional components like PoE to consider and that's not counting "copper cables with something else that can transport encapsulation ethernet data efficiently". Generally though you really don't care about how the data gets on the wire (I mean it's definitely interesting but it doesn't help you any more at a practical than thinking about what happens at the ethernet frame layer). Also when it comes down to it not only is the physical encoding wildly different most each step of the way but it's not even ethernet. I.e. the only thing that matters are the guarantees of the socket interface, not the guarantees of what it rides over. The socket may ride over some transport which guarantees in order delivery and no congestion or it may ride over some transport which guarantees nothing, not even in order delivery. What matters is what the socket guarantees, e.g. is it a TCP socket provided by the OS where the OS guarantees it'll reassemble, handle loss, handle out of order, etc for you or is it something like a UDP socket which leaves most of these up to you (or a raw socket where the OS really isn't doing much of anything for you). That being said if you want to pick a single example just to walk through it bottom to top one time pick 1G RJ45 copper between two PCs which have a TCP session going. There isn't really a need for a book, just the Wikipedia articles on gigabit Ethernet, IPv4, and TCP. It's just that this isn't always the stack so it doesn't really matter what Ethernet/IPv4 happen to give you - all that matters is what the TCP socket says it's going to guarantee.
- thequux 6y ago
- iJohnDoe 6y agoAnyone else notice how fast the site loaded?
- bombcar 6y agoIt skipped 3 of the layers. ;)
- b0afc375b5 6y agoSlightly OT but the header ascii art is broken on mobile. Had to switch to Desktop View for it to render correctly. Edit: Just finished reading. As someone who has been putting off learning about the network stack, I'm glad I read this.
- jcrawfordor 6y agoI'm sorry, I've progressively improved the site behavior on mobile but the ASCII art is the one thing I haven't been able to figure out without compromising my "values" :) I could probably do something with CSS to swap it for a version that isn't sensitive to reflowing. I'll put it on the todo list.
- arthur2e5 6y agoMaybe just make it scroll horizontally and disable wrap? header > pre { overflow-x: scroll; scrollbar-width: none; white-space: pre; } header > pre::-webkit-scrollbar { display: none } (Some extra stuff is needed to hide the scrollbar. Apparently there's no way to make it appear only when needed, duh. Oh and the last line should probably have wrap enabled to show the links.)
- b0afc375b5 6y agoYou could also try placing on a for-mobile @media rule for mobile for the <pre> tag: font-size: 6px
- comex 6y ago> The X.509 certificate format and concepts are directly used today by TLS and other cryptographic implementations, including its string representations (length-prefixed) which were a decent choice at the time but now quite strange considering the complete victory of null-terminated representations. Er, what? What network protocols even use nul-terminated strings? Even if this is referring to programming languages’ native string types, nul termination only won in C, while just about every other language uses some kind of explicit length encoding.
- TeMPOraL 6y agoIndeed, and between buffer overruns and "accidental quadratics", null terminated strings gaining widespread adoption in core system APIs are probably the biggest and most expensive mistake of computing industry.
- avodonosov 6y agoI wanted to question this phrase too - length prefixing is so common in network communications
- peanut-walrus 6y agoSession - TLS Presentation - HTTP Checkmate, OSI-haters.
- jcq3 6y agoThat article starts with a mistake, historically OSI was created after TCP/IP so it's more OSI that is based on tcp/ip by extending it to a generic network architecture
- int_19h 6y agoThe article doesn't say that OSI was created before TCP/IP. It says that X.25 was created before TCP/IP, and that OSI is an abstraction of that particular design (and thus doesn't map neatly to the IP stack).
- jcrawfordor 6y agoThis was a very busy period in the history of computer networking, and many things happened at the same time, which can make it hard to make any statements about "x is based on y." The OSI model is most definitely not based on TCP/IP or vice versa. While TCP/IP was generally an earlier effort there were revisions being made to TCP/IP at the same time that the OSI model was being designed, and TCP/IP did not become the clear leader in computer networking until after the completion of the OSI work (arguably not until as late as the mid-'90s depending on how you feel about the issue of "WANs" vs "LANs" which often took different paths in the '80s). For most purposes they were parallel efforts, and the designers of the two were each aware of the other but mostly working off of different prior art. This further makes the point that many of the differences between TCP/IP and the OSI model were very intentional choices, as the OSI designers were well aware of IP and viewed it as unsuitable while the adopters of IP were judging the OSI model to be impractical.
- unixhero 6y agoI use the OSI model to discuss cyber security at work. As such learning it at a high level has been profitable for me.
- froh 6y agoyes! It's so helpful to make colleagues understand that encryption is not the job of the application, and that authentication is not encryption, is also delegated to a lower layer protocol. I am truly curious what critics of the OSI model propose as catalyst for such conversations. https://en.wikipedia.org/wiki/OSI_model#Comparison_to_other_networking_suites https://en.wikipedia.org/wiki/OSI_model#Comparison_to_other_...
- shp0ngle 6y agoedit: I replied to wrong post, ignore, cannot delete anymore
- ChrisMarshallNY 6y agoThat was a long post, saying something that I feel didn’t need as many words, but it is correct. I learned the OSI model, and it was presented as “And THE LORD sayeth ‘LET THERE BE SEVEN LAYERS.’ And it was good...” and so forth. It was presented as “This is the way we do things.” And I have never actually seen a true implementation of OSI “in the wild.” It was confusing. It was useful, in helping me to look at communications in an organized fashion (I’ve written a fair bit of that kind of stuff), but in the same way that reading historical fiction teaches me about the Victorian Era. I also learned X.400 as an exchange protocol. Folks these days, should give thanks at dinnertime that Professor Van Helsing drove a stake through that nightmare.
- Mauricebranagh 6y agoThere where in the wild implementations x.400 and x.500 I worked on them. And x.400 had stuf that internet mail took a decade to catch up to and some cases does not have non repudiation for example.
- ChrisMarshallNY 6y agoThis is true. I worked for a company that ran X.400 commercially, before the Internet really got going. It did, indeed, have many things that we wish email had, these days, like true read receipt and routing management. But it was a complex beast, and that is why it lost out to simple SMTP and POP.
- Mauricebranagh 6y agoOh cool which one
- ChrisMarshallNY 6y agoI normally don't mention the names of companies with which I worked in social media posts, but Dialcom has been dead a long time. I don't think it matters. They also used PRIMOS. I worked in FORTRAN (4), PL/1, and C.
- kabdib 6y agoYou could download the TCP/IP standards for free. The OSI standards were thousands of dollars, I believe; a classic Big Standards move. I think the writing was on the wall, right there. You're in college, what do you think the computer science folks are implementing and trying to improve, and teaching? Certainly not anything that cost real money, or that involved a towering bureaucracy, or language that no one could comprehend. I remember the Arpanet flip-over from NCP to TCP, and that was a big deal. The TCP community had early experience implementing and getting stuff running at scale (for the time), with real users and expectations that things would more or less stay working. "I hear they're moving to 42 layers, because it's a sacred number in Bali." -- Michael Padlipsky Nobody knew what those 7 layers were for. Nobody.
- Mauricebranagh 6y agoIts quite clear what the 7 layers where for. Your right that ISO's charging an arm and a leg for the printed docs was a mistake. And the big switch only worked because it was done during the summer holidays and you could shut down things whilst it was done. OSI would have not had the Omnishambles that is ipv6
- dtech 6y agoIt's clear what the 7 layers do, but not why there are 7, and not say 4 or 11.
- Mauricebranagh 6y agoSeven is what the OSI standard says :-) Some people say there is an eighth layer which is of course "Politics"
- sekh60 6y ago8th layer is generally the user in sysadmin circles
- kabdib 6y ago
- the_biot 6y agoThe best critique of the OSI layer model was the classic "To Hell with the OSI 7 Layer Model" post. It has disappeared from the current internet, with the exception of essay sites that stole it and now want money to reproduce, but the Wayback Machine remembers: https://web.archive.org/web/19990826193318/http://www.europa.com/~dogman/osi/ https://web.archive.org/web/19990826193318/http://www.europa...
- Jedd 6y ago> However, X.25 had significant limitations, and was married to the telephone network in uncomfortable ways (both in that it relied on leased lines and in that X.25 was in many ways designed as a direct analog to the telephone network). This is a bit harsh. I downloaded Minix updates, and indeed my first Linux kernel disk images, over an X.25 network. X.25 was one of the first packet-switching protocols - predating IPv4 by a few years - and therefore is very much NOT an analog to telephone (circuit-switched, predominantly, historically and at the time) networks. (Okay, there were VC's, let's not muddy the waters.) I recall in the early/mid 1990's a colleague hunting down a weird X.25 network utilisation pattern, where a customer was establishing and tearing down connections at a rapid rate of knots. Details are fuzzy, it was a long time ago, but IIRC the customer had worked out how to embed payload in the connection establishment header, but at the far end was refusing that connection (while ingesting the payload). Billing was done based on connection establishment and subsequent transfer. Great (loophole) success, etc. TFA touches on SNA (IBM's System Network Architecture) but doesn't seem to attribute as much blame to it as I believe we should. SNA was, coincidentally, a 7-layer model. The obvious distinction, to modern minds anyway, is the hierarchical vs peer relationship between entities on a network. (An interesting question to ask graduates is to define a network -- this historical view disparity is objectively fascinating in the contemporary context where peer addressability is an assumed function of same.)
- PaulAJ 6y agoThe OSI model was created by telecom people, not computer people. This is important because the two groups have radically different views of what networks are for and how they work, to the extent that they spent a lot of the 80s and 90s talking past each other. In the telecom world at that time the fundamental unit was the "circuit", meaning a two-way voice telephone call. The upper frequency limit of a voice circuit is 4kHz, so the Nyquist criterion said that digitising a voice circuit required 8,000 samples per second. The required signal to noise ratio fit nicely into 8 bits, so a digital circuit was 64,000 bits per second each way, with strong real-time jitter and latency guarantees (because, voice). If you weren't using the link for a while you still had to pay for it by the second because you were getting the guaranteed 64,000 bits per second all the time; that bandwidth was reserved for your use and nobody else could mop up the spare. Meanwhile the correctness of the received data was best-effort because the odd corrupt bit isn't an issue in a voice circuit. If you wanted more bandwidth then you could pay for multiple circuits to the same destination. In telecoms all the intelligence goes into the exchanges; the phone is merely a dumb end-point. If you want services like call forwarding you type numbers into the phone, but all the application software lives at the exchange. If you talked to telecom engineers about the future, they would talk about video calls. They would be just like phone calls but with higher bandwidth. Meanwhile the computer people needed the exact opposite to what a voice circuit provides. If you send a file another computer you need it to arrive bit-for-bit accurate, but you don't much care about bandwidth and latency. While a physical pipe has a certain capacity, you don't need or want to reserve bandwidth on it, you just want the data to move as fast as physically possible. So telecom people wanted to provide a smart network connecting dumb end-points, with guaranteed bandwidth and latency with best-effort correctness, while computer people wanted to connect smart end-points to a dumb network that provided guaranteed correctness but only best-effort bandwidth and latency. Things got worse when the Web started being used by people at home. Now most of the data was flowing in one direction, but circuits were fundamentally about equal bi-directional communication. So now half of that expensive bandwidth was being wasted. The "adults in the room" attitude of the telcos didn't help; they had over a century of experience running international telecom networks and thought they knew how to do it. Therefore they weren't interested in the opinions of those hairy computer guys. For more on this, read "Mother Earth, Mother Board" by Neal Stephenson.
- grymoire1 6y agoThe real problem was the core concept of isolating knowledge, i.e. Layer 2 doesn't know anything about layer 3. That's a flawed concept. The trivial, yet essential protocol ARP break the OSI model, for example. And then there's firewalls...
- jcrawfordor 6y agoI think I've said this before on computer.rip, maybe not, but I've joked that "ICMP is original sin" as it's kind of the start of a whole set of consistency-breaking aspects of the IP stack - ARP is another one. I still think layers are a useful concept but yes, it's clear that believing in them too much will get you in trouble. In practice developers have seldom hesitated to violate the layer boundary if it's convenient.
- api 6y agoI find OSI layers 1-3 to be fairly descriptive of how things usually work today. Layers 4-7 are worthless as real systems are not necessarily structured that way.
- jimmySixDOF 6y agoAnd that's why, almost 40 years later we have another HN front page post [1] right now saying the NMP package netmask, used by more thank 250K apps to handle all the esoteric standard conventions for notation in IPv4, this microservice got a few edge cases wrong and so everyone needs to update ! [1] https://news.ycombinator.com/item?id=26620538 https://news.ycombinator.com/item?id=26620538
- tristor 6y agoI actually found the OSI Reference Model to be incredibly helpful both as a student and later in my work life as an operations engineer. I was able to successfully break problems down in a methodical layer-by-layer approach to troubleshooting and find the root causes and solve extremely esoteric and difficult problems that other people, including very smart talented engineers, were completely stumped by. This wasn't because I was smarter or knew some secret, but because breaking problems down into smaller pieces and identifying and learning tooling to examine those problems in isolated pieces makes it easier to find the actual cause. While it is very true that the OSI Reference Model doesn't map to real life systems exactly, it's still a relatively accurate view with a little bit of hedging as to what layers something might fit into. Additionally many of the protocols that were built for OSI networks have been adapted and implemented on top of TCP/IP networks and are extremely valuable in some circumstances at global scale, because the telecoms people designing these systems /thought about/ global scale from the get-go, where-as it was mostly an afterthought for later computer systems researchers. X.500 in particular is a fantastic protocol, that while convoluted and esoteric, enables some very complex replication topologies while providing strong guarantees that are simply not possible in lighter weight protocols. When thinking deeply about identity management and authentication, X.500 is not a bad thing to fully understand, even if you end up implementing a lighter weight protocol, because while "over-engineered" it's well thought out. That said, ASN.1 notation is a hellacious curse and should have been burned and buried in the pit it came from before it ever saw the light of day. Unfortunately, it's a key component of nearly all the X. series standards built on top of OSI.
- gumby 6y ago> Teaching students about TCP/IP using the OSI model is like teaching students about small engine repair using a chart of the Wankel cycle. So true. Worse, it's useful to use an expression like "down below layer 3" knowing it's a rough metaphor; yet that credence gives credibility to what turned out to be a muddle headed idea. (Though anything above layer 7 is an inside joke)