isn't what you're arguing for essentially to make Rustls (or at least its API) part of a Rust standard library, so that everyone's forced (or very highly encouraged) to use it instead of alternatives?
[1] https://doc.rust-lang.org/std/net/struct.TcpListener.html
Far better to let the experts do it.
I should also add that most applications won't even be using the TCP/UDP primitives directly. They'll likely be using a third party library. Rust's stdlib is intentionally minimal and lacking a lot of higher level features that are practically necessary for many applications.
I don't think you can get away with not treating HTTP as a first class citizen anymore. IMO, Go got this right.
I think people are fairly apprehensive towards a bigger std because firstly, dependency management is almost trivial (C++ needs the kitchen sink in std because dependencies don't exist to the language, for example) so it's not that big of a deal, and secondly because a bigger std means a bigger commitment to APIs and maintenance by a relatively small group of maintainers for all eternity.
At the level of the stack where it makes sense to use rust, it doesn't make sense to put HTTP in std. At least not like Go.
Rust has included TCP and UDP in the standard library* because it was rightly recognized that these protocols, like stdio and filesystem io, have become fundamental to how most modern software interacts with its environment (system, IPC). HTTP today has also become fundamental in a similar manner. I argue that it is time that we treated it as such.
* as apposed to leaving them as an external dependency, like mio.
The ecosystem is part of rust.
Rust will have support only when it is included in the standard library.
"Right this minute" is a common phrase, but "does right this" isn't (at least in UK English).