References from draft-ietf-teep-protocol
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 References Referenced by |
Best Current Practice | normatively references | |
BCP 26 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | informatively references | |
draft-ietf-rats-eat |
The Entity Attestation Token (EAT) References Referenced by |
normatively references | ||
draft-ietf-sacm-coswid |
Concise Software Identification Tags References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-suit-manifest |
A Concise Binary Object Representation (CBOR)-based Serialization Format for the Software Updates for Internet of Things (SUIT) Manifest References Referenced by |
normatively references | ||
draft-ietf-teep-architecture |
Trusted Execution Environment Provisioning (TEEP) Architecture References Referenced by |
informatively references | ||
draft-moran-suit-report |
Secure Reporting of Update Status References Referenced by |
normatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 2560 |
X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP References Referenced by |
Proposed Standard | normatively references | |
RFC 3629 |
UTF-8, a transformation format of ISO 10646 References Referenced by |
Internet Standard | normatively references | |
RFC 4122 |
A Universally Unique IDentifier (UUID) URN Namespace References Referenced by |
Proposed Standard | informatively references | |
RFC 5198 |
Unicode Format for Network Interchange References Referenced by |
Proposed Standard | normatively references | |
RFC 7049 |
Concise Binary Object Representation (CBOR) References Referenced by |
Proposed Standard | normatively 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 | |
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 | informatively references | |
RFC 8915 |
Network Time Security for the Network Time Protocol References Referenced by |
Proposed Standard | informatively references | |
STD 63 |
UTF-8, a transformation format of ISO 10646 References Referenced by |
Internet Standard | normatively references |