References from draft-hartke-t2trg-coral-pubsub

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 14 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
draft-ietf-core-coap-pubsub Publish-Subscribe Broker for the Constrained Application Protocol (CoAP)
Refs Ref'd by
informatively references
draft-ietf-core-coral The Constrained RESTful Application Language (CoRAL)
Refs Ref'd by
normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
Refs Ref'd by
Best Current Practice normatively references
RFC 3986 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references
RFC 3987 Internationalized Resource Identifiers (IRIs)
Refs Ref'd by
Proposed Standard normatively references
RFC 7228 Terminology for Constrained-Node Networks
Refs Ref'd by
Informational informatively references
RFC 7252 The Constrained Application Protocol (CoAP)
Refs Ref'd by
Proposed Standard normatively references
RFC 7641 Observing Resources in the Constrained Application Protocol (CoAP)
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 8516 "Too Many Requests" Response Code for the Constrained Application Protocol
Refs Ref'd by
Proposed Standard normatively references
STD 66 Uniform Resource Identifier (URI): Generic Syntax
Refs Ref'd by
Internet Standard normatively references