> To me, this means things like 'I want my SIP phone to party with this > new widely deployed identidy framework'.
It could mean that your SIP phone authenticates itself before registering with a SIP proxy or making a call. The proxy could then verify such claims via the identity framework before making the connection. Or you could choose two-levels of authentication - but that kind of defeats the purpose of decoupling identity from services. > Is that the same as 'support SIP as a transport'? In the scenario above SIP could be used as the transport for the identity transactions. > 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. The same argument can be made for HTTP as with SIP, after all the authentication headers are the same. The SIP RFC leverages the HTTP/1.1 specification for syntax and semantics (WWW-Authenticate, Proxy-Authenticate, etc.). You're arguing in terms of the PSTN world and the current implementations of SIP that facilitate VoIP within those boundaries. There's certainly no limitation in the RFC for the scenario above. > Put another way, is this statement above the same as saying > 'support user agents or clients using multiple ... protocols... ' ? The point is not to the limit the types of UA's that support DIX based on the transport protocol. Every protocol binding is optional in the end. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Boreham Sent: Thursday, January 19, 2006 6:09 PM To: Digital Identity Exchange Subject: Re: [dix] draft of proposed charter (#2) > "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 ? Put another way, is this statement above the same as saying 'support user agents or clients using multiple ... protocols... ' ? _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix _______________________________________________ dix mailing list [email protected] https://www1.ietf.org/mailman/listinfo/dix
