Except in the case of OSI, it's not a reputable analytical tool from the perspective of actual academics; it's rather a discredited one. Instead, it's only lay-people with an outdated view of the state-of-scientific-practice who attempt to apply the discredited tool. And this article is an attempt to get those lay-people to stop doing that.
Compare/contrast how the layman may often think that Freudian psychoanalysis is still in use in psychiatry — and may even try to apply it themselves to understand someone's motivations. Much to the chagrin of psychiatrists.
The issue is about education. People teach the model, or some variation of it. It teaches misconceptsion, such as how Ethernet and the Internet are integrated in a single network stack rather than being independent networks. It leads to professionals in IT and cybersecurity who continue to hold this misconception.
It really opened up a whole world of understanding for me when I decided to find out what happened when I searched "RFC 1." It made me realize that "the birth of the Internet" as we know it, was essentially the moment of the deployment of the first network switch (the BB&N IMP), isolating physical networks' electrical properties and collision domains from one-another and using DSPs to arbitrarily re-write packets between different signalling standards — thus rendering uniformity of physical/electrical media and LAN signalling standards, completely irrelevant.
Until that moment, I had always thought of "the Internet" as a thing that grew like a social network, with people "switching over" from using whatever networking equipment and signalling they had been using, to using Internet networking equipment and standards. But no! The whole clever thing about "The Internet" is that it didn't do that! It just took all the random proprietary networks that people had built, and connected them together, by coming up with a set of standards for how the networks would speak to one-another at their border gateways, and leaving everything else up to implementation!
And, in that view, the whole "layer separation" concept — of there being such a thing as an "IP packet" that bubbles up to userland separately from any delivery enveloping — wasn't fundamental to The Internet; in fact, existing protocols that were vertically integrated continued to work, being rewritten into something else when they reached the AS border gateway. The "layer separation" was an optimization to allow new "post-Internet" protocols to get by without AS-border-gateway packet rewriting, rather just re-enveloping, by separately standardizing "the contents of the envelope" and abstracting away "the envelope itself." But network stacks continued to support non-layer-separated communication for decades afterward!
It's really unfortunate that folks have stopped learning about it. It makes troubleshooting connectivity issues so much easier and collective knowledge of OSI helps immensely with triage and communication.
Counterpoint: DDoS attacks are routinely described as "layer 3" or "layer 7" attacks.
And if you're in the kind of industry that goes in for certifications, the OSI model comes up pretty frequently in networking exams, especially at the entry level.
I have no idea why we continue to use thes numbers instead of saying the protocols or a more descriptive name, like transpory layer or application layer.
Moreover, I have not heard anyone but myself utter the word "OSI" out loud in 8 or 10 years. Maybe it's still a thing in academia, but it's not in corporate or open source worlds. I don't know if I've met more than 2 people in 5 years that know how TCP works. It's just a magic tunnel that HTTP somehow uses under the covers. So I really don't get the need or purpose for this document. It's like describing in excruciating detail that what you know about the ancient Egyptians is a lie, because that's somehow going to be necessary for somebody?