Re: [Ohttp] Zaheduzzaman Sarker's Block on charter-ietf-ohttp-00-00: (with BLOCK)

Martin Thomson <mt@lowentropy.net> Mon, 21 June 2021 21:24 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: ohttp@ietfa.amsl.com
Delivered-To: ohttp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1653A1A3D; Mon, 21 Jun 2021 14:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level:
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=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 (2048-bit key) header.d=lowentropy.net header.b=x4Hfzz9H; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=eDpAfSyD
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 TzHV9xZV9X72; Mon, 21 Jun 2021 14:24:23 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 958C53A1A39; Mon, 21 Jun 2021 14:24:23 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F33445C0101; Mon, 21 Jun 2021 17:24:20 -0400 (EDT)
Received: from imap10 ([10.202.2.60]) by compute4.internal (MEProxy); Mon, 21 Jun 2021 17:24:20 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm2; bh=/Q 7zkIynmbmjK4vZzAbop3V/2zsgh0f/TM8zDNDb2ms=; b=x4Hfzz9HHm4l075QI4 XfgoK7q9cL7Mu8Mbxe/pO3l3MlLBFkjQ+fMAc6sUzOmy4SfiCaoMm3F4g8zxUudb 2qpe9fBtITEq0jtbTTU0OOj4gFgoGsMFiIgBOyoB2Iouvhv4VlAmSO52zucMj/sI qChCK9gDakyPtihlgYFSKkmxqf4jK5HnrTMQx2To783y2hOoKFTno1jAhNH+LwQj ibq+NLKGJgte4mFBacABJTyWRSAAbcMQ9j2IUprcX+wk4M9Vi8ezBiAVArGQOqHi gMzvJwG19J7g8e/u1CwtOvJAikp3GjnIcijxf7s0bb9bJDWpKxgp+bLP+ImiUZ7c xUDg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=/Q7zkIynmbmjK4vZzAbop3V/2zsgh0f/TM8zDNDb2 ms=; b=eDpAfSyDoxJVryK6nDs387ZgFHfBQRF5+gHv2CmVpLODbAua4L3i4Hml+ W6OyfOXEHJ032EKpiODgivT+Gr7009S6C9A0lQQgw1YAu1vFsbEYJkL6T3BxO/WR l2hnsa1fe5ScirAagdVLs9pdNWa2Y/Gu4AM2iPDu0Rig2NfXFKKneWStB176XTpd YWNHX8t52V8Yp7+t1qca1dI01EDKq+HRFAVP8iOja4KNy0W2+LTomOPlVdfIpxhO wutxlGeU4XgPs5dLmD8KUX91DYGtG1bN1wM07wD192zPzUrkZitwNkYusxj/yqv6 BTz7ukDL/arho50IOE6BrfO8iCBMw==
X-ME-Sender: <xms:hAPRYGoSdgFb-JB5liWUFot2Pg9HQKFvCywRuk0ZqnHvsj41dK9E7Q> <xme:hAPRYEovf-G9fqjscGTarOmcB-XqeE2aJ62W4BJ8Frgg-ijmYn0KC69J06ME-uJCu TEOHsfq3Pd4exDvcVU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeefledgudehlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdfo rghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqne cuggftrfgrthhtvghrnhepgfejueduieffledtgeelheejvdettdejudduhefggeefgfek gfeuieetgefftddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:hAPRYLP2OwNY1qaEimoxxtJmNHhKsTtI7Z5LH5xe7hMV7BHuyo8HfA> <xmx:hAPRYF5IFCynvC79CBbRrG0GT6ZBoH1sGYFsW7EtHFVbNYPR_lgVgA> <xmx:hAPRYF4Ik3T5W4IdagNQK-3nBsdiCx1CED9l6N1ZSDolFqbCMGYvQQ> <xmx:hAPRYHTBfDpXnAAFodTKTfuK2mijOSptDLSrqGOAux5UHMn_YgKCmQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0C32F4E0095; Mon, 21 Jun 2021 17:24:20 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-530-gd0c265785f-fm-20210616.002-gd0c26578
Mime-Version: 1.0
Message-Id: <c5d775b8-cf23-4c63-8f94-463f5f0c88d8@www.fastmail.com>
In-Reply-To: <58D1243B-D7E0-431B-A124-22F1D3F581ED@ericsson.com>
References: <162392685980.9639.17048456192736231833@ietfa.amsl.com> <2335b22b-b98d-4e7f-8481-62c8b146c70f@www.fastmail.com> <58D1243B-D7E0-431B-A124-22F1D3F581ED@ericsson.com>
Date: Tue, 22 Jun 2021 07:23:59 +1000
From: Martin Thomson <mt@lowentropy.net>
To: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, The IESG <iesg@ietf.org>
Cc: "ohttp@ietf.org" <ohttp@ietf.org>, "ohttp-chairs@ietf.org" <ohttp-chairs@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/FlsFbzTJZvlEXv3dlviGRdwr_cM>
Subject: Re: [Ohttp] Zaheduzzaman Sarker's Block on charter-ietf-ohttp-00-00: (with BLOCK)
X-BeenThere: ohttp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Oblivious HTTP <ohttp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ohttp>, <mailto:ohttp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ohttp/>
List-Post: <mailto:ohttp@ietf.org>
List-Help: <mailto:ohttp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ohttp>, <mailto:ohttp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2021 21:24:29 -0000

Hi Zahed,

Trimming this.

On Fri, Jun 18, 2021, at 19:05, Zaheduzzaman Sarker wrote:
> [ZS] I am not looking for any details about the answers in the charter 
> rather clear statements on the fact that client is ultimately 
> responsible for creating request and putting information, here in the 
> working group we will only work on the method and encryption mechanisms 
> needed to provide a solution for the clients who don’t want to share 
> information with the server. I felt like this is not clearly stated in 
> the charter and that will let others think about the question I raised. 

I'm having trouble parsing the first sentence here.  Are you asking for text in the charter on how a client is expected to use this protocol?  As I said before, I don't believe that's appropriate for a charter, because generating the answer to that is the work of a working group.  How a client uses the protocol depends on the shape of the protocol.