References from draft-ietf-secevent-subject-identifiers
This is an experimental product. 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 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 5321 |
Simple Mail Transfer Protocol Refs Ref'd by |
Draft Standard | normatively references | |
| RFC 5322 |
Internet Message Format Refs Ref'd by |
Draft Standard | normatively references | |
| RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7519 |
JSON Web Token (JWT) Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 7565 |
The 'acct' URI Scheme Refs Ref'd by |
Proposed Standard | normatively references | |
| RFC 8126 |
Guidelines for Writing an IANA Considerations Section in RFCs Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 8417 |
Security Event Token (SET) Refs Ref'd by |
Proposed Standard | normatively references |