John Merrells wrote:
On 20-Jan-06, at 9:48 AM, Peter Saint-Andre wrote:Suresh Venkatraman wrote:I think Suresh's point was that SOAP is not a transport or messaging protocol, but a message format that can be carried over such protocols. E.g., there are (AFAIK) four transport/messaging bindings for SOAP: HTTP, SMTP, BEEP, and XMPP.Yes, that was my point. It's a bit tricky since in RFC 3288, SOAP is mentioned as a XML-based messaging protocol.That text is still in RFC 4227 but I think we should depend on the SOAP specs to correctly characterize what SOAP is.How about... 'messaging formats and transports'"Any solution should allow DIX messages to be carried over multiple alternative messaging formats and transports, including, but not limited to: HTTP, SOAP, XMPP, and SIP. It is anticipated that this working group will initially focus on a HTTP based solution."
I suggest leaving SOAP out of it. In what way will SOAP be a carrier for digital identity exchange? If SOAP will be an encapsulating format for digital identity data, then it will be transported using one of the SOAP bindings (HTTP, SMTP, BEEP, XMPP). But the same could be said of methods for encapsulating digital identity data in SAML, XHTML, Atom, or whatever else people dream up as a wrapper.
Peter -- Peter Saint-Andre Jabber Software Foundation http://www.jabber.org/people/stpeter.shtml
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
