Re: [dns-privacy] Why is draft-ietf-dprive-dtls-and-tls-profiles still blocked?
Daniel Kahn Gillmor <dkg@fifthhorseman.net> Fri, 27 October 2017 22:36 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 A589313F5F4 for <dns-privacy@ietfa.amsl.com>; Fri, 27 Oct 2017 15:36:05 -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 WLg6XpE1V2Pb for <dns-privacy@ietfa.amsl.com>; Fri, 27 Oct 2017 15:36:04 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by ietfa.amsl.com (Postfix) with ESMTP id 84AE11397F3 for <dns-privacy@ietf.org>; Fri, 27 Oct 2017 15:36:04 -0700 (PDT)
Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 5ED26F99A; Fri, 27 Oct 2017 18:36:03 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id AB86920453; Fri, 27 Oct 2017 18:35:50 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Brian Haberman <brian@innovationslab.net>, dns-privacy@ietf.org
In-Reply-To: <e2db3154-d7e9-ec9c-b2f6-c6daa966cc26@innovationslab.net>
References: <20171027125510.foq7xeiqft2vl7rx@nic.fr> <e2db3154-d7e9-ec9c-b2f6-c6daa966cc26@innovationslab.net>
Date: Fri, 27 Oct 2017 18:35:50 -0400
Message-ID: <87k1zgfcc9.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/5vCeg1dm3f1M2M5C4EDrshInBM4>
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: Fri, 27 Oct 2017 22:36:06 -0000
On Fri 2017-10-27 09:30:43 -0400, Brian Haberman wrote:
> Hi Stephane,
>
> On 10/27/17 8:55 AM, 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." 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?
>>
>
> There was discussions with EKR over his issues and a revision published.
> EKR asked for a review by DKG before he would clear his DISCUSS. We are
> waiting on that review.
my apologies. I'm going through that now and hope to post a review to
the list by tomorrow.
--dkg
- [dns-privacy] Why is draft-ietf-dprive-dtls-and-t… Stephane Bortzmeyer
- Re: [dns-privacy] Why is draft-ietf-dprive-dtls-a… Brian Haberman
- Re: [dns-privacy] Why is draft-ietf-dprive-dtls-a… Daniel Kahn Gillmor
- Re: [dns-privacy] Why is draft-ietf-dprive-dtls-a… Daniel Kahn Gillmor
- Re: [dns-privacy] Why is draft-ietf-dprive-dtls-a… Sara Dickinson