- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 13 Feb 2015 16:36:04 +1100
- To: Greg Wilkins <gregw@intalio.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, "Julian F. Reschke" <julian.reschke@gmx.de>
Greg, > On 13 Feb 2015, at 12:06 pm, Greg Wilkins <gregw@intalio.com> wrote: > > On 11 February 2015 at 18:45, Julian Reschke <julian.reschke@gmx.de> wrote: > The best fix of course would be to fix the list. I don't understand why that is so hard. > > Wow, I really think the IETF needs to consider their process if simple stupid things like this can be detected by the process and still not fixed. > > I thought we had just deferred the fixing of the table until a breaking binary change - and surely updating from h2-14 to h2-17 and then eventually to h2 is a binary breaking change that would have allowed us to fix the table? Those aren't breaking changes -- i.e., they don't change the format. > > So it is a distinct possibility that we will carry these errors in this table for decades. Somebody should calculate the carbon emissions we are going to be responsible for because we didn't go for the small efficiency gains on offer with an optimised table! > > I know I say this a lot, but EPIC FAIL! Yes... -- Mark Nottingham https://www.mnot.net/
Received on Friday, 13 February 2015 05:36:35 UTC