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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 27 October 2017 12:55 UTC

Return-Path: <bortzmeyer@nic.fr>
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 C614B13F444 for <dns-privacy@ietfa.amsl.com>; Fri, 27 Oct 2017 05:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.001
X-Spam-Level:
X-Spam-Status: No, score=-5.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5] 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 CLsmy42sCP1y for <dns-privacy@ietfa.amsl.com>; Fri, 27 Oct 2017 05:55:12 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 07EA71394E4 for <dns-privacy@ietf.org>; Fri, 27 Oct 2017 05:55:12 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 39507281DB3 for <dns-privacy@ietf.org>; Fri, 27 Oct 2017 14:55:10 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 3461E281DB8; Fri, 27 Oct 2017 14:55:10 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 2DC4E281DB3 for <dns-privacy@ietf.org>; Fri, 27 Oct 2017 14:55:10 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 2A97F642A7A1 for <dns-privacy@ietf.org>; Fri, 27 Oct 2017 14:55:10 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 24474409F5; Fri, 27 Oct 2017 14:55:10 +0200 (CEST)
Date: Fri, 27 Oct 2017 14:55:10 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: dns-privacy@ietf.org
Message-ID: <20171027125510.foq7xeiqft2vl7rx@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 9.1
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.062261, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.10.27.124217
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/y1GRl1WoqqJoRqTNxGPGNLDNPk0>
Subject: [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: Fri, 27 Oct 2017 12:55:14 -0000

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." The DISCUSS was against -09,
the current version is -11 (1.5 months old) which does address the
problem "A client MUST only indicate support for raw public keys if it
has an SPKI pinset pre-configured (for interoperability reasons)."

Therefore, what's the problem with
draft-ietf-dprive-dtls-and-tls-profiles?