-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Crocker wrote:
>> Summary of the requirements.... > > While I understand that reading the cited material will, no doubt, > answer basic questions, I'll use the fact that you provided a summary to > justify asking a few, basic questions. Your summary list does not seem > to answer them, yet I believe the answers to these questions provide a > basis for evaluating something like the summary list you provided. > > That is, I see your summary list is mostly about mechanism, whereas my > own questions are about motivating factors: > > > 1. What problem does DIX solve and for whom? How is the problem > currently manifest? > > 2. What does a basic scenario for using DIX look like? That is, who are > the typical actors and what are their typical interactions, for a > single, "complete" use of DIX? > > 3. From the summary, I cannot tell what the actual "identity" is, where > it comes from, and whether or how it is assured uniqueness. Good questions. I helped write the spec for a technology called Passel that attempted to solve some problems in this space, and the whitepaper may be of interest to those on this list: http://passel.org/whitepaper.html Peter - -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD/z3lNF1RSzyt3NURAna3AJ4k0BRlXpfxfzMS6nfmm6b27//s7QCfQHUF b5y8JkgihdL75SL5patboYY= =GGpQ -----END PGP SIGNATURE-----
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
