On 13/03/2019 15.09, Travis Burtrum wrote:
On 3/13/19 3:40 AM, Philipp Hörist wrote:
Whats the use case for this XEP?
Until now i only needed DNS querys to connect to the XMPP Server, i
see this XEP is not helping with that as it already needs an active
connection to the XMPP Server.
Like DoH, where you hard-code an IP, port, path, and whether to query
via POST or GET to bootstrap your first DNS queries, the same can be
done here by hard-coding a IP, port, JID, password, and resolver JID.
The syntax I use for this in jDnsProxy is this:
xmpp://208.68.163.210:5222#user=any...@example.org/resolver;pass=y0urPa55W0rDHere;resolverJid=d...@moparisthebest.com/listener
I haven't looked in-depth towards your proposal, but this is not
probably not a valid XMPP URI, or at least not how you think it is. As
per RFC 5122, the relevant ABNF productions look like this:
xmppiri = "xmpp" ":" ihierxmpp
[ "?" iquerycomp ]
[ "#" ifragment ]
ihierxmpp = iauthpath / ipathxmpp
iauthpath = "//" iauthxmpp [ "/" ipathxmpp ]
iauthxmpp = inodeid "@" ihost
ipathxmpp = [ inodeid "@" ] ihost [ "/" iresid ]
In your case, I think your example would parses as:
iauthpath: 208.68.163.210:5222#user=any...@example.org
inode: 208.68.163.210:5222#user=anyjid
ihost: example.org
ipathxmpp:
resolver;pass=y0urPa55W0rDHere;resolverJid=d...@moparisthebest.com/listener
inode: resolver;pass=y0urPa55W0rDHere;resolverJid=dns
ihost: moparisthebest.com
iresid: listener
Although the # cannot be in inodeid (reserved and not in nodeallow), in
which case the alternative would consider everything behind the # to be
ifragment, but then ihierxmpp doesn't produce because there's no inodeid
+ "@" in the iauthxmpp, and there's no "/" + ipathxmpp following it.
You may want to have another look at this.
--
ralphm
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
_______________________________________________
