IETF Logo Mail Archive

Re: [dns-privacy] [Ext] Authentication in draft-ietf-dprive-opportunistic-adotq

Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 16 February 2021 16:28 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 981043A0AFB for <dns-privacy@ietfa.amsl.com>; Tue, 16 Feb 2021 08:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 rN0h762D8hDX for <dns-privacy@ietfa.amsl.com>; Tue, 16 Feb 2021 08:28:48 -0800 (PST)
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 5FFB43A0AFA for <dprive@ietf.org>; Tue, 16 Feb 2021 08:28:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1462CBE2E; Tue, 16 Feb 2021 16:28:46 +0000 (GMT)
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 wecR0VgmO3at; Tue, 16 Feb 2021 16:28:44 +0000 (GMT)
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 47C15BE2C; Tue, 16 Feb 2021 16:28:44 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1613492924; bh=BjxyuVzbDLlX0FGLkjuHkzOh8EtlpabnylB511GziZE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=dGNhO3aXvmd+KdPv+9q3hIzOLt/gJiJGdLH2EQyAGFKm/Zy+JiPuo5mzmFMSAPXLG Uz7+X6uH5AvM9x6X9e2JnlAlPT3sFfNnmu+eKN/SMY4yXztYec1/Zl+cxZ6cQmdd4/ NFzc8tYellPIUL5+X+zG+0OiaeX7dKiyiH1tM0pc=
To: Paul Hoffman <paul.hoffman@icann.org>, Ben Schwartz <bemasc=40google.com@dmarc.ietf.org>
Cc: "dprive@ietf.org" <dprive@ietf.org>
References: <230F580F-BA87-4921-B45B-2909ACE385B1@icann.org> <CAHbrMsCOrS7Kz9WSKXRwwFiueaGZD1EGyuy98zi=9Qo5x3vTBw@mail.gmail.com> <9B911C9E-B93E-437C-B928-B77166669444@icann.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <66aea918-b7d6-8e71-84fd-a37e307ffa23@cs.tcd.ie>
Date: Tue, 16 Feb 2021 16:28:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <9B911C9E-B93E-437C-B928-B77166669444@icann.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="nzKOmDfYEmuR59FG9o95HrvniX2YXIsFq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/o78PP4usVh_605DIQtHANFCtSlo>
Subject: Re: [dns-privacy] [Ext] Authentication in draft-ietf-dprive-opportunistic-adotq
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: Tue, 16 Feb 2021 16:28:51 -0000

Hiya,

On 16/02/2021 15:41, Paul Hoffman wrote:
> That seems fine. (Well, "self-issued" is the proper term, and we'd
> have to elaborate a bit on how to do that, but yes). This also works
> well with PaulW's prooposed sentinel.
I think I maybe said it before (sorry if this is a repeat)
but I'm against recommending self-issued certs. Even if
we're only aiming for oppo, we shouldn't be making it hard
to transition to auth if/when that becomes an option and
encouraging certs with expiry in 2038 does exactly that,
even if that's not what's intended. A "SHOULD" there is
just a bad idea.

S.

v2.23.0 | Report a Bug | By Email