Happy birthday TCP/IP!!!
- Thread starter FordSVT
- Start date
- Status
Still using Q-modem Pro..
Just tell the h4x0r's to go after 127.0.0.1.
What protocols were in use before 1983?
When the ARPANET first came online in 1969, it used NCP (Network Control Protocol). TCP (Transmission Control Protocol) was developed in 1974 to handle end-to-end communication, and then IP (Internet Protocol) was created in 1978 for device-to-device communication and packet routing.
The two protocols were substantially rewritten to work together as a protocol "suite" in 1981, and then in 1983 the new TCP/IP protocol became standardized on the ARPANET. That same year, TCP/IP was included in the communications kernel for BSD UNIX.
The two protocols were substantially rewritten to work together as a protocol "suite" in 1981, and then in 1983 the new TCP/IP protocol became standardized on the ARPANET. That same year, TCP/IP was included in the communications kernel for BSD UNIX.
That was for people lucky enough to be networked
For the rest if was things like xmodem and kermit on dialup.
Does anyone remmber the commericals Tom Baker (as the 4th Doctor) did for Prime Computers in the late 70s talking about the protocols the Primes had?
And while TCP/IP has been around 25 years it wasn't until the mid 90s and the internet taking off that it came in really wide spread usage.
Before then you had either Novell's IPX/SPX (for Novell Networks), and LanManager which then morphed in NetBui (iirc). TCP/IP support for Win3.x was an add but finally became a stardard component (though optional install) with Windows 95.
Can't remember if was NT or Win2k that marked the standardisation on TCP/IP and the demise of NetBui (though you still need NetBIOS).
Next step is will be moving the world to IPv6 (I'm wondering just how the hell I'm suppose to rember the v6 addresses
A
Amaris
Guest
J.
My greatest moment in the history of networking was when I managed to play Doom against my brother. My old Computer with MS-DOS against his with Windows, connecting different operating systems... But that was done with IPX, for which I only found the DOS-driver in a pir8ted distribution of Quake... And even today, the copy of Quake 3 Arena I purchased is running on the computers of several friends, and those of my brothers... Oh, the joy.
Ah, the trip down memory lane. In addition to IPX/SPX (for Novell junkies, er. users) and NetBeui, there was DECNet for VMS, SNA for mainframers. I still remember the heated debates about which protocols were "real". What is obvious now was not obvious then (that TCP/IP would cast the others onto the ash heap of history).
While you see the other protocols still in usage, it's like seeing the vestigel communist nations still around today. You just know their days are numbered.
While you see the other protocols still in usage, it's like seeing the vestigel communist nations still around today. You just know their days are numbered.
SNA for starters, then the others that have already been mentioned (IPX/SPX, etc..). Its was developed by IBM and then later served as a foundation for TCP/IP and the OSI layer model which all communications protocols follow now.
And we've been waiting how long for IPv6? What 10 years now? WTF is the delay for the love of pete. Sure Static and Dynamic NAT has alleviated a lot of the problems,but come on now. Roll it out already. Most hardware should already be IPv6 ready. As for remembering the addresses, I agree. Thats the one thing I hate about HEX.Marc said:
Next step is will be moving the world to IPv6 (I'm wondering just how the hell I'm suppose to rember the v6 addresses
I hear ya, but there are still many large organizations, especially in the financial sector, that aint getting rid of their system 38s with 3745 FEPs running SNA for a while. Some of it has to do with the 'if it aint broke, dont fix it' mentality as well as cost issues. Sure they put OSA (token ring) and CIP cards (Ethernet, once Cisco figured out that the MTU size on their original cards wouldnt allow it to work) cards in place of the 3745s, which then connect to IP based routers, but at the base it aint going aways. But you're right, one day it will go away. SNA is just too much of bitch to work with as a communications protocol.
Deleted 2
Vice Admiral
I think the ink on the RFCs was barely dry in 1996. IPv4 to IPv6 was always meant to be a gradual transition. But think about it, Windows didn't get support by default until XP (I think 2000 may have had an optional IPv6 stack component), and end user adoption is fundamental to IPv6's success. Even now ISPs are loathe to switch over because they know it'll screw up the connections of their customers that are still using Windows ME, or a dodgy old home router.
I have some privacy concerns about IPv6. Much has been made of 'advertising cookies' set by unscrupulous companies to track individual surfers' behaviour. IPv6 numbers will have a high chance of representing individual connections, completely mitigating the need for cookies.
The Day the Routers Died
But its ROUTE-ER, not ROOTER. Ok folks, We (the US) invented the damned things, we get to dictate how its pronounced!!!
Deleted 2
Vice Admiral
Speaking of TCP/IP, Microsoft has just released a patch for a pretty damning remote execution vulnerability in its TCP/IP stack. Don't delay this patch, folks, Update your systems today.
- Status
Similar threads
