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