- From: Eric Rescorla <ekr@rtfm.com>
- Date: Tue, 17 Jul 2018 14:41:10 -0700
- To: HTTP Working Group <ietf-http-wg@w3.org>
Received on Tuesday, 17 July 2018 21:42:16 UTC
Was talking to DKG in the hallway and he pointed out that Alt-Svc-SNI works well for the use case where you have a cert that is valid both for the original domain (the one you looked up) and the replacement domain (the one in the SNI). For instance, you want to reach a.example.com and the server has a cert for *.example.com. This would also have the advantage that you didn't need to change the Alt-Svc semantics at all. Maybe it would make sense to re-scope to that case? -Ekr
Received on Tuesday, 17 July 2018 21:42:16 UTC