Ah - that doesn't make sense for SIP in general.
You can make it make sense for certain deployments, and what you can
do in those cases
is give your client facing interface one name and your server facing
interface another.
Something like
_sip._tcp.client-interface.example.com
_sip._tcp.server-interface.example.com
So, what else are you missing?
RjS
On Jun 4, 2007, at 3:40 PM, Juha Heinanen wrote:
Robert Sparks writes:
Any name can have SRV records. What distinguishes a server srv record
from any other srv record to you?
xmpp client to server communication uses name
_xmpp-client._tcp.example.com and server to server communication nane
_xmpp-server._tcp.example.com. this allows different proxies to be
used
for client-to-server and server-to-server communication.
-- juha
_______________________________________________
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
