References from draft-ietf-core-dynlink
This is an experimental product. 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 Refs Ref'd by |
Best Current Practice | normatively references | |
| draft-irtf-t2trg-rest-iot |
RESTful Design for Internet of Things Systems Refs Ref'd by |
Informational | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 6690 |
Constrained RESTful Environments (CoRE) Link Format Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7252 |
The Constrained Application Protocol (CoAP) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 7641 |
Observing Resources in the Constrained Application Protocol (CoAP) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8132 |
PATCH and FETCH Methods for the Constrained Application Protocol (CoAP) Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8288 |
Web Linking Refs Ref'd by |
Proposed Standard | normatively references |