References from RFC 7242
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 26 |
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4838 |
Delay-Tolerant Networking Architecture
References Referenced by |
Informational | informatively references | |
| RFC 5050 |
Bundle Protocol Specification
References Referenced by |
Experimental | normatively references | |
| RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | informatively references | |
| RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | |
| RFC 6256 |
Using Self-Delimiting Numeric Values in Protocols
References Referenced by |
Informational | informatively references | |
| RFC 6257 |
Bundle Security Protocol Specification
References Referenced by |
Experimental | informatively references |