> > There's no reason a protocol can't be spec'd to let the client convey > > the name of the resource before the TLS handshake begins. > > no, there isn't. but it still wouldn't give the client a way to verify > that the server is authoritative for that domain.
<irony>If it isn't, your trust in the CA that issued its certificate is misplaced.</irony>
