Vint Cerf, “father of the Internet”, is retiring
techcrunch.com
techcrunch.com
Just the nicest guy you could imagine. He took the note-takers job during our breakouts, had beers with us after the session, and asked really good questions and never asserted anything the whole time.
What a legend.
I didn't get an opportunity to talk to him personally after the event as there was a large queue of senior academics and other VIPs already waiting, but I did see him taking the time to talk first to some school-aged kids who had attended.
He seems like a really nice, humble guy, and looked genuinely happy to be encouraging the kids' interest in the sciences.
An anecdote: I wrote a program (in Sigma-7 assembler I think) to play Jotto--a bit like Mastermind but with 5 letter words. Vint loved to poke around in people's directories to see what they were up to and found my program. He played it a few times, and then collared me to ask me a couple of questions: 1) It seemed to know some of the words he entered but not all -- what was up with that? 2) What sort of AI algorithm was I using for the program to make guesses? (It usually beat the human player.)
Answers: 1) I didn't have a digitized dictionary (it was 1969!) so I hand-entered the five letter words from a pocket dictionary but got tired halfway through so it only knew words starting with a-l. 2) The program would eliminate any words that didn't fit the responses to its guesses so far and then pick a remaining word at random.
Upon hearing my answers Vint walked away in disgust! But years later he gave me a recommendation when I interviewed with Google (it didn't work out for other reasons).
I also shared a cubicle wall with another Van Nuys High alumni, Jon Postel, aka "God of the Internet". Sartorially, Jon was the complete opposite of Vint--long scraggly beard, blue jeans, forever barefoot--but those weren't the things that mattered. Man, those were the days.
And he was disappointed in me or the program or the nature of reality that the play algorithm was so simple and dumb ... but it was a slow machine with limited memory, and doing better is actually quite hard and I hadn't invested the time to do so.
There's a big difference between working on a tobacco farm and being the spokesperson for Big Tobacco. He is the latter. I suspect history will someday remember him more for this than his work on TCP/IP.
I don't get why its suddenly fashionable to hate datacenters?
Did a lot of people really think that their code was running in an actual cloud?
Every major datacenter operator has abandoned their carbon neutral pledge since the AI race began, and have claimed disclosure of the public about their water usage is a trade secret to hide the damage from the public. In many cases these datacenters have been built near threatened bodies of water, but they are getting priority access to freshwater before and above residents. The same often happens with electricity, where a significant demand is placed on local infrastructure and taxpayers bear the cost of needed upgrades to the system.
The problem is that these are trillionaire companies because they are subsidized by dozens of taxes on ordinary people. Every transaction we make pays Google in one way or another. Every app we buy pays Google 30%. Every business we patronize is spending like 10% of their operating budget with Google. Our tax dollars are funding their datacenters.
Why is it finally fashionable to hate datacenters? People are finally realizing the costs!
Talk to your politicians about increasing water supply.
>The same often happens with electricity, where a significant demand is placed on local infrastructure and taxpayers bear the cost of needed upgrades to the system.
Talk to your politicians about increasing electricity supply.
> Every transaction we make pays Google in one way or another. Every app we buy pays Google 30%. Every business we patronize is spending like 10% of their operating budget with Google. Our tax dollars are funding their datacenters.
Google is not the only operator of data centers.
>Why is it finally fashionable to hate datacenters? People are finally realizing the costs!
You have suddenly become aware of an industry, have no idea what it does and have been spooked into violent mob behavior.
The concern about energy makes more sense, particularly when DCs burn fossil fuels to achieve their off-grid supply, but they really don't move the needle much in terms of retail electric bills
However I never forget my surprise, Idly flicking through TV one evening and coming across Earth Final Conflict - and there was Vint in a fairly substantial role
It’s like two lifetimes in tech years. I remember that summer Google Earth was launched, we were a year removed from the Gmail launch, and I worked on shipping the first Summer of Code.
Just know that my mentor was hand-holding the hiring process which basically prided itself on false negatives and still probably does.
And they were still in the era where's they'd just keep interviewing you until they "got enough signal" so people would be back 3 and 4 times.
Google hired Guido van Rossum around the same time. I worked down the hall from Rob Pike, they had already hired Peter Weinberger (the w from `awk`), and I shared a 4-person office with Gren Stein, who was then director of the Apache Software Foundation.
(I guess a decade later, was IPv6 important? Still not sure about that one. But it seemed important at the time.)
I eventually went full time at Google NYC in the early 2010s - I remember the internal uproar when Reader was sunsetted =)
Maybe having multiple streams within a single connection, like QUIC does, would have been a better choice. Also being able to demarcate message boundaries within the protocol itself, perhaps, instead of it being a simple byte stream.
This thinking can be seen in the allocation of network blocks. Mercedes Benz getting 53.0.0.0/8 is just a "we have more addresses than we ever need."
If somebody had imagined "yeah, let's give an address to each of our vehicles" they would have realized the space running out.
In a sense, he did. Take a look at RFC 4838.
1. It would have 128-bit addresses. 2. It would have end-to-end encryption (or was it authentication, I forget).
IPv6 was supposed to fix both of these, with IPsec mandatory, but the latter demand sort of faded out into obscurity. We ended up basically solving encryption by pushing everything into TLS anyway, which I guess solved much of the same problems although at a very different layer.
I always wonder if the internet is thesurvivor of the networking cambrian explosion, with a slight roll of the dice making another candidate the winner.
Yes and no. The current internet arguably does not work without a browser and a TLS stack anyway, neither of which is easily implementable (e.g. number of practically usable rendering engines is in the single digits). I mean, I can piece together an IP packet, too, but there's not that many usable services reachable that way.
Or there is too much inertia for IPv8 to overcome to become a truly backwards compatible extension / superset of IPv4?
Part of the reasons for the slow adoption of IPv6 was that it was never designed to be backwards compatible unlike IPv8.
IPv8 solves precisely zero of the problems that is causing a 'slow' roll out of IPv6 / replacement of IPv4:
"""
So it's a matter of mathematical and physical fact that to expand the address size, you must change the protocol, and that means two things immediately:
You have to change the version number.
You have to add new code to handle the new version.
Furthermore, you don't want to split the Internet in two, so you must design a method of interworking between the old version and the new version. Annoyingly, you need to do that in a way that can be done completely in machines that know about the new version, because other machines don't know anything at all about the new version, by definition. So,
You need a coexistence technique so that updated systems, with the new protocol, can connect to old systems that know nothing of the new protocol. Two minutes of thought show that this third requirement has only two solutions:
(3A) Dual stack, in which the new machines speak both the old (IPv4) and new (IPng) protocol.
(3B) Translation, in which something translates addresses between the old and new protocols.
[…]
Incidentally, "IPv8" proponents often ask why IPv6 didn't simply stick some extra bits on the front of IPv4 addresses, instead of inventing a whole new format. Actually, we tried that: the "IPv4-Compatible IPv6 address" format was defined in [RFC3513] but deprecated by [RFC4291] because it turned out to be of no practical use for coexistence or transition. The related "IPv4-Mapped IPv6 address" format is still valid and has a role in the POSIX socket API. Mappings of this kind also figured in the moderately successful coexistence technologies known as 6to4 [RFC3056, RFC3068] and Teredo [RFC4380], which have now been overtaken by events.
"""
* https://github.com/becarpenter/book6/blob/main/01.%20Introdu...
* Interview with author of article: https://www.youtube.com/watch?v=W3jkZ1Ulz-s
I'm always fascinated by how many people think IPv6 adoption would have gone lightning-fast if we just used This One Weird Trick, where said trick has actually been tried and didn't help. They usually refuse to back down even after you tell them so.
6to4 is exactly ownership:
> For any 32-bit global IPv4 address that is assigned to a host, a 48-bit 6to4 IPv6 prefix can be constructed for use by that host (and if applicable the network behind it) by appending the IPv4 address to 2002::/16.
> For example, the global IPv4 address 192.0.2.4 has the corresponding 6to4 prefix 2002:c000:0204::/48. This gives a prefix length of 48 bits, which leaves room for a 16-bit subnet field and 64 bit host addresses within the subnets.
* https://en.wikipedia.org/wiki/6to4
The relaying is a necessity:
OLD DUAL NEW
----------------------
OLD | 32 | 32 | XX |
|------|------|------|
DUAL | 32 | 64 | 64 |
|------|------|------|
NEW | XX | 64 | 64 |
----------------------
* https://github.com/becarpenter/book6/blob/main/01.%20Introdu...There's no way around it: a non-IPng-having node will have to go through a translation box of some kind.
Yes. Note that it doesn't need to be someone else's relay; anyone with IPv4 connectivity could easily route 2002::/16 into IPv4-land (without having to announce it in BGP for others to use). You could even announce 2002:aabb:ccdd::/48 as a more-specific in BGP if you wanted, although this was more exotic.
::ffff:1.2.3.4
* https://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresse...
By having 1.2.3.4 you also got 2002:1.2.3.4::/48 'for free' (per 6to4). So if you want to send things to 1.2.3.4 / ::ffff:1.2.3.4, you tell your router that it's available via 2002:1.2.3.4::/48.
Any idea that you think is clever and to 'just' do X and/or Y for IPng, and would work, has probably already been thought of and attempted in the last 20-30.
There's no one clever trick to make the transition easy, the idea is to preserve the v4 address blocks in v6. That cascades down to a bunch of different decisions, some of which include keeping NAT around. They've most likely thought of that too, and turned it down because they wanted to start with a clean slate and maybe also had some other vision of pure P2P apps.
Sure they could: if your ISP owns 1.2.0.0/16, it could advertise 2002:1.2::/24 via BGP. So if someone on the other side of the planet wants to send something to 2002:1.2.3.4::/48 they would know where to send it.
And just like how something sent to 1.2.0.0/16 globally is then handled internally via IS-IS/OSPF/etc so your ISP knows how to send something for 1.2.3.4 to your CPE, your ISP would know how to handle 2002:1.2.3.4::/48 to get it to your CPE.
Routers are told to map traffic for (::ffff:)a.b.c.d to 2002:a.b.c.d::/48. If you're sending from w.x.y.z, you can put the source address as from something in 2002:w.x.y.z::/48.
It has nothing to do with "clean slate" or not. There are two immovable facts:
"""
IPv4 implementations, in 1994 and still today, have the 32-bit address format built into their code. Whether you expand the address size to 33, 64 or 128 bits, all IPv4 implementations will discard the packets. So it's a matter of mathematical and physical fact that to expand the address size, you must change the protocol, and that means two things immediately:
1. You have to change the version number.
2. You have to add new code to handle the new version.
""
* https://github.com/becarpenter/book6/blob/main/01.%20Introdu...
And this also includes 'accessory protocols': DNS A records are fixed at 32-bits, so if you want to use hostname with IPng you needed to upgrade the DNS infrastructure, including APIs to say "give me A and Ang", and then you perhaps need fallback mechanisms, in which case you're at:
* https://en.wikipedia.org/wiki/Happy_Eyeballs
Any IPng protocol, including 'just' adding bits, regardless of how you want to hand wave it as being 'just' an extension of IPv4 will be in same situation because you can't fit >32-bits in the 32-bits of the original code. You're rolling out new code in a rolling fashion, just like had to be done with IPv6.
I understand the limitation that you can never put a 128-bit address in a 32-bit field, and one way or another two hosts and everything in between have to understand the new packet format. That didn't force them to make ipv6 its whole separate network from v4 where almost no state is shared with v4. Having separate DHCP6 vs DHCP4 was a choice, likewise with DNS, NAT, and even the routing tables. It makes the difference for service operators who would be fine adopting ipv6 but don't want it to be a big project.
Anyone can publish an IETF draft document, it doesn't mean it's a serious proposal under consideration or will ever actually be implemented.
You haven't fixed any of the problems involved in deploying v6, and you added a step that was known 35 years ago to be impossible on the Internet. This isn't a useful contribution, it's just a waste of time that you could have spent on doing v6.
We're slowly reinventing OSI, one step at a time: OSI had multiple sessions per transport connection (QUIC), 20 byte addresses (IPv6) and a directory system with public-key infrastructure (DANE, vCard, SSHFP, etc).
It's a shame TUBA (CLNP + TCP) failed.
See "The Recommendation for the IP Next Generation Protocol", §8.3 TUBA Reviews:
* https://datatracker.ietf.org/doc/html/rfc1752
The document explains why SIPP was chosen (with the tweak of 128-bit addresses instead of 64).
The "solving" of encryption with TLS should not be celebrated.
Everything needs to go over TLS/HTTP-443 because of middleware boxes basically blocking everything else by default in many cases, and so application/protocol designs have to shoehorn / kludge everything into a round hole even if it's a square peg.
Certainly I'd want everything to have encryption at the higher layers (OSI 5-7), but having opportunistic encryption at IP (OSI 3) would also be great because snoopers could tell that two nodes are communicating but not how / what: RTSP? Torrent? Mindcraft? PvP2 game? If every node could (say) do an IKEv2 negotiation with every other node have IP-level traffic wrapped in IPsec that would help with traffic analysis.
Similar ish to an influencer
so fair game to cash in on that legacy.
Contract-graph routing (a core part of dtn - where do you send packets when there are delays in your route graph) was spec'd to be used, and I believe they may have done an experiment. The balloons had schedules or predictable winds, and satellites come and go (at least back then), so forwarding packets to the right carrier (or two) to get the next hop home was a big part of it.
Disc: Former Googler, Cloud Networking.
Legends
But yeah, just an awesome guy all around. One of the few people I consider to be a source of inspiration for me.
The Internet gets a hall of fame (yes including Al Gore) | CNN Business https://share.google/zmVES2oM7hINsW3mq
https://www.internethalloffame.org/tag/2012/
Click on a profile, scroll to the bottom and click the Wired link
No matter what you think of Google
There are lots of brilliant people at Google who do no evil.
The fact that the company makes evil decisions about the direction of the web, privacy, and performs blatantly monopolistic actions does not outweigh the good things people at Google have done. At least not yet.
You can hate the company but love the brilliant work the engineers have done. The same can be said of lots of companies: Apple, Anthropic, ...
Meta, on the other hand, I'm not so sure about. It's less of an overt monopoly, but some of its actions are heinously amoral.
He worked for MCI/Worldcomm, before Google. Bernie Ebbers went to jail, for that.
Ahh… the good ol’ days, when we actually jailed scumbag billionaires, instead of voting massive pay bumps…
https://www.justice.gov/epstein/files/DataSet%209/EFTA003070...
I’m concerned about the power that Google and other Big Tech companies have, but from a technical point of view Google has a lot of impressive technologies, and from a workplace standpoint, it seemed idyllic back in the early 2010s, though I’ve heard the work culture has changed in the past decade, and I may have rose-colored glasses from only being an intern there, never a full-timer.
I interacted with many professors in OS research and other adjacent systems fields when touring grad schools and I heard or saw that some were extremely toxic or intense compared to other fields I saw. With OS at least, big tech companies seem to hold a lot of influence over research directions (eg. so much of it is specifically for AI datacenters, or for one company's AI datacenter problems), and I asked OS professors about this and got disheartened replies that there was nothing they could do because of the incentives in the field. I was quite disillusioned. I know that AI being a hot new topic makes leaves more stones unturned and might lead to more publishability, but it's still depressing.
For all that we complain, it’s still the most amazing thing ever.
What's that for?
The video probably shows a wide smile whilst saying it.
Absolutely correct — and that's not sarcasm or irony. (Gore never claimed to have "invented the Internet"; that was a calumny spread by Republicans.)
It’s astonishing, I know, but the heavily-parroted meme was always reductive and is, at this point, misnformation.
Al Gore Jr.'s father, the Sr., was instrumental in enacting the US Interstate Highway system:
* https://en.wikipedia.org/wiki/Albert_Gore_Sr.#U.S._Senate
Which transformed the economy for physical goods. Jr saw parallels with the transportation of information, and coined a term (in 1978!) about it:
* https://en.wikipedia.org/wiki/Information_superhighway
* https://en.wikipedia.org/wiki/Al_Gore_and_information_techno...
— Vint Cerf, Tracking the Internet into the 21st Century <https://www.youtube.com/watch?v=Hf0rjtnwC9A>
These women played a critical role in creating the Internet we have today.
So, eleven.
The Dream Machine is a history book by M. Mitchell Waldrop that tells the story of JCR Licklider.
https://www.amazon.co.uk/Where-Wizards-Stay-Up-Late/dp/06848...
(Well actually I'm listening to it not reading, maybe that's why I can't keep track of the protagonists!)
https://web.archive.org/web/20131104212006/http://deafness.a...
> He is routinely referred to as "the father of the internet,"
There is no one else who is referred to that way. If you google "father of the Internet", Vint pops up.
https://www.inmesol.com/blog/fathers-internet/
> Vinton Cerf (Connecticut, 1943) Considered to be the founding father of the Internet.
BTW if I google father of the internet I get Cerf and Kahn or it says "a father"
And none of this is really relevant because it's TFA that should determine HN titles. But for better or worse the mod has made his decision, so this is moot -- I won't comment on it further.
And man, for someone who calls something "nitpicking" to dig so deep into it ...
https://en.wikipedia.org/wiki/Vint_Cerf
> Widely known as one of the “Fathers of the Internet,
https://www.internethalloffame.org/vint-cerf/
> Together with Vint Cerf, Kahn is known as "the father of the Internet." https://computerhistory.org/profile/robert-kahn/
So much for "but no one ever calls him father of the Internet."
It’s widely recognized that the internet has multiple fathers.
I originally took a cue from the Wikipedia page, which says, in the opening sentence, that he is recognized as one of “the fathers of the Internet”.
I’ve since tweaked the title again to be more ambiguous, but, honestly!
> but, honesty!
Honestly I expect more maturity and less hostility from mods.
I characterize it as fulminating due to the use of capitalization (which is specifically against the guidelines), along with an overall belligerent tone.
It’s just not a cutthroat enough topic to get too insistent about. We can discuss these things in a conversational style, which is what HN is meant to be for.
Edit: I see from looking over your comments in the thread that you have a personal connection to ARPANET and Vint Cerf. That’s great and we sincerely appreciate you sharing your personal insights here. We just really want HN to be a place for curious conversation rather than belligerence, which is how your first reply came across. I can understand it may not have seemed that way to you when you wrote it and I’m sorry if there’s been a misunderstanding.
Hey just joking ... I had no idea that using capitalization for emphasis is against the guidelines ... I think it's quite a stretch to characterize it as "fulminating" or "bellerigent". In the future I will write known as ... I hope italics are not also against the guidelines. (Is my snark "belligerent"? I think it's just conversational.)
> It’s just not a cutthroat enough topic to get too insistent about. We can discuss these things in a conversational style, which is what HN is meant to be for.
Seriously? For a mod you don't seem very familiar with the place. 99% of posts are "insistent" and the person I responded to (as well as yourself) are quite insistent (and belligent--considerably more so than I, IMO). And someone can be insistent "in a conversational style", whatever the eff that means ... and "cutthroat enough topic" isn't even coherent--a category mistake. I was simply presenting a counterargument to a title change that no longer reflected TFA. Frankly I think this is complete bullpucky ... belligent mod-privileged bullpucky. Again, less hostility and belligerence and more charity, please. Moderation shouldn't include characterizing people as "fulminating" or "overly belligerent", especially on such flimsy grounds -- that's pretty effing belligerent which a rational person might expect to raise defensive emotions in the person it is directed at, and with all the insistence and belligerence all over this site (have you seen all the belligerent insistent claims that people are using AI to write their posts? those accusations are turning this place to crap more than the actual use of AI is but they not only aren't moderated against, they are implicitly encouraged) it comes across as personal, immoderate, and lacking evenhandedness.
I won't respond further on this dead topic.
I wonder what he feeling about it
That was almost nine years ago, and I actually increased my development work, with the caveat that no one pays me to do it, anymore.
Probably one of the best things that ever happened to me, but I didn’t think so, at the time.
I wish him luck.
Had I coinvented TCP/IP, I’d gladly take a bullshit, cushy paying job in my latter half of my career as a ‘reward’
I personally witnessed Vint give valuable advice to managers like me, often in difficult cases. It sounds banal but often in a large corp you know what you need to do, but will have a lot of - justified or not - doubt about whether you can get through the bureaucratic molasses and the political interests of your higher ups. Vint's backing enabled a lot of people to do what's right.
One of my colleagues has printed and framed a reply from such a thread, where he offered an opinion in support of another manger. Vint replied "This is good advice. V.".
I hope he enjoys retirement, well deserved
“It is difficult to get a man to understand something, when his salary depends on
his not understanding it.”
― Upton Sinclair, I, Candidate for Governor: And How I Got Licked
https://www.goodreads.com/quotes/21810-it-is-difficult-to-ge...[1] open access journals were a big step forward, but I was open access decades before
[2] i'll join a club which is neutral on the issue, but I can't accept the positive position, not because I feel it threatens me but because it pains me to see a brilliant data scientist being jerked around (bad enough that the HR lady leaves) and not being able to tell him "your skills are in demand and you can find another employer on the other side of the street" (this is NYC) And the argument that "startups" need it is bogus: Google can take a chance on a lottery, a key employee at a startup is key however.