Forgot your password?
typodupeerror
The Internet Software Apache IT Technology

Accelerating IPv6 Adoption With Proxy Servers 341

Posted by timothy
from the wool-over-your-own-eyes dept.
jgarzik writes "IPv6 presents a catch-22: the most popular web sites on the Internet don't have any incentive to switch to IPv6 until a large portion of their userbase is on IPv6, and their user base does not have a large incentive to switch to IPv6 until many of the popular Internet destinations support IPv6. My proposed solution is simple: Configure a proxy server that serves IPv6 requests, passing those requests through to underlying IPv4-only servers that not have yet been transitioned to IPv6. This article describes how to configure Apache's proxy server to fill this role, and suggests a few ideas for use."
This discussion has been archived. No new comments can be posted.

Accelerating IPv6 Adoption With Proxy Servers

Comments Filter:
  • by AKnightCowboy (608632) on Tuesday September 21, 2004 @09:15PM (#10315023)
    Make sure they're open to the public too. You don't want to be a stingy admin right? You should share your proxy server with the world.
  • by tbaggy (151760) on Tuesday September 21, 2004 @09:16PM (#10315033)
    This [sixxs.net] page/site already does it.
    • by zaxios (776027) <zaxios@gmail.com> on Tuesday September 21, 2004 @09:35PM (#10315156) Journal
      From there [sixxs.net]:"

      Why does this service exist?


      There appears to be a chicken and egg problem in deploying IPv6; ISP's serving endusers don't want to do it yet because there isn't any need for it from their clients, Hosting companies don't do it yet because there isn't any demand yet either from clients... Thus, we made this gateway, which allows users who do have IPv6 to get to all the content in the IPv4 world. If you don't have IPv6 connectivity (yet) you can of course try the SixXS Tunnel Broker.

      This is essentially the same observation and the same solution except that it focuses on getting ISPs (clients) to support IPv6 rather than servers.
  • Word of warning (Score:5, Informative)

    by rimu guy (665008) on Tuesday September 21, 2004 @09:24PM (#10315087) Homepage

    By having an open proxy anyone can send/receive data via your proxy server (duh). There are implications: e.g. I've seen someone's server bandwidth being used to serve images in a spam (pr0n) email.

    If you don't want people hiving off your bandwidth and potentially using your server's bandwidth for puposes you wouldn't normally approve of, then consider controlling your proxy access [apache.org].

    --
    Use your VPS proxy powers for the powers of good [rimuhosting.com]

  • But wait: (Score:4, Interesting)

    by Trejkaz (615352) on Tuesday September 21, 2004 @09:25PM (#10315092) Homepage
    Is it just me? I can't see any AAAA records for ipv6.org itself. I would have thought they would be the FIRST to change.
    • > server hornyandconfused.com
      Default Server: hornyandconfused.com
      Address: 69.9.172.7

      > set querytype=AAAA
      > www.ipv6.org
      Server: hornyandconfused.com
      Address: 69.9.172.7

      Non-authoritative answer:
      Name: shake.stacken.kth.se
      Address: 2001:6b0:1:ea:a00:20ff:fe8f:708f
      Aliases: www.ipv6.org
      • Right, yeah. I just noticed that they have them for www.ipv6.org. But I went to the site via ipv6.org... so... oh well. Guess I just wouldn't have got the AAAA records for that one even if I wanted to. :-)
    • Re:But wait: (Score:5, Informative)

      by Trejkaz (615352) on Tuesday September 21, 2004 @09:35PM (#10315160) Homepage
      Okay, I'll answer my own question. They have them for www.ipv6.org, but not for ipv6.org itself.
      • Re:But wait: (Score:4, Informative)

        by LogicX (8327) * <slashdot@logiGAUSScx.us minus math_god> on Tuesday September 21, 2004 @09:38PM (#10315180) Homepage Journal
        there's also no A record for ipv6.org itself also -- so boo; its not like they singled out AAAA
        its just another one of those loony sites thats www. only; and not just the domain name.
        • that's probably mostly because the www. is a CNAME to a swedish(?) uni...

          $ dig www.ipv6.org any shake.stacken.kth.se any

          ; <<>> DiG 9.2.1 <<>> www.ipv6.org any shake.stacken.kth.se any
          ;; global options: printcmd
          ;; Got answer:
          ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63697
          ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

          ;; QUESTION SECTION:
          ;www.ipv6.org. IN ANY

          ;; ANSWER SECTION:
          www.ipv6.org. 3449 IN CNAME shake.stacken.kt

  • extra hop (Score:3, Funny)

    by pythro (728638) on Tuesday September 21, 2004 @09:25PM (#10315093)
    An extra hop to go through on my web surfing adventure...NOT ON MY WATCH!
  • by Anonymous Coward on Tuesday September 21, 2004 @09:26PM (#10315098)
    IPv6 was primarily designed to solve a *problem*.

    That problem was IPv4 address space exhaustion.

    If the problem isn't hurting people on either side (client or server), then there is no reason for them to migrate to IPv6.

    For people in certain heavy net using countries (such as Japan and S. Korea) which have received a smaller slice of the IPv4 pie, then there is more incentive to move; for the vast bulk of the world there is very little incentive to move to IPv6.

    • by tokachu(k) (780007) on Tuesday September 21, 2004 @09:38PM (#10315175) Journal
      The problem exists just as much in the U.S. as it does anywhere else in the world. For example...
      Do you use NAT (a home router)?
      Blame your IPv4-based ISP for not having enough address space for you.
      Do you run a web-hosting company?
      You probably know how expensive address space is.
      Neither Japan nor South Korea had to use IPv6. They could've stuck IPv4 and NAT (something that rural broadband companies in the U.S. do, by the way), but they didn't. They chose to solve the problem rather than ignore it.
      • by SillyNickName4me (760022) <dotslash@bartsplace.net> on Tuesday September 21, 2004 @10:04PM (#10315323) Homepage
        > Do you use NAT (a home router)?
        > Blame your IPv4-based ISP for not having enough
        > address space for you.

        For most peopel NAT actually solves a problem instead of being one.

        Yeah, for some people it would be nice to be able to have their toaster online and reachable through the internet as well, and lack of addresses can make that difficult, but most people do not have a big urge to do such things.

        They do however have a problem with their computer and an unfiltered internet connection.

        A router that does NAT happens to function as a pretty good ip filter with state-keeping that is extremely easy to configure.

        > Do you run a web-hosting company?
        > You probably know how expensive address space
        > is.

        Yep, sadly enough, IPv6 sounds more advanced, and thus will be more expensive. The people who market the stuff have absolute controll over the supply so can set a price as they like.
        • Whilst your point is valid, it's not the biggest reason. NAT is so popular because it is EASY.
          Without NAT you have to have a REAL router and you then have to setup a REAL router, telling it which IP's you have attached to each interface, probably some subnetting. You can bet your average user has no idea how to setup a real router, but with NAT they can just plug in and go
        • by asdfghjklqwertyuiop (649296) on Wednesday September 22, 2004 @09:44AM (#10317972)

          A router that does NAT happens to function as a pretty good ip filter with state-keeping that is extremely easy to configure.


          NAT does not filter anything. A firewall does. You probably already have a firewall, so taking away the NAT would not change the security of your network one bit.

          • While NAT doesn't filter anything, it does achieve the same result as blocking connections by default, because people will either be trying to access your external IP which will not result in a connection without an appropriate forwarded port, or they will be trying to access your internal IP which is not routable, and backbone routers drop source routed frames. In fact, so does linux, by default, IIRC. Hence, while it's not filtering, it might as well be.
      • by Anonymous Coward
        The flaw with that logic is that, in reality, NAT was designed to solve a completely different issue. Mainly, keeping private networks away from public networks, with connectivity only as specifically allowed on a specific ruleset. A firewall, in a sense, except it was never designed to "stop" or "drop" packets as one thinks of a firewall-- only deliver them from the outside, in. The firewall effect is a side benefit in and of itself.

        With my ISP package, I get eight IPs. Eight! I'm only using five of
      • I use NAT because I want to. I could get extra IPs for all my computers no problem, but I like them being on non-routable private addresses.
      • But the allow NAT devices.

        Plus it is nice to be behind a firewall.

    • by DAldredge (2353) <SlashdotEmail@GMail.Com> on Tuesday September 21, 2004 @09:55PM (#10315271) Journal
      There are just a few other reasons to switch to IPv6...

      http://www.ipv6forum.org/navbar/events/birmingham0 0/presentations/YanickPouffary/sld025.htm [ipv6forum.org]

      Also, from another site:

      *
      A powerful addressing scheme that makes possible the allocation of public addresses to every device inside home networks

      *
      A protocol specification more powerful thanks to the extension headers

      *
      Restore the end-to-end of the Internet and facilitate the peer-to-peer communications

      *
      Simple: Plug and Play (thanks to stateless autoconfiguration)

      *
      A larger range of services to propose to customers

      *
      Security is natively defined in the protocol

      *
      IP mobility optimized

      *
      Multicast mode easier to deploy

      *
      (For the ISP, routing process more efficient)
    • What happens when ISPs start running ethernet and fiber to people's homes? Verizon is already begun to roll out a fiber to the residence service in slelected areas. I can't imagine them stopping, or others not following. Your voice, data, and television transmissions will be carried across the same connection at the same time. Your cell phone will probably have built in WLAN VoIP capability. As a result, NAT will end up hurting us, and the only solution is a unique IP for every device. Have you ever tried t
      • by Anonymous Coward
        Ever heard of UPnP? It allows auto-configuration of devices. Just plug in, and it works. Let's see, give me an IP address for everything in my house, so my piece of crap- windows running cable box can get a virus too. Good Idea! They have plenty of jobs open for people like you in Redmond.
        • See comment here. [slashdot.org] NAT has nothing to do with people running thier box with admin access rights. It has nothing to do with people who blindly open attachments, or do not use a good firewall, or do not use an AV program. NAT is a flase sense of security.
    • IPV6 was an issue, back in the days when folks still believed every machine should be directly accessible. Nat was invented as a work-around. It turns out, in the network world of today, NAT provides tremendous benefit in preventing external attacks from reaching the internal network.

      NAT was a workaround to a percieved problem, exhaustion of ipv4 address space. Now that the trend is to only have a couple ipv4 entry points to the typical lan, and have the rest of the lan in private ip space anyways, the

  • by mind21_98 (18647) on Tuesday September 21, 2004 @09:26PM (#10315103) Homepage Journal
    The solution is more ISP support. This is where you vote with your wallet. If your ISP doesn't support IPv6, find another. Same goes if you're hosting a Web site. They will eventually catch on and begin offering IPv6 more widely.
    • I don't agree. Let's imagine that every Internet user demands that their ISP supports IPv6, and the ISPs do so. What have you accomplished? Google, Amazon, Slashdot, etc. still won't support IPv6.
      • Those companies have ISP's, as well. The problem is as the uncle comment to this one states: how many people actually have ISP's available that support IPv6? And how many people will really switch to a more expensive ISP just for IPv6 when they don't even know what it is? It simply won't convince any ISP's to do anything but raise their prices for IPv6 service.
    • Not many people have the option to choose between ISPs. Where I am, it's either crap or crappier.
  • What's the rush? (Score:3, Insightful)

    by jobugeek (466084) on Tuesday September 21, 2004 @09:31PM (#10315138) Homepage
    I don't understand the rush for so many here to move. Unless you do live in SE Asia, then IPv6 isn't really necessary. Yes NAT can be a pain in the ass, but it is serving its purpose fairly well.

    IPv6 will take over just like anything else. When it reaches critical mass and demand forces it. Probably starting in SE Asia and moving westward.

    • You missed the point of the article. At the current rate of non-progress, IPv6 will never reach critical mass. IPv6 needs a jumpstart. (The Asia issue is a red herring since there is no address shortage in Asia [apnic.net].)
      • I believe I understood it completely. You believe that it will never reach critical mass and want to use artifical methods to induce it. I believe that demand will eventually push it.

        OK, so if there isn't a problem in Asia, what's the rush?

      • by Ungrounded Lightning (62228) on Wednesday September 22, 2004 @12:02AM (#10315988) Journal
        At the current rate of non-progress, IPv6 will never reach critical mass. IPv6 needs a jumpstart.

        IPv6 is getting its jumpstart. From the upcoming mobile IP vendors. They want IPv6 for tracking their phones/modems (for which they can't buy enough IPv4 address space to be confident of not hitting a wall). So they have made it a checkbox on equipment acquisition (i.e. you don't sell 'em a router unless it has IPv6 - period).

        Since they're talking equipment purchase totaling into the billions this is NOT something the equipment vendors are ignoring.

        Once there's a bunch of endpoints out there that can only be reached by IPv6 (or NAT/tunnel servers bridging to it) there will be a lot of pressure to migrate the rest of the net.
    • Yes NAT can be a pain in the ass, but it is serving its purpose fairly well.

      Is there a purpose for NAT that IPv6 won't solve better? And be less of a pain in the ass?
  • by jgarzik (11218) on Tuesday September 21, 2004 @09:31PM (#10315139) Homepage
    Silly people.

    A reverse proxy server (http accelerator) must be open to the public.

    However, that does not mean the server is an "open proxy"... the proxy configuration only proxies for the specific web sites listed in the configuration file.
  • What about dhcp? (Score:3, Interesting)

    by Mustang Matt (133426) on Tuesday September 21, 2004 @09:34PM (#10315152)
    It seems to me that it would be really useful if the little off the shelf linksys/dlink/netgear/etc. routers did ipv6. I don't see it really being used until hardware starts using it.

    On top of that it's my understanding that NAT should go away with ipv6. What is everyone with an internal network to do for IPs then? I've heard you can get free ipv6 blocks right now but they can be revoked once everything goes "live" but I don't want to deal with that.

    Ultimately I guess I really want NAT ipv4 for inside my network until my hardware can hand out ipv6 addresses that I own forever.
    • There is a NAT for IPv6, but it's frowned upon by the IPv6 people because it is a hack (and was one for IPv4). The goal of IPv6 is that every machine can be traced back to its owner and therefore can be positively identified as a particular user. Nice from a security standpoint, but pure evil from a privacy standpoint.

      I'm from the other camp - NAT helps security and for that matter, increases privacy since you can't identify the machine behind the firewall (especially if they leave the DHCP connection an
      • Re:What about dhcp? (Score:3, Interesting)

        by Izago909 (637084) *

        Fun stuff when the feds want to know who's been downloading mp3s over your hotspot and you honestly can't tell them :)

        Actually, from a legal standpoint, the buck would stop with you. All they would have to prove is that your negligence aided and abetted in a crime. Do you think that the RIAA cares that grandma didn't download that new Brittney song? No, of course not. They can still sue her because it's her internet connection and her responsibility. It's sort of like lying by omission. NAT does not help y

    • Re:What about dhcp? (Score:5, Informative)

      by kkane (179639) on Tuesday September 21, 2004 @10:06PM (#10315334)
      The intention with IPv6 is that you won't have "unroutable" networks, like we do with private nets such as 10.x.x.x and 192.168.x.x. Everything will have a globally unique IPv6 address. There was in the original spec what were called a "site-local" addresses, which were private addresses not routed to the outside much like their IPv4 analogues, but those have been deprecated.

      However, you'll have plenty of addresses because, in the current incarnation, you're not allocated a single address, but rather you are allocated a subnetwork, which is currently 2^64 addresses. So the first 64 bits are assigned to you by your ISP, and then the second 64 bits are yours to do with as you like.

      So that addresses the question of NAT: there won't be any lack of IP addresses necessitating its use. I am only addressing the use of NAT as a way around limited address space, and not any of the other uses for which NAT has.

      But what about DHCP? IPv6 comes with something more elementary, called "stateless autoconfiguration." Basically, the router constantly broadcasts your "prefix" to the subnetwork, which is the first 64 bit half of your 128 bit address your ISP assigns you. The machine then takes its subnetwork ID (the MAC address), and sets the second 64 bits to a function of that. In the case of Ethernet, it isn't the 48-bit Ethernet MAC address verbatim, but a published function of it. It's called stateless because it's always a function of whatever the network's prefix is plus some kind of subnet ID, and there's no concept of leases, or any of the state a DHCP server maintains.

      There is not yet an equivalent mechanism for "stateful autoconfiguration," which is more what DHCP is, where you can automatically assign an arbitrary address to a client. You can of course statically configure an interface to have a specific address, but there is no automated mechanism to always assign a particular autoconfigured client a particular address you designate. There are proposed standards for an IPv6 version of DHCP, however, and I expect eventually such a beast will eventually come around.
      • Re:What about dhcp? (Score:5, Interesting)

        by kkane (179639) on Tuesday September 21, 2004 @10:09PM (#10315351)
        Oh, yeah, I forgot one more point:

        Whether or not your "prefix" changes each time will be much the same as whether or not your single IPv4 address changes each time you connect. Either your ISP statically assigns you one (perhaps for an extra fee), or it doesn't. But that 64-bit prefix will be your global identifier that gives you an address space, much as the single IPv4 address is your global identifier now, except your address space is only 1 address.
      • by tepples (727027)

        in the current incarnation, you're not allocated a single address, but rather you are allocated a subnetwork, which is currently 2^64 addresses.

        Watch residential ISPs break the recommendation and grant a /128 instead of a /64 in the name of profiteering.

    • Check with your router vendor's website. It is quite likely they have a flash upgrade which supports ipv6.

      It would only make sense due to the fact that most of these devices are based on BSD code.
  • Not a Catch-22 (Score:5, Interesting)

    by back_pages (600753) <.back_pages. .at. .cox.net.> on Tuesday September 21, 2004 @09:35PM (#10315161) Journal
    IPv6 presents a catch-22: the most popular web sites on the Internet don't have any incentive to switch to IPv6 until a large portion of their userbase is on IPv6, and their user base does not have a large incentive to switch to IPv6 until many of the popular Internet destinations support IPv6.

    Nice try, but that's not a Catch-22.

    A Catch-22 is when the solution creates the problem. From the book (yes, there was a book) if the doctor diagnosed you as crazy, you didn't have to fly any more bombing missions. The catch was that you would have to be diagnosed crazy by a doctor to want to fly more bombing missions. Thus, by achieving the status of "unfit to fly", you were actually certifying yourself to fly.

    What we have here with IPv6 is two parties with no immediate reward for an investment. If one of them stepped forward, the other would step forward, and the world would enjoy IPv6. There is nothing about this that is remotely close to a Catch-22.

    • Re:Not a Catch-22 (Score:5, Insightful)

      by Bombcar (16057) <racbmob&bombcar,com> on Tuesday September 21, 2004 @10:07PM (#10315344) Homepage Journal
      I always thought that the way it worked was that if you were certified insane you couldn't fly, but the Catch-22 was that if you tried to get certified insane it proved that you didn't want to fly, which was an action of a sane man, therefore you had to fly. Nothing you could do would prevent you from flying.
    • Re:Not a Catch-22 (Score:3, Informative)

      by skraps (650379)
      I don't think your explanation is very clear. For anyone who is really interested, here [hyperdictionary.com] is a good explanation of the term.

      The part you missed is that the pilot can't be diagnosed by a doctor unless he asks to be seen; and since he fears for his own life enough to ask for a diagnosis, he is clearly not insane.

    • Correct. The submitter meant "Chicken or Egg", not "Catch-22"
    • http://www.wordorigins.org/wordorc.htm#catch-22

      Here's a much better explaination (your's is fine, but I find the link to be much more entertaining).

      The correct expression would have been "network effect". Which is the expression to state, that something is widely used, and anyone who starts using something different will have a hard time converting other people, thus everyone choses to continue using the original. Thus the network of people you interact with keeps you from changing.

      Kirby

    • Subject line says it all.
  • by That's Unpossible! (722232) * on Tuesday September 21, 2004 @09:37PM (#10315170)
    That killer app may be VoIP. If everyone wants their own IPv6 phone number.

    Or that killer app may be someone coming up with an awesome spam/virus/security solution that requires features found in IPv6.

    But just wanting people to switch for no good reason will never work. Market forces...
    • Unfortunately for IPv6, Skype works fine with IPv4+NAT.

      ThreeDegrees [threedegrees.com] requires IPv6, but it never really caught on. Maybe it would have had better luck if MS created a fake startup shell company to promote it, so then people would think it was some kind of revolution in the making instead of yet another tool of The Man's oppression.
  • Wow (Score:3, Insightful)

    by stratjakt (596332) on Tuesday September 21, 2004 @09:38PM (#10315174) Journal
    A reverse proxy or http accelerator with IPv6 on one side and IPv4 on the other.

    That is mightily impressive and you certainly are a genious of our time.
  • My 10.3 PowerBook seems to have both IPv4 and IPv6 running at the same time. Currently my Airport's IPv4 address is 10.0.1.25 and my airport's IPv6 address is fe80:0000:0000:0000:020d:93ff:fe88:f5c4. I can visit both http://ipv4gate.sixxs.net/ and http://ipv6gate.sixxs.net/. Does this mean my computer both has an IPv4 and IPv6 address, and I can visit both IPv4 and IPv6 websites? Maybe I am just missing the point of this news post.
    • You have a totally useless link-local IPv6 address. To get a real IPv6 address you either need 6to4, Teredo, or an IPv6 ISP.
    • Both the addresses you specify have IPv4 addresses, and that is what your computer is using. To see how to set up a 6to4 tunnel follow this link [evanjones.ca]. www.kame.net is the site to try to connect to for testing. Typing 'ping6 www.kame.net' give you something back, other than 'ping6: UDP connect: No route to host'.

      At the moment I can't get it working, so I'm trying to see what I have done wrong.

  • Where can I sign up? (Score:3, Interesting)

    by T-Ranger (10520) <jeffw@chebuctDEBIANo.ns.ca minus distro> on Tuesday September 21, 2004 @09:45PM (#10315209) Homepage
    And get me some IPv6 addresses? Which, if any, ISPs/hosting companies support IPv6? Who do I talk to to reserve me a chunk of space so when my bacasswords ISP gets in line, I can get me some public IPs for my boxen at home?
    • Who do I talk to to reserve me a chunk of space so when my bacasswords ISP gets in line, I can get me some public IPs for my boxen at home?

      Well for starters, you can set up 6to4 automatic tunnelling [linux.yyz.us] on your network, without having to bother your ISP at all.

      Hurricane Electric [he.net] and others offer tunnel broker services, which are static IPv4<->IPv6 tunnels. Note that most tunnel brokers refuse to forward IRC traffic.

      Certainly some ISPs are starting to roll out IPv6 service, and if that's available i

  • Funny solution (Score:3, Insightful)

    by ezzzD55J (697465) <slashdot5@scum.org> on Tuesday September 21, 2004 @09:53PM (#10315255) Homepage
    Sounds like a funny solution to me. Why not just multi-home the webservers? No extra hardware, extra point of failure, simpler, less dependency, etc.
  • The issue with ipv6 adoption is not an issue of servers or clients, it's an issue of routers.

    ISP's need to adopt ipv6.

    Tunnelling won't push adoption, but it might help YOU if you need to work with someone who is using ipv6.
  • by acceleriter (231439) on Tuesday September 21, 2004 @10:02PM (#10315315)
    Sure, China and Korea would like billions upon billions of addresses, but that's because they've spammed their IPv4 address space into every blacklist on Earth.
  • Ummm... (Score:3, Informative)

    by Talez (468021) on Tuesday September 21, 2004 @10:05PM (#10315330)
    Isn't this just 6to4 [6bone.net] which has been around for ages?
  • which offer IPV6 service?
  • by venomkid (624425) on Tuesday September 21, 2004 @10:36PM (#10315492)
    This may be a bit OT, but I'm reading many people talking about NAT like it's some horrible thing.

    As a longtime NAT user I like the fact that just one of my computers is hooked to the real internet and the others can't be diddled by outside computers.

    Even if I had unlimited IPs, I'd still probably do it this way.

  • multicast? (Score:4, Interesting)

    by Doc Ruby (173196) on Tuesday September 21, 2004 @10:38PM (#10315507) Homepage Journal
    Most people know that IPv6 delivers a bigger address space, and IPSec security. But what ever happened to its multicast tech? Is anyone sending a single multimedia stream over IPv6 to multiple recipients, without having a separately addressed packet stream like in IPv4? That feature would be the most timely, arriving just as large audiences are developing for online streaming multimedia content.
  • This is so obvious (Score:5, Informative)

    by jd (1658) <imipak@yaCOLAhoo.com minus caffeine> on Tuesday September 21, 2004 @10:38PM (#10315509) Homepage Journal
    I can remember arguments on the 6bone mailing list about such proxies. Back in 1997! The argument then was that proxies would just slow down the adoption of IPv6, because nobody would really need it on their machine, at either end.

    Of course, we now know that NOT having proxies has been a disasterous mistake. I can only hope the IPv6 community in general can accept that.

    IPv6 is more than just addresses. You have utterly transparent mobile IP. You have automatic network configuration. Anycasting allows you to request a service and have the closest server respond, without you needing to know where that server is. You have almost-mandatory IPSec - which is more than just encryption, it authenticates that the machines are who they say they are.

    IPv6 is a valuable tool. Back in the early days, I ran the first registered IPv6 node in Britain. At its peak, I had 10 tunnels running across Europe and the US. That was using IPv6 under Linux 2.0.20, using the-then VERY experimental IPv6 patches that existed. It started with static routes, but I later moved to MRT and finally Zebra.

    MRT and Zebra are now fast-decaying abandoned project, as far as I can tell. The only Open Source software router I can find is Click, and whilst it's good, it doesn't have the developer- or user-base to be confident that it can really do more than be a nice experimental project.

    (Any distro authors out there SHOULD put it in their distro, if for no other reason than the fact that Linux will cease to be useful as a router platform, if the last remaining projects don't get adopted.)

    IPv6 would benefit from having an IPv6-over-IPv4 protocol defined, much in the same way that SIT defines IPv4-over-IPv6. Again, I've argued this from the start. The idea of a migration to IPv6 will NOT be realised or realisable until the average person can plug in an IPv6 address into a browser or some other network software, without having to care about the fact that it is IPv6, and see a result.

    Once IPv6 is truly transparent to the "unwashed masses", you'll start to see people adopting it. After all, it IS easier to configure and maintain. That would make people like ISPs very happy. Less time wasted on network maintenance means more profit for them. And nobody is averse to getting a little richer, a little quicker, when it costs nothing to do. You even have the bonus that it's legal and ethical (though some wouldn't care about that part).

    Because IPv6 supports host authentication, it's great for Joe/Jane Average, too. It's harder to spoof mail addresses, when the mail server can validate the transmitting machine. That won't eliminate spam, but it will make using fake addresses slightly harder, which will give people a little more confidence that the sender is who they say they are.

    Because multicasting is part of the standard, it also means that video streaming to multiple recipients will be less savage on the network. Once people realise that you can get damn near TV-quality reception by multicast, versus 5 seconds a frame (with tiny, low-grade frames) via a typical webcast, who in their right minds will go back to that worn-out way?

    (And by near-TV standard, I'm talking NTSC or PAL resolution at 15 to 20 frames per second. The bandwidth would be impossible to maintain, if the server had to do point-to-point to every recipient, but it's very doable over a multicast transmission, and it's very normal for any of the multicasts advertised using SDR or similar tools.)

    The technology that people have, right now, versus the technology researchers have had for decades is pathetic. What you can buy as top-of-the-line off-the-shelf today was commonplace in most research labs 10-15 years ago. Some of the slow adoption comes from wanting to really test the technology. Most comes from corporations dragging their feet and exploiting the time-lag to squeeze their victims^H^H^H^H^H^H^Hcustomers for every penny they h

  • IPv6 (Score:3, Interesting)

    by strider_starslayer (730294) on Tuesday September 21, 2004 @10:46PM (#10315549)
    People will use IPv6 when they need it; when every device you have needs it's own internet connection, and routing/NAT will no longer do- providers will switch to IPv6, it'll happen basically overnight, though the use of a consortium.

    And even then most people will just take there shiny IPv6 address, NAT it and use IPv4 internally.
  • by Anonymous Coward
    After creating these gateways what is the incentive for users to switch? What is the incentive for popular destinations to switch? In both cases I think the answer is none.

    No. The answer to rapid IPV6 deployment is for someone to create an IPV6 only P2P network with a ferocious amount of free porn and mp3s. The next day everyone will be upgraded to IPV6.

    MOD me up this is both funny and the truth!
  • IPv6 internet?!? (Score:3, Informative)

    by rsd (194962) on Tuesday September 21, 2004 @11:00PM (#10315645) Homepage
    Please, correct me if I am wrong.

    Isn't the internet IPv4 only and IPv6 is archieved thru
    encapsulations like The 6Bone [6bone.net] ?

    If so, what's the point of worring about sites not being in the 6bone?

    If I am wrong, can you post some links please?

    Thanks
  • What problem? (Score:5, Interesting)

    by Zaffle (13798) on Tuesday September 21, 2004 @11:59PM (#10315975) Homepage Journal
    Seriously, what problem is this solution solving?

    I run ipv6 here at my site, every PC ont the LAN is using it.

    Inside the LAN its almost totaly native IPv6. Only the printers are IPv4 only. When surfing the web, the users browser does a AAAA DNS lookup, if it succeeds, then it does a native IPv6 connection. If you try to connect to IPv4 only site (very common), then the PC initiates an IPv4 connection. Our Internet router provides the IPv6 tunnel and does NAT'ing for IPv4. Its all totaly transparent, requiring no end-user setup or mucking around with.

    I regularily use IPv6 websites, and I don't notice that they are IPv6 unless a) the website notifies me I'm connecting over IPv6 (eg http://www.ipv6.org/) or b) i look at the traffic going through.

    The only thing I could do to "improve" the situation here would be to have my ISP IPv6 aware, so I didn't need to use a tunnel broker.

    The way that would work would be the ISP would issue a single IPv4 address and a IPv6 prefix on connect. Then the would would be a great place :)

    All my applications I write are IPv6 aware, infact they are primarily IPv6 applications with fallback to IPv4.

    Most applications you use today are IPv6 aware. The next step for IPv6 is hosting companies and ISPs proving IPv6 natively. This will happen once the backbone routers are fully IPv6 aware.

    Nick
  • BGP (Score:3, Informative)

    by Anonymous Coward on Wednesday September 22, 2004 @12:34AM (#10316113)
    BGP currently shows roughly 1.3B addresses as being routable. That represents a little more than 25% of the IPv4 space.

    There are alot of special use /8's around and a ton of academic institutions (MIT) and large corporations (Eli Lilly, etc.) that received /8 assignments back in the day.

    I can not imagine MIT utilizing 16.7M IP's, and most other /8 recipients from that time wont either.

    For more information see http://www.iana.org/assignments/ipv4-address-space [iana.org]
  • IPv5 ? (Score:3, Informative)

    by SammyTheSnake (630196) on Wednesday September 22, 2004 @08:10AM (#10317424)

    Did anyone else wonder, "whatever happened to IPv5?"?

    Well, this [oreillynet.com] seems to be the answer...

    Cheers & God bless
    Sam "SammyTheSnake" Penny

Our business in life is not to succeed but to continue to fail in high spirits. -- Robert Louis Stevenson

Working...