References from rfc2935
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 | Reference | |
RFC 1945 |
Hypertext Transfer Protocol -- HTTP/1.0 References Referenced by |
Informational | Reference | Possible Downref |
RFC 2048 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures References Referenced by |
Best Current Practice | Reference | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | Reference | |
RFC 2246 |
The TLS Protocol Version 1.0 References Referenced by |
Proposed Standard | Reference | |
RFC 2376 |
XML Media Types References Referenced by |
Informational | Reference | Possible Downref |
RFC 2396 |
Uniform Resource Identifiers (URI): Generic Syntax References Referenced by |
Draft Standard | Reference | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by |
Draft Standard | Reference | |
RFC 2801 |
Internet Open Trading Protocol - IOTP Version 1.0 References Referenced by |
Informational | Reference | Possible Downref |
RFC 2802 |
Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP) References Referenced by |
Informational | Reference | Possible Downref |