| rfc9923v8.txt | rfc9923.txt | |||
|---|---|---|---|---|
| skipping to change at line 222 ¶ | skipping to change at line 222 ¶ | |||
| 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 | If you use an FNV function in an application, you are kindly | |||
| requested to send a note via the process outlined at | requested to send a note via the process outlined at | |||
| <http://www.isthe.com/chongo/tech/comp/fnv/index.html#history>. | <http://www.isthe.com/chongo/tech/comp/fnv/index.html#address>. | |||
| 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 | |||
| End of changes. 1 change blocks. | ||||
| 1 lines changed or deleted | 1 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. | ||||