Showing posts with label ipv6. Show all posts
Showing posts with label ipv6. Show all posts

09 July 2008

Reasons to Be Tearful

Want one more thing to worry about? Try this. (Via Pluggd.in.)

17 July 2007

Gartner's Trough of Disillusionment

There is a scandal brewing over open standards in Europe:

On June 29 2007, the European Commission agency IDABC published document written on contract by Gartner initiating the revision of the European Interoperability Framework (EIF) and the Architecture Guidelines (AG) .

The first version of this very important document has been published in 2004 and introduced a strong support and request for open standards and xml for the exchange of data between administrations within Europe, as well as with the citizens. This has been relayed and used in many countries to support open standards as well.

This is now threatened in this new report EIF v2.0 by Gartner

This second version, not yet endorsed by the European Commission, nor by the member states, but that could well enter soon such an endorsement process, wants to update the previous version of the European Interoperability Framework but, contrary to the first version, it threatens explictely the good process of more open standards that had been a long time push of IDABC.

The core of the problem is the following passage from Gartner's report:

Gartner acknowledges the importance of open standards. IT vendors and system integrators should also recognize that open standards are the way to go. The era where proprietary standards lead to a sure base of loyal customers is fading away. IT is becoming just like any other industry where true added value and competitive pricing determine the winners.

Yet, Gartner recommends not to focus on the use of open standards per se. Whether open or not, standards are to further the deployment of public services. EIF v2.0 should facilitate the most profitable business model(s) of cost versus public value, under proper recognition of intellectual property rights, if any. The support for multiple standards allows a migration towards open standards when appropriate in the long run.

The use of 'open source' software may further the deployment of public services. However again, whether open source or not, it is the most viable software that should be allowed to survive in the infrastructure. So again, EIF v2.0 should facilitate multiple options to co-exist, and to compete.

This is completely daft. Saying

Gartner recommends not to focus on the use of open standards per se. Whether open or not, standards are to further the deployment of public services. EIF v2.0 should facilitate the most profitable business model(s) of cost versus public value

is like saying

Gartner recommends not to focus on the use of moral standards per se. Whether moral or not, standards are to further the deployment of public services. EIF v2.0 should facilitate the most profitable business model(s) of cost versus public value

In other words, it fails to take into account that focussing narrowly on "the most profitable business model(s) of cost versus public value" is short-sighted, because by definition, "not to focus on the use of open standards per se" means allowing closed standards. And so the long-term costs are going to be greater because of vendor lock-in. In fact, Gartner itself says this:

To facilitate evolution over time and to support the migration from one standard to another and to avoid vendor lock-in it is therefore paramount to design for support of multiple standards.

But it confuses multiple standards of any kind with multiple open standards. There are no easy migrations between different closed standards, or closed standards and open ones. "To facilitate evolution over time", *all* the standards must be open.

Around this deeply flawed core thesis, the rest of the report reads like a puff for Gartner's methodology - including its tiresomely pretentious Hype Cycle (talk about hype). Pretentious and useless: at the "Peak of Inflated Expectations" it places - wait for it - IPv6. I hate to break it to Gartner, but IPv6 passed through that stage about eight years ago.

Give that the IDABC, which commissioned this study (who knows why) has hitherto been pretty sensible on open standards, we can only hope they consign this whole report to the bin where it belongs. To help it on its way, do sign the petition and send your (polite) comments to the IDABC before September as they have specifically requested:

Everyone who sees interoperability as an effective means to come to better pan-European eGovernment services is invited to read the document and reflect on its content.

IDABC is interested in your reactions.

A summary of reactions (that reach us before September 15, 2007) will be published on the IDABC web-site (http://ec.europa.eu/idabc) and will constitute another input into the revision process.

Really, an offer we can't - daren't - refuse.

Update: As I signed the petition I noticed that it insists on a full physical address - country isn't enough. This seems foolish to me, and is likely to lead to people not signing. Unless they were to enter random information in the unnecessary fields....

30 April 2007

Easy Access to IPv6 at Last?

You probably don't realise it, but the Internet is a dinosaur. More specially, the Internet numbering system is palaeolithic, and needs sorting out. Ironically, the solution has been around for years (I first wrote about it nearly a decade ago). It's called IPv6, and instead of the measly 4 billion or so addresses that IPv4 allows (and which are allocated in a particularly arbitrary way), IPv6 will give us

340,282,366,920,938,463,463,374,607,431,768,211,456

of them, which should keep us going for a while.

And yet we hear little of IPv6 these days. So I was glad to see that down-under they are doing something on this front with the IPv6 for e-Business initiative. As well as scads of useful IPv6 resources, this site also has links to a highly-practical outcome of the Australian project, the memorably-named "Easy Access Device":

The Easy Access Device (EAD) has been developed with the purpose of providing a small businesses (leas than 50 employees) with a simple, easy to use IPv6 Internet access device. The system is designed as a small unit that would be installed in a small business, and connects directly into a DSL, cable or wireless broadband termination unit (typically a modem). The unit provides the basic network services normally required at a small office network boundary for both IPv6 and IPv4 networks.

Apparently it's a PC box running Ubuntu. Providing a cheap solution is probably as good a way as any of moving on from the poor old IPv4.

06 September 2006

IPv6: You Know It Makes Sense

The Internet is deeply, deeply broken, it's just that nobody's noticed. Fortunately, the solution is already to hand. Unfortunately, nobody is really bothering to use it. It's called IPv6, and is version 6 of the Internet Protocol that holds the Internet together; we're currently all running version 4, and it's just not working (version 5 seems to have got lost somewhere).

If you want to know why IPv6 is important and fun, read this great article, with more to come.