🌟 Ida Holz: "mother of the #internet", as described by Vint Cerf.

She is the pioneer behind the first Internet node in #Uruguay and a visionary leader in the development of an independent Latin American network!

We celebrate her story and her achievements 👉 https://connect.geant.org/2023/06/20/proud-of-our-female-pioneers-ida-holz-mother-of-the-internet-in-latin-america

This article features in #CONNECT43 📖 https://connect.geant.org/connect43

#connectivity #community #LatinAmerica #LatAm #RedCLARA #Historyoftheinternet #NRENs #Research #Education #Network

[#FridayReads] Did you know the Netherlands 🇳🇱 was the first European country connected to the internet?

Read this great article by @nemokennislink about the history of internet in the Netherlands and Dutch internet pioneers, including our CEO Erik Huizer @Milkshake and the major role he played in the protocol wars 👉 https://www.nemokennislink.nl/publicaties/en-toen-was-er-internet/

@SURF @ietf @nlnetlabs @SIDN @SIDNlabs

#Historyoftheinternet #internethistory #internet #internetpioneers #Netherlands

@n8chz If I'm understanding you correctly, your telephone number is a "some character string", though composed (usually, not always) of numbers.

URLs evolved from domain names plus a local path component and additional arguments or values. The domain-name system mapped logical network locations (IP addresses) to mnemonic identifiers, and provided routing through them. I remember using bang-path notation to route email, briefly, in the 1980s, prior to this being fully hammered out.

(Bang paths specified the routing instructions for email between two points, something that's now handled automatically.)

Note that DNS and host names are mappings to but also independent of the underlying network topology. I can have, say, "example.com" as a domain, but hosts "local.example.com" and "remote.example.com" be located at two distinct networks, with no underlying logical network location. It's also possible to specify "service addresses" such as "mail.example.com" and "ftp.example.com" which refer to specific protocols (email and FTP respectively, "WWW" is another of these though it's largely been dropped). Or subdomains, so that host.lon.example.com and host.nyc.example.com might correspond to sub-networks in London and New York, where "lon.example.com" and "nyc.example.com" are subdomains.

And there's a whole lot of other detail.

When DNS first started there were literally a few hundred, maybe a few thousand, internet hosts let alone domains, and the directory was printed, with the system operator's names and phone numbers in it twice (forward and reverse lookup), updated and distributed regularly.

There are now billions of hosts (devices), ranging from supercomputers to electronic doorbells and drones, and at the very least millions of domains. Management is ... more complicated than it once was.

Sorting out what namespaces should map to what address schemes is complex, and as anyone who's attempted ontologies and rational organisational schemes, there's no one solution, and correspondence of use to design intent tends to rapidly diverge over time.

It's complicated.

@dansinker

#DNS #ItsNotDNS #ThereIsNoWayItsDNS #ItWasDNS #ItsComplicated #HistoryOfTheInternet