References from RFC 5768
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 85 |
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3235 |
Network Address Translator (NAT)-Friendly Application Design Guidelines
References Referenced by |
Informational | informatively references | |
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 3264 |
An Offer/Answer Model with Session Description Protocol (SDP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 3725 |
Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
References Referenced by |
Best Current Practice | informatively references | |
RFC 3840 |
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 4566 |
SDP: Session Description Protocol
References Referenced by |
Proposed Standard | 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 | normatively references | |
RFC 5389 |
Session Traversal Utilities for NAT (STUN)
References Referenced by |
Proposed Standard | informatively references | |
RFC 5741 |
RFC Streams, Headers, and Boilerplates
References Referenced by |
Informational | Possible Reference | Possible Downref |