References from RFC 5413
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 |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 2784 |
Generic Routing Encapsulation (GRE)
References Referenced by |
Proposed Standard | informatively references | |
RFC 3990 |
Configuration and Provisioning for Wireless Access Points (CAPWAP) Problem Statement
References Referenced by |
Informational | informatively references | |
RFC 4118 |
Architecture Taxonomy for Control and Provisioning of Wireless Access Points (CAPWAP)
References Referenced by |
Informational | informatively references | |
RFC 4347 |
Datagram Transport Layer Security
References Referenced by |
Historic | informatively references | |
RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | informatively references | |
RFC 5415 |
Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | |
STD 3 |
References Referenced by |
informatively references |