Skip to main content

References from RFC 8613

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 106
References Referenced by
normatively references
BCP 14
References Referenced by
normatively references
BCP 72
References Referenced by
informatively references
draft-bormann-6lo-coap-802-15-ie Constrained Application Protocol (CoAP) over IEEE 802.15.4 Information Element for IETF
References Referenced by
informatively references
draft-hartke-core-e2e-security-reqs Requirements for CoAP End-To-End Security
References Referenced by
informatively references
draft-ietf-ace-oauth-authz Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
References Referenced by
Proposed Standard informatively references
draft-ietf-ace-oscore-profile The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework
References Referenced by
Proposed Standard informatively references
draft-ietf-cbor-cddl 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
draft-ietf-core-echo-request-tag Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing
References Referenced by
Proposed Standard informatively references
draft-ietf-core-oscore-groupcomm Group Object Security for Constrained RESTful Environments (Group OSCORE)
References Referenced by
Proposed Standard informatively references
draft-mattsson-core-coap-actuators Controlling Actuators with CoAP
References Referenced by
informatively references
draft-mcgrew-iv-gen Generation of Deterministic Initialization Vectors (IVs) and Nonces
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 3552 Guidelines for Writing RFC Text on Security Considerations
References Referenced by
Best Current Practice informatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard informatively references
RFC 4086 Randomness Requirements for Security
References Referenced by
Best Current Practice normatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 5116 An Interface and Algorithms for Authenticated Encryption
References Referenced by
Proposed Standard informatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 5869 HMAC-based Extract-and-Expand Key Derivation Function (HKDF)
References Referenced by
Informational informatively references
RFC 6347 Datagram Transport Layer Security Version 1.2
References Referenced by
Proposed Standard normatively references
RFC 6690 Constrained RESTful Environments (CoRE) Link Format
References Referenced by
Proposed Standard informatively references
RFC 7049 Concise Binary Object Representation (CBOR)
References Referenced by
Proposed Standard normatively references
RFC 7228 Terminology for Constrained-Node Networks
References Referenced by
Informational informatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard normatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by
Proposed Standard normatively references
RFC 7252 The Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7515 JSON Web Signature (JWS)
References Referenced by
Proposed Standard informatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7959 Block-Wise Transfers in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7967 Constrained Application Protocol (CoAP) Option for No Server Response
References Referenced by
Informational informatively references
RFC 8075 Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 8132 PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard 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 8323 CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
References Referenced by
Proposed Standard normatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
STD 66
References Referenced by
informatively references
STD 68
References Referenced by
normatively references