I am a huge fan of OpenID. My initial interest was piqued by the promise of no longer having to remember login credentials for dozens if not hundreds of websites. The security benefits of only having to protect one set of login credentials instead of many became quickly obvious thanks to an ebay hacker.
I must say, when I first heard about the use of URLs as identifiers, I was skeptical (and to some degree remain skeptical) that your average, not-an-early-adopter consumer will be willing to wrap her brain around the concept that a website address is sometimes also a username. To me, the most obvious identifier to use would have been the email address. Almost everyone on the internet has at least one and it is already associated with identity in everyday life.
I became increasing skeptical when I heard that as an alternative to URLs, an identifier called I-Names was also part of the OpenID spec. I-Names are XRI globally rooted at xri.net. This means one organization (a company in this case) has a monopoly on the issuance of I-Names.
We know from economics that monopoly suppliers have the incentive to create artificial scarcity and drive up prices. Yes, this means you have to pay for an I-Name. The going rate is about US$20 for an "individual I-Name" and US$55 for an "organization I-Name." Wow! Someone must have a lot of confidence the market is going to buy into I-Names even given that OpenID URLs offer many of the same benefits at little or no cost beyond a domain name registration which has almost already been paid for other reasons.
Charging more than twice the current market price for domain names for something that isn't really that valuable until the network of people that use it is pretty substantial is hardly a way to stimulate viral adoption and gain the benefits of network effect. This is especially true when OpenID URLs are out there are a direct substitute for single sign on identifiers and have a marginal cost of US$0 to the user.
Skeptic Turns SupporterDespite my early skepticism, I continued to read up on I-Names to figure out why intelligent people would spend so much time trying to create something that at first glance by an identity layman seemed to be a scheme to charge unsuspecting consumers US$20 for something that could basically get for free by using an OpenID provider such as MyOpenID.
Drummond Reed (=drummond) has been one of the most visible supporters and whose posts on the OpenID mailing lists and his blog have been most helpful in shedding light on why I-Names are technically superior and desirable for consumers.
Supporter Buys-InConvinced of the superiority and desirability of I-Names, I decided to buy my own individual I-Name. You can buy an I-Name for a number of accredited registrars. Having little info to go on, I bought mine from 2idi because it is one of the initial registrars. I falsely assumed that they would have the most well developed feature set and management interface.
I have been using my I-Name to log on to OpenID sites that support it. Hopefully, once the OpenID 2.0 spec is complete, support for I-Names will be more consistently implemented. Right now sites using older OpenID spec 1.0 libraries do not accept I-Names.
Because of the less than desirable feature set of my I-Name provider and the fact that they do not yet support the latest OpenID spec, the best security practices, or provide a means to manage relying parties, I have tried without success to delegate OpenID authority using XRDS to my MyOpenID URL. Has anyone else been able to accomplish this? Perhaps 2idi is listening and could let us know if and when we will be offered a feature set more comparable to other OpenID providers?
Much of the success or failure of I-Names will resolve on getting the world at large to accept and recognize them for what they are, a unified contact handle that has the potential to replace phone numbers, email addresses, mailing addresses and more with one simple identifier all while giving users more control over their information and who is allowed to contact them and by what means. US$20 per year is way too high for anyone but the most enthusiastic early adopters to pay if that goal of mass popularization is ever to be met, at least in the beginning.
One road to adoption that seems very promising is by employers providing delegated community I-Names to their employees or websites to their users. For example:
@example.companyMarketingFred.Smith < ----- This would be Fred Smith in Example Company's Marketing department.
@example.company*Smithy < ----- This could be the user with nickname Smithy at Example Company's Web 2.0 application.
Help DelegatingI am interested in providing users of my yet to be launched tech start up with community I-Names. However, I have yet to find an I-name registrar website that provides information on how this could work beyond simply mentioning it is possible.
Simply put, I imagine asking my users to provide their I-name or OpenID when registering. If they provide an OpenID, my site would issue them a new i-number and an associated community i-name under my company's organization i-name. If they provide an i-name during registration, the existing i-name's i-number would be used as their unique identifier and an a community i-name under my company's organization i-name would be issued and associated with the existing i-number.
Ideally, this could all be accomplished with an i-name registrar provided API so that we do not have to run an XRI resolver. Is this possible? Does anyone know of a detailed explanation of how something like this should be implemented?
If this is a service that i-name providers are already offering, how is it priced?
Linksafe seems to indicate that the US$55 / year fee includes the ability to delegate community i-names. Does this mean that Linksafe would provide login, contact, and forwarding services for community i-names that are created under an organization's i-name?
The I-Name FutureI look forward to the day where I can print my i-name on my business card and people will automatically know what it is and how to use it. Unfortunately, that day will not come until the ease with which people can get i-names is closer to that of the ease with which they get OpenID URLs by both significantly reducing the price of individual i-names and making it a lot easier for websites and companies to provide their users with community i-names with a cost structure that makes sense and minimal technology investment.
If anyone can shed more light on the questions I have raised, or point me to some answers, please leave a comment using your OpenID or I-Name.
Or contact me privately using my i-name.