- From: Joe Touch <touch@isi.edu>
- Date: Fri, 19 Aug 2016 10:27:26 -0700
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Willy Tarreau <w@1wt.eu>, Matthew Kerwin <matthew@kerwin.net.au>, tcpm@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Patrick McManus <pmcmanus@mozilla.com>, Daniel Stenberg <daniel@haxx.se>
Mark, On 8/18/2016 8:49 PM, Mark Nottingham wrote: >> On 19 Aug 2016, at 1:07 AM, Joe Touch <touch@ISI.EDU> wrote: >> >> I do think that this doc needs to figure out whom it is speaking to, what advice they actually need, etc. >> >> If the result is a set of recommendations that involve the word "sysctl", I remain skeptical it is appropriate as an RFC > > I think there's broad agreement on both of these points. > > I'm wondering if it makes sense to aim it primarily at HTTP implementers rather than administrators, with the notion that it would inform: > > - Their implementation decisions > - The configuration choices they offer to administrators / users > - Their documentation (e.g., advice to their administrators when the implementation can't change the appropriate parts of the OS) > > Would that help? I think so. I also think it would be very important to differentiate the issues that are unique to HTTP (if any) vs. those that are generic to any transaction system. > If so, it might make sense to organise it into sections for clients and servers (and intermediaries, if there's anything that isn't covered by the combination of the first two). Although IIRC Daniel was already talking about doing that. Clients, servers, proxies, and (even though a violation of so many parts of the Internet) transparent proxies. Joe
Received on Friday, 19 August 2016 17:29:33 UTC