Slashdot Mirror


Vint Cerf Calls For IPv6 Incentives In UK

sweetpea23 writes "Vint Cerf, the 'godfather' of the web and Internet evangelist for Google, has highlighted the need for cash incentives to encourage ISPs and businesses in the UK to move to version six of the IP addressing scheme (IPv6). In response to the UK government's stance that its role in the transition will primarily be advisory, Cerf suggested a system of tax credits for upgrading equipment to v6 capability — similar to the 'cash for clunkers' scheme in the US. 'You'd have to do the math to see what impact it would have, but creating some business incentive might be helpful,' he said. His words echo those of Axel Pawlik, managing director of the RIPE NCC, who warned last month that that the IT industry is adding unnecessary risk and complexity to Internet architectures by ignoring the availability of IPv6 addresses. the Internet authority IANA is expected to assign its last batch of IPv4 addresses in June 2011."

19 of 164 comments (clear)

  1. God-father of the web by RPoet · · Score: 2, Insightful

    I wonder if Berners-Lee cringes when he sees Cerf described as "the Godfather of the web" :-)

    --
    "Oppression and harassment is a small price to pay to live in the land of the free." -- Montgomery Burns.
    1. Re:God-father of the web by TheRaven64 · · Score: 2, Insightful

      Probably not as much as Cerf cringes when he reads TBL described as 'the father of the Internet'.

      --
      I am TheRaven on Soylent News
  2. Call me retro by reiisi · · Score: 2, Funny

    I still think they should have solved this in the early '90s by switching to a byte-extensible addressing scheme.

    Something like defining x.x.x.1-127 as four byte and x.x.x.128-250.y, y 128 as five byte, and so forth.

    --
    Computer memory is just fancy paper, CPUs just fancy pens with fancy erasers; the 'net is just a fancy backyard fence.
    1. Re:Call me retro by burisch_research · · Score: 3, Informative

      Er no, IPv4 headers have space for exactly 4 bytes of destination address information. You might be able to kludge the protocol to allow for a larger address space, but as a kludge it would be inefficient, and encountering extended packets would break the majority of existing IPv4 stacks. The solution was arrived at by some very smart people, and that's IPv6. We won't run out of addresses on IPv6 for a very long time indeed.

      --
      char*f="char*f=%c%s%c;main(){printf(f,34,f,34);}";main(){printf(f,34,f,34);}
  3. Re:carrot and stick by metamatic · · Score: 3, Insightful

    Lots of government procurement already depends on your product being IPv6 capable. The problem is really the ISPs. I'm ready to switch on IPv6 tomorrow, but my ISP doesn't support it, so I'm stuck tunneling.

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  4. Re:carrot and stick by Bert64 · · Score: 2, Insightful

    They should simply mandate that anyone providing internet connectivity (ie any isp or telco) MUST provide ipv6, either alongside or instead of ipv4.
    If every end user and every site they try to visit is dual stack, a lot of traffic will occur over ipv6 without users even realising it and ipv4 will gradually die out.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  5. Oversimplifiying... by Junta · · Score: 4, Interesting

    For one, the protocol defined address specifically as 32-bit. Functions processing IPv4 generally use unsigned integers for the address. Functions to do a variable length address would take longer to process/route. The routing tables would likely be atrocious even if it theoretically could work.

    In short, it only does better at backwards compatibility at the extremely superficial aspect of entering addresses textually looking more usual and making a more specific effort for an existing IP to map trivially to a new scheme. Existing IPv4 stacks would have had no easier time trying to talk to 192.168.2.250.2 than fd7e:691a:da42::1. Besides, having the high values magically become reserved on the host portion of existing networks would conflict with existing host addresses in use.

    IPv6 can work but has been subject to three major pitfals:
    -It looks scarily different. People treating addresses like phone-numbers and not doing DNS in a ubiquitous has exacerbated the problem.
    -They completely omitted a strategy for v4-only to v6-only communication until this year. For a long time they didn't want to endorse anything with the letters 'NAT' in them and delayed a sane interop strategy hoping the problem would magically disappear so the 'evil' NAT wouldn't become a pillar of v6. I'm optimistic that the results of this year paves the way for meaningful progress.
    -v6 and associated protocol largely chose to throw the baby out with the bathwater on many fronts. v6 for a long time declared DHCP dead, then when DHCP was revived for v4, they threw out the existing behavior and started from scratch, eliminating many option codes and changing client identifier behavior to be hard for existing DHCP admins to deal with. This has in some cases rendered workflows in IPv4 simply impossible and in many more exacerbates the first problem in that a *lot* of relearning and reworking is required to acheive the same results with IPv6 as in IPv4.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Oversimplifiying... by Junta · · Score: 2, Informative

      when DHCP was revived for v4

      Err, I meant v6.

      --
      XML is like violence. If it doesn't solve the problem, use more.
  6. Re:Reverse flock mentality by houstonbofh · · Score: 3, Insightful

    Or, a bunch of overworked networked admins that don't want to start a big project for a problem they are not feeling yet... Switching over my office would take a lot of time I do not have for absolutely no payoff. And my 10-12 hour days are full already.

  7. Re:Misspelled name - not broken, don't fix it by h00manist · · Score: 2, Informative
    --
    Build your own energy sources from scratch. http://otherpower.com/
  8. Re:carrot and stick by gentry · · Score: 2, Informative

    Not true. I get IPv6 straight out of a PPPoE connection (would be PPPoA if my ADSL modem/router supported IPv6). This is via Andrews & Arnold and costs £18 pcm.

  9. Re:I got a sixxs tunnel account today by klapaucjusz · · Score: 2, Informative

    What is there different to see or do? Not much.

    Of course not; the goal is not to build a new network, but to make sure that the Internet can continue to grow. So what you get over IPv6 is just the current Internet, but with a good chance that it'll be still around in ten years.

  10. Re:I got a sixxs tunnel account today by gentry · · Score: 2, Funny

    A dancing turtle is not enough?!?

  11. Re:ISP-supplied modems/routers IPV6 compatible? by KiloByte · · Score: 2, Informative

    Then they'll just use IPv4. We're not talking about single-stack IPv6 for now, and not for many years from now as well.

    There were several criminally broken models of home routers that blackholed AAAA DNS requests causing long timeouts, but they are basically the only technical obstacle to giving customers native dual stack, at least where the last mile is concerned. And those can get their firmware upgraded.

    --
    The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  12. Re:carrot and stick by lga · · Score: 2, Insightful

    How is 1GB per month enough for anything except a few emails? Here in the real world we use streaming audio and video, download software updates, and buy games on Steam at 10GB a time. Get back to us when that costs less than £100 per month with Andrews & Arnold.

  13. Farmville and IPV6 by h00manist · · Score: 4, Funny

    not customer facing because that's a much bigger job.

    Farmville is giving players free virtual cash for anyone connecting over IPV6. That will get users banging on the ears of the ISP companies.

    --
    Build your own energy sources from scratch. http://otherpower.com/
  14. Re:ISP-supplied modems/routers IPV6 compatible? by TheLink · · Score: 2, Informative

    AFAIK, Google doesn't provide AAAA records for most of their services to just anyone: http://www.google.com/intl/en/ipv6/

    --
  15. Re:Security? by j+h+woodyatt · · Score: 2, Insightful

    Doesn't adoption of IPv6 remove one of the more effective layers of security we have today, the obfuscation layer, being hidden behind the router?"

    Please read Local Network Protection for IPv6 [RFC 4864].

    --
    jhw
  16. Running IPv6 in practice by Mathieu+Lu · · Score: 2, Interesting

    I always had a hard time understanding IPv6 until I read the Running IPv6 in practice howto on Debian-administration and tried it at home. The next move is configuring the office where I work to use such a tunnel, then a friend's colo server, then our hosting environment. It's really not hard. Get over the adressing scheme. IPv6 is much easier to manage than NAT.

    Tunnelbroker by Hurricane-Electric also does a great job of making IPv6 easy to use and fun to learn (the "certification" games). They also throw in free DNS hosting, and announcing IPv6 addresses using BGP is possible.

    Now stop whining and bite the bullet :-)