References from draft-miller-json-constrained-notation
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 3629 |
UTF-8, a transformation format of ISO 10646
References Referenced by |
Internet Standard | normatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR)
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 7228 |
Terminology for Constrained-Node Networks
References Referenced by |
Informational | informatively references | |
RFC 7515 |
JSON Web Signature (JWS)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7516 |
JSON Web Encryption (JWE)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7517 |
JSON Web Key (JWK)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7518 |
JSON Web Algorithms (JWA)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7519 |
JSON Web Token (JWT)
References Referenced by |
Proposed Standard | normatively references | |
STD 63 |
References Referenced by |
normatively references |