References from draft-hartke-t2trg-coral-reef
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 |
References Referenced by |
normatively references | ||
draft-ietf-core-coral |
The Constrained RESTful Application Language (CoRAL)
References Referenced by |
normatively references | ||
draft-ietf-core-resource-directory |
Constrained RESTful Environments (CoRE) Resource Directory
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | informatively references | |
RFC 6573 |
The Item and Collection Link Relations
References Referenced by |
Informational | informatively references | |
RFC 6690 |
Constrained RESTful Environments (CoRE) Link Format
References Referenced by |
Proposed Standard | informatively references | |
RFC 7228 |
Terminology for Constrained-Node Networks
References Referenced by |
Informational | informatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8288 |
Web Linking
References Referenced by |
Proposed Standard | informatively references | |
RFC 8615 |
Well-Known Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
References Referenced by |
informatively references |