IETF Logo Mail Archive

Re: [dns-privacy] New: draft-bertola-bcp-doh-clients

Vittorio Bertola <vittorio.bertola@open-xchange.com> Mon, 11 March 2019 01:55 UTC

Return-Path: <vittorio.bertola@open-xchange.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 E3CAF130DFA for <dns-privacy@ietfa.amsl.com>; Sun, 10 Mar 2019 18:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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=open-xchange.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 mwFSidXqoj0C for <dns-privacy@ietfa.amsl.com>; Sun, 10 Mar 2019 18:55:41 -0700 (PDT)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (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 C9BB3130DE4 for <dns-privacy@ietf.org>; Sun, 10 Mar 2019 18:55:40 -0700 (PDT)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 278E76A273; Mon, 11 Mar 2019 02:55:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1552269338; bh=9/M0CkYl3TG16JZnhDX8DDCVxr0+djpJDUZGkjogTQk=; h=Date:From:To:In-Reply-To:References:Subject:From; b=6oQuemLMBL2tMsv9cAi1WkE3/ZVS0bMvZnkz4PDzgOUSCRcKnJ7cUKtkIdvxmnU7W PKu4andlO2UXnp5wU2XmBEEqDFi6frcamJtxCVAdYjsE07nsJV+XaqT0DqKRIxn1a2 u0pa5ih2rPbbGSYCfHtVBaDekc7Asv//SASPDdwmKE+UM51bpYhGITWk8wV3bHQd92 sTBWiuLFwtLXS0qlEVO+VkqD6o2lr4mVMywpPJuwrAWstgArYAmerMS8ZYddqpBeGq hRIT3Uz2WGT9x3YnwwzigMfh1FZprLoJle390L9DlOSyE3xVRL0cHX8MvuG79wORMz ZW69Jms2p4itA==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 1162E3C0734; Mon, 11 Mar 2019 02:55:38 +0100 (CET)
Date: Mon, 11 Mar 2019 02:55:33 +0100
From: Vittorio Bertola <vittorio.bertola@open-xchange.com>
To: Christian Huitema <huitema@huitema.net>, dns-privacy@ietf.org
Message-ID: <1246760431.12827.1552269338008@appsuite.open-xchange.com>
In-Reply-To: <eea64b30-aad0-a030-5360-1b1484f1d0e3@huitema.net>
References: <1700920918.12557.1552229700654@appsuite.open-xchange.com> <7667c4d7-2e78-0a27-84af-cf1c00fd4897@cs.tcd.ie> <1991054337.12802.1552259263075@appsuite.open-xchange.com> <eea64b30-aad0-a030-5360-1b1484f1d0e3@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.1-Rev9
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/Kcs3Ge1HeNlnADlPyEiKfoPNQrA>
Subject: Re: [dns-privacy] New: draft-bertola-bcp-doh-clients
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: Mon, 11 Mar 2019 01:55:43 -0000

> Il 11 marzo 2019 alle 2.05 Christian Huitema <huitema@huitema.net> ha scritto:
> 
> crypto of TLS 1.3. Similarly, putting DNS in user space allows for
> immediate adoption of DNSSEC and privacy enhancements, even when the
> operating system or the local network does not support them. That genie
> is not going back in the bottle any time soon.

I am not necessarily arguing against that, but moving DNS to the application layer breaks a lot of stuff and creates a lot of new problems. So if we want to do it to reap the benefits, we should also make sure to have a plan to address the shortcomings, and this is the discussion that several people, including myself, are trying to have.

Regards,
-- 

Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
vittorio.bertola@open-xchange.com
Office @ Via Treviso 12, 10144 Torino, Italy

v2.23.0 | Report a Bug | By Email