- From: Joe Touch <touch@isi.edu>
- Date: Wed, 17 Aug 2016 17:59:30 -0700
- To: Mark Nottingham <mnot@mnot.net>
- Cc: tcpm@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, Patrick McManus <pmcmanus@mozilla.com>, Daniel Stenberg <daniel@haxx.se>
Mark, My point is simple: this work is useless if it fails to cite the relevant prior work that explains the rationale behind its recommendations. Mine isn't the only work not being cited here - there's all the work in TCP tuning from PSC, many web workshops from the 90s, and numerous RFCs and books. I've pointed out just a few. I don't care to do the author's homework, but as AD I'm disappointed you don't seem to care about that either. Joe On 8/17/2016 5:51 PM, Mark Nottingham wrote: > The AD has spoken, and I think we're rapidly approaching the point of being off-topic here. I'll respond to your question below, and of course if you change your mind and do want to follow up with a helpful list of suggested references, you're most welcome. > > >> On 18 Aug 2016, at 1:08 AM, Joe Touch <touch@ISI.EDU> wrote: >> >>>>> If that's the case, I'd observe that the IETF isn't an academic publisher, and acknowledging all prior work in an area is neither practical, nor required, nor current practice. >>>> Plagiarism isn't an issue limited to academic environments. Publication >>>> of a document on the web is still publication. >>> Sure. It also isn't a legal issue in this form (unless you're asserting copyright?). Effectively, it's a cultural norm. Again, I will point out that in the culture of the IETF, we historically have not cited the complete provenance of every idea, both because it's impractical and because it doesn't benefit the reader. >> Although that's true in the smallest cases, the IETF does have two >> concepts that support this norm: an author list and a set of references. >> >> Can you explain how it helps the reader to not cite two documents that >> are both squarely in the same area as this doc (interaction between HTTP >> and TCP and the impact of running many small connections closed at the >> client as for HTTP)? > Oh, it can be very helpful; I don't think anyone disputes that appropriate references are helpful. > > Whether or not specific documents -- such as yours -- should be referenced is a matter for editorial discretion and eventually WG consensus. > > I note that no one else has supported your claims, but others have said (e.g., [1]) that your work probably isn't appropriate for the intended audience (HTTP implementers and administrators). > > Directing Daniel to add citations to mollify you at this point would be entirely inappropriate, because it would give an incentive to others who want their works cited without full review to make similar claims -- whether that be due to a genuine desire to help, a desire to increase their h-index, or to bolster an IPR claim against a technology. > > Or, of course, Daniel could use his editorial discretion to decide to cite your work before the WG adopts it; however, I'd very much understand if he didn't want to do so at this point. > > Regards, > > > 1. http://www.w3.org/mid/20160817064545.GD16017@1wt.eu > > -- > Mark Nottingham https://www.mnot.net/ >
Received on Thursday, 18 August 2016 01:00:35 UTC