References from draft-ietf-scitt-architecture
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 |
|---|---|---|---|---|
| RFC 2119 | Key words for use in RFCs to Indicate Requirement Levels References Referenced by | Best Current Practice | normatively references | |
| RFC 4949 | Internet Security Glossary, Version 2 References Referenced by | Informational | informatively references | |
| RFC 6838 | Media Type Specifications and Registration Procedures 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 8392 | CBOR Web Token (CWT) References Referenced by | Proposed Standard | normatively references | |
| RFC 8610 | Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures References Referenced by | Proposed Standard | normatively references | |
| RFC 8725 | JSON Web Token Best Current Practices References Referenced by | Best Current Practice | informatively references | |
| RFC 9162 | Certificate Transparency Version 2.0 References Referenced by | Experimental | informatively references | |
| RFC 9360 | CBOR Object Signing and Encryption (COSE): Header Parameters for Carrying and Referencing X.509 Certificates References Referenced by | Proposed Standard | normatively references | |
| RFC 9597 | CBOR Web Token (CWT) Claims in COSE Headers References Referenced by | Proposed Standard | normatively references | |
| STD 94 | References Referenced by | normatively references | ||
| STD 96 | References Referenced by | normatively references |