Re: [Ohttp] Meaning of "usage constraints" in charter
Thomas Mangin <thomas.mangin@exa.net.uk> Tue, 27 July 2021 20:43 UTC
Return-Path: <thomas.mangin@exa.net.uk>
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 E922A3A11F0 for <ohttp@ietfa.amsl.com>; Tue, 27 Jul 2021 13:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=exa-net-uk.20150623.gappssmtp.com
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 M26qjXQZXiFd for <ohttp@ietfa.amsl.com>; Tue, 27 Jul 2021 13:43:52 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E55E43A1236 for <ohttp@ietf.org>; Tue, 27 Jul 2021 13:43:51 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id x7so308407ljn.10 for <ohttp@ietf.org>; Tue, 27 Jul 2021 13:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=exa-net-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=KWuXv2oH4Eiog6ZawrM2QQjU+r4TJDpf8kTXb34kQk4=; b=nEVSgy8ChfG2Ub14lqQ0p/MB9Nq4VwidxLDM7INIbO4PjLckr5KJ0tzqpXyv2o3zMc xCP/aYd2h7BgxHIAdBYRZY/bc32rlBq521oM7FdasGYtJKMmpFaLkzLDY1hEGpL9q8Wx 9JtD6JuJERb9iZaOA7QIOHPgQ4oYb1n0qalmiTKSyidFKW1MKI/53JgidGwHg7qoVC6v cqMDMjsmiXYUc3i8DugunZeUKMItV/n1qt737BlB3AXry59rMrRMQ4SPc1tL2v0rOac4 bmXEK1p3exKzjQBcC3hBY2T1ag/CgEkVKl2qJN+pD2DqkeOZ9JeRyqmZjksbvswYcp9W 9QSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=KWuXv2oH4Eiog6ZawrM2QQjU+r4TJDpf8kTXb34kQk4=; b=aTSTYsJktaYMN2OlzEG7AfdrnZYhD/FhhSLRmDtJw8XXWZEPyupwdU5YB1tU4/y4k8 MOlaLCyRPTh3PtYVMn/T3HsRACucADRVpE3oTkGtH5RdRVDxwERyWG3m88RUv1FxZLiz Z4gZl08DNaHZXb+qsv1/yQB4XBLe0zHS6y+GPfM1AeIs0hkLAgSIETktI+cvQbHr1NWK aWDAaovGaCRjW+8ZWTWJCZu0mCyVDL4Pun/6roZfxQHybbAMpz7JAien1prcFJAGcshq +yZh8bApZRL4zFFbPjvOwf17e6YG7bv7cSbtxBjXXL8WNXQIVLszOjH85gbLUU2zd49+ KVAQ==
X-Gm-Message-State: AOAM532ITty6c+Hjy1hwMDere5ZivcNNQgJNJ6zZY1VEx6THsJK3WwA7 hvYwdtYIu9nGI0pldzU31qlIdXxRCP/0tuYiHWQTuFppOlu8Tw==
X-Google-Smtp-Source: ABdhPJzm5GKA6uTYmsR5DaQMUuxf7vcI8DEDJ471oCPOKkArH5FKO5/U6f4y+pOcv8wHAzmK/tpwpPm8Gb7U1YFCaPs=
X-Received: by 2002:a05:651c:906:: with SMTP id e6mr16472372ljq.385.1627418628135; Tue, 27 Jul 2021 13:43:48 -0700 (PDT)
MIME-Version: 1.0
References: <HE1PR0702MB37721B3DC9958D6FECAC24A595E99@HE1PR0702MB3772.eurprd07.prod.outlook.com> <164791655.178472.1627390180052@appsuite-gw1.open-xchange.com>
In-Reply-To: <164791655.178472.1627390180052@appsuite-gw1.open-xchange.com>
From: Thomas Mangin <thomas.mangin@exa.net.uk>
Date: Tue, 27 Jul 2021 21:43:37 +0100
Message-ID: <CAEm8Q12iFmFqsyPo_GuGtA8OtyNfHZ815Ly9ZNpUAc=SVXd-ZQ@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola=40open-xchange.com@dmarc.ietf.org>
Cc: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "ohttp@ietf.org" <ohttp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003b321a05c820ed08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/6hhczolYvS_owJxNKtSmWXal5VM>
Subject: Re: [Ohttp] Meaning of "usage constraints" in charter
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: Tue, 27 Jul 2021 20:44:02 -0000
On Tue, 27 Jul 2021 at 13:49, Vittorio Bertola <vittorio.bertola= 40open-xchange.com@dmarc.ietf.org> wrote: > I am still not convinced that this makes sense, as one would expect that > once the protocol is published it will be deployed in many other ways which > will bear significant policy and operational impacts, and so these impacts > should be discussed since the beginning. But it's just my opinion. > I very much second your opinion. It does not matter what the draft/RFC says the use cases are or should be. Once it is documented, it can be implemented and used in other ways. So any "restrictions" in the document is going to be very much advisory, at best. Brave implemented IPFS, search engine, they may decide to run their own proxies and make all traffic OHTTP, no one could stop them. This is why if we want to give users control of who they want to trust as proxies, there should be a way for them to detect and select who they trust to protect their privacy. Thomas
- [Ohttp] Meaning of "usage constraints" in charter Magnus Westerlund
- Re: [Ohttp] Meaning of "usage constraints" in cha… Vittorio Bertola
- Re: [Ohttp] Meaning of "usage constraints" in cha… Andrew Campling
- Re: [Ohttp] Meaning of "usage constraints" in cha… Thomas Mangin
- Re: [Ohttp] Meaning of "usage constraints" in cha… Mark Nottingham