[EMAIL PROTECTED] wrote:
From: "Vijay K. Gurbani" <[EMAIL PROTECTED]>
We could nail a line in the sand and make this more concrete (i.e.,
use between proxies only.) Or we could take a middle road and allow
implementors who have reflective connectivity between a UA and a
(proxy) server use connect-reuse. So far, the draft has been taking
the middle road.
It's clear that connection-reuse can be done between a UA and a proxy
(or two UA's for that matter). It doesn't solve the problem that
outbound solves, namely what if connections can only be opened in one
direction. (connection-reuse implicitly assumes that whoever wants to
send a request first can open a connection.) What we need to make
sure is that the two mechanisms don't interfere with each other. This
probably isn't hard, no more than saying "if you're using outbound to
communicate with a SIP agent, don't use connection-use to talk to that
agent".
Agreed -- sounds good. A version of such a statement is already
given in S2:
2. Applicability Statement
The applicability of the mechanism described in this document is for
two adjacent SIP entities to reuse connections when they are agnostic
about the direction of the connection, i.e., either end can initiate
the connection. SIP entities that can only open a connection in a
specific direction -- perhaps because of Network Address Translation
(NAT) and firewall reasons -- reuse their connections using the
mechanism described in [9].
I can reword this to make the outbound part more explicit; something
like:
2. Applicability Statement
The applicability of the mechanism described in this document is for
two adjacent SIP entities to reuse connections when they are agnostic
about the direction of the connection, i.e., either end can initiate
the connection. If connections can only be opened in one direction,
perhaps due to the existence of firewalls and Network Address
Translators (NATs), then the mechanism described by Jennings and
Mahy [9] MUST be used instead.
Okay?
- 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