IETF Logo Mail Archive

Re: [dns-privacy] [Ext] Re: ADoT requirements for authentication?

Jim Reid <jim@rfc1035.com> Thu, 31 October 2019 19:07 UTC

Return-Path: <jim@rfc1035.com>
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 54417120958 for <dns-privacy@ietfa.amsl.com>; Thu, 31 Oct 2019 12:07:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 aukUvhfujtQI for <dns-privacy@ietfa.amsl.com>; Thu, 31 Oct 2019 12:07:16 -0700 (PDT)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 377B312094F for <dns-privacy@ietf.org>; Thu, 31 Oct 2019 12:07:14 -0700 (PDT)
Received: from dhcp-221-71.meetings.nanog.org (dhcp-221-71.meetings.nanog.org [199.187.221.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by shaun.rfc1035.com (Postfix) with ESMTPSA id A06E6242141F; Thu, 31 Oct 2019 19:07:12 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jim Reid <jim@rfc1035.com>
In-Reply-To: <20191031012141.899B3DAE626@ary.qy>
Date: Thu, 31 Oct 2019 19:07:12 +0000
Cc: dns-privacy@ietf.org, watsonbladd@gmail.com
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A4469D0-9529-431D-B18C-99A1298FB8E8@rfc1035.com>
References: <20191031012141.899B3DAE626@ary.qy>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/qrdRBQGvifIuJI1vJRNVm1-I53g>
Subject: Re: [dns-privacy] [Ext] Re: ADoT requirements for authentication?
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, 31 Oct 2019 19:07:17 -0000


> On 31 Oct 2019, at 01:21, John Levine <johnl@taugh.com> wrote:
> 
> In article <CACsn0c=6Kv5j0SKJkTLxSNSPoz_uA62p1vTjWx=ccVJbnv4f7A@mail.gmail.com> you write:
>> Encryption at the root is very possible.
> 
> Indeed, but that's not the same question as whether it's a good idea.

+1

> 
> ...
> Let's put this in the pile of things to think about later.

+1 to that too.

v2.23.0 | Report a Bug | By Email