[Standards] Server status pages

Mathieu Pasquet mathieui at mathieui.net
Sun May 24 10:43:51 UTC 2020


On 24.05.2020 11:31, Dave Cridland wrote:
>
>
>On Sat, 23 May 2020 at 11:53, Mathieu Pasquet <mathieui at mathieui.net> wrote:
>
>    On 23.05.2020 11:38, Matthew Wild wrote:
>    >On Sat, 23 May 2020, 10:51 Maxime Buquet, <pep at bouah.net> wrote:
>    >
>    >    All those who expressed feelings against adding this to 157 at the
>    time
>    >    you sent this didn't mention why.
>    >
>    >    I personally don't see much issue with it, so I just PR'd against it
>    to
>    >    add that registry entry.
>    >
>    >
>    >Just want to add a couple of things that have come up in discussions since
>    >starting this thread:
>    >
>    >1) Someone (sorry, don't remember who) had the idea of including this in
>    DNS. 
>    >
>    >Advantages:
>    >
>    >- the client doesn't need to  discover and cache the value after login, it
>    can
>    >discover it on-demand whenever it has connection issues
>    >
>    >- the admin is able to add/update the value while the service is down
>    >
>    >Disadvantages:
>    >
>    >- Not all clients may be in a position to query TXT records (web clients,
>    may
>    >require additional dependency in native clients)
>    >
>    >- Not necessarily secure without DNSSEC
>    >
>    >- Additional work for people who want to delegate a domain for XMPP
>    hosting by
>    >a third party
>    >
>
>    Putting this part into perspective, while I like the DNS solution,
>    that’s yet another "out of band " bit to setup, and I don’t see
>    a huge benefit compared to caching regularly that bit of info
>    from the disco. (at jabberfr we have one ouf our "big" XMPP domains
>    managed by someone else, and it can take weeks to update DNS records…
>    It’s not very practical.)
>
>
>
>Would .well-known work? So for status information on xmpp:jabber.fr, you'd
>follow redirects from https://jabber.fr/.well-known/xmpp-server-status and get
>a status page back. Could easily have two, for machine-readable versus human
>readable, too.

Why not, this is easier (for most people) to setup than a new DNS
record, but this does not address the case where the server (hosting
both the HTTP and XMPP server in many case) is down, which means it
requires caching the content of that .well-known as well to be safe.

Mathieu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20200524/f3ea378b/attachment.sig>


More information about the Standards mailing list