On Thu, Aug 27, 2009 at 08:51:58AM -0600, Peter Saint-Andre wrote: > Let's say that you host microcomaustralia.com.au (hereafter m.c.a to > save typing) at foo.bar.com.au on port 5269 for s2s. If you want people > to also connect to wave.m.c.a you need a way for them to discover that > you also offer that service and how to connect to it for s2s purposes. > The way we do that is via SRV records. Yes, you can use a plain old A or > AAAA lookup as a fallback, but the SRV records are preferred. This is > explained more clearly in draft-ietf-xmpp-3920bis than in RFC 3920.
Yes, I understand the need for these SRV records: _jabber._tcp.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-server._tcp.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-client._tcp.microcomaustralia.com.au has SRV record 5 0 5222 chat.microcomaustralia.com.au. wave.microcomaustralia.com.au is an alias for chat.microcomaustralia.com.au. However some people were suggesting I needed these records too: _jabber._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-server._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5269 chat.microcomaustralia.com.au. _xmpp-client._tcp.wave.microcomaustralia.com.au has SRV record 5 0 5222 chat.microcomaustralia.com.au. Then again maybe I should read that draft standard, as I still don't really understand why wave.microcomaustralia.com.au is required, when it (I believe) must be the same server as the _xmpp-server and _xmpp-client. -- Brian May <[email protected]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
