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. "
I've been wondering about the semantics behind this thread.
To me, this means things like 'I want my SIP phone to party with this
new widely deployed identidy framework'. Is that the same as
'support SIP as a transport' ? I'm not sure, since for example you
might want to use existing protocol already used in SIP for
authentication, but have the PBX (or whatever is being the SIP
gateway)
use DIX. In that case the PBX would use HTTP transport,
wouldn't it ?
Good question. I didn't bring up SIP as a transport myself, but
to me this means that I might want to send DIX messages over
SIP. Why would I do that... we'd need a use case... not really
knowing anything about SIP i'm not very well qualified to say
... but I might be on a call to a call center and they ask me to
prove something about me... right now they ask a bunch of
questions... SSN, MMN, DOB... with DIX over SIP they might
be able to send the request to my client and assuming it
had the appropriate interface (ie capabilities) it could ask
me if i wanted to reveal that identity information... i'd click
yes and it'd be revealed. Which sounds quite nice to me.
Put another way, is this statement above the same as saying
'support user agents or clients using multiple ... protocols... ' ?
It's a given to me that any agent or client could implement
any protocols it wanted to.... so i'm not trying to say that.
John
_______________________________________________
dix mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/dix
