IETF Logo Mail Archive

Re: [dns-privacy] Why is draft-ietf-dprive-dtls-and-tls-profiles still blocked?

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Mon, 30 October 2017 15:33 UTC

Return-Path: <dkg@fifthhorseman.net>
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 800D61B0002 for <dns-privacy@ietfa.amsl.com>; Mon, 30 Oct 2017 08:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 b7XwW0nt5QHx for <dns-privacy@ietfa.amsl.com>; Mon, 30 Oct 2017 08:33:35 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by ietfa.amsl.com (Postfix) with ESMTP id E75601FE009 for <dns-privacy@ietf.org>; Mon, 30 Oct 2017 08:27:26 -0700 (PDT)
Received: from fifthhorseman.net (p578E653F.dip0.t-ipconnect.de [87.142.101.63]) by che.mayfirst.org (Postfix) with ESMTPSA id 5FC9EF99A; Mon, 30 Oct 2017 11:27:26 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id B58C42063B; Mon, 30 Oct 2017 16:27:19 +0100 (CET)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, dns-privacy@ietf.org
In-Reply-To: <20171027125510.foq7xeiqft2vl7rx@nic.fr>
References: <20171027125510.foq7xeiqft2vl7rx@nic.fr>
Date: Mon, 30 Oct 2017 16:27:16 +0100
Message-ID: <87y3nsbqqz.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/VkRnfmIfQm2erJDc5mgKFP0wf3Q>
Subject: Re: [dns-privacy] Why is draft-ietf-dprive-dtls-and-tls-profiles still blocked?
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.22
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, 30 Oct 2017 15:33:37 -0000

On Fri 2017-10-27 15:55:10 +0200, Stephane Bortzmeyer wrote:
> The datatracker tells us that draft-ietf-dprive-dtls-and-tls-profiles
> has a DISCUSS "This needs to be updated to indicate that the client
> MUST NOT offer 7250 unless it has a preconfigured SPKI, otherwise
> you're going to have interop problems."

I agree that this DISCUSS should be cleared, since draft-10 and draft-11
both state:

    A client MUST only indicate support for raw public keys if it has an
    SPKI pinset pre-configured (for interoperability reasons).

Regards,

    --dkg

v2.23.0 | Report a Bug | By Email