Hi: During the WGLC review of connect-reuse-08, I received a private email requesting that the document contain explanation of terms being used. To quote the email:
> A connection is established, and two things can happen.... > > 1. One end sends multiple messages over the same connection > for multiple sessions, where these sessions are sequential. > Example: A sends INVITE to B, and all dialog messages for the > call sessions traverse the same TCP connection until the BYE > and 200 OK BYE is completed, at which time the connection > is not torn down but remains up and a subsequent INVITE session > is then initiated over the same connection. We had been > calling this TCP Connection Reuse. > > 2. One end sends multiple messages over the same connection > for multiple simultaneous sessions. Example: A sends INVITE to > B for one call session and then sends another INVITE to B for > another call session and so on. Each session is maintained in > parallel with the others, and all dialog messages for all > sessions traverse the same TCP connection until the BYE and > 200 OK BYE is completed for each session. We had been calling > this TCP Connection Sharing. > > These are not just our usages of the terms, but are also being > used by our customers as well. Note that there are existing techniques in SIP to disambiguate multiple dialogs/sessions arriving on the same TCP stream. So the difference between connection reuse and connection sharing is not tied to whether the sessions are sequential or not. Rather, the difference is whether or not the connection can be used to send requests in the backwards direction. More specifically, Connection Reuse: The process of using the same connection to send new requests in the backwards direction (i.e., A opens a connection to B to send requests, and B uses the same connection to send new requests to A.) Connection sharing: The process of using the same connection to send multiple requests on the same connection (and of course, receive multiple responses over the connection.) A shared connection will not be reused for requests in the backwards direction. Comments? Thoughts? Suggestions? Other terms to document? 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
