[Ohttp] Robert Wilton's Block on charter-ietf-ohttp-00-00: (with BLOCK and COMMENT)
Robert Wilton via Datatracker <noreply@ietf.org> Wed, 16 June 2021 14:58 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ohttp@ietf.org
Delivered-To: ohttp@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 901873A1BA2; Wed, 16 Jun 2021 07:58:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: ohttp-chairs@ietf.org, ohttp@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.32.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <162385548488.11927.7128389725906160454@ietfa.amsl.com>
Date: Wed, 16 Jun 2021 07:58:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/XGVxAAGRQ6pC_2HdXRv5kg7ss14>
Subject: [Ohttp] Robert Wilton's Block on charter-ietf-ohttp-00-00: (with BLOCK and COMMENT)
X-BeenThere: ohttp@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 16 Jun 2021 14:58:06 -0000
Robert Wilton has entered the following ballot position for charter-ietf-ohttp-00-00: Block When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-ohttp/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- I support Eric's discuss position that it would be helpful to hold a BOF before chartering the WG to ensure that opinions have been heard and considered from all areas. I also find the scope of the charter to be somewhat unclear. Specifically, it isn't really clear to me whether the aim of this work is really for a generic oblivious HTTP mechanism to hide clients from servers, or whether it is really intended to be a point solution to support oblivious DNS over DoH? Some other points that a BOF could consider (particularly if this work is mostly focused on Oblivious DNS over DoH): - What it the latency performance overhead of introducing the proxies given the large number of DNS queries and given that they are performance sensitive to the end user experience? - Who is creating/managing these proxies and what trust relationship does the end user have to these proxies? - Do proxies impact the ability to do "malware detection as a service"? I.e., are there scenarios where the profiling of DNS requests coming from a particular source address is helpful for clients. - Is this technology encouraging more centralization of Internet services? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Should a discovery mechanism be in scope, if not in the initial work for this working group, as a secondary objective?
- [Ohttp] Robert Wilton's Block on charter-ietf-oht… Robert Wilton via Datatracker
- Re: [Ohttp] Robert Wilton's Block on charter-ietf… Eric Rescorla
- Re: [Ohttp] Robert Wilton's Block on charter-ietf… Christopher Wood