References from draft-harkins-application-csrattrs-media-type
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 |
Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
| BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2397 |
The "data" URL scheme
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2925 |
Definitions of Managed Objects for Remote Ping, Traceroute, and Lookup Operations
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2986 |
PKCS #10: Certification Request Syntax Specification Version 1.7
References Referenced by |
Informational | informatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 4288 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
| RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | normatively references | |
| STD 66 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references |