[whatwg/fetch] section #connections is vague wrt connection is HTTP or HTTPS or HTTP/2 or QUIC (#641)

The [obtain a connection](https://fetch.spec.whatwg.org/#concept-connection-obtain) algorithm in section [#connections](https://fetch.spec.whatwg.org/#connections) presently says this:
> Set connection to the result of establishing an HTTP connection to origin. [HTTP] [HTTP-SEMANTICS] [HTTP-COND] [HTTP-CACHING] [HTTP-AUTH] [TLS]
> 
> If credentials is false, then do not send a TLS client certificate. 

However, one is not going to "send a TLS client certificate" if one is not running over TLS, and there is no context in this alg whether or not a HTTP or HTTPS or HTTP/2 or QUIC or whatever connection is established.

Given the associated Note says in part: "This is intentionally a little vague as the finer points are still evolving." this is likely understood, tho I did not find an already-open issue regarding this, thus am submitting this one.

Offhand, it seems one way to nominally address this is to: 
* declare a connectionType enum with values of "HTTP, HTTPS, HTTP/2, QUIC" (for now),
* pass a connectionType param to the [obtain a connection](https://fetch.spec.whatwg.org/#concept-connection-obtain) algorithm, 
* add connectionType as part of the per-connection state maintained by the connection pool
* add logic to [obtain a connection](https://fetch.spec.whatwg.org/#concept-connection-obtain) alg to open conn of specific type per connectionType.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/641