References from draft-ietf-ace-cbor-web-token
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 |
informatively references | ||
BCP 14 |
References Referenced by |
normatively references | ||
BCP 26 |
References Referenced by |
informatively references | ||
draft-wahlstroem-ace-cbor-web-token |
CBOR Web Token (CWT)
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | informatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7515 |
JSON Web Signature (JWS)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7516 |
JSON Web Encryption (JWE)
References Referenced by |
Proposed Standard | informatively references | |
RFC 7519 |
JSON Web Token (JWT)
References Referenced by |
Proposed Standard | informatively references | |
RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | informatively references | |
RFC 8152 |
CBOR Object Signing and Encryption (COSE)
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 |