References from draft-ietf-core-object-security

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.

Reference type help

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