Elwell, John wrote:
[JRE] I just don't get how this would work. The UAC receives only one 2xx and as a result initiates one TLS handshake with the UAS concerned. The UAC never gets to hear about any of the other forked-to UASs that might have sent a 2xx, so can never establish a tunnel with those.
Yes, that is correct. Simplicity at the UAC (i.e., does not have to deal with forking) at the risk of a sub-optimal rendezvous algorithm. I do not yet know whether this is a fair tradeoff or not. We could go the 4-way handshake that rfc3265 uses. Or simply bite the bullet as Paul and Francois suggest and mandate the UAC to handle multiple 3xx responses and leave the choice on whether or not to fork and how (serial, parallel) to it. Thanks, - vijay -- Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent 2701 Lucent Lane, Rm. 9F-546, Lisle, Illinois 60532 (USA) Email: [EMAIL PROTECTED],bell-labs.com,acm.org} WWW: http://www.alcatel-lucent.com/bell-labs _______________________________________________ Sip mailing list https://www1.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
