Ralph- That would be the most appropriate way, but currently only S2S components use the SRV records, and they are still using _jabber._tcp, instead of _jabber-server._tcp. AFAIK, no clients currently support SRV record lookups.
Cheers, bs. Ralph Siemsen wrote: > Way back on 02/25/2002, David Waite wrote: > >> I think I would prefer _jabber-client-ssl._tcp and >> _jabber-server-ssl._tcp (either way should work). I could try to >> register the SSL ports, but would anyone be totally against requiring >> SRV lookups for SSL-based connections? >> >> Actually, there was another issue I didn't realize until reading the >> SRV doc. Supposedly now that there is a registered service with the >> IANA, we should be using that within the SRV lookup (see RFC 2782, >> Format -> Service (interesting bit at the top of page 3). This means >> that _jabber._tcp should really be _jabber-server._tcp. Whoops. > > > Is this the recomended usage then when creating SRV records? eg.: > > _jabber-server._tcp.mydomain.com pointing to 5269 > _jabber-client._tcp.mydomain.com pointing at 5222 > > Thanks, > -R > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
