I think you're talking past each other.  Your original statement did not 
specify their listen ports would be different.  If they're not different, ie if 
both domains end up pointing to the same IP+port on the server, then they are 
the same server, which just happens to be servicing multiple domains, and 
sending to the same connection is fine.  If they're the same IP but different 
ports, such that SRV resolves example.com to port 5060 and blue.com to 5070, 
for example, then you shouldn't send to both domains on the same connection - 
because they may well be two different processes, and example.com could lie and 
take over blue.com's requests.

-hadriel

> -----Original Message-----
> From: Vijay K. Gurbani [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 25, 2007 7:12 PM
> To: Paul Kyzivat
> Cc: IETF SIP List
> Subject: Re: [Sip] WGLC: draft-ietf-sip-connect-reuse-08.txt
>
> Paul Kyzivat wrote:
> > Interestingly, doing the DNS lookup for blue.com, and recognizing that
> > you already have a connection from that address would work in this case.
>
> Precisely, and therein lies the problem, right?  example.com
> is using one connection to the virtual server to deliver requests
> destined for another domain on the same virtual server.
>
> Or are we talking past each other?
>
> - 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


_______________________________________________
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

Reply via email to