Re: [Secdispatch] Request a short agenda slot for draft-eastlake-fnv-18.txt

Hi Martin,

On Tue, Jul 12, 2022 at 10:57 PM Martin Thomson <mt@lowentropy.net> wrote:
>
> I took a look at FNV when Google's QUIC proposal included it.  At the time, it wasn't the best option around, but also performed pretty well (I think Adam Langley picked it for QUIC and he tends to be careful about this stuff).
>
> Even then, there were tons of alternatives.  murmur3, CityHash, xxHash, FarmHash, and many more provide better performance, better random distribution, or other relevant properties.

I agree there are lots of hash functions. It seems to me that which is
"best" is a complex question depending on the application and lots of
other factors. I am NOT proposing any effort to answer such a
question, just the documentation of FNV.

> I don't see this as a standardization effort as much as an effort to ensure that stuff we use is properly written down.

Right. This is NOT proposed for Standards Track, just for Informational.

> At the time, FNV was specified on a short web page in a very loose fashion.  The ISE might be interested in taking a document like this, but I don't see the IETF adding much value here.

The RFC ISE stream is a possibility but I think going through the IETF
would provide a better review.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

> On Wed, Jul 13, 2022, at 11:09, Donald Eastlake wrote:
> > Hi,
> >
> > I request a brief time slot at the upcoming SECDISPATCH meeting. Here
> > are the questions from the wiki with answers:
> >  * pointers to a draft(s) :
> > https://www.ietf.org/archive/id/draft-eastlake-fnv-18.txt
> >  * pointers to ongoing/prior discussions: there have been various
> > discussions at various times on different IETF WG mailing lists
> > including at least the dnsop, tls, and trill WGs.
> >  * pointers to implementations: There are many implementations as
> > mentioned in the draft and at
> > http://www.isthe.com/chongo/tech/comp/fnv/index.html
> >  * pointers to any other background materials:
> > https://en.wikipedia.org/wiki/Fowler%E2%80%93Noll%E2%80%93Vo_hash_function
> >  * summarizing prior engagement with existing WGs: Well, FNV is
> > specifically used in RFC 7357 (TRILL: ESADI) and RFC 7873 (DNS Cookies)
> > and IEEE Std 802.1Qbp-2014 and is proposed to be used in
> > draft-ietf-bfd-secure-sequence-numbers-09.
> >  * summarizing who would want to advance this work: anyone wanting a
> > stable document reference or code for FNV
> >  * desired next steps: A decision by SECDISPATCH as to whether this
> > draft should be AD sponsored or handled on the SECDISPATCH mailing list
> > or referred to a WG or whatever.
> >  * desired time for discussion: I believe 5 or 6 minutes should be
> > adequate.
> > Thanks,
> > Donald
> > ===============================
> >  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >  2386 Panoramic Circle, Apopka, FL 32703 USA
> >  d3e3e3@gmail.com
> >
> > ---------- Forwarded message ---------
> > From: <internet-drafts@ietf.org>
> > Date: Mon, Jul 11, 2022 at 7:53 PM
> >
> > A new version of I-D, draft-eastlake-fnv-18.txt
> > has been successfully submitted by Donald Eastlake and posted to the
> > IETF repository.
> >
> > Name:           draft-eastlake-fnv
> > Revision:       18
> > Title:          The FNV Non-Cryptographic Hash Algorithm
> > Document date:  2022-07-10
> > Group:          Individual Submission
> > Pages:          120
> > URL:            https://www.ietf.org/archive/id/draft-eastlake-fnv-18.txt
> > Status:         https://datatracker.ietf.org/doc/draft-eastlake-fnv/
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-eastlake-fnv
> > Diff:           https://www.ietf.org/rfcdiff?url2=draft-eastlake-fnv-18
> >
> > Abstract:
> >    FNV (Fowler/Noll/Vo) is a fast, non-cryptographic hash algorithm with
> >    good dispersion. The purpose of this document is to make information
> >    on FNV and open source code performing FNV conveniently available to
> >    the Internet community.
> >
> > _______________________________________________
> > Secdispatch mailing list
> > Secdispatch@ietf.org
> > https://www.ietf.org/mailman/listinfo/secdispatch
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch