Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
The Internet Science

Vint Cerf on Internet Challenges 202

chamilto0516 writes "Phil Windley, a nationally recognized expert in using information technology, drove up to the Univ. of Utah recently hear this years Organick Lecture by Vint Cerf, one of the inventors of the Internet. In his notes, Vint talks about, 'Where is the Science in CS?' He also goes on to talk about real potential trouble spots with the Internet, but there is a bit on Interplanetary Internet (IPN). Apparently, the flow control mechanism of TCP doesn't work well when the latency goes to 40 minutes."
This discussion has been archived. No new comments can be posted.

Vint Cerf on Internet Challenges

Comments Filter:
  • Well, yeah. (Score:4, Informative)

    by Lally Singh ( 3427 ) on Wednesday April 20, 2005 @07:22PM (#12297706) Journal
    TCP assumes anything over 2 minutes is a lost packet.
  • by Beolach ( 518512 ) <beolach&juno,com> on Wednesday April 20, 2005 @07:23PM (#12297719) Homepage Journal
    /*
    * [...] Note that 120 sec is defined in the protocol as the maximum
    * possible RTT. I guess we'll have to use something other than TCP
    * to talk to the University of Mars.
    * PAWS allows us longer timeouts and large windows, so once implemented
    * ftp to mars will work nicely.
    */
    (from /usr/src/linux/net/inet/tcp.c, concerning RTT [retransmission timeout])
  • by Anonymous Coward on Wednesday April 20, 2005 @07:28PM (#12297761)
    so we can disseminate info like this [snopes.com]
  • by ajs ( 35943 ) <{ajs} {at} {ajs.com}> on Wednesday April 20, 2005 @07:30PM (#12297788) Homepage Journal
    Sigh.... again the Al Gore thing, and again it's modded as funny. It's not. It's a failure of our media to shoot down bad politics.

    To quote a site that bothers to keep the quote around for Google's sake:
    Gore never claimed that he "invented" the Internet, which implies that he engineered the technology. The invention occurred in the seventies and allowed scientists in the Defense Department to communicate with each other. In a March 1999 interview with Wolf Blitzer, Gore said, "During my service in the United States Congress, I took the initiative in creating the Internet."
    And he did take initiative in creating the Internet. In fact, he pushed funding for it through a congress that was convinced that anything attached to the military (and keep in mind that NSF and DARPA *are* connected to the military) was "the enemy". I heard Gore speak back then, and he was passionate about the creation of a national research network and how important it was.

    The Internet is here with us today as much because of the funding as because of the science, and Gore was the money man.

    Persoanlly, I find some of his politics a bit extreme, but like or hate liberal politics, you have to admit that the media dropped the ball by not calling Bush on this.
  • by kernel_dan ( 850552 ) <slashdevslashtty ... m minus math_god> on Wednesday April 20, 2005 @07:37PM (#12297847)
    I just assumed everyone ~knew~ we'd be using UDP between planets...

    Why isn't this modded funny? UDP is even worse than TCP: UDP provides no guarantees for message delivery and a UDP sender retains no state on UDP messages once sent onto the network. (For this reason UDP is sometimes expanded to "Unreliable Datagram Protocol".)
    Source [wikipedia.org]
  • by G4from128k ( 686170 ) on Wednesday April 20, 2005 @07:43PM (#12297890)
    I heard Vint Cerf speak at an e-business conference (remember when those were popular?).

    He talked extensively about how the layered architecture of the internet poses a serious challenge to business models. The fact that any application can communicate through any physical medium (of sufficient bandwidth) was great for interoperability, but hard on businesses that provide the physical layer.

    The problem is that all of the value is in the application layer -- people want to run software, download movies, chat with friends, etc. Whether the data flows on copper, fiber, or RF is irrelevant to the end-user and the layered architecture ensures that this is irrelevant. In contrast, a lot of the cost is in that "irrelevant" physical layer -- the last mile is still very expensive (we can hope WiMax reduces this problem). This gulf between cost and value forces physical infrastructure providers into a position of being a commodity providers with severe cost competition. If the end-user doesn't care how their data is carried, then they tend to treat bandwidth as a commodity.

    I think he was wearing his MCI hat at the time of this talk and was influenced by the beginnings of the dot-com crash. MCI's subsequent bankruptcy was not surprising. Understanding this issue explains why telecom companies don't want municipal wifi and insist that you only network your cellphone through their networks. The only way to make infrastructure pay is to bind the high-value software application layer to the high-cost hardware layer. But this strategy violates the entire layered model and enrages consumers.
  • by EmbeddedJanitor ( 597831 ) on Wednesday April 20, 2005 @07:47PM (#12297922)
    ftp's policy is to get every byte through byte-perfect and in sequence and it will retry until it gets there. udp just throws out packets and hopes they get there.

    Over a 100Mb LAN the difference is effectively nothing, but once you involve slow and lossy networks the difference is considerable. The impact is great enough over terrestrial radio nets and is a zillion times worse interplanetary.

    Let's say you have a rover that sends a position message once a second. What you're really interested in, typically, is the most up to date info. If you're using tcp, then you won't get the up to date info until the retries etc have been done to get the old info through (iie. it's noon, but the noon data is not being sent because we're still doing the resneds to get the 8 am data through). This means that the up to date info gets delayed. With udp the lost data is just ignored and the up to date data arrives when it should.

    Of course ftp still (might) be a useful way to shift large files etc, but often the udp equivalents (eg. tftp instead of ftp) will be more apropriate.

  • Re:What? (Score:2, Informative)

    by diogenesx ( 580716 ) <kyle.m.hallNO@SPAMgmail.com> on Wednesday April 20, 2005 @07:56PM (#12297997)
    Vint Cerf is one of two men who designed the TCP/IP protocol that we use today. See http://en.wikipedia.org/wiki/Vint_Cerf/ [wikipedia.org]
  • by rewt66 ( 738525 ) on Wednesday April 20, 2005 @07:59PM (#12298023)
    I believe that TCP requires an acknowledgement that the other end of the link received the packet. So, using your numbers, that would be 1339 * 2 = 2678 seconds, which is 44.63 minutes (40 minutes in round figures).
  • by menscher ( 597856 ) <menscher+slashdotNO@SPAMuiuc.edu> on Wednesday April 20, 2005 @08:11PM (#12298083) Homepage Journal
    Since latency's going to be over lightyears away

    Latency is measured in units of time. Lightyears are a measure of distance.

    TCP's no good using standard broadcast methods

    Huh? If I knew what you meant to say, it'd be easier to show you were wrong...

    We need something that'll be as fast as fiber, but will stretch way way longer in distance.

    So, like, line-of-sight laser communication?

    Current radio's a broadcast. Can't do that, especially with package leakage.

    How do you think we're communicating with the Mars rovers now? Or other planetary explorers?

    I belive there was some experiments in quantum transmissio of data, in which an electron was split and one half sent to Munich, the other sent to Venice, and transmissions where near-instantaneous.

    You can instantaneously determine what the other side received, but no information can be transmitted this way.

    I see you have a low user-id, and therefore have learned to get modded up for saying stuff that is nonsensical and wrong. I must admit I'm impressed. I earn all my mod points the hard way.

  • by 5E-0W2 ( 767094 ) on Wednesday April 20, 2005 @08:31PM (#12298235)
    You can't transfer information over entangled particles. Furthermore, faster than light information transfer violates relativity.
  • by Otter ( 3800 ) on Wednesday April 20, 2005 @08:49PM (#12298381) Journal
    And he did take initiative in creating the Internet. In fact, he pushed funding for it through a congress that was convinced that anything attached to the military (and keep in mind that NSF and DARPA *are* connected to the military) was "the enemy". I heard Gore speak back then, and he was passionate about the creation of a national research network and how important it was.

    Absolutely not. Gore entered Congress in 1977, well after any point that could reasonably be construed as the "creation" of the ARPAnet/Internet. It's true that he never claimed to have "invented the Internet" but what he did say is still completely untrue.

  • by Brandon Grey ( 877720 ) on Wednesday April 20, 2005 @10:32PM (#12299000) Homepage
    So who did "invent the Internet"? Vint Cerf and Bob Kahn often get much of the credit (as Cerf did in the above article) for inventing the TCP/IP protocols. The two accepted the 2004 Turing award for that work.

    According to Cerf, "The first demonstration of the triple network Internet took place in July 1977". He refers to this event as the "Birth of the Internet". Prior to that, researchers could send messages but had to be very familiar with the underlying technology.

    In a September 2000 email, Cerf and Kahn give Al Gore much credit in the development of the Internet: http://www.mintruth.com/wiki/index.php?Al%20Gore%2 0and%20the%20Internet [mintruth.com]

    Two excerpts:
    Al Gore was the first political leader to recognize the importance of the Internet and to promote and support its development.


    The Vice President deserves credit for his early recognition of the value of high speed computing and communication and for his long-term and consistent articulation of the potential value of the Internet to American citizens and industry and, indeed, to the rest of the world.
  • Nope.
    TCP: September 1981. Standard 7 [rfc-editor.org]/RFC 793 [rfc-editor.org] (replaces RFC 761 [rfc-editor.org])
    FTP: October 1985. Standard 9 [rfc-editor.org]/RFC 959 [rfc-editor.org] (replaces RFC 765 [rfc-editor.org])
  • Re:Need wormholes (Score:2, Informative)

    by anti-drew ( 72068 ) on Wednesday April 20, 2005 @11:27PM (#12299366) Homepage
    Once you're talking about wormholes big enough to send a stream of photons through, there are many other implications. Arthur C. Clarke and Stephen Baxter's The Light of Other Days [amazon.com] is an interesting thought experiment in that direction.

    Basically they suggest that it opens up the possibility of wormhole cameras which can be used to view what's happening anywhere at any time without anyone's knowledge. Privacy is completely destroyed and civilization, um, takes a while to get over that fact. Later in the book other corollary results show up which are even more far out.

    It's not a great book in terms of its plot, but it's classic SF ... it breaks some interesting ground and is very thought provoking.
  • by Alsee ( 515537 ) on Thursday April 21, 2005 @02:28AM (#12300390) Homepage
    You are talking about trying to measure theoretical information content, bits of entropy. In the proper context that is a perfectly valid concept of 'bit'. however the common definition and usage of bit is anything that can be in two states, and those states need not be equally likely.

    My computer has a about a billion of bits of RAM, even if on average 90% of them are zero.

    -
  • by batemanm ( 534197 ) <batemanm@gMENCKENmail.com minus author> on Thursday April 21, 2005 @03:17AM (#12300566)
    I thought, years ago when I was looking at it, that IPv6 had a TTL that was modifiable, and thus wouldn't time out.

    TTL (Time To Live) actually has nothing to do with time. It is a number which is decremented in the packet header each time the packet passes through a router. When the TTL field reaches (IIRC) 0 the packet is dropped. You can set the TTL in IPv4 if you want to, normally it is done when dealing with multicast traffic so that the packets don't travel too far out of the network multicast routing protocols also have an impact on this).

"God is a comedian playing to an audience too afraid to laugh." - Voltaire

Working...