References from draft-toraman-noa-action-digest
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 |
|---|---|---|---|---|
| draft-toraman-noa-settlement-evidence |
Settlement Evidence for Human-Approved Agent Payments
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 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section
References Referenced by |
Best Current Practice | informatively 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 9052 |
CBOR Object Signing and Encryption (COSE): Structures and Process
References Referenced by |
Internet Standard | informatively references | |
| RFC 9053 |
CBOR Object Signing and Encryption (COSE): Initial Algorithms
References Referenced by |
Informational | informatively references | |
| RFC 9396 |
OAuth 2.0 Rich Authorization Requests
References Referenced by |
Proposed Standard | informatively references | |
| RFC 9942 |
CBOR Object Signing and Encryption (COSE) Receipts
References Referenced by |
Proposed Standard | informatively references |