References from RFC 9727
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 |
|---|---|---|---|---|
| draft-kelly-json-hal |
JSON Hypertext Application Language
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6573 |
The Item and Collection Link Relations
References Referenced by |
Informational | normatively references | Downref |
| RFC 7284 |
The Profile URI Registry
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 8288 |
Web Linking
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8615 |
Well-Known Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8631 |
Link Relation Types for Web Services
References Referenced by |
Informational | informatively references | |
| RFC 9110 |
HTTP Semantics
References Referenced by |
Internet Standard | normatively references | |
| RFC 9264 |
Linkset: Media Types and a Link Relation Type for Link Sets
References Referenced by |
Proposed Standard | normatively references |