Re: Call for Adoption: SEARCH method

Willy Tarreau <w@1wt.eu> Wed, 04 November 2020 03:38 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65C783A138B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 3 Nov 2020 19:38:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3VookaTfqvcd for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 3 Nov 2020 19:38:31 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5848C3A1389 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 3 Nov 2020 19:38:30 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ka9aW-0005jX-HQ for ietf-http-wg-dist@listhub.w3.org; Wed, 04 Nov 2020 03:35:56 +0000
Resent-Date: Wed, 04 Nov 2020 03:35:56 +0000
Resent-Message-Id: <E1ka9aW-0005jX-HQ@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@1wt.eu>) id 1ka9aT-0005im-Ee for ietf-http-wg@listhub.w3.org; Wed, 04 Nov 2020 03:35:54 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by titan.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1ka9aR-0000Iz-JB for ietf-http-wg@w3.org; Wed, 04 Nov 2020 03:35:53 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 0A43ZW3l020354; Wed, 4 Nov 2020 04:35:32 +0100
Date: Wed, 04 Nov 2020 04:35:32 +0100
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Tommy Pauly <tpauly@apple.com>
Message-ID: <20201104033532.GB20345@1wt.eu>
References: <F0556EC2-D5AD-47FF-A780-15949F57A911@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <F0556EC2-D5AD-47FF-A780-15949F57A911@mnot.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1ka9aR-0000Iz-JB b1152717e59c0f8b3db3415b30c398dc
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Call for Adoption: SEARCH method
Archived-At: <https://www.w3.org/mid/20201104033532.GB20345@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38140
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Wed, Nov 04, 2020 at 12:07:03PM +1100, Mark Nottingham wrote:
> As discussed in the October 202 Interim, this is a Call for Adoption for the
> HTTP SEARCH method draft:
>   https://tools.ietf.org/html/draft-snell-search-method-02
>
> Please indicate whether you support adoption in response to this e-mail;

This looks reasonable to me. I do have a few concerns about how
implementations will behave in front of it, which definitely justify
that it's adopted and proposed by the WG (e.g. non-cacheability of the
method: what if a cache doesn't recognize the method and caches by
default?).

> information about intent to implement (or use) it is also useful.

I'm not in a situation where I'll need to do anything to use/implement
it as it should be transparent.

Cheers,
Willy