References from RFC 7351
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 13 | References Referenced by | normatively references | ||
| BCP 70 | References Referenced by | normatively references | ||
| draft-ietf-appsawg-media-type-suffix-regs | Additional Media Type Structured Syntax Suffixes References Referenced by | Informational | Possible Reference | |
| RFC 2045 | Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by | Draft Standard | normatively references | |
| RFC 2046 | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types References Referenced by | Draft Standard | normatively references | |
| RFC 2616 | Hypertext Transfer Protocol -- HTTP/1.1 References Referenced by | Draft Standard | informatively references | |
| RFC 3023 | XML Media Types References Referenced by | Proposed Standard | normatively references | |
| RFC 3470 | Guidelines for the Use of Extensible Markup Language (XML) within IETF Protocols References Referenced by | Best Current Practice | normatively references | |
| RFC 5261 | An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors References Referenced by | Proposed Standard | informatively references | |
| RFC 5789 | PATCH Method for HTTP References Referenced by | Proposed Standard | informatively references | |
| RFC 6838 | Media Type Specifications and Registration Procedures References Referenced by | Best Current Practice | normatively references | |
| RFC 6982 | Improving Awareness of Running Code: The Implementation Status Section References Referenced by | Experimental | informatively references |