I know exactly what it is: it's the protocol I can use in several shipping browsers. ________________________________ From: Julian Reschke<mailto:julian.reschke@gmx.de> Sent: ý2014-ý12-ý10 15:42 To: Domenic Denicola<mailto:d@domenic.me>; Chris Palmer<mailto:palmer@google.com>; Tim Berners-Lee<mailto:timbl@w3.org> Cc: Tim Bray<mailto:tbray@textuality.com>; Marc Fawzi<mailto:marc.fawzi@gmail.com>; Bjoern Hoehrmann<mailto:derhoermi@gmx.net>; Mark Nottingham<mailto:mnot@mnot.net>; Noah Mendelsohn<mailto:nrm@arcanedomain.com>; Public TAG List<mailto:www-tag@w3.org> Subject: Re: Interaction speed Re: Draft finding - "Transitioning the Web to HTTPS" On 2014-12-10 20:58, Domenic Denicola wrote: > From: Julian Reschke [mailto:julian.reschke@gmx.de] > >> 1) HTTP/2 is still pre-IETF-Last-Call > > How does this impact anything at all? "available today" is misleading, because until it's past IETF Last Call and the IESG, you really don't know what exactly it is. Best regards, Julian
Received on Wednesday, 10 December 2014 20:56:15 UTC