From nobody Thu Oct 8 16:46:26 2020 Return-Path: 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 1C5383A1024 for ; Thu, 8 Oct 2020 16:46:24 -0700 (PDT) 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 (1024-bit key) header.d=ethereum.org 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 ilZCUzIhbrQn for ; Thu, 8 Oct 2020 16:46:22 -0700 (PDT) Received: from mail-ot1-x32c.google.com (mail-ot1-x32c.google.com [IPv6:2607:f8b0:4864:20::32c]) (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 D13F43A1021 for ; Thu, 8 Oct 2020 16:46:22 -0700 (PDT) Received: by mail-ot1-x32c.google.com with SMTP id o8so7339894otl.4 for ; Thu, 08 Oct 2020 16:46:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethereum.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=tNMkybZsK5zYhg9FDAAWg20iLCfSJPB2azD5sCxVjlY=; b=Zol0bqHDesh5V+eKYRgno4HOjwk6dNDLAX7WLyl/p/NMQ6omE30UculyTxLczYADYv hgFneT4QplbsIWexVhpSMv/RYfsuk45pgUvTIiW7F1L9HTIRmVIrZU6BCQZlvmTG8yJv 82OK2Az7raUau7TPlhUuYXDLUug5seyIky7EQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=tNMkybZsK5zYhg9FDAAWg20iLCfSJPB2azD5sCxVjlY=; b=L3bkGmKwOyBpaSyqC+DBdYldNA9Kcs/xssZZXZJ03KLEWGIJJF9wHTsN3E5W9Ybe4J CH5+MKQZd1TiZL6fzvznplHCLVF4Ddn8VR/pbqWIUCQpr7xqDoPOm4TcQCLLC6nlZZEn Vus/VXr4zHZCm+PUdnbdVt/Zzdbt9swIYl1w7HSKXvStTFHITaBr3GCFGYAgCBQ6rJSq hWpAxugm3/lfjrNKa7SWvNhGRzn8CypJNWAkaT24Og5modB1wmlu57mtWeItSWXL24us 3AyQ/a04/aghebKMq8D/wnUIuA/L79lr6+DDB9E8cGDZQusRlGcAB/LciJ2NOdnCl1jl pzuw== X-Gm-Message-State: AOAM533Fqc3En1Nc569+Axg9gpevK14JKrR1lwFRCJ3RJWb+RHDhXRj6 bTKFqHBVNmwoPg0dCRVVgmbuDtGc7OFMvbj5M6OsMWlbVhWrUa0H X-Google-Smtp-Source: ABdhPJxry+vlgpkbq5IHMwJhTzBrgp7KIe6GdhSrL3XirkQjDmJoj/2HRe/31BCYUNKwCLTkBjcqqGFjSyk3ASXUHLM= X-Received: by 2002:a9d:5547:: with SMTP id h7mr6974718oti.248.1602200781677; Thu, 08 Oct 2020 16:46:21 -0700 (PDT) MIME-Version: 1.0 From: Nick Johnson Date: Fri, 9 Oct 2020 12:46:10 +1300 Message-ID: To: dnsop WG Content-Type: multipart/alternative; boundary="000000000000737ed605b13170d5" Archived-At: Subject: [DNSOP] What is the purpose of NSEC3 "closest encloser" proofs? X-BeenThere: dnsop@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IETF DNSOP WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Oct 2020 23:46:24 -0000 --000000000000737ed605b13170d5 Content-Type: text/plain; charset="UTF-8" I'm reading RFC 5155, and I'm a bit puzzled by the requirement for "closest encloser" proofs to prove nonexistence of a domain. Given that the RFC requires generating NSEC3 records on empty non-terminals, isn't it sufficient to examine a single NSEC3 record to prove nonexistence? For example, if I want to prove the nonexistence of a.b.c.example, isn't it sufficient to validate an NSEC3 record that covers that name and is one level higher (eg, somehash.b.c.example)? Why do I need to prove the closest-encloser with a second NSEC3 record? -Nick Johnson --000000000000737ed605b13170d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm reading RFC 5155, and I'm a bit puzzled b= y the requirement for "closest encloser" proofs to prove nonexist= ence of a domain. Given that the RFC requires generating NSEC3 records on e= mpty non-terminals, isn't it sufficient to examine a single NSEC3 recor= d to prove nonexistence?

For example, if I want to= prove the nonexistence of a.b.c.example, isn't it sufficient to valida= te an NSEC3 record that covers that name and is one level higher (eg, someh= ash.b.c.example)? Why do I need to prove the closest-encloser with a second= NSEC3 record?

-Nick Johnson
--000000000000737ed605b13170d5--