I'll repeat the most important argument from my previous email, which
you elided in your response: You're smart. If someone offers you enough
money to make this work in your product, you'll figure it out.
/a
On 11/20/08 3:58 PM, Hadriel Kaplan wrote:
-----Original Message-----
From: Adam Roach [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 20, 2008 3:47 PM
But those B2BUAs are all in the same administrative domain.
Unfortunately they're not.
Alice calls Benny; Alice is in foo.com, Benny is in bar.com; foo.com b2bua
sends it to pwned.com, which sends it to bar.com. Benny then sends an
out-of-dialog Subscribe to [EMAIL PROTECTED] There's no guarantee it will go
through pwned.com on its way back there.
But anyway even just hitting a different b2bua at pwned.com will make it
unlikely to work. :(
Given that
fact, there are solutions to the problem, such as synchronized minimal
state
Oh yeah that's fun. We're nuts, not crazy. :)
-- or, preferably, stateless reversible dialog identifier
transformations.
We tried that - gets too big. (did I mention many devices appear to have finite
header string length limits?)
Since this problem at some level is that the From-URI is being used instead of
contact-uri, if you'd prefer we can also just munge the From-URI to identify
the specific b2bua. Yuck. And it won't work if there are 2 pwned.com transit
domains. And down the rabbit-hole we go...
Or we can go do this little thing like Session-ID. :)
-hadriel
_______________________________________________
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
_______________________________________________
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
