IETF Logo Mail Archive

Re: [dns-privacy] Second Working Group Last Call for draft-ietf-dprive-bcp-op

Christoph <cm@appliedprivacy.net> Thu, 07 November 2019 00:17 UTC

Return-Path: <cm@appliedprivacy.net>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D511412004A for <dns-privacy@ietfa.amsl.com>; Wed, 6 Nov 2019 16:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=appliedprivacy.net header.b=AwdWNeDf; dkim=pass (2048-bit key) header.d=appliedprivacy.net header.b=tC2nrfHd
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 kHeJIYnW1sJ0 for <dns-privacy@ietfa.amsl.com>; Wed, 6 Nov 2019 16:17:27 -0800 (PST)
Received: from mout-p-202.mailbox.org (mout-p-202.mailbox.org [80.241.56.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76A0A120025 for <dns-privacy@ietf.org>; Wed, 6 Nov 2019 16:17:27 -0800 (PST)
Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:105:465:1:2:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mout-p-202.mailbox.org (Postfix) with ESMTPS id 477kVr4l8RzQlB2 for <dns-privacy@ietf.org>; Thu, 7 Nov 2019 01:17:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= appliedprivacy.net; h=content-transfer-encoding:content-language :content-type:content-type:in-reply-to:mime-version:date:date :message-id:from:from:references:subject:subject:received; s= v20171117; t=1573085841; bh=VIcOL7aWkCaVFPnj6SB85H8dFDWimI3vvMu7 NFuwcPc=; b=AwdWNeDf1RnyAb+c07DGciiv6ouZbq3hZNftAS1brDlKYExf1ev9 ptmu5j1PprjLI6ZwK5I8ARxByi0C6Bip8Z+MEfvPXQvmcynJT+JwsL9FsPo1bcP9 PzbLQ1RhXnnO+sTM00xqJxM6SSSxD0x2oWOBHL0mgcmh9v7ajBaqG2n6mWJd9tuR 0Qyj5K9O12xKM8suifAKQda1R+JJCCj35jGJmDr1H+BWq9FSrk43x+Tb5q46RxuN jAS63DrWzeBdwF4+vUBKDkAXXuO4ljnPJtTIwIpSjwdELclT9bi4aO4u5d6eaErJ TCE8UTU+bTDZx/kL/z2tzpUyugd+6nNxPw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=appliedprivacy.net; s=v20171117; t=1573085842; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uZT6BF0P1SYgEiYDYovWqzvGfDk+viawuxsfsTnbJ0k=; b=tC2nrfHdLxsdLE6CpXFHcDoz5u0BR9dHf0lqlxGCnb7uXtCyD7oZayU8X0Tyx8DV6FaR3O cu24LkSixc6wIhaK3rTz8bCwq3QuWlu/H+UaO3Fb12dJ2t5rlTxWA4pZUJ7kZDAA10yRF1 S/KvR+5UxIwUP3CJq5IYHCucLeweTCyz5IjZPnFCB7kXaWMJPWQJ8at1yPFbNRClXCfPvi kV7xpWV5hV5M4McNkzFyolhbreFJSCnuOOWNPHbvgQEFb9h0Ho9v5TLZqWGdDLoEnTb7o5 VCIGILF0yRLKa08hb0UPtlfyc2c5dlZ9oGivT655ckBsi8NNeLrYK5d1lUd/fQ==
X-Virus-Scanned: amavisd-new at heinlein-support.de
Received: from smtp2.mailbox.org ([80.241.60.241]) by spamfilter05.heinlein-hosting.de (spamfilter05.heinlein-hosting.de [80.241.56.123]) (amavisd-new, port 10030) with ESMTP id QpEXYX9TfZ1f for <dns-privacy@ietf.org>; Thu, 7 Nov 2019 01:17:21 +0100 (CET)
References: <CADyWQ+GirqA_VKYTAjGpV+aFMQiio2AAqtMX_2SRg45Crpf_-A@mail.gmail.com> <20191101103831.GA22563@sources.org>
From: Christoph <cm@appliedprivacy.net>
To: dns-privacy@ietf.org
Message-ID: <f2bac009-8828-0ce6-ca7a-18acb3c88d12@appliedprivacy.net>
Date: Thu, 07 Nov 2019 00:17:00 +0000
MIME-Version: 1.0
In-Reply-To: <20191101103831.GA22563@sources.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/9UCzMX8LWr3FnErJdbMfV7aqtfs>
Subject: Re: [dns-privacy] Second Working Group Last Call for draft-ietf-dprive-bcp-op
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2019 00:17:30 -0000

Stephane Bortzmeyer wrote:> * "A DNS privacy service must be engineered
for high availability."
> I'm not in favor of this sentence. 1) It seems to despise small 
> resolvers managed by small organisations, while we need many diverse 
> DoT and DoH resolvers, to avoid centralisation 2) Today, Firefox, 
> unfortunately, does not allow to add more than one DoH resolver,
> which makes the DoH resolver a very critical resource. But I hope
> that in the future, we will be able to configure several resolvers,
> with an efficient fallback, making the issue of availability less
> important.

I second that.

> “A DNS privacy service should strive to engineer encrypted services
> to the same availability level as any unencrypted services they
> provide.”?

Sounds good to me.

> * DROP is not a perfect acronym 
+1
maybe "DROPS"?

> "be held only memory"

"in memory.."


kind regards,
Christoph

v2.23.0 | Report a Bug | By Email