Introduce TlsConnect and QuicConnect trait to be more flexible about hickory-dns HOT 4 OPEN

What is the actual problem you're trying to solve?

from hickory-dns.

What is the actual problem you're trying to solve?

First, to use other tls / quic backends such as boringssl or quiche.
Second, to be able to update the tls / quic backends independently.

from hickory-dns.

Out of curiosity, can you give more context on why you/Bytedance want to use different TLS/QUIC backends?

from hickory-dns.

I have forked a variant-ssl crate from openssl, which added support Tongsuo and AWS-LC that won't be accepted by openssl crate. So I don't want to have another openssl dependency.

We have been using rustls in the G3 project for all of the hickory features,
but for this part, it's really a long time to wait when we want to update the version to 0.22 (rustls -> quinn -> h3_quinn -> hickory), I can disable the DoQ and DoH3 features for some time, but I don't want to disable DoT and DoH features.

And we may also have to support TLCP (a TLS variant protocol that is officially promoted in China) usage in DoT and DoH, so we have to use Tongsuo or some other tls crates in such case.

from hickory-dns.