« October 27, 2004 | Main | October 29, 2004 »
October 28, 2004
DIDW 2004 Wrap-up
I'm back at home and feeling great about the trip. As usual, Phil, Andre, Eric, and Kathi did a bang-up job of putting together a conference that was well run and fun to be at. Overall the talks were good and I found plenty there to get me thinking.
I'd love to see the conference expanded along one crucial axis, however. There's not much of a developer presence there and I think that they miss a big part of the identity puzzle without it. They also risk becoming a collection of vendors, which will pay the bills, but not necessarily achieve the goals I think Phil has of this being about all aspect of identity. There's plenty of open source and other work going on that touches identity. DIDW needs to find a way to reach out to that community and mix it in with what they've got. The result could be truly electric.
07:27 PM | Recommend This | Print This
DIDW 2004: Doc Searls on The Dawn of Independent Identity
|
Doc gives the closing keynote.
|
When we look at markets, we usually think of the transaction, but the exchange is only the bottom level of a market. Above that are conversations (ala Cluetrain) and above that are relationships. Federation is the relationship level of a market.
Gordon Eubanks pointed to the problem of silos, but the real silos are in our wallets. As an individual, I can't federate the relationships I have with various companies. I'm left to hope that the companies I care about get together.
Doc says "when we lost the industrial revolution (to industry) we lost the meaning of our names." Crafts we replaced by jobs, work was reduced to labor, and our occupations were reduced to positions somewhere in the org chart. The identity revolution has the power to give people back the meaning of their names.
Doc does a riff on podcasting and how it and the iPod are a response to the radio industry failing to meet the demands of the market. Lots of good stuff that I couldn't capture.
Doc wants rental car companies to compete for his business based on what kind of car he wants to drive. Right now, there's no way for that to happen, but technology could make it possible. Doc calls this "Company Relationship Management (CoRM)." CoRM is made possible by independent identity (ala i-names). CoRM can deliver on the idea that independent identities are where real marketing power comes from.
|
Drummond Reed shares the stage with Doc
|
Scott Mace talks about an important part of the CoRM problem: privacy. Scott says that its unreasonable to expect users to click thru privacy policies on devices like cell phones in a take it or leave it way. CoRM systems need a way to publish the complementary half of a companies privacy policy, that is my privacy policy. I added that privacy wasn't a thing, but a transaction. If users believe they are getting fair value for their identity information they will exchange it for what you're offering. CoRM system need to be built in a way that allows them to enter into negotiations about privacy.
Drummond says that an i-name is an independent identifier that is not attached to a specific mode of interaction or a specific company. Doc explains his fantasy about i-names: he's on the road a lot and drinks coffee a lot. He wants to talk into StarBucks with his card that is a pointer to his identity broker that can tell them that he wants a non-fat double latte. That card transcends everyone of the silos in his wallet.
Jamie Lewis says not to worry about the connection to Liberty and other protocols for individual identity. Develop the solar system (i.e. the mass of customers that will make big guys pay attention) and the relationships will form. The one thing big companies have figured out is that there will never be one way to do things.
12:23 PM | Recommend This | Print This
DIDW 2004: Federated identity Provisioning Panel
|
Federated identity provisioning panel: Archie Reed, Howard Ting, Chris Ceppi, Ranjeet Vidwans, and Justin Taylor (l to r)
|
10:39 AM | Recommend This | Print This
DIDW 2004: Justin Taylor on Identity Driven Computing
There were three sessions I wanted to attend this morning. I knew that Linda Elliot's session on compliance would be a good one and probably have some information I could use, but in the end I opted to go to Justin Taylor's session on identity driven computing.
Justin opens with the usual schtick that you hear opening talks at DIDW (including mine) about how today's ID systems are siloed with different protocols, standards, tools, and management styles. There's no common paradigm among the various vendor products and trying to get them to work together is an exercise in frustration.
Justin wants identity to go beyond "carbon-based life forms" and apply the things we've learned about managing human identity to documents, servers, and other resources. He defines digital identity as the "distinguishing characteristics of an entity in a digital system." He says "an identity is the sum of its attributes." This of course is not meant to be deeply philosophical, its just a practical realization of what we're really talking about when we speak of digital identity.
Viewing identity this way allows you to create a lifecycle for the identity and that allows you to manage it.
The identity driven computing model is a common set of services utilized by today's, as well as next generation systems and applications to manage the behavior between all the identities in your enterprise to address the challenges of business. These services are integrated through a service oriented architecture. This idea relies on loosely coupled directories.
Justin applies this to home-based identity. Is there a place for holistic identity management in the home? Every DVD player has different parental control locks but they're all different and unmanaged. This is likely to proliferate over time. Can identity management be made "consumer friendly?"
Justin speaks to the centralization-decentralization debate. He uses policy as an example of something that has to be centralized (for regulatory compliance, for example) but must be decentralized in its use. This is not an either/or kind of thing, but points out that there are different activities that take place everywhere along the centralization spectrum.
Decision that use identity must be made in context. Context is the sum of the human, the device, and the application or resource. Knowing the attributes of each of these identities allows intuitive policy management. SAML allows this, although its not typically used in this fashion.
Justin uses the example of an executive accessing corporate financial data from an iPAQ over the net. The CEO has declared that "access to financial data restricted to Sr. VP or higher" while the CSO has declared "access to financial data restricted to desktop or laptop." These two different policies need to be applied together even though they're created separately.
In the end, I'm not sure Justin lived up to the billing of "identity driven computing" to the extent I'd hoped. The talk was good and the information useful, but this was more of an analyst's talk that a technical talk. I think that's what I was hoping for.
09:47 AM | Recommend This | Print This
DIDW 2004: A Few Technologies that Interested Me
You already know that I liked the Identity Commons and i-names. There were a few other technologies I ran across at the show that I liked as well. Briefly, here they are:
- Core Street makes technology for controlling physical access, among other things. What I thought was cool is that they use smart cards (their vendor agnostic) as a form of sneaker net to carry revocation lists, access changes, new certificates and so on from lock to lock. This allows them to put smart card access-controlled locks on places that can't be networked (like the door of an airplane cockpit) and still keep it up to date. I think that's very clever. As an aside, the CEO of Core Street, Phil Libin writes a weblog called Vastly Important Notes.
- sxip Networks (pronounced "skip") is a person-centric identity company, giving people the ability to manage an identity that can be federated across multiple sites. Once you create a sxip ID at your home site (which could be your own computer), you can use it to log into any sxip membersites. There's a demo on their site which you can use to actually create a sxip ID and then use it.
- Midentity is a British company founded by Simon Grice. I met Simon and heard about Midentity last year at DIDW 2003. Midentity allows you to create identity profiles and then share them with others. Midentity did the attendee list for DIDW 2004 and I've used it already to contact some people at the conference who I didn't have email addresses for. I wish O'Reilly would do this at their conferences instead of the printed page of names and addresses.
There's plenty of other companies here at the show and I'm sure they've got some good tech, but these seemed particularly innovative and interesting.
08:51 AM | Recommend This | Print This
Doc's Got an I-Name
Doc Searls has an i-name, =searls. Doc hopes this will "finally give us what I call The Fully Empowered Customer."




