- From: Patrick McManus <mcmanus@ducksong.com>
- Date: Tue, 28 Feb 2017 04:55:35 -0800
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Cc: Alex Rousskov <rousskov@measurement-factory.com>
- Message-ID: <CAOdDvNo5fqFphe6xwq+P6D7fkEW6eY-BVntUXs+sYW=P4usJiQ@mail.gmail.com>
On Mon, Feb 27, 2017 at 10:37 PM, Willy Tarreau <w@1wt.eu> wrote: > The root cause of the problem is that it's hard to get consensus on a > solution to a problem not everyone agrees with. > I agree with that - I also think there is large dose of confusion between "interop the wg can define" and "expectations of what other products implement". As co-chair I think its perfectly fine for this group to consider technical gaps for any problems related to HTTP (there are chartering considerations for documents - but let's just handwave that for a minute) including this one - Mark's old draft is a good example. That's the easy part. The hard part is whether it addresses the fundamental problem or not - and sometimes you can't assess that right away (although that's a reason we try and gauge implementor interest before officially taking on new work). In this case, if the problem is one of clarity and an unconstrained vocabulary then maybe we're onto something. If the problem is more that a User Agent thinks it should be emphasizing two party instead of three party communication (as I suggest upthread) then this working group is unlikely to be the forum where that fundamental stalemate is broken until something about the market conditions shift. I think you could make arguments for the market having shifted simultaneously in contradicting directions already and that might have ramifications for HTTP interop. -Patrick
Received on Tuesday, 28 February 2017 13:00:39 UTC