- From: Eliot Lear <lear@cisco.com>
- Date: Sun, 29 Nov 2015 22:07:50 +0100
- To: Alex Rousskov <rousskov@measurement-factory.com>, HTTP Working Group <ietf-http-wg@w3.org>
Received on Sunday, 29 November 2015 21:08:27 UTC
On 11/29/15 2:24 AM, Alex Rousskov wrote: > On 11/25/2015 10:29 PM, Mark Nottingham wrote: > > >> Now that we have RFC7686, there's a new requirement applicable to HTTP clients: > That requirement is for RFC 7686 applications, not HTTP applications. If > some HTTP applications decide to comply with RFC 7686, then they may do > so, of course, but that decision has pretty much nothing to do with HTTP. > > Proof: If the requirement were to apply to all HTTP clients, RFC 7686 > would have been marked as "updating" HTTP (and 100s of other protocols > with RFCs). > This puts more stock in IETF document practices than is probably worthy of calling a proof. I would rather we examine the issue from a pragmatic approach such that unnecessary and/or dangerous queries are suppressed at the appropriate level. Eliot
Received on Sunday, 29 November 2015 21:08:27 UTC