IETF Logo Mail Archive

[dns-privacy] Status of implementations

Paul Hoffman <paul.hoffman@icann.org> Wed, 28 June 2023 01:38 UTC

Return-Path: <paul.hoffman@icann.org>
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 8C438C15155E for <dns-privacy@ietfa.amsl.com>; Tue, 27 Jun 2023 18:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNa7fLX6n8bj for <dns-privacy@ietfa.amsl.com>; Tue, 27 Jun 2023 18:38:51 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 1B37DC151092 for <dns-privacy@ietf.org>; Tue, 27 Jun 2023 18:38:51 -0700 (PDT)
Received: from MBX112-E2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.7]) by ppa2.lax.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 35S1coUo016861 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dns-privacy@ietf.org>; Wed, 28 Jun 2023 01:38:50 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.26; Tue, 27 Jun 2023 18:38:48 -0700
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.026; Tue, 27 Jun 2023 18:38:48 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
Thread-Topic: Status of implementations
Thread-Index: AQHZqWFJ143eriCXW0uOXeUfe18hGg==
Date: Wed, 28 Jun 2023 01:38:48 +0000
Message-ID: <6A128332-74F0-4D39-B952-69031DB4B53D@icann.org>
References: <abc2826b-9e2b-6cea-85f9-b2060408105b@innovationslab.net>
In-Reply-To: <abc2826b-9e2b-6cea-85f9-b2060408105b@innovationslab.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7A5F390C5BA5D147B560AF7B284546A6@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-06-27_16,2023-06-27_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/VfYSgTSsX8uePbWwTSsb3sqyLqE>
Subject: [dns-privacy] Status of implementations
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Addition of privacy to the DNS protocol <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, 28 Jun 2023 01:38:51 -0000

On Jun 26, 2023, at 8:20 AM, Brian Haberman <brian@innovationslab.net> wrote:
> 1. The authors verify that the implementations listed in Appendix A is up-to-date. The chairs will request that this list be retained in the published RFC.

This is that request for verification. The section in the current draft is:

=====
# Early Implementations

This appendix lists some of the implementations of the protocol as it finished working group last call in the DPRIVE Working Group.
This list reflects reporting from the DNS community.

- The Unbound resolver has initial experimental code paths to probe over DoT
- The Drink authoritative server supports DoT
- The check-soa tool can probe over DoT
- The Bleau tool can probe over DoT through RIPE Atlas probes
- The PowerDNS Recursor resolver can probe over DoT
- Nameservers for various DNS zones support DoT. These include the root zone (one of the 13 root server identifiers), a social media site, some DNS software developers, and others
=====

Can everyone who contributed to this list earlier please verify that their entry is (entries are) still correct? 

Are there other early implementations that we should add?

--Paul Hoffman

v2.23.0 | Report a Bug | By Email