References from draft-pelov-rich-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 |
|---|---|---|---|---|
| BCP 14 |
References Referenced by |
normatively references | ||
| draft-bhutton-json-schema |
JSON Schema: A Media Type for Describing JSON Documents
References Referenced by |
informatively references | ||
| draft-pelov-bounded-agent-capabilities |
Bounded Capabilities for Agent Tool Interfaces: Problem Statement
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 6920 |
Naming Things with Hashes
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7493 |
The I-JSON Message Format
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 | |
| RFC 8785 |
JSON Canonicalization Scheme (JCS)
References Referenced by |
Informational | normatively references | |
| RFC 9334 |
Remote ATtestation procedureS (RATS) Architecture
References Referenced by |
Informational | informatively references | |
| RFC 9457 |
Problem Details for HTTP APIs
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9880 |
Semantic Definition Format (SDF) for Data and Interactions of Things
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9943 |
An Architecture for Trustworthy and Transparent Digital Supply Chains
References Referenced by |
Proposed Standard | informatively references |