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

Hi Mike,

On Tue, Jul 12, 2022 at 10:34 PM Mike Ounsworth
<Mike.Ounsworth@entrust.com> wrote:
>
> Maybe a dumb question, but what is the driver for getting FNV published as an RFC? Is it "just because"? Is there a protocol coming through some working group that needs an FNV spec as a dependency?

FNV has been used in a bunch of applications and I believe it will be
used in a bunch more. I think that having a stable written reference,
such as the Informational RFC proposed, would be a good thing as would
additional availability of code. I've done this sort of thing before.
See the following Informational RFCs:
https://datatracker.ietf.org/doc/html/rfc4634
https://datatracker.ietf.org/doc/html/rfc4635
https://datatracker.ietf.org/doc/html/rfc6234
I believe these were all handled as AD sponsored which is why I think
AD sponsored is a reasonable way to go.

> I see you added draft-ietf-bfd-secure-sequence-numbers as a dependent draft in your most recent versions, so should your FNV draft go through the BFD WG along with it?

Pretty much all draft can be improved by review. I think Security
expertise would be more relevant than BFD expertise to review this
draft.

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

> ---
> Mike Ounsworth
>
> -----Original Message-----
> From: Secdispatch <secdispatch-bounces@ietf.org> On Behalf Of Donald Eastlake
> Sent: July 12, 2022 9:17 PM
> To: Eric Rescorla <ekr@rtfm.com>
> Cc: IETF SecDispatch <secdispatch@ietf.org>
> Subject: [EXTERNAL] Re: [Secdispatch] Request a short agenda slot for draft-eastlake-fnv-18.txt
>
> WARNING: This email originated outside of Entrust.
> DO NOT CLICK links or attachments unless you trust the sender and know the content is safe.
>
> ______________________________________________________________________
> On Tue, Jul 12, 2022 at 9:19 PM Eric Rescorla <ekr@rtfm.com> wrote:
> > Given that FNV isn't a cryptographic hash, isn't DISPATCH the right location for this draft?
>
> DISPATCH is for the ART Area but I don't see how FNV is either an Application level protocol or a Real Time protocol.
> Security might not be the perfect Area for a non-cryptographic hash, but it seems to me like the closest fit.
>
> Assuming a willing AD, my personal belief is that AD sponsored is a reasonable way to go.
>
> Thanks,
> Donald
> ===============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  2386 Panoramic Circle, Apopka, FL 32703 USA  d3e3e3@gmail.com
>
> > -Ekr
> >
> >
> > On Tue, Jul 12, 2022 at 6:10 PM Donald Eastlake <d3e3e3@gmail.com> 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://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-eas
> >> tlake-fnv-18.txt__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-
> >> B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFca1kW_v$
> >> 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
> >> https://urldefense.com/v3/__http://www.isthe.com/chongo/tech/comp/fnv
> >> /index.html__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnM
> >> kyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFTRhkPqR$
> >> pointers to any other background materials:
> >> https://urldefense.com/v3/__https://en.wikipedia.org/wiki/Fowler**BNo
> >> ll**BVo_hash_function__;4oCT4oCT!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZ
> >> zUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFWQGu9nF$
> >> 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://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-eastlake-fnv-18.txt__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFca1kW_v$
> >> Status:         https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-eastlake-fnv/__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFeFJsTFR$
> >> Htmlized:       https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-eastlake-fnv__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFdhWbvf1$
> >> Diff:           https://urldefense.com/v3/__https://www.ietf.org/rfcdiff?url2=draft-eastlake-fnv-18__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFZXFSnKc$
> >>
> >> 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://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/sec
> >> dispatch__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyf
> >> eZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFUAGFV3s$
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/secdispatch__;!!FJ-Y8qCqXTj2!cR5g_yh6UQob5PWlhMwKMZzUQmERwOVptz-B9DnMkyfeZy3xux40F4Hsi-8347KUwMQrpm-yZ0H1VTljFUAGFV3s$
> Any email and files/attachments transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If this message has been sent to you in error, you must not copy, distribute or disclose of the information it contains. Please notify Entrust immediately and delete the message from your system.