> > ... > > > I agree it's far from ideal. There are two possible solutions > > > to this sort of problem: > > > > > > - Some sort of authenticated history mechanism that gives > > > the gateway > > > confidence that the call was routed correctly > > > > A different take on a solution (aimed at ssh and self-signed HTTP > > certificates) is discussed at: > > http://www.cs.cmu.edu/~dwendlan/perspectives/ > > I don't see how the technique described here can plausibly work > with SIP, given that they rely on probes from different locations > getting the same response, which is not a requirement for SIP.
If there is only one entity that 'owns' an identity -- which is absolutely the case with email-style URIs with SIP -- it would work. And with E.164, there should also be only one entity that 'owns' a number. If there are multiple, they are PSTN gateways and none of them own the number at all. -d _______________________________________________ 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
