- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Wed, 10 Feb 2016 19:30:32 +1100
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Kari Hurtta <hurtta-ietf@elmme-mailer.org>, HTTP WG <ietf-http-wg@w3.org>, Patrick McManus <mcmanus@ducksong.com>, "Julian F. Reschke" <julian.reschke@greenbytes.de>
On 10 February 2016 at 14:31, Mark Nottingham <mnot@mnot.net> wrote: > This is difficult to specify; one way we could do it is to specify the way we know here (using HTTPS with a strong cert), and require other ways to update this specification (with an Updates: field on the Standards Track). This seems reasonable. If h2c starts to see wider deployment, then a good definition for that that assurance might look like will have to emerge (or alt-svc won't be used there).
Received on Wednesday, 10 February 2016 08:31:02 UTC