References from draft-ietf-dispatch-mime-protobuf
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 | normatively references | |
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 4648 | The Base16, Base32, and Base64 Data Encodings References Referenced by | Proposed Standard | normatively references | |
| RFC 6838 | Media Type Specifications and Registration Procedures References Referenced by | Best Current Practice | normatively references | |
| RFC 6839 | Additional Media Type Structured Syntax Suffixes References Referenced by | Informational | normatively references | |
| RFC 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by | Best Current Practice | normatively references | |
| RFC 8259 | The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by | Internet Standard | normatively references | |
| RFC 8264 | PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols References Referenced by | Proposed Standard | informatively references | |
| RFC 8446 | The Transport Layer Security (TLS) Protocol Version 1.3 References Referenced by | Proposed Standard | informatively references | |
| RFC 9205 | Building Protocols with HTTP References Referenced by | Best Current Practice | informatively references |