Re:Email could have been X.400 times better
by chuckadams on Friday April 24, 2026 @05:54PM
(#47896282)
There's an entire book devoted to ripping up the OSI model: https://docs.google.com/document/d/1iL0fYmMmariFoSvLd9U5nPVH...
Re:Email could have been X.400 times better
by MrDrMcCoy on Friday April 24, 2026 @08:38PM
(#47897495)
Everyone who knows what the OSI model is should read at least some of this book.
Re:Email could have been X.400 times better
by matheusmoreira on Friday April 24, 2026 @11:52PM
(#47898486)
What an interesting read. Thank you for posting it.
Re:Email could have been X.400 times better
by bombcar on Saturday April 25, 2026 @08:21AM
(#47900870)
The OSI model and its consequences have been a disaster for the networking race.
Re:Email could have been X.400 times better
by pseudohadamard on Friday April 24, 2026 @09:58PM
(#47897950)
X.500 was stripped down to form LDAP
No, LDAP was a student project from UMich that somehow gained mindshare because (a) it wasn't ISO, and (b) it cleverly had an 'L' in front of it. It's now more complex and heavyweight than the original DAP, but people think it isn't because of that original clever bit of marketing.
Re:Email could have been X.400 times better
by lukeh on Saturday April 25, 2026 @01:40AM
(#47898977)
Well, it started off simpler, but, yes.
Re:Email could have been X.400 times better
by otabdeveloper4 on Saturday April 25, 2026 @07:23AM
(#47900560)
It's still lightweight. I implemented a working implementation on a literal weekend.
Re:Email could have been X.400 times better
by pseudohadamard on Sunday April 26, 2026 @12:15AM
(#47907283)
That's certainly possible, you can get a basic implementation that uses it as a database lookup, "search" with baseObject/scope fixed, filter is your search string, return the attribute you want, done without too much effort. In fact a number of early LDAP databases were actually DBMSes underneath, so you take your SQL-style query (select emailAddress where name = "John Doe"), convert it into baseObject/scope/filter/attributes and send it over the wire, the other side converts it back into an SQL query and queries the Ingres database that's doing the actual work, and everyone gets to pat themselves on the back over how well "a bunch of networking types reinventing 1960s database technology" (Marshall Rose, I think) works.
However when you need to implement the whole HDAP protocol, that's when you wish you'd taken up some easier job, like maintaining the bank's COBOL accounting code.
X.509 absolutely lives on -- https://www.itu.int/rec/t-rec-x.509 last update was October 2024. However WebPKI uses PKIX which is fairly stubbornly stuck on RFC5280.
On the ITU side, they have made improvements including allowing a plain fully qualified domain name as the subject of a certificate, as an alternative to sequence of set of attributes.
Re:Email could have been X.400 times better
by tosti on Saturday April 25, 2026 @01:24AM
(#47898891)
If you mean the presentation layer, hard disagree. Not thinking about presentation creates problems. For example, Go treating ASCII headers as UTF-8 caused trouble. Only slightly not worrying about an HTTP/2 vs HTTP/1.1 mismatch caused trouble for reverse proxies.
Now I'm young enough not to have seen teletypes in an actual production use setting, but I've never heard anyone suggesting the presentation layer was for teletypes. That's just Google-level FUD.
Re:Email could have been X.400 times better
by jcranmer on Saturday April 25, 2026 @01:39AM
(#47898973)
No, it was the session layer.
Re:Email could have been X.400 times better
by otabdeveloper4 on Saturday April 25, 2026 @07:22AM
(#47900553)
TLS is our session layer.
Of course, the biggest--and weirdest--success of the ITU standards is that the OSI model is still frequently the way networking stacks are described in educational materials, despite the fact that it bears no relation to how any of the networking stack was developed or is used. If you really dig into how the OSI model is supposed to work, one of the layers described only matters for teletypes--which were are a dying, if not dead, technology when the model was developed in the first place.