Re: [dnsext] [Technical Errata Reported] RFC5155 (4622)
Ben Laurie <ben@links.org> Sat, 20 February 2016 20:43 UTC
Return-Path: <benlaurie@gmail.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 220261ACE6E for <dnsext@ietfa.amsl.com>; Sat, 20 Feb 2016 12:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 8PbfFFu-5Mvm for <dnsext@ietfa.amsl.com>; Sat, 20 Feb 2016 12:43:07 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 9AE741ACE69 for <dnsext@ietf.org>; Sat, 20 Feb 2016 12:43:06 -0800 (PST)
Received: by mail-lb0-x233.google.com with SMTP id x4so64695039lbm.0 for <dnsext@ietf.org>; Sat, 20 Feb 2016 12:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=otzgXNRG906BbIIVvwnZK9yw0BqJSOvRkou0qz9TGVQ=; b=tAYud1SVZZ/EM6LO62ffd/7hF/n8IR3CMy04qqptiJFcOktLT+2CA+devCEHWNkezX sbrSkUYyAlFVnCHWmDBm9/imQiMiVvyrvD89KWStJjmbjypMisAq0RzeCPgQJ2N15P36 z8TOEW9hd1Tcwqjr8ni2HWNYW+sqPpZRxx0njfpwjeueTkOeCQdD7qJbuDyBw9l6RIaW zQeHadck8iluQH8qm+fQ06ZDiOagQsksOpbthrwQRqakc7fuM+2q1DxWgfGWA1wXSi/d HHvNQunYcbFyFRHRZvusJqUIQ/7ti9nexxcFl366/j4wBouGfyRU38WlVoukMvkfR55b UBIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=otzgXNRG906BbIIVvwnZK9yw0BqJSOvRkou0qz9TGVQ=; b=gim/ZmAnr8K1qa+00w9Zr4r4Iune0/tUXQVT5Jp2x1X5f/qm17sKVEn4FKJ95SD5pN z6UqpQ19aPgljGYuUZLUNqERFTTKYV9nRs25Ll26a8+zawWeKniZluOfAkV1sr0NW/eV JphV9tyjdw+ln3URY6i8NEeXS2oz0XpZ8z3DG+rC+3gUbVuW2RhQk4inDWjMCf/q604S //OUXt3eWV1V2Rrt8Yew+sSR9gsQHRV+Wbad3xyUjHIwZuaVuLyQiF6YmOW+aHT8DqF5 Bv9HMNEyC+M8cWjd/C+kS5Q97lSUPaPeT1IJY4eMXWGLmahpbNYwoUthbo9Le9jyn3jj redw==
X-Gm-Message-State: AG10YOSKIVmP2ydcu/PT7s/xuGJqHaBrUKJeMVL9dlWKUg5HVa5N3+e/pMPM5e+VM8yjF+MaP5sKXZRfh/eKjQ==
MIME-Version: 1.0
X-Received: by 10.112.14.39 with SMTP id m7mr7668031lbc.20.1456000984824; Sat, 20 Feb 2016 12:43:04 -0800 (PST)
Sender: benlaurie@gmail.com
Received: by 10.112.20.226 with HTTP; Sat, 20 Feb 2016 12:43:04 -0800 (PST)
In-Reply-To: <354ECEF6-49FA-4819-8FA5-9F9AC9116B0A@verisign.com>
References: <20160218013620.0ABC6180209@rfc-editor.org> <56C7309D.8080603@innovationslab.net> <354ECEF6-49FA-4819-8FA5-9F9AC9116B0A@verisign.com>
Date: Sat, 20 Feb 2016 20:43:04 +0000
X-Google-Sender-Auth: stSJqSgy3kJYvp0PwBi32_-Z-NE
Message-ID: <CAG5KPzySL64MJw5RsRMzgTcAorWkmB=zHpuNwpKt65wO2izLKg@mail.gmail.com>
From: Ben Laurie <ben@links.org>
To: "Blacka, David" <davidb@verisign.com>
Content-Type: multipart/alternative; boundary="001a11c3726a7e4545052c39a5af"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsext/Nlw3EB0hyt-AHeCULPqgzrzTymY>
Cc: Brian Haberman <brian@innovationslab.net>, "geoff-s@panix.com" <geoff-s@panix.com>, "dnsext@ietf.org" <dnsext@ietf.org>, Ólafur Gu∂mundsson <ogud@ogud.com>
Subject: Re: [dnsext] [Technical Errata Reported] RFC5155 (4622)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsext/>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Feb 2016 20:43:10 -0000
Me, too, though it could be more economically expressed as "no _other_ RR types exist...". On 19 February 2016 at 16:37, Blacka, David <davidb@verisign.com> wrote: > > > On Feb 19, 2016, at 10:11 AM, Brian Haberman <brian@innovationslab.net> > wrote: > > > > Does anyone have an opinion on the validity of this erratum? It seems > > like a reasonable clarification in my reading. > > The clarification looks correct and reasonable to me. > > > > > Brian > > > > On 2/17/16 8:36 PM, RFC Errata System wrote: > >> The following errata report has been submitted for RFC5155, > >> "DNS Security (DNSSEC) Hashed Authenticated Denial of Existence". > >> > >> -------------------------------------- > >> You may review the report below and at: > >> http://www.rfc-editor.org/errata_search.php?rfc=5155&eid=4622 > >> > >> -------------------------------------- > >> Type: Technical > >> Reported by: Robert Edmonds <edmonds@mycre.ws> > >> > >> Section: 7.2.8 > >> > >> Original Text > >> ------------- > >> 7.2.8. Responding to Queries for NSEC3 Owner Names > >> > >> The owner names of NSEC3 RRs are not represented in the NSEC3 RR > >> chain like other owner names. As a result, each NSEC3 owner name is > >> covered by another NSEC3 RR, effectively negating the existence of > >> the NSEC3 RR. This is a paradox, since the existence of an NSEC3 RR > >> can be proven by its RRSIG RRSet. > >> > >> If the following conditions are all true: > >> > >> o the QNAME equals the owner name of an existing NSEC3 RR, and > >> > >> o no RR types exist at the QNAME, nor at any descendant of QNAME, > >> > >> then the response MUST be constructed as a Name Error response > >> (Section 7.2.2). Or, in other words, the authoritative name server > >> will act as if the owner name of the NSEC3 RR did not exist. > >> > >> > >> Corrected Text > >> -------------- > >> 7.2.8. Responding to Queries for NSEC3 Owner Names > >> > >> The owner names of NSEC3 RRs are not represented in the NSEC3 RR > >> chain like other owner names. As a result, each NSEC3 owner name is > >> covered by another NSEC3 RR, effectively negating the existence of > >> the NSEC3 RR. This is a paradox, since the existence of an NSEC3 RR > >> can be proven by its RRSIG RRSet. > >> > >> If the following conditions are all true: > >> > >> o the QNAME equals the owner name of an existing NSEC3 RR, and > >> > >> o no RR types exist at the QNAME besides NSEC3, nor at any > >> descendant of QNAME, > >> > >> then the response MUST be constructed as a Name Error response > >> (Section 7.2.2). Or, in other words, the authoritative name server > >> will act as if the owner name of the NSEC3 RR did not exist. > >> > >> > >> Notes > >> ----- > >> If the QNAME is equal to the owner name of an existing NSEC3 RR, then > the NSEC3 RR type itself will exist at the QNAME, and the second condition > will always be false. > >> > >> Instructions: > >> ------------- > >> This erratum is currently posted as "Reported". If necessary, please > >> use "Reply All" to discuss whether it should be verified or > >> rejected. When a decision is reached, the verifying party (IESG) > >> can log in to change the status and edit the report, if necessary. > >> > >> -------------------------------------- > >> RFC5155 (draft-ietf-dnsext-nsec3-13) > >> -------------------------------------- > >> Title : DNS Security (DNSSEC) Hashed Authenticated Denial > of Existence > >> Publication Date : March 2008 > >> Author(s) : B. Laurie, G. Sisson, R. Arends, D. Blacka > >> Category : PROPOSED STANDARD > >> Source : DNS Extensions > >> Area : Internet > >> Stream : IETF > >> Verifying Party : IESG > >> > > > > -- > David Blacka <davidb@verisign.com> > Distinguished Engineer Verisign Product Engineering > > > > > >
- [dnsext] [Technical Errata Reported] RFC5155 (462… RFC Errata System
- Re: [dnsext] [Technical Errata Reported] RFC5155 … Brian Haberman
- Re: [dnsext] [Technical Errata Reported] RFC5155 … Blacka, David
- [dnsext] [Errata Verified] RFC5155 (4622) RFC Errata System
- Re: [dnsext] [Technical Errata Reported] RFC5155 … Paul Hoffman
- Re: [dnsext] [Technical Errata Reported] RFC5155 … Ben Laurie