> -----Original Message----- > From: John Merrells [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 19, 2006 9:43 PM > To: [EMAIL PROTECTED]; Digital Identity Exchange > Subject: Re: [dix] draft of proposed charter (#2) > > > On 19-Jan-06, at 6:09 PM, David Boreham wrote: > > >> "Any solution should support multiple transport and messaging > >> protocols, including but not limited to: HTTP, SOAP, XMPP, > and SIP. " > > > "Any solution should allow DIX messages to be carried over > multiple alternative transport and messaging protocols, > 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." > > Hmm, almost as much weaseling as a legal document.
John, I would suggest that your charter should describe a need to specify at least one "mandatory to implement" transport/messaging protocol to ensure a minimal level of interoperability. I don't care if you use weasel words now to avoid picking one at charter time, but you should commit to settling on one. -Scott- _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
