References from draft-ietf-sacm-coswid

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.

Reference type help

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 178 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
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 normatively references
BCP 47 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
draft-birkholz-rats-tuda Time-Based Uni-Directional Attestation
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 3629 UTF-8, a transformation format of ISO 10646
References Referenced by
Internet Standard normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
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 5646 Tags for Identifying Languages
References Referenced by
Best Current Practice normatively references
RFC 5892 The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)
References Referenced by
Proposed Standard normatively references
RFC 6648 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
References Referenced by
Best Current Practice normatively references
RFC 7049 Concise Binary Object Representation (CBOR)
References Referenced by
Proposed Standard normatively references
RFC 7252 The Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 8126 Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by
Best Current Practice normatively 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 8288 Web Linking
References Referenced by
Proposed Standard normatively references
RFC 8322 Resource-Oriented Lightweight Information Exchange (ROLIE)
References Referenced by
Proposed Standard informatively references
RFC 8412 Software Inventory Message and Attributes (SWIMA) for PA-TNC
References Referenced by
Proposed Standard normatively references
RFC 8520 Manufacturer Usage Description Specification
References Referenced by
Proposed Standard informatively 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
STD 63 UTF-8, a transformation format of ISO 10646
References Referenced by
Internet Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references