References from draft-jenkins-jmap
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 14 |
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 5785 |
Defining Well-Known Uniform Resource Identifiers (URIs)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6186 |
Use of SRV Records for Locating Email Submission/Access Services
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6238 |
TOTP: Time-Based One-Time Password Algorithm
References Referenced by |
Informational | normatively references | |
| RFC 6570 |
URI Template
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6750 |
The OAuth 2.0 Authorization Framework: Bearer Token Usage
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6764 |
Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7493 |
The I-JSON Message Format
References Referenced by |
Proposed Standard | normatively references | |
| STD 66 |
References Referenced by |
normatively references |