Re: [TLS] Draft updates: tls-dnssec-chain

Viktor Dukhovni <ietf-dane@dukhovni.org> Sat, 28 April 2018 18:51 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602591272E1 for <tls@ietfa.amsl.com>; Sat, 28 Apr 2018 11:51:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 p49RBAjxIiAK for <tls@ietfa.amsl.com>; Sat, 28 Apr 2018 11:51:22 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8885B127241 for <tls@ietf.org>; Sat, 28 Apr 2018 11:51:22 -0700 (PDT)
Received: from [192.168.1.161] (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 133027A3309 for <tls@ietf.org>; Sat, 28 Apr 2018 18:51:21 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <alpine.LRH.2.21.1804281422130.11560@bofh.nohats.ca>
Date: Sat, 28 Apr 2018 14:51:18 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: TLS WG <tls@ietf.org>
Message-Id: <52DD3AEA-B1A5-43AB-8BC5-3CA0F1879672@dukhovni.org>
References: <CAHPuVdW4kJQ5-mhCGR9BW6dDaN25Lv_Dsr9ygoNwrDsC=c7vuA@mail.gmail.com> <alpine.LRH.2.21.1804281422130.11560@bofh.nohats.ca>
To: TLS WG <tls@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/vp_gL7dKUqGfgC_Xtz95xANDFoI>
Subject: Re: [TLS] Draft updates: tls-dnssec-chain
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Apr 2018 18:51:24 -0000


> On Apr 28, 2018, at 2:34 PM, Paul Wouters <paul@nohats.ca> wrote:
> 
> But more importantly, it does not specify what the extension content
> should be in the absense of a signed TLSA record and not wanting to
> put in the denial of existene. Are you expecting an empty payload?
> A single NULL payload? Or are you expecting the extension should be
> omitted entirely? And what is the expected client behaviour in that case?

The first commit in my pull-request provides a more complete description
of DoE processing.

  https://github.com/tlswg/dnssec-chain-extension/pull/14/commits/859b164a5369e8c997713711771cfb3f7d87c90a#diff-bcaaf747fc40b8dd4fe4e10917b518f2L370

Don't know whether the authors have had a chance to take a look.
The present text is IMHO still a bit too skimpy as you note:

  https://github.com/tlswg/dnssec-chain-extension/blob/master/draft-ietf-tls-dnssec-chain-extension-08.xml

-- 
	Viktor.