The Atlantic today published a reminder that the Associated Press has declared in their style guide as of today that the word âInternetâ will be spelt with a lowercase âiâ rather than an uppercase âIâ.
The title is âElegy for the Capital-I Internetâ, but manages to be neither elegy nor eulogy, and misses the mark entirely, focusing as it does on the awe-inspiring size of the Internet being why the upper-case initial was important; then moving to describe how its sheer ubiquity should lead us to associating it with a lower-case i.
The "Internet", capital I, gives the information that this is the only one of its kind, anywhere, ever. There is only one Internet. A lower-case I would indicate that there are several "internets". And, sure enough, there are several lower-class networks-of-networks (which is the definition of âinternetâ as a lower-case noun).
Iâd like to inform the people who are engaging in this navel-gazing debate over big-I or small-i, that there functionally is only exactly one Internet. When their cable company came to "install the Internet", there was no question on the form to say "which internet do you want to connect to?" and people would have been rightly upset if there had been.
So, from that perspective, very much capital-I is still the right term for the Internet. There’s only one. Those other smaller internets are not comparable to âthe Internetâ.
From a technical perspective, we’re actually at the time when it’s closest to being true that there’s two internets. We’re in the midst of the long, long switch from IPv4 to IPv6. We’ve never done that before. And, while there are components of each that will talk to the other, it’s possible to describe the IPv6 and IPv4 collections of networks as two different "internets". So, maybe small-i is appropriate, but for none of the reasons this article describes.
Having said that, IPv6 engineers work really really hard to make sure that users just plain don’t notice that there’s a second internet while they’re building it, and it just feels exactly like it would if there was still only one Internet.
Again, you come back to "there is only one Internet", you don’t get to check a box that selects which of several internets you are going to connect to, it’s not like "the cloud", where there are multiple options. You are either connected to the one Internet, or you’re not connected to any internet at all.
Capital I, and bollocks to the argument from the associated press – lower-cased, because itâs not really that big or important, and neither is the atlantic. So, with their own arguments (which I believe are fallacious anyway), I donât see why they deserve an upper-case initial.
The Atlantic, on the other hand â thatâs huge and I wouldnât want to cross it under my own steam.
And the Internet, different from many other internets, deserves its capital I as a designation of its singular nature. Because itâs a proper noun.
This year is a special one for anniversaries â my 45th birthday, 20 years since I arrived in the USA, 10 years since beating cancer â seems like the perfect time for ISOC to honour me by switching everyone to IPv6.
Are you ignoring IPv6 for the moment, knowing itâs not going to affect you any time soon? I have news for you â you will be significantly affected in the next two months.
It seems that a large fraction of the world is really rather dismissive about the coming of IPv6, which is, after all, the best IPv.
But there are people who are intent on providing a move to the new world, and theyâve geared up to provide a âWorld IPv6 Dayâ on which they will be enabling IPv6 on their main sites. (There is an ever-increasing list of participants)
So what is going to happen when some web sites â some big web sites â turn on IPv6 for a day this June? And what will happen when IPv6 is turned on permanently at those sites?
Individual users are probably thinking âsomeone will make it all work for meâ â and some of that is likely true, if you have someone managing your network for you. Your Internet Service Provider will eventually do what they can to provide IPv6 service to your home, and your employerâs IT department is probably thinking in some terms about what to do when they feel like itâs time to deploy IPv6 to the company. But most home routers are not currently able to provide native IPv6 service.
If your cable modem, DSL router, or other entry device is rented to you by the ISP, then you probably have nothing to worry about, they will eventually get replaced to support IPv6, when the ISP is ready to accept IPv6.
If you have bought your own entry device, or other routers (such as a wireless router), you will have to replace it to support IPv6. Donât run out and get a new router yet â there are no home routers on the market that currently support IPv6 fully â or even enough to consider upgrading for that functionality. Those of us using IPv6 at home are generally using custom software that we have installed, not something the average consumer wants to do.
This means you are stuck on IPv4 for the foreseeable future, although your computer is most likely capable of using IPv6 when connected to a network that supports it. But you will still be affected â see the section below, âFor Everyoneâ for more.
If youâre not already engaged in some form of IPv6 project, you really should be.
If your IT department are telling you that IPv4 addresses have not run out, ask them âthen why are we flailing around behind a NAT, and having to write or purchase software that specifically knows how to make its way out and back through a NAT?â
The fact is, IPv4 addresses ran out years ago, and weâre really only in this last couple of years in a situation where we can deploy IPv6 to fix the problem. Operating Systems for desktops and laptops now support IPv6, and usually have it enabled by default; business-class routers and switches are available with IPv6 support built in, and firmware for some not-so-new devices in that class is available to provide IPv6 support.
More than that, though, you have to make sure that you have staff on-hand who are trained to understand IPv6, because training your staff may be the investment that takes the longest to get right. When you read the section âFor Everyoneâ below, consider what the impact will be to your support centres and to your customers when something breaks. Will you have to explain away broken links, images or even broken pages? [Any site that has previously seen broken pages because of inability to download ads should know how this comes about]
If youâre an IT department, you probably have some people on staff who are into new technology â the more they can get, the better. Quite frankly, everyone in an IT department should have something of that feel, or theyâre in the wrong team. So, when you get management approval to start down the IPv6 road, it should be a simple matter of asking âwho wants it?â and letting people sign up to work on learning the new technology and finding the solutions. Ideally, when your management asks âwhoâs the IPv6 guyâ, youâll be able to point him out right away.
You should obviously consider a staged roll-out of IPv6 technology, starting with internal networking, to make sure you have an infrastructure that supports it, and only later considering allowing incoming IPv6 to connect to your web site, or to other externally-facing systems.
As a part of enabling routing, make sure that you match, in your IPv6 environment, the protections you already have for IPv4. Do not try to match feature-for-feature, because of features like NAPT, where there is some accidental / incidental security protection from a feature that is essentially unavailable in IPv6. Match protection-for-protection â an IPv4 NATâs security protection is that it is a firewall with no holes punched in it. So, its IPv6 equivalent protection is a default-deny firewall.
Consider grouping servers into subnets or address ranges based on their use, so that you can configure your firewall using contiguous ranges, rather than individual address assignments. This will make your IPv6 firewall fast â perhaps faster than when operating on its IPv4 rules â and simple.
When external sites turn on IPv6, and start resolving their site names to IPv6 addresses as well as IPv4, there will be some users who have poorly-configured IPv6 installations. Their DNS name servers will say âhereâs an IPv6 addressâ, their operating system and web browser will say âI understand IPv6, so letâs connect to that address!â, and some portion of their network will say âhuh? What is this, the future or something? Iâm still wearing shoulder-pads and leg-warmers and watching Dynasty, because itâs been the 1980s for the last several decades!â
What that user will see is that the IPv6-capable web site just dropped off the Internet. At best, it may simply cause a long delay (several seconds) in reaching the site, as the browser tries â and fails â to connect to IPv6, and then switches to IPv4. At worst, it will cause the big red X to appear, and sites to fail to load completely, as the browser (or other client software) gives up.
Fine, so maybe all this means is that those sites who take part in World IPv6 Day will drop off the Internet for a day, to some of their users, and then the next day all will be just perfect.
You see, with âWeb 2.0â, everythingâs mashed up and interconnected. Googleâs everywhere. So are some of the other participants in World IPv6 Day. Each one of those sites being unreachable could affect your favourite mashups, whether you are consumer or service provider. And what is an advertising-laden website if not a mashup of its advertising and its content?
Businesses â what if your adverts fail to load? What about that mapping site you use? Is your technical support ready for an estimated 0.1% of your customers calling in with failures on your site?
Consumers â are you ready to take these errors as a sign that you need to fix your network, or to bug your ISP, or are you going to insist, wrongly, that the problem is with the web sites participating in World IPv6 Day? At least, will you accept that these errors are a necessary part of learning how to move to IPv6?
ISPs â even if you have no plans for IPv6, are you ready for the technical support requests from people who have errors connecting to an IPv6-supporting site?
Quitting, or refusing to take part in the move to IPv6, is not an option. IPv6 will roll out. World IPv6 Day is only the FIRST of many shake-outs that will happen, as sites increasingly add support for IPv6 to their existing IPv4 lineup.
For a preview of what will happen to your machine, try connecting to a system that supports IPv6 and IPv4. The usual example is http://www.kame.net â it displays a picture of a turtle. The turtle dances for IPv6 users, and sits there doing nothing for IPv4 users (although your browser may choose to display the IPv4 version as its default even if you support IPv6).
If you are one of those rare individuals in an IPv6-capable network island that is unreachable by the IPv6 Internet, you will see an error.
Sadly, with new organisations joining World IPv6 Day every day, you canât really predict what exactly will break â but you can predict how some of it will break, and train your staff to handle this, whether it is by deploying changes, or simply handling support calls.
Iâd love to know what effects youâve anticipated will come on World IPv6 Day, and what work youâve done to mitigate these issues.
IANA just held a ceremony (streamed live, and with a press conference following at 10amEST) to hand out the last of the IPv4 /8 blocks to Regional Internet Registries â RIRs.
Itâs a quiet, but historical moment, as it truly marks the time we can finally tell people âyes, I know nothing appeared to be happening, but finally itâs happenedâ. Preparing for IPv6 has to happen, because there just isnât any stopping this particular juggernaut. IPv4 addresses will run out, and there will arise a time when web sites can no longer find a public IPv4 address.
BEFORE that happens, something has to change to allow us to work together on an IPv6 Internet. Iâm doing what I can.
As a client user, I live on the Hurricane Electric IPv6 Tunnel Broker, because Comcast have yet to extend their IPv6 trial to my neck of the woods, seeing as how I live in technology-deprived Seattle.
Iâm still trying to persuade my web siteâs ISP, 1&1, to put an IPv6 capability in place before World IPv6 Day on June 8, so I can host my web page there in IPv6, but I definitely have my FTP server software, WFTPD and WFTPD Pro, ready to support IPv6 fully.
What are you doing?
OK, so IPv4 is probably right to be acting like the old man in Monty Python and the Holy Grail, and screaming âIâm not dead yet!â, but we certainly shouldnât hold out any hope that itâll be getting any better. Clonk it on the head as soon as possible, because really, itâs been extremely poorly for many years now.
Iâve mentioned before that my biggest argument that IPv4 has already exhausted itself is the mere presence of aggregating NATs â Network Address Translators, whose sole purpose is to take multiple hosts inside a network, and expose them to the outside as if they were really only processes on one host with one IP address. If IPv4 were large enough, we wouldnât have needed these at all, and at best, they were a stop-gap measure, and an inconvenient one at that.
Well, now we canât really stop the gap any longer. Weâve hit the first of a set of dominoes that leads to us not even having enough IPv4 addresses to support the Internet with NATs in place.
Thatâs right, no more /8 networks are left in IANAâs pool to assign. OK, I know it says â5/256â are left, but thatâs only because the IANA (Internet Assigned Numbers Authority) havenât yet announced that theyâve given out those last five, and they have previously announced that when they get down to five, those five will automatically be distributed.
Yesterday, the counter said â7/256â, but earlier today, APNIC â the RIR for the Asia & Pacific region (RIR â Regional Internet Registry) â bought two entries to serve their ever-growing Internet market. That will trigger the IANA to distribute the remaining five blocks.
And no, Egyptâs IP blocks are not available for re-use.
Yes, thatâs right, this isnât a âshut everything off and go homeâ moment â as I said before, this is merely the tipping of an early domino in a chain. Next, the last five /8s will be given to the five RIRs, and then they will use those to continue handing out addresses to their ISPs. At some point, the supply will dry up, and it will either become impossible, or expensive, to get new public-facing addresses. Existing addresses will still work even then, of course, and several of the new IPv4 address assignments will, ironically, be aggregating NATs that will allow the IPv6 Internet to access old IPv4 sites!
The only question now is what we call this momentous slide into IPv4 exhaustion. Certainly, RagNATok has a pleasant ring to it, as it invokes the idea of a twilight of the old order, a decay into darkness, but this time with a renewal phase, as the new Internet, based entirely on IPv6, rises, if not Phoenix-like from the ashes, then at least alongside, and eventually much larger than the old IPv4 Internet.
As you can tell from my tone, I donât think itâs doom and gloom â Iâm quite looking forward to having the Internet back the way I remember it â with every host a full-class node on the network. Itâs going to mean some challenges, particularly in the world of online security, where there will be new devices to buy (bigger addresses mean larger rule-sets, and existing devices are already pretty much operating at capacity), new terminology to learn, and new reasons to insist on best practices (authentication by IP address was never reliable, and is particularly a bad idea when every host has multiple addresses by default, and by design will change its source address on a regular basis).
Perhaps the Mayans were right in deciding that 2012 is the year when everything changes (to borrow a line from Torchwood).
The rather unassuming name that has been chosen for this particular date â when the last assignment leaves the IANA â is âX-Dayâ â X as in âeXhaustionâ.
The next date for your calendars, then, is World IPv6 Day, two days after my birthday, or for those of you that donât know me, June 8, 2011, which is when major Internet presences including Google, Yahoo and others, will be switching on full IPv6 service on their main sites, and seeing what breaks. Look forward to that, and in the meantime, test some known IPv6 sites, like http://ipv6.google.com to ensure that youâre getting good name resolution and connectivity.
If youâre running an FTP server on Windows, I encourage you to contact me at firstname.lastname@example.org if you would like to test WFTPD or WFTPD Pro for IPv6 connectivity. We are currently beta-testing a version with much greater IPv6 support than before.
I saw the Belkin Play N600 HD router (F7D8301) at Costco a couple of days ago, for a very good price.
Iâd been looking for a good price on an 802.11n router for some time â partly to increase coverage through my house, but also to ensure that I had a new router that would cope with improving technology as I buy it over the next few years.
Sadly, this router isnât it â there are several existing protocols that it just doesnât support, which is rather odd for a new router.
Specifically, I note that the router does not state support in its interface for PPTP or IPsec passthrough â protocols 47, 50, 51. When I asked the Belkin tech support about this, they directed me to âtry forwarding ports on the routerâ, apparently not aware that there is a difference between port and protocol forwarding. Thatâs an astonishing lapse in ability and knowledge for technical support on a router, and doesnât give me much comfort that the router itself is developed with skill or knowledge.
Another protocol not supported by this router, which seems just crazy when weâre one hundred days away from X-day, is IPv6. Thatâs right, IPv6, the next-generation Internet Protocol, required for numerous features of modern Windows systems such as HomeGroups, DirectAccess, etc (Iâm sure there are IPv6-only features for Mac and Linux, but those arenât my specialisation), and it isnât supported. You can connect to the router as a wireless client, but the IPv6 protocol, access to local DHCP servers, etc, isnât supplied to your host computer. My Linksys WRT54GL has supported that for several years, and this new router from Belkin canât handle it.
Also unsupported is â6in4â (aka v6tunnel), as used in IPv6 tunnel schemes such as http://tunnelbroker.net, which is how I make my network a part of the global IPv6 Internet until Comcast gets around to supporting native IPv6 service. Again, this wouldnât require the router to understand anything about IPv6, just to forward IPv4 protocol 41 correctly.
In addition to missing such basic functionality, the Belkin Play N 600 HD also fails in the reliability stakes. Two days itâs been in our house, and both mornings, weâve woken up to a complete lack of Internet service and wireless connectivity, although the light on the front of the router is solid green, indicating that it thinks everything is fine.
Pinging the router does nothing, restarting computers (in the vain hope that it might be a wireless card issue, or some network driver failure, though our network has been fine for many years) does nothing. The only action that has an effect is that of restarting the Belkin router. Clearly, the Belkin canât make it through the night without locking up.
As if to pour salt onto the wound, this router isnât even able to increase range in our house â the boy still canât get a connection from his room on his iPod. Perhaps thatâs not such a bad thing, but since we were hoping to increase range with the routerâs ability to pick signals out with MIMO technology, it seems like there really isnât much point to us keeping the router.
Costcoâs return policy is pretty reliable in cases like these â we take the failed device back, say that it wasnât capable of reliable, basic use, and they refund us our purchase price. Iâll be giving it just a couple more days, in case Belkin has any hope to offer in terms of support of basic network router functionality, but I suspect Iâll just have to suck up the extra cost of using plain old reliable Linksys.
Put simply, the memo gives a timetable for moving the US Federal government to using native IPv6 for all public-facing web and Internet sites. The end of Financial Year 2012 is the deadline for that. Thereâs also a deadline of end of FY 2014 for all internal client apps to support IPv6.
Here at Texas Imperial Software, weâve provided basic support for IPv6 in WFTPD and WFTPD Pro for some time.
Because of a lack of significant expressed customer interest, weâve basically kept the IPv6 support out of the interface, despite a personal interest on my part in supporting IPv6. Now itâs time to change that and bring IPv6 in as an equal platform, rather than hiding it in the background.
Weâre looking for beta testers for this IPv6 support. Drop me a line at email@example.com if you are able to test out an IPv6-capable FTP server. Priority is given to registered users, but if you can test out WFTPD or WFTPD Pro, on a native IPv6 network, weâd love to hear from you.
You donât have to be associated with a government, or even enterprise, just interested, capable, and ready to give your feedback.
As you can see from the IPv4 Exhaustion Counter to the left (snapshot taken 7/16/2010, 7:30 pm PDT), IPv4 addresses are dwindling.
OK, so thatâs perhaps a rather simplistic description of whatâs going on â these are a count of the IANA blocks that have not yet been handed out to other providers. Usually what happens is that the IANA hands blocks out to regional network block managers, and they hand them out, piece by piece, to the local providers, who hand them out one (or more for larger organisations) at a time to consumers.
So, even when all these blocks have been handed out (known as âX-Dayâ), there will still be addresses to be handed out to consumers â but it is a key indicator to follow in realising that IPv4 is a dead-end strategy, and something else needs to be investigated.
Yes, weâve had these calls to move to a new addressing format for years â back in 1993, when I first got on the Internet, there was a lot of discussion about âIPng â Internet Protocol, the Next Generationâ (STNG was current then, you must understand).
Later, as IPv6 came along, NATs (Network Address Translators) were brought out as the saviour to IPv4. The idea was that weâd all use the same internal addresses as one another (so each company has their own local 10.* netblock behind the NAT), and a single external IP address for each NAT. To put it mildly, this is not a solution to the problem, it merely postponed it a little â if anything the fact that we have to use NATs is indicative that we have already run out of IPv4 addresses. Until you look into it, you really have no idea how much work we have already put into changing our applications to work with NATs in an effort to prop up IPv4, when we could have spent that time in adopting IPv6.
Sure â but hey, what’s not to like about IPv6? Unless you’re the developer of a piece of network software, it all just plain works.
Applications accessing file shares by name – can still access file shares over IPv6, without a line of change. Only if you’re dealing specifically with the IP layer and IP addresses will you see a problem. It doesn’t take a lot to turn an app from IPv4-only to IPv6-capable, and users will hardly notice a difference, if you expose names, rather than IP addresses. [It took me two hours to convert the underlying engine of WFTPD and WFTPD Pro to use IPv6. The user interface took/is taking me longer, because I’m not so good at UI, and haven’t had the focused time I need. But itâs coming.]
You have to reconfigure your routers a little – they at least need to either act as DHCPv6 sources, or handle DHCPv6 traffic to/through a redirector. Ask your router manufacturer what they recommend. And, since you wonât be using a NAT as an accidental firewall, youâll want to make sure your routers have real firewall functionality.
Technology leaders should be asking to beta test our ISPs’ IPv6 support, and if your ISP isn’t at least beta testing IPv6 support, get them to catch up, or move to one that does. Good gracious, even laggard Comcast is testing IPv6 for its customers!