References from RFC 2913
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 |
|---|---|---|---|---|
| RFC 2045 |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
References Referenced by |
Draft Standard | Reference | |
| RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | Reference | |
| RFC 2068 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Proposed Standard | Reference | |
| RFC 2234 |
Augmented BNF for Syntax Specifications: ABNF
References Referenced by |
Proposed Standard | Reference | |
| RFC 2295 |
Transparent Content Negotiation in HTTP
References Referenced by |
Experimental | Reference | |
| RFC 2434 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | Reference | |
| RFC 2506 |
Media Feature Tag Registration Procedure
References Referenced by |
Best Current Practice | Reference | |
| RFC 2530 |
Indicating Supported Media Features Using Extensions to DSN and MDN
References Referenced by |
Proposed Standard | Reference | |
| RFC 2533 |
A Syntax for Describing Media Feature Sets
References Referenced by |
Proposed Standard | Reference |