IETF Logo Mail Archive

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

Bob Harold <rharolde@umich.edu> Wed, 04 November 2020 16:10 UTC

Return-Path: <rharolde@umich.edu>
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 97F913A1324 for <dnsop@ietfa.amsl.com>; Wed, 4 Nov 2020 08:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.edu
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 hnpBksfwbQwA for <dnsop@ietfa.amsl.com>; Wed, 4 Nov 2020 08:10:57 -0800 (PST)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 1D6C13A1322 for <dnsop@ietf.org>; Wed, 4 Nov 2020 08:10:57 -0800 (PST)
Received: by mail-qt1-x82c.google.com with SMTP id c5so12555908qtw.3 for <dnsop@ietf.org>; Wed, 04 Nov 2020 08:10:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Zt2GB28PofwqL3XATNbvSncWlqfyVycSW1EwUajayWk=; b=Q+l/1nI6kCmN1GIciDzGJjmv0Y6nAL1miepO1Ydt6MK1UGjW5zTH+9tgocv5azUDII SKRYx7r+APzZ/a4tRl3H0+JBEKLt/IE8iTdr8W5yzSqByVXvY8l0fksewxs2uIkqny3D TgUvxwdvCPW24IzVXrssEwaNfHxmqHSI9W/Qn4qVTddVglqtI/CvTdA3jtRznGtehaMu ujC0X7FvgM4GmBlHEWsJLCFpr/ohgwISzcrF0xi3EQWjCG6cv2qgPYFtfrY6nXTcwSPN SG/4F7Xfm3xtg1q0LfK0y3/G4SjMffrehQo9QX1cKIUgm+z3QP60m7BweQIvejhrChc7 utUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Zt2GB28PofwqL3XATNbvSncWlqfyVycSW1EwUajayWk=; b=uaezF1TOB9Lj3X/Cpe+L10bHzh4Dtj1/rAHf/OVshBDQ2X1SCRfq+NBbmm5qN4L7qA f7JjjYxHj7ZYP3G5Gl3n/srsV2f2SMnG2fViFQGY5c8I7K9AmCjI0YAkg+yCfhjC5sQY HATJF0GsUIzL137jh7bihLdyDDUbgYuFr4NPyIqEItAiB6cWCs4rIn6ly0C3qXTWw1ol I0yYJKNk5Qdyq7e1uUOUYMRlxCuLBwtKnb0U8j3sWSphQlc/9+Z6x11qo8y0tjcyoBbj KcHoS+Dr5CNkojE9pjFT0a18SKmK+ikT1dc5AoCsQmnnex0wm6ZXjtImGfV8ickaOXl9 pigQ==
X-Gm-Message-State: AOAM533b9IEDr8lHbLalwedxYsSNQ6rSFqV2fzsG99U2iBbpKlAD6oJY zBOzXmqHh0jZF2jNJ2Vk7UoG4rAs4gpNT5bRyQtVO5AYVXM=
X-Google-Smtp-Source: ABdhPJwAAopbEmlPBY01LVz2wcwRif8jbrRygdwu5FDBJK+5hPaRXaQVCj0JSJlw2jiNjEXbAkHjBWauCLoqxWtd+zA=
X-Received: by 2002:aed:22ab:: with SMTP id p40mr20110589qtc.200.1604506256115; Wed, 04 Nov 2020 08:10:56 -0800 (PST)
MIME-Version: 1.0
References: <20201104.133137.359450294432060529.fujiwara@jprs.co.jp>
In-Reply-To: <20201104.133137.359450294432060529.fujiwara@jprs.co.jp>
From: Bob Harold <rharolde@umich.edu>
Date: Wed, 04 Nov 2020 11:10:45 -0500
Message-ID: <CA+nkc8D_6vrdH7dkgqfdDKq+prGjDAsUUd+bcFgj+sH7oJhHRg@mail.gmail.com>
To: fujiwara@jprs.co.jp
Cc: IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006f9cac05b34a39b9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/8YYsdwliDBgkpFl5iiSo_R9xkrE>
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: Wed, 04 Nov 2020 16:10:59 -0000

If an attacker is spoofing responses, it seems that they could send a
different NS and A record, and a new calculated DS hash.  So this provides
no protection against spoofing?

We would need instead (or in addition) an RRSIG record to actually protect
this.

An example would help.

-- 
Bob Harold
DNS and DHCP Hostmaster - UMNet
Information and Technology Services (ITS)
rharolde@umich.edu   734-512-7038


On Tue, Nov 3, 2020 at 11:31 PM <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
>

v2.23.0 | Report a Bug | By Email