References from draft-li-core-cbor-equivalents
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 |
---|---|---|---|---|
BCP 14 |
References Referenced by |
normatively references | ||
draft-ietf-core-links-json |
Representing Constrained RESTful Environments (CoRE) Link Format in JSON and CBOR
References Referenced by |
Proposed Standard | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 5988 |
Web Linking
References Referenced by |
Proposed Standard | normatively 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 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | Possible Reference | |
RFC 7390 |
Group Communication for the Constrained Application Protocol (CoAP)
References Referenced by |
Experimental | normatively references |