<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4134.600" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Firstly, any known problems with using Mozilla to
send mail to this list. Whenever I use MozMail to send mail, it takes for
ever to get through. With outlook express, it gets through straight away
:(</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Anyway, there seems to be some interest in this
topic. Therefore I think I will send a JEP to the foundation asking for the
creation of a JIG. A few comments:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Liberty Alliance: An interesting project that has
all the right ideas, but so far is pure vapourware from what I can tell. There
is no reason why we should not join this project if allowed, but I dislike it's
entirely commericial viewpoint. The aim of the LA seems to be entirely
getting access to even more information on consumers. The term "user" is not
mentioned on its front page, only "business" and "consumer". Email wasn't built
for mass marketing, IM wasn't built for market research. Identity shouldn't be
built for companies either. It should be built for the people.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Kerberos: Wasn't designed for the web at all. Also
very very complex, I looked into this in depth recently. It's also a
not-quite-standard as there is an "enhanced" (cough) version that MS uses, and
then the MIT version that everyone else uses. However, it's beginning to look
like Kerberos will act as the glue between different systems, allowing them to
at least partially interoperate.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>DCE: I tried to find information on it, all I got
was a page written in 1995. I've never seen a Windows implementation either.
Perhaps this software solves all, but I remain to be
convinced.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>To answer Scott Cote: obviously the final
implementation would be decided in the JIG. But it would probably be based on
the jabber network. So for instance, to login to a website/service you would
provide your Jabber network address ( i suggest this as a more user friendly
name JID ) and then your jabber server would be contacted to
authenticate.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>However, like I've said before, we should recognise
that this is bigger than Jabber. If we define a protocol, it should be
sufficiently abstracted to allow bindings to other protocols as well, therefore
allowing interoperability.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So - unless anyone has major objections I will post
the JEP tomorrow.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>thanks -mike</FONT></DIV>
<DIV><FONT face=Arial size=2>_______________________<BR>Michael Hearn<BR><A
href="mailto:mhearn@neuk.net">mhearn@neuk.net</A><BR>Jabber (jabber.org) <A
href="mailto:tweedledee@jabber.org">tweedledee@jabber.org</A><BR>ICQ#
34800568</FONT></DIV></BODY></HTML>