IPv6 Application Competition - win $10,000 217
sneekz writes "The IPv6 Promotion Council of Japan has announced a competition for developers of IPv6-enabled applications. Various prizes up to $10,000 for ideas and actual implementations, and you keep the rights to your work. From their site: 'The contest will award developers of applications and software which helps to create new possibilities in the Internet world.'"
but... (Score:5, Interesting)
Re:but... (Score:5, Informative)
Or IPv6 Tunnel Broker (Score:5, Informative)
And even if your ISP won't assign you an IPv6 subnet, you can always utilize a free Tunnel Broker [tunnelbroker.net] to obtain a huge IPv6 address space of your very own (tunneled to your IPv4 IP). I used this recently when adding basic IPv6 support to the Nmap Security Scanner [insecure.org]. My announcement [insecure.org] also provides a concrete example of IPv6 being used to subvert firewall rulesets.
A ton of useful IPv6 information is available from Kame.Net [kame.net] -- once your setup is working, the turtle on the top of that page starts to dance :). I also found the Linux IPv6 HOWTO [tldp.org] to be incredibly helpful.
-Fyodor
Concerned about your network security? Try the Free Nmap Security Scanner [insecure.org]
Re:Or IPv6 Tunnel Broker (Score:2)
Re:Or IPv6 Tunnel Broker (Score:2, Informative)
If there would be more endpoints listening on the 6to4 prefix, it would be Good...
Re:Or IPv6 Tunnel Broker (Score:3, Informative)
huh?
6to4 users can interact perfectly well with non-6to4 IPv6 addresses. They just need to set a default route to a 6to4 relay router. And RFC 3068 makes that universally trivial.
Re:Or IPv6 Tunnel Broker (Score:2)
Re:Or IPv6 Tunnel Broker (Score:2)
Oh, and if anyone reading this is in a position to do so, setting up a 6to4 relay router and advertising the RFC 3068 route is probably one of the best ways to help the cause of IPv6 migration.
Re:but... (Score:1)
IPv6 info (Score:5, Informative)
Re:IPv6 info (Score:2)
Re:IPv6 info (Score:4, Interesting)
Re:IPv6 info (Score:1)
Re:but... (Score:2)
Re:but... (Score:5, Informative)
seems like everybody sometimes... (Score:4, Informative)
ah, lots of people, actually... it's all over the routers and servers, nowdays... but the local network admin and network engineers are probably doing their best to make the migration as invisible as possible.
A good starting point to learn more about IPv6 would be www.internet2.edu [internet2.edu]. If you check out the corporate partners, you'll notice that ATT&T, Cisco, IBM, Intel, Lucent, Microsoft, Nortel, Qwest, SBC, and Sun are all in on the "Internet2" act, which includes the IPv6 protocol And the list of affiliated universities stretches nearly 200 members long...
Anyhow, Sun Solaris 9, Microsoft Windows2000, Microsoft WindowsXP, and Cisco IOS all have support for IPv6, as I understand... They're publicaly using it and supporting it.
If you want to know more about IPv6, check out this link [rfc-editor.org] and just search for the term "IPv6"... you should get about 93 articles regarding the Request For Comments (RFC) procedure used to define the protocol... As you will notice, IPv6 is a 128bit protocol, and was designed to be able to be broken up into 4 32bit packets, which allows it to interoperate with older IPv4 networks...
Moral of the story is that there are millions of people already using IPv6 on their client machines, who already don't know and don't care about the specific protocol implementations...
The article refers to an award for application developers to develop IPv6 enabled applications... If you calculate the ratio between IPv6 address and the total surface area of the earth, you will notice that there are approximately 2,000 IP addresses per square meter, with the IPv6 protocol... enough to give an address to every nut, bolt, and widget in every plane, train, and automobile on earth, with billions and billions left over... The awards will be going to people who figure out not just how to use IPv6, but how to code new applications and new uses for that kind of domain space...
Re:seems like everybody sometimes... (Score:2, Informative)
"If you calculate the ratio between IPv6 address and the total surface area of the earth, you will notice that there are approximately 2,000 IP addresses per square meter..."
However I can't seem to recreate it. Here is my math.
IPv6 is 128 bits: 2^128 = 3.4028e38
Surface area of Earth: 5.1007e14 m^2 (verified on 3 different sites)
3.4028e38/5.1007e14 = 6.6713e23 IP/m^2
That is a whole lot more than 2000, so one of us made a mistake.
Re:seems like everybody sometimes... (Score:2)
Just a quick guess, but use 30% of 5.1007e14 and it will probably be closer to 2,000. The stat probably only takes into account land mass.
That is an interesting idea though, geographically assigned IP addressing. Although DNS services will have to become much more configurable with IPv6 before it gets really widespread adoption. I'd like to see a named that utilizes a quick stripped down SQL database.
Re:seems like everybody sometimes... (Score:3, Informative)
Anyway, I think the most common ways to implement IPv6 and IPv4 "interoperability" are:
- Use a dual IP layer to support both IPv4 and IPv6. This requires both IPv4 and IPv6 addresses however, and address selection rules. DSTM (Dual Stack Transition Mechanism) might help solve problems with too few IPv4 addresses for the mapping.
- Tunnel the IPv6 traffic over the IPv4 infrastructure. Encapsulate IPv6 packets within IPv4. This method is used on the 6bone [6bone.net].
- Translate the headers with transition tools. Simply translate the IPv4 header into an IPv6 header. This method can only translate information shared by both protocols. This method can be used to make IPv4 hosts on a LAN able to interoperate with an outside IPv6 network, where the translator function much the same as a NAT.
Re:seems like everybody sometimes... (Score:2)
Great question and well asked...
Will there be some kind of latency / higher traffic usage due to larger headers or some such with ipv6 traffic due to the extra "detail" it provides (apologies on lack of terminology)
The answer depends on how you measure latency and traffic usage... so, in some sense, the answer is both yes and no. The packets are larger, by protocol definition, so there will definately be higher overhead. This is offset, however, due to the fact that IPv6 is a protocol which has been designed and formulated with specific technologies in mind... specifically, high bandwidth connections. As fiber optics, fast ethernet, and gigabit-copper become more common, total bandwidth will increase, and the relative increase in latency/traffic is offset by higher bandwith availability. Call it information inflation, if you will...
In some sense, IPv6 was designed with fiber optic backbones and routers in mind... so, yes.. there will be slightly more traffic usage and latency, but the next generation of network cards and routers are expected to be optimized for 128 bit mathematics... (specifically, in order to deal with 128 bit address routing tables) so, the latency and traffic usage will be offset by the reduced processor overhead needed to calculate the 'details' which are incorporated into the header (such as quality of service and such...). That is, the network engineers know that fiber is becoming more common, and this protocol was designed with forward-thinking concepts: high network bandwidth, very large numbers of nodes, dynamic network topologies, security and cryptology, etc. etc.
In the long run, IPv6 won't cause excessive latency or traffic usage on future networks... It may be a resource-hog on circa-1990s network equipment, however...
Anyhow... I'm rambling... there are people more knowledgable than I in this matter, and I'm sure they'll post their 2 cents worth as well. Best of luck in learning more...
Worldcom/UUNet isn't.... (Score:2)
That pretty much kills any possibility that I'll be putting it to real-world use anytime soon.
-Chris
How about one that creates the slightest interest (Score:2, Insightful)
Re:How about one that creates the slightest intere (Score:2)
NTT has offeredIPv6 connectivity (both tunnels and native) in Europe and the States for about two years now. I don't know how long they've been operating in Japan (NTT is a Japanese firm). See this [ntt.net] site for lots of information.
My idea... (Score:3, Funny)
More of everything (Score:4, Funny)
.. would be just MORE of everything. Like:
- increased timewasting at the office due to faster, clearer, saucier porn downloads
- even greater levels of theft and destruction of the capitalist system as we know it by illegal music sharing
- yet more time spent deleting bucketloads of crap from our inboxes as spam increases to unprecedented levels
Yeah, its pretty revolutionary stuff all right.
For Idea Contest... (Score:3, Informative)
Aren't there enough papers [nec.com] already on IPv6? Especially on purpose #1 (i.e. increasing the internet experience).
For #2 (i.e. promoting widespread), it's highly debatable, IMHO...
All packets are created equal (Score:4, Funny)
although a bit more address space would do nicely...
Re:All packets are created equal (Score:4, Informative)
Re:All packets are created equal (Score:2)
Re:All packets are created equal (Score:2)
IPv6 is only a good thing; How it is administered is a separate issue. This is the concept I was trying to hint at :)
Re:All packets are created equal (Score:5, Insightful)
unless you (and your ISP) are manually setting all of your TOS bits to 0, that is.
Protocols are mechanism, not policy. The reason why you haven't complained as yet of your IPv4 traffic being "slowed to a crawl" is that TCP's QOS features (minimal though they are) are typically only used when needed and ignored otherwise.
I would rather have the possibility open to shape traffic, should I want to, than to pre-emptively close the door because others might use it in ways I disapprove of. There are plenty of legitimate uses for QOS besides pissing off gamers (though I consider that an important activity in its own right
Diffserve/IntServe (Score:2, Interesting)
It is a while ago now and I have had other things on my mind, but basically what I found out is that on the internet there is no real need for QOS as bandwidth is increasing all the time, satellite links are reolaces by fiber (less latency and delay, and a lot more bandwidth), fiber is being replaced by "thicker" fibers, etc.
Just to give you an idea of the amount of bandwidth available - only 2.9% of all fiber optic cables layed alongside powerlines, rail roads etc are actually lit. And those that are lit, thos in use for the internet only have a maximum use basically of 50%.
Also, in order to give certain datastreams priorities over others, you need to track these, which adds processing delays and with networks where bandwidth is not a problem - why do this?
Also, something often overlooked:
In order to actually give packets priority over others and shape the traffic depending on priotities, you need to queue at least 200 packets it was discovered by some researchers, otherwise the queuing algorithms just do not have enough data to actually put into different queues. Think of it this way, if the queues are empty, then of course the data is sent to the top priority queue and you gain nothing.
Basically, there are two concepts: Diffserve and Intserve.
Intserve goes against the nature of the internet (in my opinion), as it uses RSVP to set up a quasi-static route through the internet, does the reservations, and then the flows have to be monitored. Keeping track of individual flows on the backbone routers? No way! And if the route changes, all the reservations have to be done again. Intserve (IPv6 has a Flow Label to facilitate this) has no place on the internet backbone in my opinion.
Intserve is very useful though in an organisation, where you have control of the network, and to give certain flows priorities getting out of that bottleneck router to the internet and then let best effort scheduling do it's work.
DiffServe on the other hand is viable in my opinion as this is hop per hop based. Diffserve works by marking packets and assigning it a traffic class.
This is very useful when you have flatrate customers, and customers that have are willing to pay for bandwidth. Of course the routers could and may already mark traffic of those customers paying for bandwidth with a higher priority.
Something which I really like about Diffserve is the ability to give packets a drop priority ("Hello you little nice router, If you really need to drop a packet, please drop this one").
This could be very useful in the case of video over the internet where the network itself regulates the quality of the video. What I proposed in my thesis, was to have an algorithm that send the most important coefficients in a packet with a low drop priority, the next batch with a medium priority and the rest with a high one, and in addition to that also have the software on the other end report back some statistics so sending is also reduced.
What this is allows is to have video not stop, but just instantly become of less quality if there are congestions.
Speaking of congestions, they only exist till the packets they reach the backbone.
And of course getting down from them again.
What has my post got to do with IPv6? Well, IPv6 has a Flow Label and Traffic Class in the IP header which are for IntServe/DiffServe.
Ipv6 facilitates IntServe/Diffserve, but does not really add anything new in this respect. It just makes it easier to process, because it is always at the same place whereas this info in an IPv4 packet could be at varying locations due to the variable length of an IPv4 header.
Re:All packets are created equal (Score:4, Interesting)
The end points (eg your Quake client and the server) usually set the QOS field, and what is theorically suppose to happen is the routers along the way go.. ah, he wants low latency, so I'll send these packets down this link.
However, what usually happens is most routers ignore the QOS bits.
As for the slow downs, etc. That may be your upstream (ISP), who may twiddle the bits, but they can only do that based on a number of factors, to/from port, IP address, bandwidth usuage, etc.
There is nothing (much) you can do to avoid your ISP slowing down certain connections, except by making it hard to identify what is "legitimate" and what is "illegitmate" traffic. Eg giFT uses random port numbers of both sides, so its very difficult for the ISP to say, lets throttle giFT traffic. Freenet does much the same thing.
IPv6 will not answer the bandwidth and traffic shapping problems, all it will answer is the limited number of IP addresses problem. (And if you think about it, probably cause more bandwidth problems because you'll be able to have *LOTS* of different devices all plugged into your upstream bandwidth, all sapping it).
My recommendation is if you live under a draconian ISP is one of the following:
1) Move ISPs. If All ISPs are like this, move country.
2) Go postal, grab yourself a semiautomatic assult rifle, storm into your local ISPs NOC (network operations centre), and demand a 100mbit connection for your laptop, "right this instant!".
3) Find an open proxy, use that to bypass port based traffic shapping. If your ISP is shapping every port but port 80 (web), go find an open proxy that is running on port 80 and use that for other connections. The best bet would be find some willing (or otherwise) machine somewhere outside of draconia, and put a SOCKS proxy on port 80 on the machine.
4) Implement IP over carrier pigeon. Pigeons are not known for looking at each IP packet and flying differently because of its contents, though if the packet size is too large, it could slow the transport mechinisim down. I'm not sure if this RFC supports IPv6, but sinces its a transport mechinisim, I should think it would matter.
Re:All packets are created equal (Score:2)
I have this idea... (Score:4, Funny)
Woohoo! (Score:4, Funny)
For high level languages like Python, I imagine all the work has been done for me already.
exchange rates... (Score:3, Funny)
So that's like what, 50 bucks total?
Re:exchange rates... (Score:2, Informative)
Why
Figures are off (Score:5, Informative)
Award for Promotion 5 works 150,000 yen each (1,246.03 USD)
Award for Planning 5 works 50,000 yen each (415.332 USD)
Grand Prix 1 work 1,000,000 yen (8,306.775 USD)
Award for Excellence a few works Total 1,000,000 yen
Award for Fine Works a few works Total 500,000 yen (4,153.15 USD)
So they are paying people to port applications to IPv6 now? hmp.. I would have thought that the ISP's and telicos would have ported to it automaticly when Internet IP's started to dry up.
Re:Figures are off (Score:1)
Re:Figures are off (Score:1, Insightful)
Just be patient... (Score:2)
Re:Figures are off (Score:2)
still, they're not infinitely available like they will be with IPv6, so development is hindered within IPv4. This, in a sense, implies that we'd quickly run out of IP addresses if we used them for everything we want to.
Sponsors (Score:5, Informative)
NTT Communications Corporation
A subcompany of the NTT group; the country's largest ISP.
Fujitsu Limited
One of Japan's largest manufacturers of PCs and servers.
Impress Corporation /. users should know this one - it runs the Akiba PC Watch site.
Internet Research Institute, Inc.
A company founded to take advantage of academic research. Funded by Yahoo Japan/Softbank (Softbank's one of Japan's largest Internet-related companies, and actually runs Yahoo Japan).
KDDI CORPORATION
Japan's #2 phone company after NTT.
Matsushita Electric Works, Ltd.
Japan's largest manufacturer of electronic goods.
Nokia-Japan Co., Ltd.
Need I say more?
Mitsubishi Research Institute, Inc.
The Mitsubishi group's research organization.
The reason Japan's so hot for IPv6 is that it got rather shortchanged in the IPv4 handout - the ratio of IPv4 addresses to users is much worse than in the US.
Re:Sponsors (Score:2)
Each office that Verio had was done through a buy out. So Verio has an immense amount of IPv4 adresses. Hence NTT has them.
NTT is just being smart, thats all.
Puto
Re:Sponsors (Score:2)
The reasons why new IPv4 addresses are harder to come by in Japan than in the US are mainly internal JP politics - the policies of ARIN and APNIC are almost the same, and there's still new IP addresses to be had, if you're able to navigate the paperwork. (For a few years more).
Re:Sponsors (Score:5, Informative)
IP addresses (US): 1,847,483,219
IP addresses (Japan): 41,943,663
IP addresses (Canada): 61,747,968
The number of users is debatable, but make it, say, around 30% of the population of each country.
Users (US): 250 million x 0.2 = 50,000,000
Users (Japan): 120 million x 0.2 = 24,000,000
Users (Canada): 30 million x 0.2 = 6,000,000
Which means the ratio of IP addresses to population is:
US: 36.95 IPs/person
Japan: 2.573 IPs/person
Canada: 10.29 IPs/person
So, as you can see, Japan's getting a little desparate... hell, even Canada has five times more IPv4 addresses per user.
Re:Sponsors (Score:1)
Otoh... (Score:2)
Obviously, a huge problem.
Re:The polite, wired Canadians (Score:2)
nostalgia (Score:5, Funny)
-a
My entry (Score:5, Funny)
-John Ashcroft
Great Idea! (Score:1, Funny)
2) ???
3) Profit!!
money savings (Score:1)
It seems like a good idea to me. Having a contest and offering a small lump sum is probably cheaper then hiring a whole bunch of developers to think up some applications. Not only will it get people to dream up ipv6 apps, but get more people to understand what its all about.
I must say that this seems to be a great idea on the ipv6 promotional councils part
Re:money savings (Score:2, Interesting)
It appears you get all the copyrights but they are allowed to disclose and distribute your product whatever that means. It could mean they can sell it or give it to whoever they want. The terms sound a bit iffy to me. Any lawyers out there want to offer up an interpretation?
Re:money savings (Score:2)
Back on topic, I think offering contests to promote tech and keeping the rights is a great idea for buisness. Google does that with their contests.
RIAA may hate me for saying this.... (Score:5, Funny)
Imagine a world with IPv6 enabled devices.
Now when someone receives a subpoena from RIAA with the IP address, they can always reply back that there was a mistake because that IP address belongs to the microwave or the toilet bowl cleaner scheduler device..
what this contest proves (Score:3, Interesting)
A consortium of some 300 individuals and corporations interested in the promotion of IPv6 have to offer significant amounts of money just to generate interest in this new protocol. A decent Internet protocol should not be forced on the public cum pecunia; it should be developed openly and freely under the currently-existing RFC standards. If there were any real, useful applications of IPv6 to the whole world, then an open, free-entry consortium would be overseeing the transition from IPv4 to IPv6 now.
However, there is no desperate shortage of IP addresses under the current scheme. While there are less IPs than theoretically possible (256^4 = 4,294,967,296), thanks to overhead and mismanagement (MIT getting its own Class A subnet makes perfect sense...NOT), nevertheless there is no current need for this initiative.
The fact is, this contest is simply a ploy by these companies to get your intellectual capital at a fraction of its potential worth. Do the world a favor and make your ideas and code snippets public and free (or GPL'd). Death to corporate tyranny!
Re:what this contest proves (Score:4, Informative)
The desire for point-to-point connectivity is nothing more than that; a desire. The real-world Internet doesn't really care all that much if it can't touch millions or billions of anonymous hosts behind NAT. The fact that it can't means, for example, that Slammer was only able to infect the routable hosts. Imagine the effects of something like Slammer if every single MS SQL server was actually routable from the public network. Yes, I know, NAT is not security. Until the IETF invents a way to force network operators to care enough about security to be worthy of allowing all their hosts to be routable, I'll remain pretty appreciative of the benefits of NAT in the real world.
Claims that IPv4 is inherently doomed due to the demands placed on routers I find difficult to believe. The size of the graph that is the Internet will not get smaller with IPv6. If IPv6 provides a more efficient means for "routers" to comprehend that graph, why can't that solution also apply to IPv4? Routers get faster right along side all other computing devices. Routers are also becoming a figment of the IETFs imagination. The old fashioned IP Internet is quickly being supplanted by ATM et al, and most of the "routing" is being done via virtual circuits between IP endpoints. IP "routing" is being relegated to the edges of the core.
The commercial world solved the IPv4 problem. IETF just doesn't care to notice.
Re:what this contest proves (Score:2)
It could, but it would force everyone to be renumbered, which they will not accept.
Re:what this contest proves (Score:2)
As opposed to IPv6, which everyone is clearly so excited about accepting? Which of these three options is more likely to be considered acceptable outside the ivory towers of IETF;
a.) mitigating the size of routing tables by renumbering existing subnets
b.) implementing an entirely new protocol
c.) buying bigger, faster routers
If you know anything of the commercial world, you have absolutely no doubt about the correct answer.
Re:what this contest proves (Score:5, Insightful)
Dumb network, smart edges.
When IPv4 was designed, there was no plan for exponential user growth outside of military/R&D/education. If there had been, addresses would've been 48+ bits from 1980 onward.
The failing with pre-existing networks which IP was meant to surmount is that the interior of the network was too intelligent. That sounds like a good thing, but it means that the network as a whole is less flexible- the inner nodes (routers) cannot be easily upgraded to support new applications and features. Under IP, all interesting computers are into hosts on the edge of the network. Each can be upgraded by an end-user, without supplication to the network templars- be they Bell Atlantic frame relay technicians, or Novell NOS admins. Those smart edges are served by a dumb cloud- the rest of the network just passes data from one place to another, without translating or modifying it in anyway. In the past, network application growth was slowed because users couldn't easily tell what was going on inside the cloud. IP made the cloud's job boring, so that you were no longer interested in seeing what went on there.
That change triggered the explosive growth of computer networks until they combined into the shared entity we all know and love.
NAT betrays this heritage
NAT boxes move intelligence back into the cloud- instead of IP packets being routed to the desired host and no other, there are now entities hidden in the cloud which waylay your packets. They seize them, pull them apart, inspect their innards- then, maybe, they'll deign to alter the packet and send it along further.
The damage isn't just a theoretical one- real end-users are being held back by NAT and other violations of the IP promise. New applications which would be easier to deploy with real per-host addressing are difficult or impossible to install reliably. This is things like high-speed game servers, file/web servers, P2P clients, cheap VOIP, videoconferencing, VPN, and prehaps things that haven't been invented yet.
The internet should be about giving power to the users on its edges. IPv6 would encourage that, but NAT hinders it. There are forces who don't want to empower users- major content providers and big ISPs. (Which may be the same [aol.com] thing [time.com]). Fearful of losing control of mass audience's entertainment patterns, they want to keep mass creativity centralized. AOL doesn't want users to download ClickNRun IRC-like servers to create TeenTalkDaytonville chatrooms, they want to sell them as a value added service. Time Warner doesn't want 100s of cheap FTP servers passing out free copies of 56 year old TV shows (which by rights are public domain [eldred.cc]), they want you to wait for the DVD or PPV options.
The desire exists. A chicken in every pot, and permanent IP address in every study! The powers that be are fearful, though. The existing entertainment/datacomm oligopoly was harmed enough by the Internet. End-users sharing data amoung themselves could ruin them- but the exhaustion of IP addresses provided an excuse to keep end-users cordoned off from the real internet. They could download, but not serve files- as long as the people remain "consumers", the corporations can keep them under control.
NAT boxes bring the internet a tiny bit back towards the shape of traditional TV and telephone networks, which is just how big business likes it.
Re:what this contest proves (Score:3, Insightful)
I see... Then the car companies also *solved* the gasoline/oil problems. Intel and AMD *solved* the power consumption and heat issues.
A band-aid is not a solution...
Re:what this contest proves (Score:2)
He also has an essay about why ATM is bad for computer networks [clock.org] here.
Re:what this contest proves (Score:3, Funny)
"Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats." -- Howard Aiken
Re:what this contest proves (Score:2, Insightful)
Funny how the term "hack" is a pejorative with regard to NAT.
Why doesn't my mobile phone have a real IP address?
Why should it?
Why does a 1 MBit residential ADSL service come with just
Because the ISP is being frugal with their netblock. They know, as well as you do, that 1 address is enough. Do you think that IPv6 will suddenly provide the means to operate a vast subnet with that ADSL service? That's naive. Most DSL contracts for home users already prevent this sort of thing.
Do they think the average home with DSL has only one computer?
Nope. They know damn well there's likely to be >1 host behind those endpoints. I bet they're also well aware of the fact the most of those hosts are vulnerable to no end of remote attacks that most of their customers are blissfully unaware of this because they're safely behind NAT.
Current allocation strategies are punitive, and the aggregation problems already have caused some small organizations to "fall off the network" due to routing table overflow.
There are routers available that are capable of keeping up. You get what you pay for in ISPs just like everything else. If an ISP allows this to happen to it's customers, what makes you think they're interested in the investment necessary for IPv6?
Of course this means people like you are going to imagine a conspiracy right up until they notice that now 10 billion hosts are on the Internet...
I agree. This is no corporate conspiracy. This is a conspiracy of the elite. The commercial world solved the IPv4 problem. The academic world doesn't care to hear about it.
As to an "open, free-entry consortium" there are any number of organizations that more or less match that description. Governments and larger ISPs have given a lot of money to these projects so that the transition goes smoothly. Far sighted people (e.g. those who can do a quick head count and see that 6 billion potential users on a network with 4 billion addresses won't work) have been trying to kick start this for ages, and the longer we wait the more painful it will be.
If there were a real problem IPv6 wouldn't need all this nursing.
Re:what this contest proves (Score:3, Insightful)
I want to use peer services with my phone. My solution is IPv6. Your solution "Don't do that".
I want to use peer services with my laptop in the kitchen, from a pad in the TV room, and with my games PC upstairs. My solution is IPv6. Your solution? "Don't do that".
Five billion more people want to use the Internet. My solution is IPv6. Your solution is to either deny them service or provide a 2nd class "host" service behind NAT.
You're not American by any chance are you? This "the customer can go fuck himself" type of solution reminds me of dealing with US banks, and certainly Americans are very smug about the fact that >50% of routable addresses are permanently assigned to their low population continent.
Sadly, people with this attitude will be saved at the last minute by the efforts of others, like those dopes who refuse to move from their home because "God is with me, and the floods won't come this high" and then have to be rescued by helicopter. Once in a while we should leave a few of you behind.
Use DNS. (Score:2)
Whilst in your house why not:
mylaptop.here
gamespc.here
tialaramex.here
a
Which resolve to private addresses.
If a host in Mongolia can reach my fridge, it better be because I INTENTIONALLY allowed it.
e.g.
fridge.mydomain.org-> public address.
Not because some stupid toy a kid left somehow routed to the global internet.
I agree we're running out of IPv4 space. But let's not use the wrong tool for the task, then say there's a problem, then propose using a tool that supposedly solves all sorts of problems, but barely works for the common case.
IPv6 has no backward compatibility. That's why it hasn't caught on. Maybe it's the only way to go, but if there is no backward compatible method, then it's going to take a lot of pain before people will switch.
Re:what this contest proves (Score:2)
Isn't it, though? The real 'hack' is replacing IPv4 with IPv6 to 'fix' a problem which is really in the directory services/DNS level. People think that some how static IP addresses will magically make things better, but that's only because they are changing the network protocol to fix a problem in the application layer (i.e. name look-ups).
A better solution would be to fix the directory services at that layer so that IP addresses were not used inside applications. That would also make a transition between IPv4 and IPv6 easier if the applications got their out from being too deep into the network directly. (I.e. get rid of fixed port numbers for specific services, use the equivalent of SRV records or such to let the network layer figure out which port and IP address to send the packets to -- by allowing ports to be looked up as well as IP addresses, that would allow mulitple servers behind NAT behind static port mappings.)
NAT has no effect on transport. You put data in, you get data out. The only reason that NAT seems like a 'hack' is because of bad coding design that has integrated far too much transport-level network information into the applications. If applications and name-look up were written properly, not only would switching applications to IPv6 be trivial because of less internal code dependence on IPv4 rather than a generic network/transport API, but NAT wouldn't be a problem, either.
The static IPv6 address auto-assignment is going to be fun to watch. Suppose the network admin doesn't do DHCP, and just lets all hosts auto-configure. Now, there are a couple things that happen -- the hosts choose random host network values -- makes no sense because the whole point of this is to have a static IPv6 address, right? So, host ABC always chooses the same host part of his IPv6 address (perhaps from his MAC address, which now gives his computer the equivalent of the Intel CPU serial ID number), or some other fixed value. What stops someone else from trying to swipe that same value on the network? Your computer reboots, and when it comes on, there is another host claiming to have that MAC/host address on the network already -- so much for that static IPv6 address. No smart network administrator is going stick their hands into that one -- either things will be dynamically autoconfiguring, and static IPc6 addresses may or may not happen depending on your luck and your neighbors, or the admin is going to assign the addresses specifically rather than letting the network autoconfig.
Plagarize a submission (Score:3, Funny)
For those who have no idea wth I am talking about, go an google, "serial experiment lain" then watch it. Some acid might make it clearer on your first viewing too.
Re:Plagarize a submission (Score:2)
How about... (Score:2)
How to get up and running (Score:5, Informative)
e.g RH Linux, set NETWORKING_IPV6=yes in
If you don't have upstream IPv6 then (1) Tell your provider that you think they should look into it sooner rather than later (2) round up the OS specific documentation for a technology called "6to4" tunnels.
A 6to4 tunnel can be created from any fully operational IPv4 host, even if it's a dialup link on some mom&pop ISP. Like the rest of IPv6 this is autoconfigured, you set a few options according to the documentation from your OS vendor and then it Just Works (TM).
If you have a typical small office/ geek house NAT setup with a single router & a lot of hosts spread around a building, the 6to4 tunnel will let you give all those hosts unique IPv6 addresses too, by assigning a
To check that it's working visit e.g. http://www.kame.net/ for visual confirmation. You may have to restart your browser if IPv6 wasn't installed when it was first started.
Re:How to get up and running (Score:2)
No (Score:2)
Re:No (Score:2)
That wasn't my question. My question was are we not wasting vast address space with
Now you may have implied that I suggest some similarity with IPv4. I do. The IETF and it's believers are always quite proud in pointing out that 128 bits is a vast space. No doubt. However, even vast spaces can be wasted through mismanagement.
If we're already doling out
I have every faith in the power if ignorance and greed to screw up what appears to be a limitless supply of addresses. The fact that we're already pissing away
No need for panic (Score:4, Insightful)
Look at it this way:
IPv4 addresses were indeed first allocated badly. It can be said that it's unfair that apple.com and
Now. Let's pretend that we could snap our fingers and give every "site" on the Internet a *single* IPv4 address. That means that apple.com gets a single IPv4 address and every cable modem user gets a single IPv4 address. All of the class As and class Cs get freed up. All of a sudden there are a lot more addresses available.
That's the case with IPv6, except that the public hierarchy is SIXTEEN TIMES larger than that. Sites in IPv6 are supposed to get a single
IPv6 is designed to last us 50 years or so. Personally, I think it will last a lot longer than that.
Oops, math correction (Score:3, Informative)
It's actually 16 bits larger, or 65,536 times larger.
But I can't let it go at that, because that's also a bit wrong.
The top 3 bits of IPv6 addresses are a format prefix. It cuts the address space into 8 pieces. The top and bottom ones are used for things like multicast, link local and IPv4 mapped addresses. One of them is the place where allocations are happening today - the Agregatable Global Unicast space. So if we lop off the top 3 bits from the 16, we get that the current allocation space is 12 bits, or 4096 times larger than the IPv4 space.
And we've got another 5 of those waiting in the wings if we need them.
Yer *way* off... (Score:2)
You misunderstood (Score:2)
Re:No (Score:2)
Proposal (Score:5, Funny)
Re:Proposal (Score:3, Funny)
Paging Linksys... (Score:4, Interesting)
Re:Paging Linksys... (Score:3, Informative)
NAT is an abomination that must die.
Well... (Score:2)
How about... (Score:2, Funny)
Hrm... (Score:4, Insightful)
IPv6 (Score:4, Informative)
IPv6 RFCs [hs247.com]
It offers some really neat, and much need security imporovements, like secure hashing, encryption at the IP level(data link layer) and seriously, there is no longer a need for DHCP. It is a network administrators dream come true, now if only people would start using it...
Sorry for being an anonymous coward, i haven't posted in so long, i forget my userid...
Re:IPv6 (Score:2)
The point of my post is that listing IPSec as an advantage to using v6 is misleading. List true advantages and people in the know will actually listen. Otherwise, you just sound like another clueless advocate.
Didn't someone once say... (Score:2, Funny)
There's something missing here (Score:3, Interesting)
So, seriously, anyone have any wonderful ideas?
Re:There's something missing here (Score:2, Interesting)
I enjoy doing low-level network programming, like designing protocols, ponder upon network routing issues, etc. I got bored about doing IPv4 stuff for some years ago, so I moved into the IPv6 area in 98-99, after a while I got bored of doing IPv6 unicast stuff becouse that area are much covered today, not much design and research to be done there. IPv6 multicast is fairly new and un-expoited and are evolving quick, so its a fun area to be involved in, I'm part of a global IPv6 multicast research network called M6bone [m6bone.net], most things revolve about research of new protocols like MLD and SSM and effecient multicast routing.
In a future world I would be able to stream video from my server at home to my Cellphone/PDA anytime via Mobile IPv6 (MIPv6) connectivity. Most new phones today have a IPv4 stack and color-screen but no IPv6 support in the phones yet. With Linux on the Ipaq I can get fully Mobile IPv6 in my pocket thru WiFi networks or wireless GSM/GPRS today if I wish.
I would like to see IPv6 being deployed in broadband networks to the homes, I think that would fuel IPv6 into mainstream usage in conjunction with P2P filesharing and true high-quality video streaming.
Enough ranting from my side.
Presentations required in PowerPoint format (Score:2)
Read the standards for judgement [v6pc.jp] page. They require PowerPoint format presentations. OK, does this mean I finally have to install an office package on my Linux workstation, such as Star Office or Open Office?
Why doesn't slashdot.org have IPv6 yet? + Solution (Score:2, Informative)
8<-------------
jeroen@purgatory:~$ host -t aaaa slashdot.org
slashdot.org AAAA record currently not present
-------------->8
But:
8<-------------
jeroen@purgatory:~$ host -t aaaa slashdot.org.sixxs.org
slashdot.org.sixxs.org CNAME ipv6gate.sixxs.org
ipv6gate.sixxs.org AAAA 3FFE:4007:1:1:210:DCFF:FE20:7C7C
------------->8
http://slashdot.org.sixxs.org [sixxs.org]
Et tada.... Slashdot and every other IPv4 only site over IPv6
Read more about it on http://ipv6gate.sixxs.net [sixxs.net]
Re:Wait a second... (Score:1, Informative)
Re:Wait a second... (Score:2, Informative)
I quote:
"IPv5 exists and it's specified in RFC 1819. It's a connection-oriented alternative to IPv4 but before discussions went too far the IPv6 standards were implemented, and other protocols provided the proposed functionality of IPv5. Some experimental implementations of IPv5 are in limited use but mostly outside the United States. You won't see many references to "IPv5" but you may encounter it by it's experimental name, "ST2" or "ST2+". This stands for "STreaming" protocol. Here's what RFC 1819 says about it:
The Internet Stream Protocol, Version 2 (ST2) is an experimental connection-oriented internetworking protocol that operates at the same layer as connectionless IP. It has been developed to support the efficient delivery of data streams to single or multiple destinations in applications that require guaranteed quality of service. ST2 is part of the IP protocol family and serves as an adjunct to, not a replacement for, IP. The main application areas of the protocol are the real-time transport of multimedia data, e.g., digital audio and video packet streams, and distributed simulation/gaming, across internets.
ST2 can be used to reserve bandwidth for real-time streams across network routes. This reservation, together with appropriate network access and packet scheduling mechanisms in all nodes running the protocol, guarantees a well-defined Quality of Service (QoS) to ST2 applications. It ensures that real-time packets are delivered within their deadlines, that is, at the time where they need to be presented. This facilitates a smooth delivery of data that is essential for time-critical applications, but can typically not be provided by best-effort IP communication."
Re:Wait a second... (Score:1, Funny)
Re:IPv6 (Score:1)
I'll shoot myself the day a troll bothers to log in.
Re:Hmm, creative way to win... (Score:2)
Why is that so hard? Can't you just run a dictionary attack using the DNS? By dictionary attack, I mean, search for those "valuable 4 and 5 letter domain names" and move on from there.