IETF Logo Mail Archive

Re: [Add] meeting hum: should the IETF take up this work?

Eric Rescorla <ekr@rtfm.com> Wed, 24 July 2019 13:33 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4242120384 for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 06:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20150623.gappssmtp.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 nIbIzcN8HRgc for <add@ietfa.amsl.com>; Wed, 24 Jul 2019 06:33:40 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25776120376 for <add@ietf.org>; Wed, 24 Jul 2019 06:33:40 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id z15so27701359lfh.13 for <add@ietf.org>; Wed, 24 Jul 2019 06:33:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5SmeJ/vUjQWA+H9L8hzVJfjiPbUJsdq6ONZL3bXTYG0=; b=fvMTNwVlScC+mpqI3h0BtOI0GijYgK3Mcb1r5JwvVnOzxjruumf9yrbwBB7bNFUSnz NTGddi01QUQU4oicdX837nPsdhahguGO3dtNVPxqRqqN2XNCzBZor8kYyiZ/6L9f4sF7 ff5gx8TLdYhJ5WAdvI0gsec3cTZS+jpGuo8ngHNvQs3cU4gJvbF74A0wRDNcQTEkiROS qINSQ81sYPGHdNElfjbsynE56Do1u3PVDBcFgvp5/++q36hjiQx348cBREl8DsvoKMZn BM9pOsCDWVOoMIPwL302xLpmU6e9u8i4MFAf0VvvV3mRtutdWWnCJ8Ii67HIh7JQGtRK P0Ww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5SmeJ/vUjQWA+H9L8hzVJfjiPbUJsdq6ONZL3bXTYG0=; b=lFJVQbR40d1bY/yS2dFuTxqwUcrW7gnmgW8dC/TDomrUpM/93X4LZbNv6908THKsQg xmS+omrg+BUc/bhR68CnjX5Mo5RCNxvl5Hif7ajF0lvD5fOqufo28Q7XuxhkIan3YzT5 Dm9vLwV/6gnuA5V5jv7s9nZJXL9dXGsUGBP2Tluk9KbkLS42kqfucGv48FmuDsm+yJN1 W5l46gwVhbjDWHmybx9sC00bW9GrbzbbIvDDPmDnX43G2rPqwiTQ61BTd1wuZsuoXpdB lpRv8TBIkIGkF6dNKXZQZquB/Ct4LT9PRE6ixPZb5HVzBa12lY46STDLzJ1x4KIBsVUz GHrA==
X-Gm-Message-State: APjAAAV7K+LvnXbugobe+AedN75p+uRBBELhtCuyEqtSVh+dRy6ZRrA3 D+thk3sskJRbcVHWISrvmno8tyPABuc/azrTcfk=
X-Google-Smtp-Source: APXvYqwjgyoiimyUYzwCGdoB7rIoPiz5WxNGIQyaG18mgn+gpt0COQuR9mcEykDgmk/yghG55reSZ5woB5hnICy5d3Y=
X-Received: by 2002:ac2:4202:: with SMTP id y2mr4064366lfh.178.1563975218411; Wed, 24 Jul 2019 06:33:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6Sx9TEt6CMzRRrdb-HwT_k987oW=4yF1FCbDF17zkaE2Vg@mail.gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E23910C@GAALPA1MSGUSRBF.ITServices.sbc.com> <CAChr6SwLZgjkCNDqbR1ZiJvxAiK77_Pv0-tXyTMjZZkHZAsBYg@mail.gmail.com> <475222798.24238.1563974435834@appsuite-gw1.open-xchange.com>
In-Reply-To: <475222798.24238.1563974435834@appsuite-gw1.open-xchange.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 24 Jul 2019 06:33:02 -0700
Message-ID: <CABcZeBO1uJTEVs=V6CMO3SoX85TvTSuiYtmAK=kV2m1R+u2fbg@mail.gmail.com>
To: Vittorio Bertola <vittorio.bertola@open-xchange.com>
Cc: Rob Sayre <sayrer@gmail.com>, "add@ietf.org" <add@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000054cd09058e6d5bd6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/2a3tFEQfiEw5wfRIN-cmpM5DY3w>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2019 13:33:48 -0000

On Wed, Jul 24, 2019 at 6:21 AM Vittorio Bertola <vittorio.bertola=
40open-xchange.com@dmarc.ietf.org> wrote:

>
> Il 24 luglio 2019 00:58 Rob Sayre <sayrer@gmail.com> ha scritto:
>
> The bottom line is this: the IETF has been unable to secure DNS in a
> successful way for 31 years. I think people are losing patience.
>
> Well, if the Web and OTT industry is "losing patience" about a presumed
> lack of security in DNS, perhaps they could start by actually deploying
> DNSSEC and DANE in browsers, in their big email platforms and the likes,
> isn't it?
>

As I indicated in a previous message: DNSSEC does not address a number of
the security issues that we are concerned with. DANE is an orthogonal issue.

-Ekr


> Rather than on a blame game, I think it would be much better if we could
> focus on imagining how the DNS should work in the future and be a great
> naming system for the 21st century. Both DNSSEC and encrypted transport are
> part of this, and possibly other pieces that still need to be developed,
> such as a way to discover and negotiate policies between the client and the
> network.
>
> --
>
> Vittorio Bertola | Head of Policy & Innovation, Open-Xchange
> vittorio.bertola@open-xchange.com
> Office @ Via Treviso 12, 10144 Torino, Italy
>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>

v2.23.0 | Report a Bug | By Email