The HTTP/2 RFC should not mandate RSA certificates

Hello,

Late last year, I submitted a patch to Go’s HTTP/2 library to allow the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 cipher as an alternative MTI cipher to the TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher that the HTTP/2 RFC mandates.

My reasoning for this patch is that many servers only use ECDSA certificates and so the TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 cipher will never be used in those situations and thus we should allow TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as an alternative MTI cipher.

See https://go-review.googlesource.com/c/net/+/30721 <https://go-review.googlesource.com/c/net/+/30721> for further information and discussion.

After some discussion and feedback on my patch, it seems this may be a spec bug.

So is this a spec bug? Is it alright to allow TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 as an alternative MTI cipher?

Regards,
Anmol