Skip to main content

References from draft-dijk-core-groupcomm-bis

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
References Referenced by
normatively references
BCP 188
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-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-core-coap-pubsub A publish-subscribe architecture for the Constrained Application Protocol (CoAP)
References Referenced by
informatively references
draft-ietf-core-echo-request-tag Constrained Application Protocol (CoAP): Echo, Request-Tag, and Token Processing
References Referenced by
Proposed Standard normatively references
draft-ietf-core-oscore-groupcomm Group Object Security for Constrained RESTful Environments (Group OSCORE)
References Referenced by
Proposed Standard normatively references
draft-ietf-core-resource-directory Constrained RESTful Environments (CoRE) Resource Directory
References Referenced by
Proposed Standard informatively references
draft-ietf-tls-dtls13 The Datagram Transport Layer Security (DTLS) Protocol Version 1.3
References Referenced by
Proposed Standard informatively references
draft-tiloca-core-oscore-discovery Discovery of OSCORE Groups with the CoRE Resource Directory
References Referenced by
informatively references
RFC 1122 Requirements for Internet Hosts - Communication Layers
References Referenced by
Internet Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 3376 Internet Group Management Protocol, Version 3
References Referenced by
Proposed Standard normatively references
RFC 3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6
References Referenced by
Proposed Standard normatively references
RFC 4443 Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
References Referenced by
Internet Standard normatively references
RFC 4944 Transmission of IPv6 Packets over IEEE 802.15.4 Networks
References Referenced by
Proposed Standard normatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by
Proposed Standard informatively references
RFC 6092 Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service
References Referenced by
Informational informatively references
RFC 6347 Datagram Transport Layer Security Version 1.2
References Referenced by
Proposed Standard informatively references
RFC 6550 RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks
References Referenced by
Proposed Standard informatively references
RFC 6636 Tuning the Behavior of the Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) for Routers in Mobile and Wireless Networks
References Referenced by
Informational informatively references
RFC 6690 Constrained RESTful Environments (CoRE) Link Format
References Referenced by
Proposed Standard 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 7258 Pervasive Monitoring Is an Attack
References Referenced by
Best Current Practice informatively references
RFC 7346 IPv6 Multicast Address Scopes
References Referenced by
Proposed Standard informatively references
RFC 7390 Group Communication for the Constrained Application Protocol (CoAP)
References Referenced by
Experimental informatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7731 Multicast Protocol for Low-Power and Lossy Networks (MPL)
References Referenced by
Proposed Standard informatively 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 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 8323 CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
References Referenced by
Proposed Standard informatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard informatively references
RFC 8613 Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard normatively references
RFC 8710 Multipart Content-Format for the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard informatively references
STD 3
References Referenced by
normatively references
STD 89
References Referenced by
normatively references