References from rfc8516
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 | |
| draft-ietf-core-coap-pubsub |
Publish-Subscribe Broker for the Constrained Application Protocol (CoAP) 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 6347 |
Datagram Transport Layer Security Version 1.2 References Referenced by |
Proposed Standard | informatively references | |
| RFC 6585 |
Additional HTTP Status Codes References Referenced by |
Proposed Standard | informatively references | |
| RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing References Referenced by |
Proposed Standard | 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 |