Re: Call for Adoption: SEARCH method

Austin Wright <aaa@bzfx.net> Wed, 04 November 2020 20:43 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 192383A0DD4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 4 Nov 2020 12:43:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.747
X-Spam-Level:
X-Spam-Status: No, score=-2.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bzfx.net
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 ubg0igsmSVEq for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 4 Nov 2020 12:43: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 CA30F3A0E3E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 4 Nov 2020 12:43:16 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1kaPaH-0005AD-TB for ietf-http-wg-dist@listhub.w3.org; Wed, 04 Nov 2020 20:40:45 +0000
Resent-Date: Wed, 04 Nov 2020 20:40:45 +0000
Resent-Message-Id: <E1kaPaH-0005AD-TB@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <aaa@bzfx.net>) id 1kaPaG-00059E-BN for ietf-http-wg@listhub.w3.org; Wed, 04 Nov 2020 20:40:44 +0000
Received: from mail-pf1-x429.google.com ([2607:f8b0:4864:20::429]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <aaa@bzfx.net>) id 1kaPaE-0001UD-Fo for ietf-http-wg@w3.org; Wed, 04 Nov 2020 20:40:44 +0000
Received: by mail-pf1-x429.google.com with SMTP id 10so18294534pfp.5 for <ietf-http-wg@w3.org>; Wed, 04 Nov 2020 12:40:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bzfx.net; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=KYXqCeGXG5kmxkaztw1w1wGQNHurGN3afsMKfulFJG8=; b=ANbGtFfNRFHdJcDcg5DPw68NkSCk6v7NBzn0ajMxsCzrZQZgx/V9CpdUxj4PWYlixm 4m1F/Y/i80rTa3h2AXbkNY/eXycfqUVi16J9cGlNXSBSMzXU6IURpjlqF5wiCO2pLcS9 f5NT4jesBLuPXShQFbFwJtjTiZ1Mn/v5FyTYY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=KYXqCeGXG5kmxkaztw1w1wGQNHurGN3afsMKfulFJG8=; b=KX62c4jD6iS9rczbUto4Eaq/IUeBHAJRDDzOV7oMIZgq67ImXs869IBjyypKZStCD9 lBq+bQHewqFGDN3eTkp5RL3d4WVBkJyOG6vfA+97rp2r0nJ1LnPeA6UNXXXVC6juNJrM KbRRLnesZAqH7j685AuaNGFbriyZtsDqEXtbz0M/t2HYQfxpwa4tjo4h7J18vANpD+G/ vOkdR5EPmlHl7alse2c/UUcpuK4YoJy/s25kec5C6iXSXL6/AJqS0eEsgkCWbAbnyIZr lo7eiJPsauVYayAaYnx6GxvJAYs/LOd4MQ9ZnUYcnnJsjOvzEDZd+7BjwoXJRT5q8E1T iVgA==
X-Gm-Message-State: AOAM533rSRTUAJK/aX3A7ryvV6gc12W6glXJ8PVHR8mtg7fFfsKLXfW2 7ZCOg08r74q96quugw+6vTAwUN6o7N5FbQ==
X-Google-Smtp-Source: ABdhPJywcN8VTjiI7FOofmoV+SS3BPJHHjItXqRtl6aNrnATtgUSNXra63Ip84/AhoS+R1/m2Br5Xg==
X-Received: by 2002:a62:be11:0:b029:15f:ea29:9228 with SMTP id l17-20020a62be110000b029015fea299228mr30862675pff.8.1604522430995; Wed, 04 Nov 2020 12:40:30 -0800 (PST)
Received: from [192.168.0.122] ([97.124.238.248]) by smtp.gmail.com with ESMTPSA id d22sm2790750pgv.87.2020.11.04.12.40.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Nov 2020 12:40:29 -0800 (PST)
From: Austin Wright <aaa@bzfx.net>
Message-Id: <8AE9002C-78DE-41E6-8D5E-C2FAF76A3A3B@bzfx.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_58A2747C-F69A-49E6-BA33-977D0188F186"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Wed, 04 Nov 2020 13:40:28 -0700
In-Reply-To: <F0556EC2-D5AD-47FF-A780-15949F57A911@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Tommy Pauly <tpauly@apple.com>
To: Mark Nottingham <mnot@mnot.net>
References: <F0556EC2-D5AD-47FF-A780-15949F57A911@mnot.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Received-SPF: pass client-ip=2607:f8b0:4864:20::429; envelope-from=aaa@bzfx.net; helo=mail-pf1-x429.google.com
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1kaPaE-0001UD-Fo efb3afb7c13a6671553faff9ce638c6d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Call for Adoption: SEARCH method
Archived-At: <https://www.w3.org/mid/8AE9002C-78DE-41E6-8D5E-C2FAF76A3A3B@bzfx.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38159
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 Nov 3, 2020, at 18:07, Mark Nottingham <mnot@mnot.net> 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; information about intent to implement (or use) it is also useful.
> 
> The Call for Adoption will end on 18 November 2020.
> 
> Cheers,
> 
> Mark and Tommy
> 
> 


I’m very much in favor of a safe variation of POST.

However,
> for backwards compatibility with existing WebDAV implementations, SEARCH requests that use the text/xml or application/xml content types MUST be processed per the requirements established by [RFC5323 <https://tools.ietf.org/html/rfc5323>].
I think this is too restrictive. If it’s not possible to relax the RFC5323 requirements, I would favor using REPORT instead.

I intend to implement whatever is adopted.

Thanks,

Austin Wright.