Ask Internet Visionary and Pioneer Vint Cerf
As co-designer of TCP/IP (along with Robert E. Kahn), and former chairman of ICANN, it is no exaggeration to say that Vint Cerf is certainly one of the fathers of the internet, and is often referred to as simply the father. His lifetime of network engineering accomplishments — meriting, among many other laurels, the Turing Award — leaves little doubt as to why he's now a full-time internet visionary for Google (and formerly with WorldCom) as well as a Google VP. Now, Cerf has graciously agreed to answer Slashdot readers' inquiries about the past and future of this little thing called the Internet, and his role in it thus far. This short call for questions is inadequate to sum up his contributions to engineering the data flows that entangle and enlighten us in 2011, but read through a few of these capsule descriptions to get a sense of them. In accord with the interview guidelines, please try not to lump together unrelated questions. (You may find that your questions are moderated downward if they aren't concise; if you have several distinct questions, simply submit separately as many as you'd like.)
If there was one thing you could go back and change about TCP/IP -- something that is far too entrenched to change now -- what would it be?
My work here is dung.
Can you talk about any time when you felt that the direction of Internet development was not going in the way that you hoped it would?
What level of success does TCP/IP owe to your glorious beard?
My work here is dung.
I'm wagering you've studied many communications protocols -- is there any protocols that you feel was terribly designed and implemented? Any modern day elegant/simple/innovative protocols that you've admired?
My work here is dung.
Anything you can tell us about Dennis Ritchie?
He was like a hermit... that's why I would like to know more about him.
And what are you doing for a living?
... in the Thunderdome? Or was it more of a Highlander thing?
My work here is dung.
"I'll tell you one thing. If we had known that someday politicians and corporations would come out and destroy everything, they'd have stayed in our cubicles and written the internet off as a bad idea!"
Agree?
I'm curious what technologies you would like to see developed next, or what you think would be most important to develop next. In other words, what do you think researchers should work on now that would be most significant?
Oh, and thank you for changing my life!
In your opinion, what is it going to take to get the Internet switched over to IPV6?
A house divided against itself cannot stand.
TCP/IP started as a military project but has been adapted for all the Internet applications we see today. What sort of applications do you foresee/imagine for the Interplanetary Internet, aside from the stated purpose of coordinating NASA devices?
What impact did your college experience have on you? Do you feel it set the foundation for your future or not?
What is you opinion regarding Internet privacy?
Do you think anything should be changed?
Google and the University Internet-2.5 consortium are experimenting with it. Other forward-looking countries have 10x broadband speed at lower cost than US.
Do you think governments and corporations world-wide will be able to kill the Internet as we know it?
Could you see a protocol ever supplanting TCP/IP?
So you went to high school with Postel and Crocker according to wikipedia? Did you guys hang out all along or meet up decades later?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Where do you stand on the issue of Net Neutrality?
Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
So you're on the board at ARIN. Anything public you want to say about how ARIN is handling ip address exhaustion other than the "company line"?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
So are you keeping current with IPv6 and if so what is your opinion of IPv6 NAT? Good / evil / other?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Which area of online service provision should entrepreneurs and market speculators sink their attention into
My question: Do you feel the security concerns over collected information will trump the leveraging of information in future Internet technologies? Will there be a separate "opt-in" or "opt-out" web to cater to each preference?
Context: There have been many controversies recently regarding the collection of data and the privacy of individual information. As we move forward, I've heard a mixed set of messages regarding the direction we should expect to see.
Consumerism is indeed driving innovation and everything is going mobile these days (there's an app for that I think). One example I heard recently of the benefit of the convergence of information and mobility: a consumer can point their mobile phone at a shelf of groceries, get an active "overlay" of information regarding the products and determine which best suits the customer needs. On the flip side, sensors that track customer behavior are installed at the grocery shelf and based on detected behavior (like stopping for a moment to reminisce about Coco-Puffs even though you know they are bad for you) initiates a coupon for whatever the vendor may feel would provide enough motivation to purchase their product -- in the example a $1 off coupon to the mobile phone of a shopper.
Will this become reality in the future? I think there are benefits to be had, but also am fiercely protective of my personal information and preferences.
"There *IS* no patch for stupidity" -www.sqlsecurity.com
It seems that it is getting more and more difficult to successfully run your own SMTP server. See, for example, this post responding to the idea that a user was going to move off gmail to their own server. Are there any prospects for meaningful SMTP reform that would lower the barrier to entry for legitimate emailers?
DNS has been often criticized as a centralized single point of failure / censorship. Have you been following the development of namecoin and P2P DNS? Are these systems viable in your estimation? How would you improve them or encourage their adoption?
The US Customs department recently created headlines in seizing domains. These seizures appear to be extra-legal (not founded in law), but ICANN has gone along with them. Are those fair statements? Should ICANN's trustworthiness be suspect as a result of this process?
Thanks and cheers.
-molo
Using your sig line to advertise for friends is lame.
Two extremely closely related questions:
1) Conversion from 16 bit to 32 bit BGP AS numbers half a decade ago or so: Went smoother or rougher than you personally expected? Or just right?
2) How does the answer to #1 above modify your view of whats likely to happen with the ipv4 to ipv6 transition?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Greetings. Once upon a time I was fortunate enough to ask you about IPv6, way back in 2002. The phrase '6 by 6' (for IPv6 by 2006) was the goal, but it seems we've missed that target. Do you ever foresee mandatory widespread adoption of IPv6 happening? Should IPv6 have been designed to be interoperable with IPv4?
"Powers. I have them."
How can your average Internet user best ensure that net neutrality is continued or even strengthened and not whittled away or outright canceled?
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
Hardware accelerated ipv4 routing/switching was out there, I donno, at least a decade ago, or more. Your expectations on the rollout of hardware accelerated ipv6 switching?
"Science flies us to the moon. Religion flies us into buildings." - Victor Stenger
Sorry if this brings back traumatic memories but was "The Architect" in "The Matrix Reloaded" (the second Matrix film) supposed to be you? Did the producers get your permission? Did you like your portrayal?
(Or maybe that was "The Colonel" from KFC after he went on a diet.)
The key advantage of TCP/IP is how it handles for Loss packets, going across an unknown network and far more failure prone hardware. However today as the internet is now running on much more reliable hardware and the path goes threw some well maintained backbone. Would you have come with TCP/IP today if you had access to modern technology/infrastructure?
Or do you think you would have a different design all together?
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
What a giant mess you've created. You really didn't think this whole internet thing through did you?
Dr. Cerf,
I had the pleasure of working with you years ago at MCI. I recall that at the time, you spoke frequently of the need for an "Interplanetary TCP/IP" standard leading to development of an "Interplanetary Internet." With the recent budget cuts for U.S. manned missions, do you see this effort becoming more or less imperative? On a related topic, do you believe humanity will need to rely more on autonomous robots for space exploration? Or will Americans have Chinese and Russian space-chauffeurs for the foreseeable future?
Thank you as always.
In the future, hopefully in the not too distant future, we will begin to utilise the moon.
Do you think that it will be possible to extend the terrestrial internet to encompass the moon? Would you envisage if that happened that it would be using an extended version of TCP? Or do you think that there would have to be two separate internets one on each body?
Can you elaborate how TCP "slow start" got its name.
Since the congestion window is exponentially opened, it's not exactly slow.
I mean, congestion avoidance, with additive increase, that's what I would call slow in comparison.
Do you think that Internet traffic should be encrypted end-to-end? If TCP/IP would be created today, would it include encryption features?
The technical project that is most close to you, right now.
Did you ever forsee the primary usage of the internet being pornography?
There are currently pretty widely held beliefs that some groups (such as Facebook) have superbly evil business practices. I know Google is in competition with the company, but what, if anything, is Google planning to do top stop the actual perpetrators of suck things hiding behind the indemnification of a corporation?
Where can I get one of those cool "IP on everything!" tshirt?!? Thanks!
How would you go about stopping, or at least curtailing, the erosion of privacy on the internet?
What is your view on communication integrity and privacy?
The Internet has provided an excellent medium for freely expressing different viewpoints. But governments and businesses are increasingly threatened by such freedoms, and doing a lot to suppress them. How do you see this playing out, and how can we ensure that we keep such freedoms?
Software sucks. Open Source sucks less.
Do you think there should be a .here TLD, reserved officially for local use in an analogous way to the way that the RFC1918 IP addresses are reserved officially for private use?
Currently many are coming up with their own adhoc TLDs for local use. In my opinion this is suboptimal. Having a standard official TLD would allow more interesting things to "organically grow" on it.
See also: http://tools.ietf.org/html/draft-yeoh-tldhere-01
The flip side of the same coin:
"What is you opinion regarding Internet DRM?
Do you think anything should be changed?"
Looking at the state of the world, and the Internet today, what is your (a) greatest hope for the Internet's future, and (b) greatest fear?
Do other people (who may not be that computer literate) perceive you as some kind of cool tough-looking computer wizard? Anyone can admit you don't look like the stereotypical slightly overweight caveman-looking nerd, but rather like a big tough well-dressed and classy man with an awesome beard. How do other people (teenagers, average Joes/Janes, etc.) see you when you brag about creating the Internet? Do they admire you (or at least give the impression that they do)?
Could IPv6 have been designed to be more like IPv4 and thus easier to adopt? In retrospect, would it have been better to restrict design changes to the minimum required to support larger addresses?
Have you got your LWN subscription yet?
Hello,
6lowpan is the proposed/open ip-standard for microcontrollers (for e.g. domotics, streetlighting, "smart powergrids", ...). Vint Cerf's whine-cellar is already controlled by it - it uses products from Arch Rock, which was bought by Cisco - and google will probably launch a lightbulb based on it by the end of the year, which can then be controlled by an android-phone. It is based on ipv6 so that it can form the internet of things.
I've split it up in multiple small questions:
* Will it have enough support to take off? (biggest competitor is Zigbee, which also is going towards ip) ,* Will the lack of support for ipv6 (in Western countries) not slow down the take up? ...?
* When will it probably take off? (next year?)
* Will it be standardized/open enough for an opensource community? There is a mesh-header in the protocol, which isn't used by open implementations like those in Contiki because it there are drawbacks to it. The routing-protocol RPL was developed to work on the ip-layer and which is standardized. However, implementations like those of NXP (the google light-bulb uses their hardware at least) use their own stack (jennet-ip), which uses this mesh-header, which causes routing at layer 2. The stack will be opensourced at the end of this year - the time at which google will "launch" the lightbulb -, but I would rather use an open implementation like that one contiki. It also doesn't use the mesh-header, but that is a personal preference.
* Will it be cheaper then current home-automation-systems as it is more open?
* Will people/companies be cautious enough regarding the security-aspects of 6lowpan (and similar technologies). What about a virus causing havoc in your home - lights don't go on, temperature goes up and up,
I'm quite interested into this myself as I would like to use 6lowpan myself and even develop for it (if it is open enough).
References:
* Arch Rock - Cisco: http://newsroom.cisco.com/dlls/2010/corp_092010.html
* wine cellar/internet of smart objects: http://www.ipforsmartobjects.org/2010/07/video-vint-cerf-smart-grid-talk.html
* google light bulb: http://www.sunwavelighting.net/index.php?option=com_content&task=view&id=171&Itemid=9
Almost every protocol on top of TCP has to re-invent framing. Why is TCP/IP a byte-stream protocol instead of a packet stream protocol?
One of the biggest hurdles to IPv6 adoption today is that the average home user simply cannot get an IPv6 address from their ISP. Tunnels are hacker toys, and completely impractical/impossible for people who are using their ISP's "home router". What do you think we can do to convince ISPs to start rolling out IPv6 [i]before[/i] there is a crisis? Everybody agrees that the transition will go smoother if we take it slow and easy, but nobody is willing to make the first step, and IPv4 addresses aren't still being inexorably depleted the world over.
I read the internet for the articles.
Hello, 6lowpan is the proposed/open ip-standard for microcontrollers (for e.g. domotics, streetlighting, "smart powergrids", ...). Vint Cerf's whine-cellar is already controlled by it - it uses products from Arch Rock, which was bought by Cisco - and google will probably launch a lightbulb based on it by the end of the year, which can then be controlled by an android-phone. It is based on ipv6 so that it can form the internet of things.
I've split it up in multiple small questions:
* Will it have enough support to take off? (biggest competitor is Zigbee, which also is going towards ip)
* When will it probably take off? (next year?) ,* Will the lack of support for ipv6 (in Western countries) not slow down the take up?
* Will it be standardized/open enough for an opensource community? There is a mesh-header in the protocol, which isn't used by open implementations like those in Contiki because it there are drawbacks to it. The routing-protocol RPL was developed to work on the ip-layer and which is standardized. However, implementations like those of NXP (the google light-bulb uses their hardware at least) use their own stack (jennet-ip), which uses this mesh-header, which causes routing at layer 2. The stack will be opensourced at the end of this year - the time at which google will "launch" the lightbulb -, but I would rather use an open implementation like that one contiki. It also doesn't use the mesh-header, but that is a personal preference.
* Will it be cheaper then current home-automation-systems as it is more open?
* Will people/companies be cautious enough regarding the security-aspects of 6lowpan (and similar technologies). What about a virus causing havoc in your home - lights don't go on, temperature goes up and up, ...?
I'm quite interested into this myself as I would like to use 6lowpan myself and even develop for it (if it is open enough).
References:
* Arch Rock - Cisco: http://newsroom.cisco.com/dlls/2010/corp_092010.html
* wine cellar/internet of smart objects: http://www.ipforsmartobjects.org/2010/07/video-vint-cerf-smart-grid-talk.html
* google light bulb: http://www.sunwavelighting.net/index.php?option=com_content&task=view&id=171&Itemid=9
Michel Brabants
Belgium
Hello Vint
I've enjoyed since com-priv days, the rise of the Internet - Thank you. 20/20 hindsight shows the Internet grew without statutory jurispudence. Is that statutory blackhole in which the Internet now lives responsible for holding back growth and development of Internet economies, digital cash and cyber laws that are truly global w/o jurisdictional boundary?
If a global medium is not able to support global economy, however does the world escape market constraints bounded by juridictional rules, regs, statutes and accords to enable freedom of exchange, trade, commerce and rising World-wide economic tide?
RexRiley
The biggest thing I hate about IPv6 is that the standard format uses colon as the digit separator. On most keyboards, that is a fairly awkward character to type, especially in rapid fire between groups of hex digits. Also, it causes problems for the many many programs that specify ports after IP addresses with a colon (like URIs!). IPv4's use of the period instead is much nicer. If you didn't want to reuse the period (so programs can distinguish between the two types of addresses more easily), why not use dash instead? It's just as visually appealing and doesn't require you to hit shift to type it. It would have saved a whole lot of ugly brackets around IP addresses.
Any aesthetic qualities of the colon are lost when you have to do this:
http:/// [1005:3321:5a52:4fca::1]:8080/
instead of:
http://1005-3321-5a52-4fca--1:8080/
And that second example was noticeably quicker for me to type.
Edit: And of course because this is Slashdot it made a huge mess of the first URL and forced me to mess it up slightly to be readable!
I read the internet for the articles.
growing up as the son of Bennet Cerf?
I'm a consultant - I convert gibberish into cash-flow.
That is to say do you think that too much power & control now lies in the hands of the Internet Service Providers, thereby making it, at least in terms of control if not routing, too centralised & too easily manipulated by the powerful few. I guess this question stems from a viewpoint that it should be somehow democratic & free (as in free speech). Also do you share my pedantic belief that the public Internet should be spelt with a capital 'I'?
The ducks in the bathroom are not mine. [http://www.27bslash6.com]
How do you feel about the censorship & control efforts of countries such as China?
The ducks in the bathroom are not mine. [http://www.27bslash6.com]
What are your views on IGMP/RTP/UDP as a transmission interface?
How do you see the future of interactions between the internet of things and Google?
Few human's can attributed to be both communications protocol inventers and well.. dapper.
Can you speak to the importance of being well dressed, groomed, etc. when interacting with non-technical people? Do you attribute your stylistic dress to your overall success in anyway?
Moreover, every C standard library that I have ever tried is able to resolve this bigger number to the correct address. If I ping a 10 digit number in that address range, the C standard library will figure it out. It is my position that this is a feature and not a bug.
It seems that the OSX Firefox Guys don't agree with me. Admittedly they do have an RFC on the subject, but their browser breaks a known behavior that every other TCP/IP client program on the planet exhibits, including other operating system versions of Firefox!
Would you kindly bludgeon one of us into submission? I don't really care which side of the argument you come down on, but one of us has to be able to say "Because Vint Cerf said so!"
Oh, and while I've got you, I'm sick of writing stateless http applications. May I have your permission to go back to writing plain old socket servers on other ports, providing data based on whatever query format I feel like implementing? It kind of looks like REST, I suppose, except that I don't have to load 14 layers of frameworks to get to that point.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
With IPv6 we could all have fixed IP addresses (or blocks of them) at home. Is this likely to happen? What do you see as the pros and cons from the ISP point of view for doing this? I think the reasons I want it are the reasons they don't, but I'd like to know how someone with your perspective sees it.
People always say the internet started with the first networked computers, or the ARPANET & similar networks. I, on the other hand, put the epoch at the first implementation of TCP/IP. What do YOU consider it to be?
Mod parent up. In ten years I've never said that. Old dog, new trick. Also, was the mistake thinking we needed to do this too quickly?
Absolutely, there are many questions here unworthy of extended discussion. One doesn't to consult Donald Knuth to master quicksort. There's a huge literature on overdesign, discounting through net-present-value, adoption risk, and the difficult promulgation of technical standards.
TCP/IP has had roughly the same amazing thirty year run as x86. I've followed the twists and turns with x86 far more than IP, so I have a pretty good idea what I'd write on a napkin to send back to the original x86 design team--supposing it was actually a going concern to make the design not suck and that suckitude was not actually the criteria by which IBM originally chose this part, leading it's relevance thirty years later. (On the former question, I think Intel wanted to make a good part; on the later question, I think IBM was seriously gun shy about the future arriving quick and capable. In Terminator mythology, the napkin to Intel would fail, and be followed by a cyanide capsule to quavering bean counters over at Big Blue.)
First suggestion for Intel: offset the segments by 8 bits instead of 4 bits. This gets you a 16MB address space which gets you to viable 32-bit multitasking without a foray through DOS extenders. Let me put this iron into the fire to demonstrate, in a few minutes, the pleasure it will bring to thousands of programmers if you don't follow this advice. I think there would have been very little practical cost to this--even if I don't tell them that segmented data protection would fail. That feeble 20-bit address space was penny wise and pound foolish any way you look at it.
Second suggestion: either set all the status bits, or none at all with extremely few exceptions. In the short term this simplifies compilers, in the long run it expedites data flow implementations (i.e. OOO scheduling).
Third: Variable instructions length is a mixed blessing. Good if the first byte determines instruction length. Have at most one byte in the instruction which encodes allowed combinations of what might otherwise become prefixes/overrides. Variable instruction length improves icache density; a 30% efficiency gain over 32K of icache more than pays for 500 extra transistors in the instruction decode logic. Think about slope and intercept on instruction encoding density. Ideally your first byte tells you if you have a override bitfield and which byte contains it.
Fourth: Have more index registers than just SI and DI. This one is tricky since any expansion of the register set slows task switching. Maybe it should wait and become "have more index registers than ESI and EDI". But I think not. 16 registers is plenty in a RMW architecture. You don't need 32 registers unless blinded by RISC purity.
Fifth: Plan to transition the x87 co-processor from stack-based to register addressed at the earliest possible opportunity.
Sixth: Add an instruction to bit reverse bytes. Add an instruction to popcnt bytes. Chicken and egg problem. If you build it, they will come. Always have an instruction to byte reverse your longest supported register.
All the other x86 complaints: ignore completely. It's the future trying to eat your lunch after depreciating your opportunity cost and adoption risk to zero.
If you recall clearly what the world looked like when ideas are first on the drawing board (x86 is my personal case study for thinking about this), it's a lot harder to send advice back through the time machine that isn't actively dangerous.
How many of my suggestions would have rewarded them right out of the gate? Not a one, unless they put a full court press on high quality C compiler, to exploit the suggested register
TCP port 443 is the new waist of the Internet, and it doesn't look like that's going to change with the transition to IPv6 either. Should we just forget about concurrent multi-path and multi-streaming at the transport layer and do it all at the application layer? Or do you think there might still be room for fixing these problems at the transport layer?
jhw
simply, where does your responsibility for the internet end? Are you to blame for only the good things?
-rick
Which wasn't there before initially as good as it could be (because look @ it out there today online with all the hacker-cracker types, security breaches, or malwares that took advantage & just due to flaw in base early original yet current IP design... E.G.-> DNS for example (kaminsky hack, redirection/dns-poisoning, & far more), & many other services over time too)...
* I'd wager that I would do the security end better because it's widely known it was a major factor/concern in the original design as was say, re-routing automatically around downed routers etc. (due to for instance, nuclear attacks)
Just based on the "malware/hacker-cracker explosion" the last 8++ yrs. now, etc./et al, too mostly...
APK
P.S.=> More address space possible too, of course. I wager the folks that designed it NEVER thought it was going to be so widely used & by so many first of all, or, get to be as "big" as it is today possibly as well - because IF they did? We would have had a more "IPv6-like" setup already for example...
... apk
What did you think of two girls one cup?
What are your feelings towards goaste.cx?
As we (hopefully) step out into the solar system, how do you see the internet adapting to meet the need for interplanetary communication (communication protocols, addressing, name resolution, carrier mediums, etc...)?
The head of UN's WIPO believes that the Internet (and obviously the stack on which it runs) should have been patented. How do you believe it would have evolved, would TCP/IP be protected by patents?
You're currently on the Governing Board of the NIST Smart Grid Interoperability Panel. What is the state of standards development, and how big an impact does it have to move national infrastructure communications into the public IP arena so far as our ability to strengthen and expand our infrastructure? Conversely, how big are the threats in this new world?
Do you see a use for subnet-independent multicast? By this I mean: instead of one address, the packet has a list of addresses and is only duplicated when routing requires. It seems to me this could drastically reduce the bandwidth needs in cases like broadcast video streaming.
I take it that the "route around failures" and other original design features of TCP/IP and the Internet as a whole relied upon trusting others always having good intentions and cooperating. Those designs were necessary at the time and the reason the internet exists today.
Nowadays distrust, firewalls, and coding defensively is the norm (or it should be). In that light, the internet's design seems creaky and vulnerable.
Do you have any thoughts or feelings on how software has changed and seemingly become so treacherous since you first designed TCP/IP? Would you advocate a ground-up redesign of internet transports and protocols starting with TCP/IP?
One of the secrets of the internet's massive success is the lack of controls over it; if there had been strict security and processes in place it would likely not have come about. One of the downsides is that all our security measures are tacked-on, there is no built-in security to the protocols used on the internet and as a result security is a massive problem. How do we go from the wild west to having at least a reasonable level of trusted computing?
If we really do have an IP address for every atom in the universe, how can we use it in physics?