Slashdot Mirror
IPv6 Application Competition - win $10,000
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.'"
who's actually using IPv6? I know some use it privately within their org, but are there any publicly using it?
In big corp/gov users to move to IPv6
An IPv6 application competition, with a $5,000 prize! That should help promote IPv6, no?
.. 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.
[x] auto-moderate all posts by this user as insightful
Aren't there enough papers already on IPv6? Especially on purpose #1 (i.e. increasing the internet experience).
For #2 (i.e. promoting widespread), it's highly debatable, IMHO...
--
Error 500: Internal sig error
from ipv6.org IPv6 is short for "Internet Protocol Version 6". IPv6 is the "next generation" protocol designed by the IETF to replace the current version Internet Protocol, IP Version 4 ("IPv4"). Most of today's internet uses IPv4, which is now nearly twenty years old. IPv4 has been remarkably resilient in spite of its age, but it is beginning to have problems. Most importantly, there is a growing shortage of IPv4 addresses, which are needed by all new machines added to the Internet. IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4 addresses. It also adds many improvements to IPv4 in areas such as routing and network autoconfiguration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a number of years during a transition period. It prevents spoofed UDP backets (no more easy, D.O.S attacks, and spoofted packets) It makes the amount of posible adresses so large that worms that use simple seek algotrithems (such as slammer) would take like 20 years to infect enough systems to do any damage and would allow for all the future embedded apps, to get their own ip's.
come comment on the madness at http://slashdot.org/~phreak03/journal/
I will not support a protocol where all packets are not created equal. I wish to be treated with respect, not my game of quake slowed to a crawl because its deemed unessential. I fail to see the need.
although a bit more address space would do nicely...
You know...I have this idea for IPV6...you set up a server, then write a client...people register whatever songs they have in MP3...then...oh, nevermind.
$10,000 for recompiling with -lipv6 and changing some u32's to u128's in the structs... oh yea.
For high level languages like Python, I imagine all the work has been done for me already.
- Adam L. Beberg - The Cosm Project - http://www.mithral.com/
So that's like what, 50 bucks total?
Grand Prize is 1,000,000 yen... thats 8,306.775 USD not $10,000.
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.
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.
Sigh... remember when a good idea used to be worth $40 million?
-a
An application that keeps tabs on all information of everyone according to their unique IPv6 number, and then ranking them on an anti-american scale.
-John Ashcroft
And even if your ISP won't assign you an IPv6 subnet, you can always utilize a free Tunnel Broker 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. My announcement also provides a concrete example of IPv6 being used to subvert firewall rulesets.
A ton of useful IPv6 information is available from 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 to be incredibly helpful.
-Fyodor
Concerned about your network security? Try the Free Nmap Security Scanner
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..
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!
I'd like to submit lain - just watched it last night and they clearly said that it was development of the sixth gen protocol that made the creation of lain possible.
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.
When information is power, privacy is freedom.
If the upstream router from you (whether that's a $20k rack box from Cisco or some Pentium Linux box) has IPv6 connectivity then all you need to do on your hosts is turn on IPv6 and the rest happens automatically.
/etc/sysconfig/network and restart networking
/48 to each subnet in the building.
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.
I propose an IPv6 protocol app that allows you to browse other sites on the internet. Each site will store one or more files in a standard markup language. The app will download these files and render the text and images in a desktop window. The markup language should include links to other sites and files, creating a sort of "web." It could be useful for scientists who want to exchange research data.
We should push Linksys (and other cable/DSL router manufacturers) to write firmware capable of creating an IPv6 intranet, as opposed to the typical class C. Better still, I'm sure they could add support for something like TunnelBroker (as mentioned above) and map one's intranet into genuine IPv6 space. Yes, you could do the same thing with a 486 running BSD or Linux, but I think using a nice, small, energy-efficient box would be more elegant.
...all porn stars get IPv6 addresses? Now THAT'S revolutionary!
Life is like pants... fit in or you don't fit in.
To answer your question on do they get the rights do anything submitted here is rule #7 from the rules page "The applicant will maintain all applicable intellectual, technology and design copyrights for the entries submitted to the contest, but the right for disclosure and distribution of entries submitted will belong to both the applicant and the contest host.".
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?
/me starts thinking that the net will move to ip v6 about the same time the US moves to metric.
forget it.
who's actually using IPv6? I know some use it privately within their org, but are there any publicly using it?
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. 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 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...
Last year i did a research paper on IPv6 for my data communications class. People, those who think IPv6 is dumb, unecessary, or already dead, pull your head from where the sun ain't shining and take a look at what it has to offer, you might consider giving some RFC's a read, that is unless your a pussy, and if thats the case, why do you read /. ?
IPv6 RFCs
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...
Er... no.
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."
noone will ever need more than IPv4
-my other sig is your mom
I don't believe there's any need for concern with the way IPv6 addresses are being dished out.
.jp both wound up with a class A (unfair to Japan, in this comparison). These legacy allocations are most of the reason we're in a mess with IPv4. In fact, it's the complexity of the non-default routing table at the heart of the Internet that is driving the transition more than the lack of address space.
/48 prefix. A /48 is going to be sufficient for the largest of organizations. They can have 65,536 subnets, each with a potential 2^64 nodes. IPv4, in theory, was supposed to be subnettable. The problem is that if you want to cut a class C into 8 pieces, each of those pieces is only going to be able to have 32 hosts. It's this tight binding between the number of subnets and the number of possible hosts in the subnet that has resulted in the proliferation of switches and flat networks. That's not really how it is supposed to be.
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.
I don't think it's that IPv6 gives anyone necessarily any new ability to create some awesome application that they couldn't already do with IPv4. The problem with this whole thing is, to create really radical new applications, we need the BANDWIDTH behind Internet2. And by just creating an IPv6 app, you don't get magic access to that bandwidth.
So, seriously, anyone have any wonderful ideas?
"Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
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.
I actually wrote a thesis about using IntServe/Diffserve for a video conferencing application across the internet.
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.
Hmmm:
;)
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
Et tada.... Slashdot and every other IPv4 only site over IPv6
Read more about it on http://ipv6gate.sixxs.net
http://unfix.org