References from RFC 5334
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 14 | References Referenced by | normatively references | ||
| BCP 72 | References Referenced by | informatively references | ||
| BCP 78 | References Referenced by | informatively references | ||
| RFC 2045 | Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies References Referenced by | Draft Standard | normatively references | |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 3533 | The Ogg Encapsulation Format Version 0 References Referenced by | Informational | normatively references | Downref |
| RFC 3534 | The application/ogg Media Type References Referenced by | Proposed Standard | informatively references | |
| RFC 3552 | Guidelines for Writing RFC Text on Security Considerations References Referenced by | Best Current Practice | informatively references | |
| RFC 4281 | The Codecs Parameter for "Bucket" Media Types References Referenced by | Proposed Standard | normatively references | |
| RFC 4288 | Media Type Specifications and Registration Procedures References Referenced by | Best Current Practice | normatively references | |
| RFC 4648 | The Base16, Base32, and Base64 Data Encodings References Referenced by | Proposed Standard | informatively references | |
| RFC 5215 | RTP Payload Format for Vorbis Encoded Audio References Referenced by | Proposed Standard | informatively references |