Questions on HTTP URI schemes and QUIC

[Sridhar Bhaskaran <[e-mail]>]

Dear Quic experts,

I am Sridhar Bhaskaran from Huawei. Going through the drafts on QUIC transport and HTTP over QUIC, I have the following queries

1. If a HTTP URI uses http:// scheme and the origin server advertises alternate service via QUIC, can a HTTP client use QUIC to connect to the origin server and still use the http:// scheme URI?
2. If a HTTP URI uses https:// scheme and the HTTP client is configured to connect to a HTTP proxy and if the HTTP proxy supports QUIC, my understanding is the following sequence of events
	a. HTTP client to HTTP proxy QUIC connection is setup
	b. HTTP client issues a HTTP CONNECT request to the proxy with the ":authority" HTTP/2 pseudo header pointing to the origin server
	c. HTTP proxy upon getting the CONNECT request sets up a TCP connection with the origin server
	d. HTTP proxy sends HTTP CONNECT response to the client
	e. HTTP client then initiates a TLS connection towards the origin server via the proxy and the proxy simply tunnels it.
	f. Actual HTTP traffic happens between client and origin server

Is this correct?

Where I am not clear is whether step /e/ actually happens. If it does, then for step /f/ is the client required to do ciphering 2 times - one for the TLS and other for the QUIC connection to proxy itself.

Could you please clarify?

Thanks
Sridhar