RE: Let's fix THE PROBLEM

Markus Isomaki wrote:
> So, I don't think the problem is that there wouldn't
> be generic enough PubSub protocols available for the 
> Internet, even defined by the IETF. There are probably 
> even too many...
	In XMPP, Presence is a single monolithic package. More general
PubSub requirements aren't being addressed by XMPP even though there is
an effort to do so under the Jabber process (see JEP-0060). Also, XMPP
Presence is so different from the PubSub proposed in JEP-0060 that it is
hard to imagine XMPP implementations ever publishing presence data over
a PubSub transport even if JEP-0060 eventually gets folded into the IETF
process. Unless something drastic happens, it would seem that Presence
and PubSub will never meet in XMPP...
	Things are better in the SIP/SIMPLE world since, as you note,
there is Adam Roach's RFC3265. And, yes, SIP Publish is a move in the
right direction, however, the document is completely tied up with
references to Presence. While it claims that it is trying to define  a
general capability, it is entitled "(SIP) Extension for Presence
Publication" and is heavily encumbered by references to Presence. This
poor decomposition is, I think, the source of such overloading as is
exhibited in draft-rosenberg-peterson-simple-pidf-phone-00.txt. 

		bob wyman




  [reminder: [email protected] for non-technical discussions, please]