IETF Logo Mail Archive

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

Sara Dickinson <sara@sinodun.com> Wed, 01 November 2017 09:23 UTC

Return-Path: <sara@sinodun.com>
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 3E13713F5CC for <dns-privacy@ietfa.amsl.com>; Wed, 1 Nov 2017 02:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 U1Hbjo-npPIv for <dns-privacy@ietfa.amsl.com>; Wed, 1 Nov 2017 02:23:09 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 052DE13F4FA for <dns-privacy@ietf.org>; Wed, 1 Nov 2017 02:23:09 -0700 (PDT)
Received: from [2001:b98:204:102:fffa::14b4] (port=60786) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <sara@sinodun.com>) id 1e9pEp-0001BI-N6; Wed, 01 Nov 2017 09:23:07 +0000
From: Sara Dickinson <sara@sinodun.com>
Message-Id: <ACD012CD-F53A-4F4E-BD9D-8158AE223310@sinodun.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6673C1ED-63EE-4332-A989-7CCBEAB87910"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 01 Nov 2017 09:23:06 +0000
In-Reply-To: <87y3nsbqqz.fsf@fifthhorseman.net>
Cc: dns-privacy@ietf.org
To: Eric Rescorla <ekr@rtfm.com>
References: <20171027125510.foq7xeiqft2vl7rx@nic.fr> <87y3nsbqqz.fsf@fifthhorseman.net>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 13
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/mOqtnM8rTpllZcH8nYBt9YbzLms>
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: Wed, 01 Nov 2017 09:23:10 -0000

> On 30 Oct 2017, at 15:27, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
> 
> 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).

Hi Ekr,

Could you just confirm if version -11 addresses your DISCUSS?

Sara.

v2.23.0 | Report a Bug | By Email