References from draft-ietf-jmap-refplus
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 |
|---|---|---|---|---|
| draft-ietf-jmap-calendars |
JSON Meta Application Protocol (JMAP) for Calendars
References Referenced by |
Proposed Standard | informatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6901 |
JavaScript Object Notation (JSON) Pointer
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 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references | |
| RFC 8620 |
The JSON Meta Application Protocol (JMAP)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8621 |
The JSON Meta Application Protocol (JMAP) for Mail
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9535 |
JSONPath: Query Expressions for JSON
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9610 |
JSON Meta Application Protocol (JMAP) for Contacts
References Referenced by |
Proposed Standard | informatively references |