References from rfc3969
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
References Referenced by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
| BCP 67 |
Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area
References Referenced by |
Best Current Practice | normatively references | |
| BCP 78 |
Rights Contributors Provide to the IETF Trust
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references | Downref |
| RFC 3427 |
Change Process for the Session Initiation Protocol (SIP)
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 3486 |
Compressing the Session Initiation Protocol (SIP)
References Referenced by |
Proposed Standard | Possible Reference | Possible Downref |