References from draft-ietf-core-multipart-ct
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 |
informatively references | ||
| BCP 14 |
References Referenced by |
normatively references | ||
| draft-ietf-ace-coap-est |
EST-coaps: Enrollment over Secure Transport with the Secure Constrained Application Protocol
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2046 |
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by |
Draft Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7049 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7641 |
Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8610 |
Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
References Referenced by |
Proposed Standard | informatively references |