References from rfc3265
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 | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 2779 |
Instant Messaging / Presence Protocol Requirements
References Referenced by |
Informational | normatively references | Downref |
| RFC 2848 |
The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3261 |
SIP: Session Initiation Protocol
References Referenced by |
Proposed Standard | normatively references |