Skip to main content

References from draft-keranen-t2trg-rest-iot

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-ietf-core-coap-pubsub A publish-subscribe architecture for the Constrained Application Protocol (CoAP)
References Referenced by
informatively references
draft-ietf-core-object-security Object Security for Constrained RESTful Environments (OSCORE)
References Referenced by
Proposed Standard normatively references
draft-ietf-core-resource-directory Constrained RESTful Environments (CoRE) Resource Directory
References Referenced by
Proposed Standard normatively references
draft-ietf-core-senml Sensor Measurement Lists (SenML)
References Referenced by
Proposed Standard informatively references
draft-irtf-t2trg-iot-seccons Internet of Things (IoT) Security: State of the Art and Challenges
References Referenced by
Informational informatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
References Referenced by
Internet Standard normatively references
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by
Proposed Standard normatively references
RFC 5280 Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
References Referenced by
Proposed Standard normatively references
RFC 5590 Transport Subsystem for the Simple Network Management Protocol (SNMP)
References Referenced by
Internet Standard normatively references
RFC 5988 Web Linking
References Referenced by
Proposed Standard normatively references
RFC 6202 Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
References Referenced by
Informational normatively 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 normatively references
RFC 6763 DNS-Based Service Discovery
References Referenced by
Proposed Standard informatively references
RFC 6943 Issues in Identifier Comparison for Security Purposes
References Referenced by
Informational informatively references
RFC 7049 Concise Binary Object Representation (CBOR)
References Referenced by
Proposed Standard normatively references
RFC 7159 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Proposed Standard informatively 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 informatively references
RFC 7320 URI Design and Ownership
References Referenced by
Best Current Practice informatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
References Referenced by
Proposed Standard normatively references
RFC 7925 Transport Layer Security (TLS) / Datagram Transport Layer Security (DTLS) Profiles for the Internet of Things
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
STD 66
References Referenced by
normatively references
STD 78
References Referenced by
normatively references