Dave Dykstra wrote: >>Since we now have >>jabber-client and jabber-server defined by the IANA, it should be >>_jabber-client._tcp.example.com >> > >What about SSL client connections on port 5223? Should they be >_jabber-clients._tcp.example.com? > I don't know, I didn't standardize the SSL ports. The application was apparently delayed because they were upset about us using two separate ports (I would imagine it is because there are only 48k or so total).
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. -David Waite _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
