References from RFC 5780
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 127 |
References Referenced by |
normatively references | ||
BCP 14 |
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 2782 |
A DNS RR for specifying the location of services (DNS SRV)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3424 |
IAB Considerations for UNilateral Self-Address Fixing (UNSAF) Across Network Address Translation
References Referenced by |
Informational | informatively references | |
RFC 3489 |
STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)
References Referenced by |
Proposed Standard | informatively references | |
RFC 4787 |
Network Address Translation (NAT) Behavioral Requirements for Unicast UDP
References Referenced by |
Best Current Practice | normatively references | |
RFC 5245 |
Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols
References Referenced by |
Proposed Standard | informatively references | |
RFC 5389 |
Session Traversal Utilities for NAT (STUN)
References Referenced by |
Proposed Standard | normatively references | |
RFC 5626 |
Managing Client-Initiated Connections in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference |