References from RFC 7967
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
draft-ietf-core-coap-tcp-tls |
CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets
References Referenced by |
Proposed Standard | informatively references | |
draft-ietf-core-http-mapping |
Guidelines for Mapping Implementations: HTTP to the Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | informatively references | |
draft-koster-core-coap-pubsub |
Publish-Subscribe Broker for the Constrained Application Protocol (CoAP)
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | Possible Reference | |
RFC 5405 |
Unicast UDP Usage Guidelines for Application Designers
References Referenced by |
Best Current Practice | informatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively 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 | informatively references |