Skip to main content

References from draft-tiloca-core-groupcomm-proxy

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
draft-amsuess-core-cachable-oscore Cacheable OSCORE
References Referenced by
informatively references
draft-bormann-coap-misc Miscellaneous additions to CoAP
References Referenced by
informatively references
draft-ietf-ace-key-groupcomm-oscore Key Management for OSCORE Groups in ACE
References Referenced by
Proposed Standard informatively references
draft-ietf-core-groupcomm-bis Group Communication for the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
draft-ietf-core-observe-multicast-notifications Observe Notifications as CoAP Multicast Responses
References Referenced by
normatively references
draft-ietf-core-oscore-groupcomm Group Object Security for Constrained RESTful Environments (Group OSCORE)
References Referenced by
Proposed Standard normatively references
draft-tiloca-core-oscore-capable-proxies OSCORE-capable Proxies
References Referenced by
informatively references
draft-tiloca-core-oscore-discovery Discovery of OSCORE Groups with the CoRE Resource Directory
References Referenced by
informatively references
RFC 2046 Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
References Referenced by
Draft Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 4648 The Base16, Base32, and Base64 Data Encodings
References Referenced by
Proposed Standard normatively references
RFC 5234 Augmented BNF for Syntax Specifications: ABNF
References Referenced by
Internet Standard normatively references
RFC 6347 Datagram Transport Layer Security Version 1.2
References Referenced by
Proposed Standard informatively 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 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 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice 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 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
RFC 8613 Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard normatively references
RFC 8949 Concise Binary Object Representation (CBOR)
References Referenced by
Internet Standard normatively references
RFC 9112 HTTP/1.1
References Referenced by
Internet Standard normatively references
RFC 9147 The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
References Referenced by
Proposed Standard informatively references