Re: [Ohttp] Robert Wilton's Block on charter-ietf-ohttp-00-00: (with BLOCK and COMMENT)
Eric Rescorla <ekr@rtfm.com> Wed, 16 June 2021 15:16 UTC
Return-Path: <ekr@rtfm.com>
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 D84843A1C32 for <ohttp@ietfa.amsl.com>; Wed, 16 Jun 2021 08:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.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 OBxdX_cd6rIN for <ohttp@ietfa.amsl.com>; Wed, 16 Jun 2021 08:16:43 -0700 (PDT)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 A3D3C3A1C34 for <ohttp@ietf.org>; Wed, 16 Jun 2021 08:16:43 -0700 (PDT)
Received: by mail-il1-x129.google.com with SMTP id h3so2635390ilc.9 for <ohttp@ietf.org>; Wed, 16 Jun 2021 08:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mxATCNZvs3T5N4qVC1Pk+bLL5z7KqgL6HTDnzlbvEdc=; b=FAD4wIezK0dWSDQSJZDP91umXgkwhIQ0Zs0SVf/L1LTiXOQYwuF6yoL+BLWSsluTKB N5HuTOZ22N5OuPRKMXnlcFU91tTTIu+xByJ9j/1vQjKYvXbT5ZgvoilEZs4g9tUZrLqc SAq86iqFOVTw2Z6l5jyA+Cyamd/1osXI6D4zS/6N1gV5DMcQ50VPiR+TSFrG2UJZRPWp hfhbuP0E8TVtqgD0VKMTBgO6NJ4Dm5duzFDQ3WEMfSFqTCrgmeXqc1lVSdAEy6SuOjij gzZ/b7cTLaVOMLyVnWJqNozSpTrKislFfdnzZSQPpoM4nENP1I4P8WHTg8Z+DEN2CoDf RvkQ==
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=mxATCNZvs3T5N4qVC1Pk+bLL5z7KqgL6HTDnzlbvEdc=; b=PV2hVaUthz3a/7AcULAWw5vdLW+9c/RxSAJWmAj9t1xUc/JLjEW3P/8s4K/hhfbldI s2cBhGgsBa1SfCbZgMfU5F2YVBTPlVdU7akc0gjguBA8kLyAlJsP3H6ucm/roG+ODwSD hjfOy2APvFbdw49FpslScqTEULQpM9IhSlpbBjtRodSdmSG8PZ3AxSyRGuT9AMb5X3LD y1BR8XHUPavS6tf2OlYLvKkLbvy0iY7hw5KMkc7nl1fkNnXCvXxU4gjfU3fk5fxR3x7+ BHbv6RCIlhzCMHVv9u+6oRvIHHEu3NkSS/a4F8BU/vb4A0tLF2XsepfGTaZjx16kcEWa x3eg==
X-Gm-Message-State: AOAM530BqZjA2U10CuCxlD+p7fEOnrJf8dXG5IsKf/KQygOUxWYsVB8m W8bcTsSTQjAlY+QdVXvd1ivncSaW74AeT2mDfCREEQ==
X-Google-Smtp-Source: ABdhPJz2SeXrKYexufz9byLw7Zb/aSD2mUrCe76t5jSwK3e3ZwFgokd2V795XGcMwRro5fVLWkLKMatw4WScFFmcK0I=
X-Received: by 2002:a92:c5a9:: with SMTP id r9mr140296ilt.56.1623856602150; Wed, 16 Jun 2021 08:16:42 -0700 (PDT)
MIME-Version: 1.0
References: <162385548488.11927.7128389725906160454@ietfa.amsl.com>
In-Reply-To: <162385548488.11927.7128389725906160454@ietfa.amsl.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 16 Jun 2021 08:16:06 -0700
Message-ID: <CABcZeBMNpBhW+te5mM-0FZBt9UWNe=NNobyUn06q5wxKaHgR7Q@mail.gmail.com>
To: Robert Wilton <rwilton@cisco.com>
Cc: The IESG <iesg@ietf.org>, ohttp@ietf.org, ohttp-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f0123a05c4e393ce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ohttp/cT2wWS6k0KqqWU1ioBr-zpU5npU>
Subject: Re: [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
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: Wed, 16 Jun 2021 15:16:48 -0000
> 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? Not just ODoH, but other things of that flavor. > 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? I would assume quite low, as there is essentially no processing by the proxy. Presumably approximately the same as a DND recursive resolver. Perhaps Apple has some data from their initial ODoH deployments. > - Who is creating/managing these proxies and what trust relationship does the > end user have to these proxies? See my response to Eric. > - 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. Maybe? But clients who want that service can not use this service. > - Is this technology encouraging more centralization of Internet services? No. -Ekr On Wed, Jun 16, 2021 at 7:58 AM Robert Wilton via Datatracker < noreply@ietf.org> wrote: > 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 mailing list > Ohttp@ietf.org > https://www.ietf.org/mailman/listinfo/ohttp >
- [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