On 10/13/2009 Peter Saint-Andre wrote: Hi,
> And why do we have to hardcode a port? You're right that XEP-0156 > provides what we need. The TXT record could be: > > _xmppconnect IN TXT "_xmpp-client-xbosh=https://bosh.jabber.org:5280/bind"; > > That specifies the hostname, the port, and the path. No need for any of > this discussion (other than perhaps registering 5280 with IANA). I try to figure out what the implications of this are, but it kind of boils my mind. Please help me out. In the introduction of xep-0156 I read why SRV records won't work for BOSH: "2. Define a way to specify alternative connection methods as part of the existing DNS SRV records (see RFC 2782 [7]) for a domain that offers XMPP services. While this approach sounds promising, it is not feasible since the DNS SRV Target field can be used only to specify domain names and cannot be used to specify full URIs (such as the URL for an HTTP connection manager)." But later on in the business rules it says: "1. TXT lookups MUST be used only as a fallback after the methods specified in RFC 3920 have been exhausted." Now rfc3920 doesn't deal with BOSH at all, it only considers classic c2s and s2s conenctions. About the relation between SRV and address resolution it says: "If the SRV lookup fails, the fallback is a normal IPv4/IPv6 address record resolution to determine the IP address, using the "xmpp-client" port of 5222, registered with the IANA." Ok, fair enough I think, rfc3920 doesn't deal with BOSH. But why then does xep-0156 mention RFC 3920. Isn't it irrelevant there? Or should I keep to RFC 3920 and connect my BOSH connections to port xmpp.domain.exampt:5222/? (Beacuse the SRV-lookup doesn't work with BOSH and rfc3920 states that that is what should be reverted to.) Doesn't seem to be valid to me either. The most logical way out I see, is skipping the reference to rfc3920 in xep-0156 altogether and incorporate in xep-0206 that a xep-0156 lookup should be done before reverting to ehhh... to what? To port xmpp.domain.example:5280/http-bind/? Hmmm maybe we should register port 5280 and recommend a path anyway... Not that I really care anyway. I only work with clients that reside inside a javascript sandbox, so I can configure them on this. Defaulting to something would only make configuration and changing implementations a bit easier. Also note that in some cases the control over the DNS is limited. About half of my customers are unable configure SRV or TXT records at their DNS provider (this is one of the few points where XS4ALL really sucks, sorry guys). But I can imagine that this does matter to standalone clients that use bosh as stability enhancer or firewall penetrator. best whishes, Winfried -- http://www.tilanus.com xmpp:[email protected] tel. +31.15.3613996 / +31.6.23303960 fax. +31.15.3614406
