Interestingly, doing the DNS lookup for blue.com, and recognizing that
you already have a connection from that address would work in this case.
Paul
Vijay K. Gurbani wrote:
Paul Kyzivat wrote:
Unfortunately, people are using it and as such something ought to
be said about it in the draft. I agree that as the less said, the
better. I also agree that putting the "alias" parameter in the
Via request for TCP.
There seems to be something wrong with the last sentence. Did you
forget a word or two?
Yes, sorry; I meant to say that "I also agree that putting the "alias"
parameter in the Via request for TCP is not a good idea."
This still does not solve the problem of reusing TCP connections
for virtual servers; i.e., B does not know that that A's physical
IP address is being used by multiple virtual domains.
I don't understand what point you are making here.
Consider named-based virtual hosting in SIP, where the same IP
address supports multiple domains. red.com and blue.com are hosted
on a physical server that uses one IP address. Now, when red.com
makes a TCP connection to another domain -- example.com -- then
example.com may want to use this TCP connection to send requests
to blue.com (because blue.com's IP address matches red.com's).
Same problem we had in TLS, except the way we solved it in TLS
was to associate the identity picked up from the certificate with
the connection.
Thanks,
- vijay
_______________________________________________
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
