References from draft-rsalz-drbg-speck-wap-wep
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
| Document | Title | Status | Type | Downref |
|---|---|---|---|---|
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| BCP 188 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| BCP 201 |
Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
References Referenced by |
Best Current Practice | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7366 |
Encrypt-then-MAC for Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7693 |
The BLAKE2 Cryptographic Hash and Message Authentication Code (MAC)
References Referenced by |
Informational | informatively references | |
| RFC 7696 |
Guidelines for Cryptographic Algorithm Agility and Selecting Mandatory-to-Implement Algorithms
References Referenced by |
Best Current Practice | informatively references |