IETF Logo Mail Archive

Re: [Add] What to do in this potential working group

"Patrik Fältström " <paf@frobbit.se> Thu, 22 August 2019 05:52 UTC

Return-Path: <paf@frobbit.se>
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 C0912120143 for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 22:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=frobbit.se
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 jG8fIxe8MCFh for <add@ietfa.amsl.com>; Wed, 21 Aug 2019 22:52:25 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6A9512006F for <add@ietf.org>; Wed, 21 Aug 2019 22:52:25 -0700 (PDT)
Received: from [169.254.213.39] (unknown [IPv6:2a01:3f0:1:0:9109:5e28:d24c:aca4]) by mail.frobbit.se (Postfix) with ESMTPSA id C59062150A; Thu, 22 Aug 2019 07:52:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=frobbit.se; s=mail; t=1566453141; bh=CUmZaAYLtHf/5JfcrN5HEp9LUdYK7NtdhD3zqWfBYCw=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ppztgDslFQdGWu6sc3b/Ry2+UphfDrSfKivroFj3mmSkTED1CgPyIdHXNjlmfwVGe hxZTq6qgh5Lqmg3WwuQpatxWm2kqrJ90Kjdh/6oaBHwGAMXwnNgw5t/6WUJjtkbhTj IloexSE1dxF9pOwEcSk4HbGe4nBpJCZoiF0S2cXg=
From: Patrik Fältström <paf@frobbit.se>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Jari Arkko <jari.arkko@piuha.net>, Eric Rescorla <ekr@rtfm.com>, ADD Mailing list <add@ietf.org>
Date: Thu, 22 Aug 2019 07:52:21 +0200
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <458B5AD2-D956-43B5-A0A3-28660BBDC6E2@frobbit.se>
In-Reply-To: <CA+9kkMAfuOwJu8_qJTuhAY4mUwR+tVUxr+k3QFHBk3byV672Ow@mail.gmail.com>
References: <A1128702-1E19-4657-9740-E84AE09992F2@piuha.net> <CABcZeBMfOTjq-8hDDoKMtJvfHUA5nC8o60zuk-2Xe-ZhfwriJQ@mail.gmail.com> <766112E1-F532-4C6B-8CA8-A096671E02EE@piuha.net> <CA+9kkMAfuOwJu8_qJTuhAY4mUwR+tVUxr+k3QFHBk3byV672Ow@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_37C3F551-1562-4B6B-A667-A7B967A9219D_="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/-XIMLtzr3O3G7KrZ8UsOICrl8Pg>
Subject: Re: [Add] What to do in this potential working group
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: Thu, 22 Aug 2019 05:52:28 -0000

On 21 Aug 2019, at 19:36, Ted Hardie wrote:

> The second threat model is that a resolver may provide an untrustworthy answer (e.g. captive portal). The use of DoT and DoH can help with this if the client device, application, or user selects a trustworthy resolver** and uses the TLS certificate to verify they have reached that service.

This is resolved by having DNSSEC validation in the client.

   Patrik

v2.23.0 | Report a Bug | By Email