Re: [DNSOP] Updated NSEC5 protocol spec and paper

Phillip Hallam-Baker <> Tue, 07 March 2017 15:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 225E6129640 for <>; Tue, 7 Mar 2017 07:54:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.368
X-Spam-Status: No, score=-2.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZdJ_yPpMzfP6 for <>; Tue, 7 Mar 2017 07:54:50 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5C5A612949B for <>; Tue, 7 Mar 2017 07:54:31 -0800 (PST)
Received: by with SMTP id h10so72743295ith.1 for <>; Tue, 07 Mar 2017 07:54:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2f54LUDSf6I9tlko0/Fw7hHpn9dW4dSOsp96vbSCz8U=; b=L5X++Xq8zo5FLNAjE+ORZxBfegzBcR+MxOkiAUKb8RXBiC7rFTL0u2mdyFM0wa+SeD bjL4tF1uFodt+1ER1vqKsrUemu71X1/JrKLSDAOfs0MRpQXOZsP/tzYIUGmlKHNptT9I PjRaDsOJNsKwVLowGSFFI40YvuVNwQbCyDTAvwGImp8r1NjXCZVxtTBc1Ya4n2rVXpX1 lC/659oP8vHBN0gjHLA00sB9r7yb51Bpb6kb6Hmmeb3HHqhAS5y8bgEzHSVIMWQwzLuI X1peEMSP8Xt6iwRjH3L3B8VGqUU3I9ye/E1Stp9khtnW0vCemLsjgfSj0jVLwiNLm9rv 2aMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2f54LUDSf6I9tlko0/Fw7hHpn9dW4dSOsp96vbSCz8U=; b=i9IP/JSUHN/gfkKoD2h/dSeL28/U+RCRTLLerLqYz+FA/EoIXRYFD9zwz5fRF0aHdd i8+DfWWHy4/0/nDd9Z8Io/07SwGJZk5uMu9V5+2BZjNVeRfc8Y03aDASabqiceCGBkZO 7jM5xEuqmvOsKnGdrgL1aeDs9pL9dTQO8G2sHHZ1MxV19C4f1QcxWNyR2txzSVEPQlfK Dg90dUTzmGbFAFVj6kZUx02owhG+BeZHVcL29sqfUvFOW9sz+tjyVF5uFrubunxRd6gC UqK0WH1nEwWYoK2X+d1lvMB+59+Thrh4C0P6ZKBgs5HAiTaSHnlvj0yTuRdpWfwGdG2K 4/bQ==
X-Gm-Message-State: AMke39lhEvmlhdYLjuhcShnkOto6gKg4xGolu4I+jQ66Y0e1p9/ur/P6Ul+e7VpoZDkScQj4Zqnjf3r/simmYA==
X-Received: by with SMTP id r129mr358292ybr.126.1488902070561; Tue, 07 Mar 2017 07:54:30 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 7 Mar 2017 07:54:30 -0800 (PST)
In-Reply-To: <>
References: <>
From: Phillip Hallam-Baker <>
Date: Tue, 07 Mar 2017 10:54:30 -0500
X-Google-Sender-Auth: jHo0AmHjkuUyvNy1y9_RMaaeLhk
Message-ID: <>
To: Shumon Huque <>
Content-Type: multipart/alternative; boundary="94eb2c13587c056fd7054a2607aa"
Archived-At: <>
Cc: " WG" <>
Subject: Re: [DNSOP] Updated NSEC5 protocol spec and paper
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 07 Mar 2017 15:54:56 -0000

There are two reasons for splitting out the VRF

1) It is a useful building block

2) The intersection between the people who really understand the VRF math
and really understand DNS is very small

I think most DNSOps folk will want to treat VRF as a black box and let the
crypto folk put what they think is right in it and many of the people we
need to review the VRF are not going to want a lesson on DNS or NSEC5 use
of it.

On Tue, Mar 7, 2017 at 10:29 AM, Shumon Huque <> wrote:

> Hi folks,
> We've requested an agenda slot at the DNSOP working group meeting at
> IETF98 to talk about the NSEC5 protocol. Our chairs have requested that
> we send out a note to the group ahead of time, so here it is.
> This protocol has not to our knowledge been presented at dnsop before,
> but has been discussed previously at other IETF venues, such as SAAG.
> Sharon Goldberg has recently presented NSEC5 to good reception at
> the following venues:
> 1) Real World Crypto conference, New York (Jan 2017)
> 2) IETF Boston Hub Meetup (Feb 2017)
> 3) DNS Privacy Workshop at NDSS'17 (Feb 2017)
> The latest NSEC5 protocol now supports elliptic curve cryptography,
> and uses verifiable random functions. The protocol has been implemented,
> and we have good performance results to share.
> There is a research paper, with many more details:
> The current draft for the NSEC5 spec is here:
> Some IETF security folk have recommended that we split out the VRF
> construction (currently described in the draft's appendix) into a
> separate draft, as it may be useful to other IETF protocols. We think
> that's a good idea and are working on it - we hope to have updated
> drafts before the IETF98 draft cutoff deadline.
> Hope to chat in person at IETF, and/or on the list.
> Shumon, Sharon, Dimitris, Jan, and Dave.
> _______________________________________________
> DNSOP mailing list