rfc9923v6.txt   rfc9923.txt 
Independent Submission G. Fowler Independent Submission G. Fowler
Request for Comments: 9923 Google Request for Comments: 9923 Google
Category: Informational L. Noll Category: Informational L. Noll
ISSN: 2070-1721 Cisco Systems ISSN: 2070-1721
K. Vo K. Vo
Google Google
D. Eastlake 3rd D. Eastlake 3rd
Independent Independent
T. Hansen T. Hansen
AT&T AT&T
January 2026 January 2026
The FNV Non-Cryptographic Hash Algorithm The FNV Non-Cryptographic Hash Algorithm
skipping to change at line 220 skipping to change at line 220
and many other uses. It is also referenced in the following and many other uses. It is also referenced in the following
standards documents: [RFC7357], [RFC7873], and [IEEE8021Q-2022]. standards documents: [RFC7357], [RFC7873], and [IEEE8021Q-2022].
A study has recommended FNV in connection with the IPv6 flow label A study has recommended FNV in connection with the IPv6 flow label
value [IPv6flow]. Additionally, there was a proposal to use FNV for value [IPv6flow]. Additionally, there was a proposal to use FNV for
Bidirectional Forwarding Detection (BFD) sequence number generation Bidirectional Forwarding Detection (BFD) sequence number generation
[BFDseq]. [NCHF] discusses criteria for evaluating non-cryptographic [BFDseq]. [NCHF] discusses criteria for evaluating non-cryptographic
hash functions. hash functions.
If you use an FNV function in an application, you are kindly
requested to send a note via the process outlined at
<http://www.isthe.com/chongo/tech/comp/fnv/index.html#history>.
1.4. Why Is FNV Non-Cryptographic? 1.4. Why Is FNV Non-Cryptographic?
A full discussion of cryptographic hash requirements and strength is A full discussion of cryptographic hash requirements and strength is
beyond the scope of this document. However, here are three beyond the scope of this document. However, here are three
characteristics of FNV that would generally be considered to make it characteristics of FNV that would generally be considered to make it
non-cryptographic: non-cryptographic:
1. Sticky State - A cryptographic hash should not have a state in 1. Sticky State - A cryptographic hash should not have a state in
which it can stick for a plausible input pattern. But in the which it can stick for a plausible input pattern. But in the
very unlikely event that the FNV hash variable accidentally very unlikely event that the FNV hash variable accidentally
skipping to change at line 6251 skipping to change at line 6255
Hoffman, Charlie Kaufman, Eliot Lear, Bob Moskowitz, Gayle Noble, Hoffman, Charlie Kaufman, Eliot Lear, Bob Moskowitz, Gayle Noble,
Stefan Santesson, Mukund Sivaraman, and Paul Wouters. Stefan Santesson, Mukund Sivaraman, and Paul Wouters.
Authors' Addresses Authors' Addresses
Glenn S. Fowler Glenn S. Fowler
Google Google
Email: glenn.s.fowler@gmail.com Email: glenn.s.fowler@gmail.com
Landon Curt Noll Landon Curt Noll
Cisco Systems Email: contact-landon@asthe.com
170 West Tasman Drive URI: http://www.isthe.com/chongo
San Jose, California 95134
United States of America
Phone: +1-408-424-1102
Email: fnv-ietf8-mail@asthe.com
URI: http://www.isthe.com/chongo/index.html
Kiem-Phong Vo Kiem-Phong Vo
Google Google
Email: phongvo@gmail.com Email: phongvo@gmail.com
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Independent Independent
2386 Panoramic Circle 2386 Panoramic Circle
Apopka, Florida 32703 Apopka, Florida 32703
United States of America United States of America
 End of changes. 3 change blocks. 
8 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.48.