IETF Logo Mail Archive

Re: [dns-privacy] Root Server Operators Statement on DNS Encryption

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 31 March 2021 13:15 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 79E553A281F for <dns-privacy@ietfa.amsl.com>; Wed, 31 Mar 2021 06:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 kGO06ow1ASNB for <dns-privacy@ietfa.amsl.com>; Wed, 31 Mar 2021 06:15:43 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13EED3A2831 for <dns-privacy@ietf.org>; Wed, 31 Mar 2021 06:15:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4CFA2BE4C; Wed, 31 Mar 2021 14:15:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrzbVTUjm2zQ; Wed, 31 Mar 2021 14:15:34 +0100 (IST)
Received: from [10.244.2.242] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F0D18BE3E; Wed, 31 Mar 2021 14:15:33 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1617196534; bh=KZMraBUrXaSGK693TZO6IRpvJgCR0wyP+UOyDEmbGsY=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=gtqSKMEIk1bnPTa3FgJuwQqqPP0ElH+uVPChZQBtgAB+2jFrNl+4za58hUcEIb0xo eyecAMHNSQa5rI23oSYUHYwEAMApknplj+an6G/P6SKkMtecBo4eZ+8DxB3B27qbBc YnBn5pvb5ku1oIws9Xv0gW6m8KWr4Dmh4b23HqBk=
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, "jim@rfc1035.com" <jim@rfc1035.com>, "brian@innovationslab.net" <brian@innovationslab.net>
Cc: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
References: <c925da9089fa4b1e991ec74fc9c11e7f@verisign.com> <CAChr6Sxwao=FAcoeHMuOf0L=JCZ+wvhsr9BNZW_dbt+1=HWQwg@mail.gmail.com> <CAMGpriX5rbswMQnjh4gZqsLjh2xUJxjJVxe2rEAVu=RdLAbGFw@mail.gmail.com> <CABcZeBOntrAqq_bVL-y-BP0DZLvYmVMkvKqi8K0D_SFqAfCVXg@mail.gmail.com> <96c2475d-ad93-a442-2003-db6f8782e450@cs.tcd.ie> <CAMGpriXdU7_mJh8CQvSiZGQaDUD9aZF=0iYu0yKBS06khAHgng@mail.gmail.com> <4094551f-4b39-a996-f12f-8c5317c4fe21@nic.cz> <20210331092449.GD10597@nic.fr> <cefd04bf-8685-1894-ef3a-b61ce6a37167@innovationslab.net> <155BAF8D-9F65-4C5C-9EB1-58EFD70827B5@rfc1035.com> <c1ae3401-2565-016b-7acc-4891d0bde067@cs.tcd.ie> <a8eacd5988df461c9ec3c858dd426bb7@verisign.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <4d07508c-eb2a-3f48-4e4d-046e9a50dfc1@cs.tcd.ie>
Date: Wed, 31 Mar 2021 14:15:33 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <a8eacd5988df461c9ec3c858dd426bb7@verisign.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="PswOMHIYYMuERdnBoeFMXLAK5d3QP8hfn"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/SXqjJ1W1zo5w9emZe5g_ioBzQMk>
Subject: Re: [dns-privacy] Root Server Operators Statement on DNS Encryption
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: Wed, 31 Mar 2021 13:15:50 -0000


On 31/03/2021 14:00, Hollenbeck, Scott wrote:
>> -----Original Message-----
>> From: dns-privacy <dns-privacy-bounces@ietf.org> On Behalf Of Stephen
>> Farrell
>> Sent: Wednesday, March 31, 2021 8:58 AM
>> To: Jim Reid <jim@rfc1035.com>; Brian Haberman
>> <brian@innovationslab.net>
>> Cc: dns-privacy@ietf.org
>> Subject: [EXTERNAL] Re: [dns-privacy] Root Server Operators Statement on
>> DNS Encryption
>>
>>
>> Hiya,
>>
>> On 31/03/2021 13:52, Jim Reid wrote:
>>
>>> We all want better privacy of course. For some definition of privacy.
>>> But what does that actually mean in the context of queries to
>>> authoritative servers at the root or TLDs?
>>
>> Workable answers for the root and TLDs are likely very different, as the scale
>> of risk is very different.
>>
>> I think it doesn't really help to try discuss both root servers and TLDs at the
>> same time.
>>
>>> And is TLS the*only*  game
>>> in town?
>> When encrypting DNS based on some standard protocol? It is, though of
>> course you can have that DoT or DoH or DoQ or maybe even opaquely
>> flavoured;-(
> 
> [SAH] Why assume that encryption is required to provide confidentiality?

I didn't make that assumption.

S.

> 
> Scott
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy
>

v2.23.0 | Report a Bug | By Email