Mon, 8 Jan 2018 23:19:36 -0500 Travis Burtrum <[email protected]> wrote:
> In my opinion, at least all of cannot-connect-to-port, non-XML, > not-proper-stream and invalid TLS cert should trigger a fallback to > the next highest priority SRV record. I disagree. In the most cases the same result will be for other SRV records and you just waste resources and introduce delays. It seems like you have a particular problem (misconfigured software, or what? I'm not sure), you generalize it and now try to solve this generalized non-existing problem. Initially, from what I understand, the RFC has the exact problem to solve: dead network links or halted/overloaded hardware/software, now you're adding a misconfiguration? _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
