References from draft-vanderstok-core-patch
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 | ||
BCP 26 |
References Referenced by |
normatively references | ||
draft-vanderstok-core-comi |
CoAP Management Interface
References Referenced by |
informatively references | ||
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs
References Referenced by |
Best Current Practice | normatively references | |
RFC 5789 |
PATCH Method for HTTP
References Referenced by |
Proposed Standard | normatively references | |
RFC 6902 |
JavaScript Object Notation (JSON) Patch
References Referenced by |
Proposed Standard | normatively references | |
RFC 7252 |
The Constrained Application Protocol (CoAP)
References Referenced by |
Proposed Standard | normatively references | |
RFC 7396 |
JSON Merge Patch
References Referenced by |
Proposed Standard | normatively references |