References from RFC 7641
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 | ||
BCP 145 |
References Referenced by |
informatively references | ||
RFC 1982 |
Serial Number Arithmetic
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 5405 |
Unicast UDP Usage Guidelines for Application Designers
References Referenced by |
Best Current Practice | informatively references | |
RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | normatively references | |
RFC 5989 |
A SIP Event Package for Subscribing to Changes to an HTTP Resource
References Referenced by |
Proposed Standard | informatively references | |
RFC 6202 |
Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
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 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 |