Re: [DNSOP] draft-fujiwara-dnsop-delegation-information-signer

Mark Andrews <marka@isc.org> Thu, 05 November 2020 03:00 UTC

Return-Path: <marka@isc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB073A1641 for <dnsop@ietfa.amsl.com>; Wed, 4 Nov 2020 19:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 JV5mqe_o15it for <dnsop@ietfa.amsl.com>; Wed, 4 Nov 2020 19:00:34 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 A75183A163F for <dnsop@ietf.org>; Wed, 4 Nov 2020 19:00:34 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 404BB3AB0D8; Thu, 5 Nov 2020 03:00:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id E46D716006F; Thu, 5 Nov 2020 03:00:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D2988160044; Thu, 5 Nov 2020 03:00:33 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id vFSsdWX4oebH; Thu, 5 Nov 2020 03:00:33 +0000 (UTC)
Received: from [172.30.42.67] (n114-75-120-99.bla3.nsw.optusnet.com.au [114.75.120.99]) by zmx1.isc.org (Postfix) with ESMTPSA id 1846416006F; Thu, 5 Nov 2020 03:00:32 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
From: Mark Andrews <marka@isc.org>
In-Reply-To: <20201104.133137.359450294432060529.fujiwara@jprs.co.jp>
Date: Thu, 5 Nov 2020 14:00:30 +1100
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <484191FC-B161-4AC3-9A4A-538BEDA3BA6E@isc.org>
References: <20201104.133137.359450294432060529.fujiwara@jprs.co.jp>
To: fujiwara@jprs.co.jp
X-Mailer: Apple Mail (2.3445.9.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/uThEXLG4H9U6vgzZ0UjeLjDTJmM>
Subject: Re: [DNSOP] draft-fujiwara-dnsop-delegation-information-signer
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2020 03:00:36 -0000

One problem with DiS is that assumes that address records in the additional
section *always* come from the delegating zone (see how the hash is created).
This is not how DNS works.  Address records can, correctly, come from other
sources, even when the name is *below* the zone cut.

Take a server that serves example.net and sub.child.example.net.  That A record
comes from sub.child.example.net not example.net when the name of the server is
a.sub.example.net.

	child.example.net NS a.sub.example.net
	a.sub.example.net A 1.2.3.4

Mark

> On 4 Nov 2020, at 15:31, fujiwara@jprs.co.jp wrote:
> 
> I submitted draft-fujiwara-dnsop-delegation-information-signer-00.
> 
> Name:		draft-fujiwara-dnsop-delegation-information-signer
> Revision:	00
> Title:		Delegation Information (Referrals) Signer for DNSSEC
> Document date:	2020-11-03
> Group:		Individual Submission
> Pages:		6
> URL:            https://www.ietf.org/archive/id/draft-fujiwara-dnsop-delegation-information-signer-00.txt
> 
> DNSSEC does not have a function to validate delegation information.
> I think it is a large missing peace of DNSSEC.
> 
> I have a question why we did not include signature validation function
> to delegation information ?
> 
> Probably, because it is non-authoritative information.
> Or, because it was difficult to define the necessary and sufficient
> delegation information.
> 
> It is now widely agreed (although not explicitly documented) that the
> delegation information is the information used for name resolution and
> does not result in name resolution.
> 
> We have a word "in-domain" glue which is the necessary and sufficient glue.
> 
> And the idea may offer the signature for root priming data.
> 
> If someone interested the document, I would like time slot at dnsop WG
> meeting.
> 
> Regards,
> 
> --
> Kazunori Fujiwara, JPRS <fujiwara@jprs.co.jp>
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742              INTERNET: marka@isc.org