Accelerating IPv6 Adoption With Proxy Servers 341
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."
Proxy server fun (Score:3, Funny)
Re:Proxy server fun (Score:5, Insightful)
I can't imagine that's abusable. I mean, nobody would embed ads in their IPv6 proxy if it became too popular, right?
Just a thought.
Re:Proxy server fun (Score:4, Funny)
I use mine not only to convert to IPv6, but also to convert English measurements to Metric, Relational Databases to Object Databases and any text to Esperanto.
Re:Proxy server fun (Score:5, Insightful)
Re:Proxy server fun (Score:3, Funny)
So not at all then?
The opposite is already there.. (Score:4, Informative)
re: The opposite is already there (Score:5, Informative)
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 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]
Re:Word of warning (Score:5, Informative)
But wait: (Score:4, Interesting)
Re:But wait: (Score:2)
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
Re:But wait: (Score:2)
Re:But wait: (Score:5, Informative)
Re:But wait: (Score:4, Informative)
its just another one of those loony sites thats www. only; and not just the domain name.
Re:But wait: (Score:2)
extra hop (Score:3, Funny)
Re:extra hop (Score:5, Funny)
I don't even have internet on my mobile phone yet, let alone my watch. I bow to your uber-geekiness.
Most people don't care about IPv6 (Score:5, Insightful)
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.
Re:Most people don't care about IPv6 (Score:4, Insightful)
Re:Most people don't care about IPv6 (Score:5, Informative)
> 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.
Re:Most people don't care about IPv6 (Score:3, Insightful)
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
Re:Most people don't care about IPv6 (Score:4, Informative)
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.
Re:Most people don't care about IPv6 (Score:3, Informative)
Re:Most people don't care about IPv6 (Score:3, Informative)
I'm not talking about source routing. I'm talking about plain old vanilla routing.
You've got two machines on one big network which from our perspective is an ethernet. Perhaps the underlying stuff is the cable cloud in your part of town.
One machine on this network is a router with public IP 172.30.0.2, not filtering anything. Behind this router is 10.0.0.0/
Re:Most people don't care about IPv6 (Score:3, Informative)
With my ISP package, I get eight IPs. Eight! I'm only using five of
Re:Most people don't care about IPv6 (Score:2)
Bzzzt. Wrong. My ISP Charges for IP addresses (Score:2)
Plus it is nice to be behind a firewall.
Re:Most people don't care about IPv6 (Score:5, Interesting)
http://www.ipv6forum.org/navbar/events/birmingham
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)
Re:Most people don't care about IPv6 (Score:3, Insightful)
Re:Most people don't care about IPv6 (Score:3, Interesting)
They want to start rolling out services that will require full time IP connectivity to EVERY phone. If you start doing the math thats a major chunk of the IPv4 address space.
Re:Most people don't care about IPv6 (Score:2)
Re:Most people don't care about IPv6 (Score:3, Funny)
Re:Most people don't care about IPv6 (Score:3, Interesting)
Re:Most people don't care about IPv6 (Score:2)
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
Nobody's running out of space (Score:5, Informative)
Re:Nobody's running out of space (Score:2)
What do you mean that I can not get one with IPv4? What do you mean that I have to pay somebody else and even then I do not own it? Hummmmm.
Irrelevant (Score:2)
It is true that you cannot own IP addresses.
That has nothing to do with the fact that there is no address shortage (under a sane usage model).
Re:Irrelevant (Score:2)
Re:Irrelevant (Score:2)
Switch area codes, get a new phone number - switch ISPs, get a new block... seems similar enough to me...
Or am I missing something?
Re:Nobody's running out of space (Score:2)
That's not the solution. (Score:5, Informative)
Re:That's not the solution. (Score:2)
Re:That's not the solution. (Score:2)
Re:That's not the solution. (Score:2, Insightful)
What's the rush? (Score:3, Insightful)
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.
Re:What's the rush? (Score:2)
Re:What's the rush? (Score:2)
OK, so if there isn't a problem in Asia, what's the rush?
IPv6 is getting a jumpstart. (Score:4, Interesting)
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.
Re:What's the rush? (Score:2)
Is there a purpose for NAT that IPv6 won't solve better? And be less of a pain in the ass?
Re:What's the rush? (Score:3, Insightful)
Re:What's the rush? (Score:2, Interesting)
A purpose for NAT is the closed-by-default firewall that its common implementations provide as a useful side effect.
Reverse proxy servers always open (Score:5, Insightful)
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)
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.
Re:What about dhcp? (Score:2)
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)
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)
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)
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.
Re:What about dhcp? (Score:2, Insightful)
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.
Re:Why would a residential customer WANT a /64? (Score:3, Insightful)
Just as a comment: "some people" probably amounts to 0.01% of paying customers, and is therefore totally insignificant. Even networking professionals - who understand well why IPv6 is better - realize that IPv6 can not happen overnight, and there is really no clear need for it today. Majority of people just buy a $99 wireless router (NAT) from Linksys, and they are all set on their own Class A network. What else is there for them to ask for?
It is also understood that IPv6 shines in a lot of areas (w
Re:Why would a residential customer WANT a /64? (Score:3, Interesting)
Re:What about dhcp? (Score:2)
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)
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)
Re:Not a Catch-22 (Score:3, Informative)
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.
Re:Not a Catch-22 (Score:2)
Re:Not a Catch-22 (Score:2)
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
It's called a "viscious circle" or "chicken & (Score:3, Interesting)
IPv6 Needs a Killer App (Score:5, Interesting)
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...
Re:IPv6 Needs a Killer App (Score:3)
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)
That is mightily impressive and you certainly are a genious of our time.
So what does Mac do? (Score:2)
Re:So what does Mac do? (Score:2)
Re:So what does Mac do? (Score:2)
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)
Re:Where can I sign up? (Score:2)
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)
This has been mentioned before. It's still moot. (Score:2, Informative)
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.
Re:This has been mentioned before. It's still moot (Score:2)
Getting an ISP to make large technical changes is too not hard..
Getting any of the union telco/comm workers to lift a finger in the name of change; that is the hard part.
The world doesn't need all that address space. (Score:4, Funny)
Ummm... (Score:3, Informative)
Are there any DSL providers in the US (Score:2)
IPv6 as a "solution" to NAT? (Score:3, Interesting)
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)
This is so obvious (Score:5, Informative)
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)
And even then most people will just take there shiny IPv6 address, NAT it and use IPv4 internally.
How does this help? (Score:2, Insightful)
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)
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)
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)
There are alot of special use
I can not imagine MIT utilizing 16.7M IP's, and most other
For more information see http://www.iana.org/assignments/ipv4-address-spac
IPv5 ? (Score:3, Informative)
Did anyone else wonder, "whatever happened to IPv5?"?
Well, this [oreillynet.com] seems to be the answer...
Cheers & God bless
Sam "SammyTheSnake" Penny
Re:ISPs (Score:2)
mod parent up (Score:2)
Re:ISPs (Score:5, Insightful)
What would be interesting is if ISPs would assign a static IPv6 address to customers who have dynamic IPv4 addresses. If the ISP has IPv6 at all, they have a huge block of addresses, which they could trivially assign to their customers by account number. And then there would be people who would set up IPv6-only sites or sites where the IPv6 address was more reliable, because the address was free.
Re:Users will never switch... (Score:2)
Though, I do predict that once ppl realize that they can own their own IP's space, then we will see a rush to it similar to dns as well as phone numbers.
I can get a vanity ipv6 space? Cool
Re:IPv6: Not Ready For Prime Time (Score:4, Informative)
The IP numbering allocation in IPv6 is hierarchal, which they are not in IPv4. The first 16 bits are the FP and Top Level Address (allocated to "trunk" cos like MCI), the next is a 32 byt "Next Level Addres" allocated to ISPs, and finally "Sight Level Address"es allocated to people like you and me.
At the moment many routing tables on the trunks have thousands of entries, increasing as allocation of IPv4 becomes more and more fragmented, significantly slowing down the trunks. IPv6 will mean considerably fewer routing table entries there, increasing performance.
Although the raw IPv6 header is larger than the minimum IPv4 header, a system of, in effect, encapsulating parts of the headers in the data packet that are not needed in routing exists where it does not in IPv4 (such as those needed in TCP). The savings there should more than make up for the degregation in increasing the minimum size of 20 to a fixed size of 40.
It is a misconception that IPv4 produces 4 billion IP addresses for the world to use. By the time all the university's Class A addresses and all the wasted IP addresses of those who have networks with machines missing are considered, all the network and bradcast addresses and so on are also considered you will be lucky to see 3 billion. In fact I would not be surprised if the figure was nearer 2. This may be enough for the Western World but not for Asia as well.
IPv6 is also neccessary to adopt the up and coming internet technologies, such as those that use MultiCast (IPv4 implementation of this will NEVER get adopted). I agree with you that it is the routers that are holding this back - but once an area is enjoying the benefits of IPv6 then I believe it will rapidly spread.
My 2c worth....
Re:IPv6: Not Ready For Prime Time (Score:2)
That's what happens when you let the MBA's dictate the path of technological development. I mean, why use the best solution when you can... forget using logic to justi
I call bullshit. (Score:3, Insightful)
Re:IPv6: Not Ready For Prime Time (Score:5, Informative)
Okay, I won't argue with you there.
It's deliberate overkill. It allows things like 64-bit subnets, which in turn allow for stateful autoconfiguration. It also allows for large chunks of address space that won't be allocated at all; if it turns out in the future that our current allocation method is inadequate for our needs, we can simply devise a new allocation method in this empty space, rather than having to migrate to a whole new version of IP.
Yes, if an IPv6 router had to hold nearly 150,000 routes in memory like it does in the current IPv4 world, it would be massive. Fortunately, IPv6 is designed to have properly aggregated addresses, so that things are much more hierarchical, and routing tables can be stored much more efficiently.
Aside from the fact that more and more connections are using much larger MTUs these days, IPv6 also supports more aggressive header compression than IPv4 did, often resulting in similarly compact headers.
Re:IPv6: Not Ready For Prime Time (Score:5, Informative)
If you're so confident that your dissertation has academic merit, why don't you put your name to your post?
1) No arguments, mainly because I don't know about the architectures of the Cisco and Juniper PEs used.
2) For a post-grad student, you don't seem to know much about IPv4. Almost 17 million addresses taken by each of 127/8 and 10/8. Another million gone with 172.16/12. 192.168/16 rounds that all out to about 36 million. Almost one percent of the address space gone, just on reserved ranges. The experimental ranges take some more space again. Then there're all the network and broadcast addresses, with CIDR making that problem worse, even while it does solve the issue of giving organisations blocks of space that're wildly in excess of their requirements.
3) I dunno who makes your NIC, but all mine have a 48-bit MAC.
IPv6 does nice aggregation. Routers only need to know about their immediate network, everything else they see as an aggregation. So rather than knowing about every
Plus, RAM's cheap. Even the Kingston stuff you need for Ciscos. Couple cheap memory with the very good route summarisation in the IPv6 spec, and it's a non-issue.
4) The current IP network has these restrictions. With jumbo frame and the various other techniques now in existence, you don't think it's possible that part of the migration to IPv6 will be to throw a few more bytes into the packet size?
I can't belive you got a +4 (Informative) for that load of tripe. No wonder people have no respect for the moderators!
Re:IPv6: Not Ready For Prime Time (Score:4, Informative)
A few quick issues with your points, just be glad I'm not on your review board, it wouldn't be pretty.
Oh, and if you actually read said RFC you would learn that it is not a solution, it is a bandaid. Just read the abstract: