Re: [Doh] panel discussion on DoH/DoC

Ted Lemon <mellon@fugue.com> Thu, 07 February 2019 12:55 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D519E12D4F2 for <doh@ietfa.amsl.com>; Thu, 7 Feb 2019 04:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.041
X-Spam-Level:
X-Spam-Status: No, score=-2.041 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=fugue-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 fiBpnpds0k2m for <doh@ietfa.amsl.com>; Thu, 7 Feb 2019 04:55:51 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 4706B126C7E for <doh@ietf.org>; Thu, 7 Feb 2019 04:55:51 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id e5so11677789qtr.12 for <doh@ietf.org>; Thu, 07 Feb 2019 04:55:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=mT8JQuf5UgITjcnom93fh6WWM0SJf3jXYg/NLPLY5PY=; b=XscjMWhi3qUYyennn2X7PILd1rLi+ynWJJ0WHTGO3+KLT/qWTxAbXd1jso+3o82n+n OKM7v9UnKN0Nt1dzn+mvruN/EdTEWqaMQyHjrJD4PTb2luiSMaBUBbyLUsVgR6I8um1J lvx5px6LWUT5xC6WGkqmPeNrbc3p6mK3o2eKuHrRzqHM8bghYfEd8ZCMKiiWTef0Ycmx +L1i5NIngmp3A0u5+SDlww7/Y07+T/YZuXH7hL5Jldn7JcI0UkHZ/mOMKKP+OhEGZ/RF hYo9JihkM/Z2d1VersgLhMNan2JebIrhzX8o+nEwBWa1KCmaDHoWKCtOa1rCpoiGk0XL jeAQ==
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=mT8JQuf5UgITjcnom93fh6WWM0SJf3jXYg/NLPLY5PY=; b=HaWiox1dGlXh2ZDiPtr8/HYqrdzQ7AgyQmVaYiI8VbHthqo309GtqNQaEMItTxKsum SyKL1DhS8Bm/nf6GUImhwgKVPW6uIBU5rsgpVu6NlFeqqIv6NtyzubkjKoGZUV4aFCHc +lnjHpwKRlfyvUpa2hvMZjqkNp/sDOOCSr0TByxFpsYR4i62DAOYm9S88B8Fkb7J3Ynn B+BZj9K07apX0qqXq+6gh69ZZlgPdpATiFgEjSDR2f/sT6aU9hOCZBAwbLFZ4yiRJA2Q E/XMiHgAyW82xkHSZYq64OyipG8gdYgLY8/VZmI+38yC/kmZlXq/UMjLY3Sr2WnaCfyg xfSw==
X-Gm-Message-State: AHQUAuZWC7KrrA++x5XwALEvJPYdJLNHZVK+LQI2HERNdz+jof/zFw8t TN4h1bOu0EDPe4MVNBsMnHHJ7YcwJlI=
X-Google-Smtp-Source: AHgI3Ib7Vj/8m1/eTx3sDjMp2uGKtZkT7NgsvzGMRx3AlG/ZVjyJCZVvfGwq6FvMgqIrLBFYgDtKiA==
X-Received: by 2002:ac8:7518:: with SMTP id u24mr11927445qtq.75.1549544150444; Thu, 07 Feb 2019 04:55:50 -0800 (PST)
Received: from [10.0.100.12] (c-73-186-137-119.hsd1.nh.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id x202sm23390978qka.67.2019.02.07.04.55.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 04:55:49 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C7C3BAF7-4BD4-4EE2-B3F2-1F8B49222980@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4B3906A5-F753-4B41-B992-9090D4A6FBE2"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Thu, 07 Feb 2019 07:55:46 -0500
In-Reply-To: <20190207105106.GB1772@server.ds9a.nl>
Cc: doh@ietf.org
To: bert hubert <bert.hubert@powerdns.com>
References: <20190207105106.GB1772@server.ds9a.nl>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/hcFfgZ6rrhskWHAD0uLrX8lRXuk>
Subject: Re: [Doh] panel discussion on DoH/DoC
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2019 12:55:53 -0000

On Feb 7, 2019, at 5:51 AM, bert hubert <bert.hubert@powerdns.com> wrote:
> For further discussions, if someone is venting on DoC but calling it DoH, we
> can point out that they should not direct their anger at the poor DoH
> protocol that can't help what people do with it.

You could get into a really big fight with the HRPC folks about this statement.   DoH is perfectly designed to support the DoC use case, so doesn’t that mean that it effectively _is_ DoC?   It’s only _not_ DoC if there’s some way to prevent it from being DoC, and there isn’t.    So you might as well own it.