References from RFC 9410
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 |
---|---|---|---|---|
draft-ietf-sipcore-multiple-reasons |
Multiple SIP Reason Header Field Values
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 3326 |
The Reason Header Field for the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7340 |
Secure Telephone Identity Problem Statement and Requirements
References Referenced by |
Informational | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8224 |
Authenticated Identity Management in the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 8225 |
PASSporT: Personal Assertion Token
References Referenced by |
Proposed Standard | normatively references | |
RFC 8226 |
Secure Telephone Identity Credentials: Certificates
References Referenced by |
Proposed Standard | normatively references |