This naive utopian view of yours - its silly. Your not inventing anything new here - just trying to fit into the existing servers and practices that have been with us for years. At the end of the day - all we want is a client that works, with all servers. TLS 1.2 is quite old, but only recently started to be adopted, including Filezilla. But you seem to have an agenda for some other purpose.
MS is not going to change a server code just to suit your sloppy coding desires. The RFC is very specific about the issues you will encounter with your current coding methods. In fact RFC 5246 Appendix E has three paragraphs discussing this very issue and finishes with the warning "No single value will guarantee interoperability with all old servers....". Yet your program tries to do just that - sends out conflicting version methods, and fails because of it. Doh!
You hold the RFC in high regard, but then ignore the warnings, difficulties it describes, and its suggested methods on this very issue. What makes you such a hypocrite?
MS is not going to change a server code just to suit your sloppy coding desires. The RFC is very specific about the issues you will encounter with your current coding methods. In fact RFC 5246 Appendix E has three paragraphs discussing this very issue and finishes with the warning "No single value will guarantee interoperability with all old servers....". Yet your program tries to do just that - sends out conflicting version methods, and fails because of it. Doh!
You hold the RFC in high regard, but then ignore the warnings, difficulties it describes, and its suggested methods on this very issue. What makes you such a hypocrite?