#arpanet — Public Fediverse posts

Vor 43 Jahren: Wie TCP/IP aus ARPANET das Internet machte
Am 1. Januar 1983 startete ein Protokollwechsel, der das Fundament für das heutige Internet legte. ARPANET stellte schrittweise vom Network Control Program (NCP) auf TCP/IP um.

Vom Insellösungs-Netz zum globalen Standard
Am Neujahrstag 1983
https://www.apfeltalk.de/magazin/news/vor-43-jahren-wie-tcp-ip-aus-arpanet-das-internet-machte/
#Mac #News #ARPANET #Internetgeschichte #Netzwerkprotokolle #RobertKahn #TCPIP #VintonCerf

Happy birthday to the Internet!

On this day in 1983, the ARPANET network officially switched to using the TCP/IP protocol, effectively creating the Internet. https://www.usg.edu/galileo/skills/unit07/internet07_02.phtml

#UnofficialDiaryDates #ARPANET #Internet #TCPIP

CENI - La Chine vient de mettre en service l'héritier d'ARPANET

https://fed.brid.gy/r/https://korben.info/ceni-chine-reseau-innovation-arpanet.html

Une conférence datant de 2023, mais riche en informations et en échanges : “Internet, histoire et enjeu” par Gérard Le Lann. La présentation aborde également, avec un regard critique, le rôle de Louis Pouzin dans le projet #Cyclades et le développement du #datagramme.
https://www.armorhistel.org/35/publications/conference-debat-40-ans-dinternet/
#arpanet #tcpip

Repórter Retro 120

https://retropolis.com.br/2025/11/28/reporter-retro-120/

#ReprterRetro #8BitGuy #AcornArchimedes #AdrianBlack #Amiga #Apple #ARPANET #ArtefatosDeCor #Bendix #C #CmeraDigital #CoCoTown #Comix35 #Comx35 #COSMAC #crash #DeVoltaParaOFuturo #DosBox #DRAM #ElectronikaBK #Elektronika #FbioNMI #fail #Hercules #Homebrew #IBM #imagens #Intel80386 #Jogos #Macintosh #MazeOfGalious #MSDOS #MSXRio #MSXSP #NTSC #Olivetti #PampasAndSelene #PhintageCollector #ProdestPC #Quicktake #RCACDP

Repórter Retro 120

https://retropolis.com.br/2025/11/28/reporter-retro-120/

#ReprterRetro #8BitGuy #AcornArchimedes #AdrianBlack #Amiga #Apple #ARPANET #ArtefatosDeCor #Bendix #C #CmeraDigital #CoCoTown #Comix35 #Comx35 #COSMAC #crash #DeVoltaParaOFuturo #DosBox #DRAM #ElectronikaBK #Elektronika #FbioNMI #fail #Hercules #Homebrew #IBM #imagens #Intel80386 #Jogos #Macintosh #MazeOfGalious #MSDOS #MSXRio #MSXSP #NTSC #Olivetti #PampasAndSelene #PhintageCollector #ProdestPC #Quicktake #RCACDP

Repórter Retro 120

https://retropolis.com.br/2025/11/28/reporter-retro-120/

#ReprterRetro #8BitGuy #AcornArchimedes #AdrianBlack #Amiga #Apple #ARPANET #ArtefatosDeCor #Bendix #C #CmeraDigital #CoCoTown #Comix35 #Comx35 #COSMAC #crash #DeVoltaParaOFuturo #DosBox #DRAM #ElectronikaBK #Elektronika #FbioNMI #fail #Hercules #Homebrew #IBM #imagens #Intel80386 #Jogos #Macintosh #MazeOfGalious #MSDOS #MSXRio #MSXSP #NTSC #Olivetti #PampasAndSelene #PhintageCollector #ProdestPC #Quicktake #RCACDP

Repórter Retro 120

https://retropolis.com.br/2025/11/28/reporter-retro-120/

#ReprterRetro #8BitGuy #AcornArchimedes #AdrianBlack #Amiga #Apple #ARPANET #ArtefatosDeCor #Bendix #C #CmeraDigital #CoCoTown #Comix35 #Comx35 #COSMAC #crash #DeVoltaParaOFuturo #DosBox #DRAM #ElectronikaBK #Elektronika #FbioNMI #fail #Hercules #Homebrew #IBM #imagens #Intel80386 #Jogos #Macintosh #MazeOfGalious #MSDOS #MSXRio #MSXSP #NTSC #Olivetti #PampasAndSelene #PhintageCollector #ProdestPC #Quicktake #RCACDP

Repórter Retro 120

https://retropolis.com.br/2025/11/28/reporter-retro-120/

#ReprterRetro #8BitGuy #AcornArchimedes #AdrianBlack #Amiga #Apple #ARPANET #ArtefatosDeCor #Bendix #C #CmeraDigital #CoCoTown #Comix35 #Comx35 #COSMAC #crash #DeVoltaParaOFuturo #DosBox #DRAM #ElectronikaBK #Elektronika #FbioNMI #fail #Hercules #Homebrew #IBM #imagens #Intel80386 #Jogos #Macintosh #MazeOfGalious #MSDOS #MSXRio #MSXSP #NTSC #Olivetti #PampasAndSelene #PhintageCollector #ProdestPC #Quicktake #RCACDP

Are you not a capitalist?

#capitalism #economy #poll #fyp #pyf #tiktok #markzuckeberg #gretathunberg #israel #elonmusk #highquality #nasilemak #ostatus #myspace #googlesearch #arpanet

Episódio 166 – 30 anos de Internet comercial no Brasil – Parte A

https://retropolis.com.br/2025/08/06/episodio-166-parte-a/

#Podcast #3270 #Alternex #ARPA #ARPANET #ASCIIArt #BITNET #BobKhan #CETEL #CGIBr #ControlData #DARPA #DEC #Embratel #enlace #FakeNews #FAPESP #Fermilab #GuerraFria #GuiaDaInternetBr #IBASE #IBM #internet #JosephLickner #Kremvax #LinhaCruzada #LNCC #Londres #MIT #modem #MTP #NCP #NICBr #PDP #rede #RedeRio #Registrobr #retrocomputing #retrogaming #Retrpolis #revista #RN

Episódio 166 – 30 anos de Internet comercial no Brasil – Parte A

https://retropolis.com.br/2025/08/06/episodio-166-parte-a/

#Podcast #3270 #Alternex #ARPA #ARPANET #ASCIIArt #BITNET #BobKhan #CETEL #CGIBr #ControlData #DARPA #DEC #Embratel #enlace #FakeNews #FAPESP #Fermilab #GuerraFria #GuiaDaInternetBr #IBASE #IBM #internet #JosephLickner #Kremvax #LinhaCruzada #LNCC #Londres #MIT #modem #MTP #NCP #NICBr #PDP #rede #RedeRio #Registrobr #retrocomputing #retrogaming #Retrpolis #revista #RN

Episódio 166 – 30 anos de Internet comercial no Brasil – Parte A

https://retropolis.com.br/2025/08/06/episodio-166-parte-a/

#Podcast #3270 #Alternex #ARPA #ARPANET #ASCIIArt #BITNET #BobKhan #CETEL #CGIBr #ControlData #DARPA #DEC #Embratel #enlace #FakeNews #FAPESP #Fermilab #GuerraFria #GuiaDaInternetBr #IBASE #IBM #internet #JosephLickner #Kremvax #LinhaCruzada #LNCC #Londres #MIT #modem #MTP #NCP #NICBr #PDP #rede #RedeRio #Registrobr #retrocomputing #retrogaming #Retrpolis #revista #RN

Episódio 166 – 30 anos de Internet comercial no Brasil – Parte A

https://retropolis.com.br/2025/08/06/episodio-166-parte-a/

#Podcast #3270 #Alternex #ARPA #ARPANET #ASCIIArt #BITNET #BobKhan #CETEL #CGIBr #ControlData #DARPA #DEC #Embratel #enlace #FakeNews #FAPESP #Fermilab #GuerraFria #GuiaDaInternetBr #IBASE #IBM #internet #JosephLickner #Kremvax #LinhaCruzada #LNCC #Londres #MIT #modem #MTP #NCP #NICBr #PDP #rede #RedeRio #Registrobr #retrocomputing #retrogaming #Retrpolis #revista #RN

@carlmalamud we have never met - but I wanted to say I was listening yesterday to the Geek of the Week conversation https://town.hall.org/radio/Geek/092993_geek_ITR.html with Robert Braden. as I was trying to figure out how #ARPANET worked on System/360 computers.

Thank you!

@peterhoneyman

#mainframe #mvs

@larsbrinkhoff

Thank you! I have watched the Youtube video, nice summary and easy to follow.

I was wondering if there is #MVT implementation available somewhere, as 360/75 was the third #arpanet node at UCSB.

https://apps.dtic.mil/sti/tr/pdf/ADA155057.pdf has a very interesting summary how NCP and then TCP were done on the mainframe later at UCLA

It was based on ICT (a multiprocessing supervisor) and The Exchange (some form of IPC).

Any chances to find the docs and the implementations running back then?

@me_

«Сети Судного дня». Как разработка противоядерной ПВО привела к рождению Интернета? Часть 2. Система SAGE

Продолжим рассказ о том, как путь к появлению Интернета наметили и проложили исходно военные соображения. В прошлой части мы обсудили , как у военных обеих сверхдержав появилась идея увязки систем ПВО в электронные сети с ЭВМ, и как это с противоречивыми результатами пытались сделать в СССР. Теперь пришла очередь переключиться на США и посмотреть, как попытка создания зенитного заслона на потенциальном пути советских бомбардировщиков привела к появлению сетевой системы управления ПВО SAGE континентального масштаба с автоматизированным компьютерным управлением. И заронила в своих разработчиков идеи, изменившие со временем всю жизнь нашей цивилизации.

https://habr.com/ru/companies/ruvds/articles/911854/

#ruvds_статьи_выходного_дня #история #arpanet #sage #bomarc #darpa #arpa #Джозеф_Ликлайдер #IBM

«Сети Судного дня». Как разработка противоядерной ПВО привела к рождению Интернета?

О том, как с технической и организационной стороны создавался ARPAnet, «дедушка» нашего Интернета, написано немало — в том числе и у нас на Хабре. Однако причины и предыстория того, как в научно-исследовательском центре Пентагона DARPA/ARPA дошли до этой идеи и её реализации, обычно упоминаются почти скороговоркой: «нужна была распределённая сеть, которая при поражении части узлов атомными ударами продолжала бы работать». За этой фразой, однако, скрывается большая история, полная поисков, страхов, экспериментов и непростых решений. Попробуем разобраться, как попытки решить сугубо военные проблемы ранней ядерной эпохи привели к появлению компьютерных сетей, без которых современный мир почти невообразим.

https://habr.com/ru/companies/ruvds/articles/909886/

#ruvds_статьи_выходного_дня #история #arpanet #sage #алдан #с25 #darpa #arpa

This amazing, cursed, fun, terrifying, makes you sick if you've ever worked in #networking and incredibly entertaining all at the same time:

https://1.6.0.0.8.0.0.b.e.d.0.a.2.ip6.arpa/@domi/statuses/01JQHWXY605XVPGY5MAXV30K5X

#dns #mtr #traceroute #demoscene #arpa #arpanet #ipv6

Debunking the Nuclear Myth: The True Origins of the Internet

For decades, a pervasive myth has suggested that the internet was designed to survive a nuclear attack. However, the truth is far less dramatic and rooted in the collaborative spirit of academia rathe...

https://news.lavx.hu/article/debunking-the-nuclear-myth-the-true-origins-of-the-internet

#news #tech #InternetHistory #ARPANET #PacketSwitching

I have now repeatedly heard the claim that #ADVENT was spread over #ARPANET. I'm pretty sure that this is a modern misconception since bandwidth was so limited in the 70s that 100s of kilobytes or even megabytes surely couldn't just be transferred at will.

Can anyone shed more light on this? A proof one way or the other?

#earlyinternet #filetransfer #DECUS

Repórter Retro 110

https://retropolis.com.br/2024/12/25/reporter-retro-110/

#ReprterRetro #6809 #ACTApricotPortable #adventure #Amazon #Amiga #Arcade #ArcadiaSuperSelectSystem #ARPANET #Atari400 #Atari8bits #Atari800 #AventurasNaSelva #BASIC #Cecconoid #CoCo3 #DeskMate #eletrnica #EncontroDeUsurios #Ensjo #FlatMac #GeoCities #internet #Itlia #Ja #Jogos #KazuhikoNishi #LaCoCoStrangiato #MC1000 #MSXSP #msica #NoelLlopis #PisaMSXDevcon #rdio #RenatoDegiovani #RetroSC #RioRetroGames #RMC #sega

Repórter Retro 110

https://retropolis.com.br/2024/12/25/reporter-retro-110/

#ReprterRetro #6809 #ACTApricotPortable #adventure #Amazon #Amiga #Arcade #ArcadiaSuperSelectSystem #ARPANET #Atari400 #Atari8bits #Atari800 #AventurasNaSelva #BASIC #Cecconoid #CoCo3 #DeskMate #eletrnica #EncontroDeUsurios #Ensjo #FlatMac #GeoCities #internet #Itlia #Ja #Jogos #KazuhikoNishi #LaCoCoStrangiato #MC1000 #MSXSP #msica #NoelLlopis #PisaMSXDevcon #rdio #RenatoDegiovani #RetroSC #RioRetroGames #RMC #sega

Repórter Retro 110

https://retropolis.com.br/2024/12/25/reporter-retro-110/

#ReprterRetro #6809 #ACTApricotPortable #adventure #Amazon #Amiga #Arcade #ArcadiaSuperSelectSystem #ARPANET #Atari400 #Atari8bits #Atari800 #AventurasNaSelva #BASIC #Cecconoid #CoCo3 #DeskMate #eletrnica #EncontroDeUsurios #Ensjo #FlatMac #GeoCities #internet #Itlia #Ja #Jogos #KazuhikoNishi #LaCoCoStrangiato #MC1000 #MSXSP #msica #NoelLlopis #PisaMSXDevcon #rdio #RenatoDegiovani #RetroSC #RioRetroGames #RMC #sega

Repórter Retro 110

https://retropolis.com.br/2024/12/25/reporter-retro-110/

#ReprterRetro #6809 #ACTApricotPortable #adventure #Amazon #Amiga #Arcade #ArcadiaSuperSelectSystem #ARPANET #Atari400 #Atari8bits #Atari800 #AventurasNaSelva #BASIC #Cecconoid #CoCo3 #DeskMate #eletrnica #EncontroDeUsurios #Ensjo #FlatMac #GeoCities #internet #Itlia #Ja #Jogos #KazuhikoNishi #LaCoCoStrangiato #MC1000 #MSXSP #msica #NoelLlopis #PisaMSXDevcon #rdio #RenatoDegiovani #RetroSC #RioRetroGames #RMC #sega

Repórter Retro 110

https://retropolis.com.br/2024/12/25/reporter-retro-110/

#ReprterRetro #6809 #ACTApricotPortable #adventure #Amazon #Amiga #Arcade #ArcadiaSuperSelectSystem #ARPANET #Atari400 #Atari8bits #Atari800 #AventurasNaSelva #BASIC #Cecconoid #CoCo3 #DeskMate #eletrnica #EncontroDeUsurios #Ensjo #FlatMac #GeoCities #internet #Itlia #Ja #Jogos #KazuhikoNishi #LaCoCoStrangiato #MC1000 #MSXSP #msica #NoelLlopis #PisaMSXDevcon #rdio #RenatoDegiovani #RetroSC #RioRetroGames #RMC #sega

Happy birthday to ARPANET, the forerunner of the modern internet! 53 years ago, the first message was sent over this pioneering network, paving the way for a world of interconnection and innovation.

As a tech enthusiast, I am constantly amazed by the ways the internet has transformed our lives, allowing us to communicate, learn and share ideas across boundaries and borders. From social media to e-commerce, from telemedicine to remote work, the internet has become an essential part of our daily routines, enabling us to connect with others and access a wealth of information at our fingertips.

#ARPANET #InternetAnniversary #Transhumanism #TechInnovation
#InternetHistory #Networking #DigitalRevolution #Innovation #Communication #Cyberculture #OnlineCommunity #TechHerstory #NetNeutrality #OpenSource #Decentralization #DataPrivacy #Cybersecurity #DigitalRights #Accessibility #Inclusion #SocialImpact #DigitalTransformation #FutureTech #TechOptimism #InternetOfThings #AI

🔗 https://ethw.org/Milestones:Birthplace_of_the_Internet,_1969

'We were just trying to get it to work': The failure that started the internet

https://www.bbc.com/future/article/20241028-the-failure-that-started-the-internet

#BBCFuture #ARPANET #CharleyKline #BillDuvall

Yes, I can somewhat relate 😊🤘🏻

"The failure that started the internet"

https://www.bbc.com/future/article/20241028-the-failure-that-started-the-internet

#Internet #discovery #invention #Fidonet #arpanet #inthebeginning

E o que rolou no Computer History Museum recentemente?

https://retropolis.com.br/2024/05/02/e-o-que-rolou-no-computer-history-museum-recentemente/

#MundoRetro #ARPANET #atividades #Audible #brinquedo #CHM #computao #DonnaDubinsky #ElizabethFeinler #Furby #GraceHopper #Handspring #histria #HomebrewComputerClub #IA #JeanBartik #museu #NIC #NiklausWirth #Palm #Pascal #PDA #podcast #smartphone #USAToday

"Le Minitel et le datagramme : une histoire bien française"

Les explications techniques et le point de vue industriel de Philippe Picard (Transpac, Corps des Télécoms) : https://forumatena.org/le-minitel-et-le-datagramme-une-histoire-bien-francaise/

#Télécoms #réseau #internet #TCPIP #Cyclades #Inria #Iria #DGT #VGE #Pouzin #Zimmermann #Transpac #DATAR #CNET #innovation #FranceTelecom #ARPA #ARPAnet #EST #SupTelecom #histoire #Orange #Minitel

Robert Kahn: The Great Interconnector
https://spectrum.ieee.org/bob-kahn-2667754905
#ycombinator #medal_of_honor #internet #bob_kahn #arpanet #tcp_ip #Medal_of_Honor

Deux possibilités pour organiser le transport des données : mettre les paquets à la “queue leu leu” dans le réseau, ou bien, les lancer au hasard avec la possibilité, à la fin, de reconstituer le message.

Le réseau Cyclades est le premier à faire la démonstration que les datagrammes fonctionnent.

Une série en 8 épisodes : https://www.radiofrance.fr/franceculture/podcasts/une-histoire-de/cyclades-la-france-a-failli-inventer-internet-6295923

#conseilPodcast #réseau #internet #TCPIP #Cyclades #Inria #Iria #DGT #AlpesMaritimes #SophiaAntipolis #VGE #Pouzin #Zimmermann #Transpac #DATAR #CNET #innovation #FranceTelecom #ARPA #ARPAnet #internet #histoire

Okay I thought I'd share this recent post here on the #Fediverse. To give it some context, it's an answer to a common question, often a misunderstanding (even by many knowledgeable folks) as to just how we got here.

So first, the question, posed HERE.

And my answer follows below:

There's a lot of apples and oranges here. And everyone had a lot of good points made, but your question is simple, and has a very simple answer. I'll endeavor to address that directly, but do need to tend to some of what has already been said.

## Scroll down to the tl;dr for the succinct answer of your question

Ethernet, ARCNET, Token Ring, Thick net (RG-59), Thin net (RG-58 A/U), and UTP (Cat 3, Cat 5, and Cat 6 unshielded twisted pair, Etc.) really have zero bearing on your question insofar as IP is concerned. All of these specifications relate to the definition of technologies that, although are indeed addressed in the OSI model which is indeed very much in use to this day,but are outside the scope of Internet Protocol. I'll come back to this in a minute.

It's quite common to say TCP/IP, but really, it's just IP. For example, we have TCP ports and we have UDP ports in firewalling. i.e., TCP is Transmission Control Protocol and handles the delivery of data in the form of packets. IP handles the routing itself so those messages can arrive to and from the end points. Uniform Data Protocol is another delivery system that does not guarantee arrival but operates on a best effort basis, while TCP is much chattier as it guarantees delivery and retransmission of missed packets - UDP is pretty efficient but in the case of say, a phone call, a packet here and there won't be missed by the human ear.

That's a very simplistic high level-view that will only stand up to the most basic of scrutiny, but this isn't a class on internetworking ;) If you just want to be able to understand conceptually, my definition will suffice.

Networking (LAN) topologies like Token Ring, ARCNET, and Ethernet aren't anywhere in the IP stack, but figure prominently in the OSI stack. I'm not going to go into the details of how these work, or the physical connection methods used like Vampire Taps, Thin net, or twisted pair with RJ-45 terminators, but their relationship will become obvious in a moment.

The OSI model unfolds like so, remember this little mnemonic to keep it straight so you always know:

> People Don't Need To See Paula Abdul

Okay, touched on already, but not really treated, is the description of that little memory aid.

> Physical, Data Link, Network, Transport, Session, Presentation, and Application layers (From bottom to top).

The physical and Data Link layers cover things like the cabling methods described above,and you're probably familiar with MAC Addresses (medium access control) on NICs (network interface controller). These correlate to the first two layers of the OSI stack, namely, the Physical (obvious - you can touch it), and the Data Link layer - how each host's NIC and switches on each LAN segment talk to each other and decide which packets are designated for whom (People Don't).

In software engineering, we're concerned mostly with the Session, Presentation, and Application layers (See Paula Abdul). Detailed explanation of these top three layers is outside the scope of this discussion.

The Beauty of the OSI model is that each layer on one host (or program) talks to exclusively with the same layer of the program or hardware on the other host it is communicating with - or so it believes it is, because, as should be obvious, is has to pass its information down the stack to the next layer below itself, and then when it arrives at the other host, it passes that information back up the stack until it reaches the very top (Abdul) of the stack - the application.

Not all communication involves all of the stacks. At the LAN (Local Area Network) level, we're mostly concerned with the Physical and Data Link layers - we're just trying to get some packet that we aren't concerned about the contents of from one box to another. But that packet probably includes information that goes all the way up the stack.

For instance, NIC #1 has the MAC: 00:b0:d0:63:c2:26 and NIC #2 has a MAC of 00:00:5e:c0:53:af. There's communication between these two NICs over the Ethernet on this LAN segment. One says I have a packet for 00:00:5e:c0:53:af and then two answers and says, "Hey that's me!" Nobody else has that address on the LAN, so they don't answer and stop listening for the payload.

Now for Internet Protocol (IP) and TCP/UDP (Transmission Control Protocol and User Datagram Protocol):

IP corresponds to Layer 3 (Need) - the Network Layer of the **OSI Model.

TCP and UDP correspond to Layer 4 (To) - the Transport Layer of the OSI model.

That covers the entire OSI model and how TCP/IP correspond to it - almost. You're not getting off that easy today.

There's actually a bit of conflation and overlapping there. Just like in real life, it's never that cut and dried. For that, we have the following excellent explanation and drill down thanks to Julia Evans:

- Layer 2 (Don't) corresponds to Ethernet.
- Layer 3 (Need) corresponds to IP.
- Layer 4 (To) corresponds to TCP or UDP (or ICMP etc)
- Layer 7 (Abdul) corresponds to whatever is inside the TCP or UDP packet (for example a DNS query)

You may wish to give her page a gander for just a bit more of a deeper dive.

Now let's talk about what might be a bit of a misconception on the part of some, or at least, a bit of a foggy conflation between that of the specification of the OSI model and a Company called Bolt Beranek & Newman (BBN) a government contractor tasked with developing the IP stack networking code.

The TCP/IP you know and depend upon today wasn't written by them, and to suggest that it was the OSI model that was scrapped instead of BBN's product is a bit of a misunderstanding. As you can see from above, the OSI model is very much alive and well, and factors into your everyday life, encompasses software development and communications, device manufacturing and engineering, as well as routing and delivery of information.

This next part is rather opinionated, and the way that many of us choose to remember our history of UNIX, the ARPANET, the NSFnet, and the Internet:

The IP stack you know and use everyday was fathered by Bill Joy, who arrived at UC Berkeley in (IIRC) 1974), created vi because ed just wasn't cutting it when he wanted a full screen editor to write Berkeley UNIX (BSD), including TCP/IP, and co-founded Sun Microsystems (SunOS / Solaris):

> Bill Joy just didn’t feel like this (the BBN code) was as efficient as he could do if he did it himself. And so Joy just rewrote it. Here the stuff was delivered to him, he said, “That’s a bunch of junk,” and he redid it. There was no debate at all. He just unilaterally redid it.

Because UNIX was hitherto an AT&T product, and because government contracting has always been rife with interminable vacillating and pontificating, BBN never actually managed to produce code for the the IP stack that could really be relied upon. In short, it kinda sucked. Bad.

I highly recommend that you take a look at this excellent resource explaining the OSI model.

# tl;dr:

So! You've decided to scroll down and skip all of the other stuff to get the straight dope on the answer to your question. Here it is:

> What were the major things that caused TCP/IP to become the internet standard protocol?

The ARPANET (and where I worked, what was to become specifically the MILNET portion of that) had a mandate to replace NCP (Network Control Protocol) with IP (Internet Protocol). We did a dry run and literally over two thirds of the Internet (ARPANET) at that time disappeared, because people are lazy, software has bugs, you name it. There were lots of reasons. But that only lasted the better part of a day for the most part.

At that time the ARPANET really only consisted of Universities, big Defense contractors and U.S. Military facilities. Now, if you'll do a bit of digging around, you'll discover that there was really no such thing as NCP - that is, for the most part, what the film industry refers to as a retcon, meaning that we, as an industry, retroactively went back and came up with a way to explain away replacing a protocol that didn't really exist - a backstory, if you will. Sure, there was NCP, it was mostly a kludge of heterogeneous management and communications programs that varied from system to system, site to site, with several commonalities and inconsistencies that were hobbled together with bailing twine, coat hangers, and duct tape (for lack of a better metaphor).

So we really, really, needed something as uniform and ubiquitous as the promise that Internet Protocol would deliver. Because Bill Joy and others had done so much work at UC Berkeley, we actually had 4.1BSD (4.1a) to work with on our DEC machinery. As a junior member of my division, in both age and experience, I was given the task of, let's say throwing the switch on some of our machines, so to speak, when we cut over from the NCP spaghetti and henceforth embraced TCP/IP no matter what, on Flag Day - 01 January 1983.

So you see,the adoption of Internet Protocol was not a de facto occurrence - it was de jure, a government mandate to occur at a specific time on a specific day.

It literally had nothing to do with popularity or some kind of organic adoption, the erroneously described, so-called demise of the OSI model, or any physical network topology.

### DARPA said 01 January 1983 and that's it, and that was it - Flag Day.

Sure, it took a few days for several facilities to come up (anyone not running IP was summarily and unceremoniously cut off from the ARPANET).

And one also needs to consider that it wasn't every machine - we only had some machines that were Internet hosts. We still had a lot of mainframes and mini computers, etc., that were interconnected within our facilities in a hodgepodge or some other fashion. Nowadays we have a tendency to be somewhat incredulous if every device doesn't directly connect over IP to the Internet in some way. That wasn't the case back then - you passed traffic internally, sometimes by unmounting tapes from one machine and mounting them on another.

There was a lot of hand wringing, stress, boatloads of frustration, and concern by people over keeping their jobs all over the world. But that's why and when it happened. Six months later in the UNIX portions of networks we had much greater stability with the release of 4.2BSD, but it wouldn't really be until a few years later Net2 was released that things settled down with the virtually flawless networking stability that we enjoy today.

Enjoy!

#tallship #DARPA #IP #Internet_Protocol #Computer_History #internetworking #Internet #ARPANET #MILNET #NSFnet #Bill_Joy #BBN #UNIX #BSD

⛵

.

Data Networks decades before the Internet (via Vint Cerf on the internet-history mailing list). https://www.youtube.com/watch?v=XFkwWZ6ujy0

#internet
#internethistory
#computerscience
#packetswitching
#arpanet
#telegraphy

@tedu

Fuckers.

I will always be BT74, going back all the way to NIC.DDN.MIL aka, yet another nom de plume of SRI, or, as was affectionately referred to as, "The NIC".

Back in the mid-80's after we introduced DNS in 1985 (and even before), you could actually call up Jake Feinler directly over the phone for time sensitive issues of a priority nature. She was always able to get things resolved in a matter of hours - sometimes I'd get a call back in a few minutes from an engineer at SRI to confirm that all was well.

according to the man pages, you should still be able to a #WHOIS searches #NIC handles for "NET-...", POCs like my handle above (um... sort of, I'll get to that), etc.

So I should note, that the NIC Handle I've listed above hasn't actually been searchable for quite some time now (at least ten years). but you should still be able to grep for it (coz I've made certain to still listed that way in my registry records). A simple, elegant system that lends well it's usage to humans, is now being cast aside for something less readable and in many ways, relevant, when you're quickly trying to pull a piece of primary data to reach someone responsible for a contact point (PoC), with respect to themselves, their property, or a "Role Account" that is responsible for a resource and shared by perhaps, several individuals.

So, the various contacts in the WHOIS records are variously, Registrant, Admin, Tech, and Billing contacts. In reality (and I've not seen a change in the RFCs on this point, but I don't follow that closely nowadays), the TECH CONTACT is defined as the person or role account responsible for the direct administration of DNS - not neccessarily the same as any other contact role account. ADMIN is important too, but not really as important as the TECH contact. In theory and still many times in practice, a remote sysadmin somewhere needs to get ahold of the DNS administrator to report abuse or some other issue, so a WHOIS is performed and voila! - you have a contact point to help fix a technical situation.

REGISTRANT is the owner of the domain registration, and as such, might legitimately have a reason to pay a privacy bureau to act as a proxy for contacting (to block stalkers, spammers, whatev), and the BILLING contact really has little technical relevance, but unlike the REGISTRANT, is the actual person or role account to interact with when it comes to domain renewals, etc.

So the ADMIN and at the very least, TECH contacts must (or should) be live phone and/or Fax numbers and email addresses that are searchable and reachable by anyone. In reality, however, after #NSI started to become less of a NIC, and shed themselves of the internic.net moniker as they commercialized under pressure from the nascent ICANN in order to have their contract renewed, anyone who registered a domain ended up having the fields to all of the contacts being filled out with the same data as that of the* registration owner/admin*, instead of what it should have been for at least the TECH and ADMIN contacts - you can override these defaults, but most will never bother, and have no idea why there are all these various roles in the records. (/me sighs....).

Okay, so after Jon Postel's untimely passing, the miscreants pretending to be legitimate enough to bootstrap ICANN quickly came to the realization that there's really no such thing as IANA - it was just a pseudonym for Jon, who literally ran pretty much everything we hold sacred today - like, being the RFC editor, and being IANA, managing the AUTH delegations of the #ccTLDs and even the DNS root servers (litterally moved one unilaterally once). So IANA was created by these miscreant folks, like Esther Dyson and Mike Roberts - pretenders provocateur. But I digress.

So now we've got these RIRs (which is a good thing, some better than others, but still). RIPE still uses NIC-HANDLEs, and so does #ARIN.

And as I promised, my NIC-HANDLE, once and always BT74, evolved into BT74-ARIN once that RIR was created. More explanations are in the alt-text accessibility tags for the two attached images.

So I won't go on further with this historical perspective that just sort of quietly was usurped by commercial pressures in the special interest lobby sector, #ICANN, and #WIPO, but anyone who's really interested can check out and read my friend Ellen Rony's book about the #Domain_Wars.

But just for shits and giggles, I've included a couple of screenies attached to this post:

- my current, automatically evolved NIC-HANDLE following the formalization of ARIN, from the ARIN website, and...
- An explanation of the usage of NIC-Handle's from the current man pages of WHOIS.

I hope that helps!

All the best!

#tallship #UNIX #DNS #FOSS #systems_administration #Stanford_Research_Institute #ARPANET #MILNET #NSFNET

⛵

.

RE: https://honk.tedunangst.com/u/tedu/h/4g4vG2g8TH52x5g3PY

@tedu

David L. Mills, Who Kept the Internet Running on Time, Dies at 85 - He developed and implemented the protocol that synchronizes the digital clocks nestled wi... - https://www.nytimes.com/2024/01/26/technology/david-l-mills-dead.html #computersandtheinternet #universityofdelaware #networktimeprotocol #deaths(obituaries) #davidl.mills #arpanet #time

Inventor of NTP protocol that keeps time on billions of devices dies at age 85 - Enlarge / A photo of David L. Mills taken by David Woolley on April 27,... - https://arstechnica.com/?p=1997331 #networktimeprotocol #internetpioneers #internethistory #theinternet #davemills #retrotech #vintcerf #arpanet #biz⁢ #nsfnet #tech #ping #ftp #ntp

@memory
RIP: David Mills

In 1977, Mills began working at #COMSAT.

There he worked on synchronizing the clocks of computers connected to #ARPANET, inventing the Network Time Protocol. #NTP

He told The New Yorker in 2022 that he enjoyed working on synchronized time because no one else was working on it, giving him his own "little fief".

In the mid-2000s, Mills turned over full control of the NTP reference implementation to Harlan Stenn.

Mills was the chairman of the Gateway Algorithms and Data Structures Task Force ( #GADS ) and the first chairman of the Internet Architecture Task Force.

He invented the DEC LSI-11 based #Fuzzball router that was used for the 56 kbit/s NSFNET (1985), inspired the author of #ping for BSD (1983), and had the first #FTP implementation. He authored numerous #RFCs.

The Third University of Cambridge: BBN and the Development of the ARPAnet

History of BBN, the contractors for the ARPAnet / proto-internet:

https://www.freaktakes.com/p/the-third-university-of-cambridgehttps://www.freaktakes.com/p/the-third-university-of-cambridge

#arpanet #bbn #history

https://alecmuffett.com/article/108871

[#ARPANET|#HISTORY] 10/04/1983: the day Arpanet separated in two, Arpanet and Milnet (excellent article in french)

Il y a 40 ans, Arpanet sortait du contrôle militaire

#milnet #nethistory

https://www.nextinpact.com/article/72626/il-y-a-40-ans-arpanet-sortait-controle-militaire

“What will the implications be for humanity? Who will benefit and who will suffer? These are the important questions that we as a society must seriously ask ourselves. We are all atomic and subatomic particles and we are all wireless”

#Arpanet #Techno #Drexciya #NowPlaying

#Introduction

The kids I grew up with knew I was "different", but my parents and school insisted I was normal. Now I've explored #Autism #Prosopagnosia #Alexithymia and #Aphantasia and have an idea what was going on, but then I thought everyone saw the world like I did, just coped better. I coped by becoming a #PluralSystem by age three when I realized my girl self would have to be hidden. After six "guy" IDs, I'm now back being that girl. Still running the system, but with more E and less T...

Age nine I was forced to wear #Bifocal #PlusLensTheory glasses every waking moment. Shattered my body sense and #CognitiveMap - https://www.psychoros.com/consumed-by-the-light/ Spent endless days of lonely boredom exploring the ~30° wedges of #SpatialViewCells and the flat dioramas between them. Now I'm rebuilding a 3D world around my body, where #HeadDirectionCells can have a single basis and #DorsalStream depth can pop out of the flat distance like content from a random dot stereogram.

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

#Introduction

The kids I grew up with knew I was "different", but my parents and school insisted I was normal. Now I've explored #Autism #Prosopagnosia #Alexithymia and #Aphantasia and have an idea what was going on, but then I thought everyone saw the world like I did, just coped better. I coped by becoming a #PluralSystem by age three when I realized my girl self would have to be hidden. After six "guy" IDs, I'm now back being that girl. Still running the system, but with more E and less T...

Age nine I was forced to wear #Bifocal #PlusLensTheory glasses every waking moment. Shattered my body sense and #CognitiveMap - https://www.psychoros.com/consumed-by-the-light/ Spent endless days of lonely boredom exploring the ~30° wedges of #SpatialViewCells and the flat dioramas between them. Now I'm rebuilding a 3D world around my body, where #HeadDirectionCells can have a single basis and #DorsalStream depth can pop out of the flat distance like content from a random dot stereogram.

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

#Introduction

The kids I grew up with knew I was "different", but my parents and school insisted I was normal. Now I've explored #Autism #Prosopagnosia #Alexithymia and #Aphantasia and have an idea what was going on, but then I thought everyone saw the world like I did, just coped better. I coped by becoming a #PluralSystem by age three when I realized my girl self would have to be hidden. After six "guy" IDs, I'm now back being that girl. Still running the system, but with more E and less T...

Age nine I was forced to wear #Bifocal #PlusLensTheory glasses every waking moment. Shattered my body sense and #CognitiveMap - https://www.psychoros.com/consumed-by-the-light/ Spent endless days of lonely boredom exploring the ~30° wedges of #SpatialViewCells and the flat dioramas between them. Now I'm rebuilding a 3D world around my body, where #HeadDirectionCells can have a single basis and #DorsalStream depth can pop out of the flat distance like content from a random dot stereogram.

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

#Introduction

The kids I grew up with knew I was "different", but my parents and school insisted I was normal. Now I've explored #Autism #Prosopagnosia #Alexithymia and #Aphantasia and have an idea what was going on, but then I thought everyone saw the world like I did, just coped better. I coped by becoming a #PluralSystem by age three when I realized my girl self would have to be hidden. After six "guy" IDs, I'm now back being that girl. Still running the system, but with more E and less T...

Age nine I was forced to wear #Bifocal #PlusLensTheory glasses every waking moment. Shattered my body sense and #CognitiveMap - https://www.psychoros.com/consumed-by-the-light/ Spent endless days of lonely boredom exploring the ~30° wedges of #SpatialViewCells and the flat dioramas between them. Now I'm rebuilding a 3D world around my body, where #HeadDirectionCells can have a single basis and #DorsalStream depth can pop out of the flat distance like content from a random dot stereogram.

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

#Introduction

The kids I grew up with knew I was "different", but my parents and school insisted I was normal. Now I've explored #Autism #Prosopagnosia #Alexithymia and #Aphantasia and have an idea what was going on, but then I thought everyone saw the world like I did, just coped better. I coped by becoming a #PluralSystem by age three when I realized my girl self would have to be hidden. After six "guy" IDs, I'm now back being that girl. Still running the system, but with more E and less T...

Age nine I was forced to wear #Bifocal #PlusLensTheory glasses every waking moment. Shattered my body sense and #CognitiveMap - https://www.psychoros.com/consumed-by-the-light/ Spent endless days of lonely boredom exploring the ~30° wedges of #SpatialViewCells and the flat dioramas between them. Now I'm rebuilding a 3D world around my body, where #HeadDirectionCells can have a single basis and #DorsalStream depth can pop out of the flat distance like content from a random dot stereogram.

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

Despite all that, I've been online since #ARPAnet and #DJNR, wrote the first magazine article with simultaneous code distribution (via 8" floppies in the post), coded fab robots to move 6" & 8" Silicon wafers, built my (almost) independent #SolarPV and #SolarThermal house (7K lines of C++ from 1998, 42 device outs), and evolved an audio system with bandwidth from DC to a half MHz. Helped raise four unique kids, as adult minds in young bodies. Still mystify most of the adults I encounter...

@blacklight @DrHyde @tyil The #JargonFile started being passed around and accumulating entries through the 1970s at #Stanford, #MIT, #CarnegieMellon, Bolt Beranek and Newman, and other pre-Internet computing centers. Some terms date back to the late 1950s MIT Tech Model Railroad Club, a very early progenitor of #hacker culture.

Far more than you ever wanted to know here: https://en.wikipedia.org/wiki/Jargon_File

#SAIL #CSAIL #CMU #BBN #ARPANET #AI #Lisp #TMRC