IETF Logo Mail Archive

Re: [dns-privacy] [Ext] DS Hacks

Ilari Liusvaara <ilariliusvaara@welho.com> Fri, 06 August 2021 18:43 UTC

Return-Path: <ilariliusvaara@welho.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 5928C3A0FE7 for <dns-privacy@ietfa.amsl.com>; Fri, 6 Aug 2021 11:43:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 qp2MgCiDL8SB for <dns-privacy@ietfa.amsl.com>; Fri, 6 Aug 2021 11:43:40 -0700 (PDT)
Received: from welho-filter4.welho.com (welho-filter4b.welho.com [83.102.41.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B2D83A0FE5 for <dns-privacy@ietf.org>; Fri, 6 Aug 2021 11:43:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by welho-filter4.welho.com (Postfix) with ESMTP id B461767BC7 for <dns-privacy@ietf.org>; Fri, 6 Aug 2021 21:43:37 +0300 (EEST)
X-Virus-Scanned: Debian amavisd-new at pp.htv.fi
Received: from welho-smtp3.welho.com ([IPv6:::ffff:83.102.41.86]) by localhost (welho-filter4.welho.com [::ffff:83.102.41.26]) (amavisd-new, port 10024) with ESMTP id jg0cqtZg9dbb for <dns-privacy@ietf.org>; Fri, 6 Aug 2021 21:43:37 +0300 (EEST)
Received: from LK-Perkele-VII2 (87-92-216-160.rev.dnainternet.fi [87.92.216.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by welho-smtp3.welho.com (Postfix) with ESMTPSA id 6978D2323 for <dns-privacy@ietf.org>; Fri, 6 Aug 2021 21:43:36 +0300 (EEST)
Date: Fri, 06 Aug 2021 21:43:36 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: DNS Privacy Working Group <dns-privacy@ietf.org>
Message-ID: <YQ2C2IA/TQ5wXdQ/@LK-Perkele-VII2.locald>
References: <CAHbrMsAXFiPT_P_hdWXborXnbw3YagjW6aXXvGJnxWbtRofB2g@mail.gmail.com> <5f649d68-94be-579a-31c6-6ad02466cd15@time-travellers.org> <CAHbrMsCj8LzJff7BXwnY4TOcOU2POuZfP4h+fyA6VUKeGpksCQ@mail.gmail.com> <E0430A84-D844-4B79-B71F-A92A21942329@icann.org> <CAHbrMsCPPq-o8U4mhFPZ1U+GE+57yneEGo7AD5uDQ_QDDUO0rw@mail.gmail.com> <03FDA925-2BC3-4830-B27B-5F6E19676678@icann.org> <CAPp9mxJM1b4+OFHX0x6QwhoJpE+8Sz82K_e=DJ9EJFaK691_3Q@mail.gmail.com> <4AE29BBE-9B29-4E89-93CF-14153B25FD5C@icann.org> <CAHbrMsBQ88mKx-FLU0KT8W-AGyi=3HS3f5nuSO93-TOo_HTyNw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CAHbrMsBQ88mKx-FLU0KT8W-AGyi=3HS3f5nuSO93-TOo_HTyNw@mail.gmail.com>
Sender: ilariliusvaara@welho.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/dBon9SVC4QRSe_JHVZ5Dbt9FyzE>
Subject: Re: [dns-privacy] [Ext] DS Hacks
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Addition of privacy to the DNS protocol <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, 06 Aug 2021 18:43:46 -0000

On Fri, Aug 06, 2021 at 11:21:35AM -0400, Ben Schwartz wrote:
> Hi DPRIVE.  I've written this up as a proper I-D at
> https://datatracker.ietf.org/doc/html/draft-schwartz-ds-glue-00.  Please
> review.
> 
> In addition to the precise description of how to extend "DS" in this way,
> there's also some text explaining how this interacts with DANE and PKI
> authentication, making creative use of NSEC for performance.

I am confused about the NSEC parts. 

- Usually NSEC lists the next name and present types for current name.
- In this draft, it seems to be  list of types that are not present.
- In this draft, I do not see any explanation on how the name in the
  NSEC record should be set. In the examples, it seems to be the set
  to full owner name.
- The draft mentions NSEC3 too, but as far as I can see, no
  explanation or examples of its use.



-Ilari

v2.23.0 | Report a Bug | By Email