References from RFC 9610
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 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 | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8264 |
PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8620 |
The JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9553 |
JSContact: A JSON Representation of Contact Data
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9670 |
JSON Meta Application Protocol (JMAP) Sharing
References Referenced by |
Proposed Standard | normatively references |