References from RFC 7434
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 63 |
References Referenced by |
normatively references | ||
draft-ietf-cuss-sip-uui |
A Mechanism for Transporting User-to-User Call Control Information in SIP
References Referenced by |
Proposed Standard | normatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | |
RFC 3372 |
Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
References Referenced by |
Best Current Practice | normatively references | |
RFC 3398 |
Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
References Referenced by |
Proposed Standard | normatively references | |
RFC 3840 |
Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 6567 |
Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIP
References Referenced by |
Informational | informatively references |