References from draft-ietf-jmap-core
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 |
normatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 165 |
References Referenced by |
normatively references | ||
BCP 195 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
normatively references | ||
BCP 73 |
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 2782 |
A DNS RR for specifying the location of services (DNS SRV)
References Referenced by |
Proposed Standard | normatively references | |
RFC 2818 |
HTTP Over TLS
References Referenced by |
Informational | normatively references | Downref |
RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
RFC 3553 |
An IETF URN Sub-namespace for Registered Protocol Parameters
References Referenced by |
Best Current Practice | normatively references | |
RFC 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
RFC 4648 |
The Base16, Base32, and Base64 Data Encodings
References Referenced by |
Proposed Standard | normatively references | |
RFC 4790 |
Internet Application Protocol Collation Registry
References Referenced by |
Proposed Standard | normatively references | |
RFC 5051 |
i;unicode-casemap - Simple Unicode Collation Algorithm
References Referenced by |
Proposed Standard | normatively references | |
RFC 5322 |
Internet Message Format
References Referenced by |
Draft 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 6335 |
Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry
References Referenced by |
Best Current Practice | normatively references | |
RFC 6570 |
URI Template
References Referenced by |
Proposed Standard | normatively references | |
RFC 6749 |
The OAuth 2.0 Authorization Framework
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 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
RFC 6901 |
JavaScript Object Notation (JSON) Pointer
References Referenced by |
Proposed Standard | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by |
Proposed Standard | normatively references | |
RFC 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by |
Proposed Standard | normatively references | |
RFC 7493 |
The I-JSON Message Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 7525 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by |
Best Current Practice | normatively references | |
RFC 7617 |
The 'Basic' HTTP Authentication Scheme
References Referenced by |
Proposed Standard | normatively references | |
RFC 7807 |
Problem Details for HTTP APIs
References Referenced by |
Proposed Standard | normatively references | |
RFC 8030 |
Generic Event Delivery Using HTTP Push
References Referenced by |
Proposed Standard | normatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
RFC 8246 |
HTTP Immutable Responses
References Referenced by |
Proposed Standard | informatively references | |
RFC 8259 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Internet Standard | normatively references | |
RFC 8264 |
PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application Protocols
References Referenced by |
Proposed Standard | normatively references | |
RFC 8291 |
Message Encryption for Web Push
References Referenced by |
Proposed Standard | normatively references | |
RFC 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by |
Proposed Standard | normatively references | |
STD 63 |
References Referenced by |
normatively references | ||
STD 90 |
References Referenced by |
normatively references |