-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/27/09 6:53 PM, Brian May wrote:
> 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
That record is no longer necessary -- it was obsolete in 2004 by the
_xmpp-client._tcp record (e.g., we haven't used it at jabber.org in years).
> 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.
Correct.
> wave.microcomaustralia.com.au is an alias for chat.microcomaustralia.com.au.
It's not necessarily an alias -- it could be hosted elsewhere.
> 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.
Since Wave is server to server only, you need only the second one.
> Then again maybe I should read that draft standard,
Always a good idea. :)
> 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.
There's no must here.
The relevant text is:
Note: Many XMPP servers are implemented in such a way that they
can host additional services (beyond those defined in this
specification and [xmpp-im]) at hostnames that are subdomains of
the hostname of the main XMPP service (e.g.,
conference.example.net for a [XEP-0045] service associated with
the example.net XMPP service) or subdomains of the first-level
domain of the underlying host (e.g., muc.example.com for a
[XEP-0045] service associated with the im.example.com XMPP
service). If an entity from a remote domain wishes to use such
additional services, it would generate an appropriate XML stanza
and the remote domain itself would attempt to resolve the
service's hostname via an SRV lookup on resource records such as
"_xmpp-server._tcp.conference.example.net." or "_xmpp-
server._tcp.muc.example.com.". Therefore if a service wishes to
enable entities from remote domains to access these additional
services, it needs to advertise the appropriate "_xmpp-server" SRV
records in addition to the "_xmpp-server" record for its main XMPP
service.
http://tools.ietf.org/html/draft-ietf-xmpp-3920bis-01#section-4.2
Peter
- --
Peter Saint-Andre
https://stpeter.im/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqXN+MACgkQNL8k5A2w/vx++gCgh9HC6TVgSbG8bXLFJgpHmpho
WU4AnR4C3gALk+GgX22CgqR/n7pKPFMs
=rwFX
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
