MIME-Version: 1.0
Sender: hallam@gmail.com
In-Reply-To: <CAHPuVdXTcSaVcN6fBbPy3e=PgRvg8=GemSN_YFhzX387x8YW-A@mail.gmail.com>
References: <CAHPuVdXTcSaVcN6fBbPy3e=PgRvg8=GemSN_YFhzX387x8YW-A@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 7 Mar 2017 10:54:30 -0500
Message-ID: <CAMm+Lwhk9pkV5SVNNHPH0fUeA9zkpE7cJJ5k04xPEKiDTKF-mQ@mail.gmail.com>
To: Shumon Huque <shuque@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c13587c056fd7054a2607aa
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/r8glFv89nVwi82qM-T-rsrwbbUI>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Subject: Re: [DNSOP] Updated NSEC5 protocol spec and paper
Precedence: list

--94eb2c13587c056fd7054a2607aa
Content-Type: text/plain; charset=UTF-8

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 <shuque@gmail.com> 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:
>
>     https://eprint.iacr.org/2017/099.pdf
>
> The current draft for the NSEC5 spec is here:
>
>     https://tools.ietf.org/html/draft-vcelak-nsec5-04
>
> 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
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>

--94eb2c13587c056fd7054a2607aa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">The=
re are two reasons for splitting out the VRF</div><div class=3D"gmail_defau=
lt" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">1) It is a useful building block</div><div class=3D"gm=
ail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-size:small">2) The intersection between the people who rea=
lly understand the VRF math and really understand DNS is very small</div><d=
iv class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">I think most DNSOps folk will =
want to treat VRF as a black box and let the crypto folk put what they thin=
k is right in it and many of the people we need to review the VRF are not g=
oing to want a lesson on DNS or NSEC5 use of it.</div><div class=3D"gmail_d=
efault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-size:small"><br></div></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">On Tue, Mar 7, 2017 at 10:29 AM, Shumon Huque <span =
dir=3D"ltr">&lt;<a href=3D"mailto:shuque@gmail.com" target=3D"_blank">shuqu=
e@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div di=
r=3D"ltr"><div>Hi folks,</div><div><br></div><div>We&#39;ve requested an ag=
enda slot at the DNSOP working group meeting at</div><div>IETF98 to talk ab=
out the NSEC5 protocol. Our chairs have requested that=C2=A0</div><div>we s=
end out a note to the group ahead of time, so here it is.</div><div><br></d=
iv><div>This protocol has not to our knowledge been presented at dnsop befo=
re,</div><div>but has been discussed previously at other IETF venues, such =
as SAAG.</div><div><br></div><div>Sharon Goldberg has recently presented NS=
EC5 to good reception at</div><div>the following venues:</div><div><br></di=
v><div>1) Real World Crypto conference, New York (Jan 2017)</div><div>2) IE=
TF Boston Hub Meetup (Feb 2017)</div><div>3) DNS Privacy Workshop at NDSS&#=
39;17 (Feb 2017)</div><div><br></div><div>The latest NSEC5 protocol now sup=
ports elliptic curve cryptography,</div><div>and uses verifiable random fun=
ctions. The protocol has been implemented,</div><div>and we have good perfo=
rmance results to share.</div><div><br></div><div>There is a research paper=
, with many more details:</div><div><br></div><div>=C2=A0 =C2=A0 <a href=3D=
"https://eprint.iacr.org/2017/099.pdf" target=3D"_blank">https://eprint.iac=
r.org/2017/<wbr>099.pdf</a></div><div><br></div><div>The current draft for =
the NSEC5 spec is here:</div><div><br></div><div>=C2=A0 =C2=A0 <a href=3D"h=
ttps://tools.ietf.org/html/draft-vcelak-nsec5-04" target=3D"_blank">https:/=
/tools.ietf.org/html/<wbr>draft-vcelak-nsec5-04</a></div><div><br></div><di=
v>Some IETF security folk have recommended that we split out the VRF</div><=
div>construction (currently described in the draft&#39;s appendix) into a</=
div><div>separate draft, as it may be useful to other IETF protocols. We th=
ink</div><div>that&#39;s a good idea and are working on it - we hope to hav=
e updated</div><div>drafts before the IETF98 draft cutoff deadline.</div><d=
iv><br></div><div>Hope to chat in person at IETF, and/or on the list.</div>=
<div><br></div><div>Shumon, Sharon, Dimitris, Jan, and Dave.</div><div><br>=
</div></div>
<br>______________________________<wbr>_________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnsop</a><br>
<br></blockquote></div><br></div>

--94eb2c13587c056fd7054a2607aa--