References from rfc8824
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 | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5116 |
An Interface and Algorithms for Authenticated Encryption
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7641 |
Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7959 |
Block-Wise Transfers in the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7967 |
Constrained Application Protocol (CoAP) Option for No Server Response
References Referenced by |
Informational | normatively references | Downref |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8613 |
Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8724 |
SCHC: Generic Framework for Static Context Header Compression and Fragmentation
References Referenced by |
Proposed Standard | normatively references |