On Apr 12, 2008, at 6:59 AM, Ben Campbell wrote: > > On Apr 12, 2008, at 4:16 AM, Dean Willis wrote: >> >> I think at least one carrier has gotten a workaround in place to >> user caller-ID as an authenticator, but only when the call is >> originating from a mobile in their network and they've handled the >> GSM authentication themselves. > > So to bring the conversation back to something vaguely relevant-- > they've stopped trusting CallerID for interdomain (or intercarrier > at least) authentication. >
1) The SIP Authentication Service described in RFC 4474 is not caller- ID. It is an authentication service -- more or less, the SIP alternative to Kerberos or Radius. One might well envision it as the solution to the problem that the mobile operators have with caller ID as an authenticator, and (should mobile operators use SIP) as the interdomain authentication tool of choice. 2) The problem is still that, since it is considered "string authentication" (not caller ID), RFC 4474 cannot reasonably be used for a call originating on the PSTN. But we require RFC 4474 be used on calls that need integrity protection of their media key for the IP path (which ideally would be all calls traversing IP paths). Consequently, we can not use the full benefits of DTLS-SRTP when the UAC is a PSTN gateway. -- Dean _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
