Constrained RESTful Environments (CoRE) Resource Directory
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 60
- Abstract
- In many Internet of Things (IoT) applications, direct discovery of resources is not practical due to sleeping nodes or networks where multicast traffic is inefficient. These problems can be solved by employing an entity called a Resource Directory (RD), which contains information about resources held on other servers, allowing lookups to be performed for those resources. The input to an RD is composed of links, and the output is composed of links constructed from the information stored in the RD. This document specifies the web interfaces that an RD supports for web servers to discover the RD and to register, maintain, look up, and remove information on resources. Furthermore, new target attributes useful in conjunction with an RD are defined.
- Publication Date
- 2022-04-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9176- Link
- https://doi.org/10.17487/RFC9176
- Author(s)
- Christian AmsüssZach ShelbyMichael KosterCarsten BormannPeter Van der Stok
- Keyword(s)
- Web Linking, Resource Discovery, Resource Directory
Latest version of IETF RFC 9176
Document Versions — IETF RFC 9176
-
▶ IETF RFC 9176 (2022-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 6570 [Active*]
- IETF RFC 6690 [Active*]
- IETF RFC 6763 [Active*]
- IETF RFC 7230 [Superseded*]
- IETF RFC 7252 [Active*]
- IETF RFC 8126 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8288 [Active*]
- IETF RFC 9175 [Active*]
Bibliographic Reference(s)
- 10.1145-320434.320440 — ER EXTERNAL
- IETF.draft-bormann-t2trg-rel-impl-02 — I-D.bormann-t2trg-rel-impl EXTERNAL
- IETF.draft-ietf-ace-oauth-authz-46 — I-D.ietf-ace-oauth-authz EXTERNAL
- IETF.draft-ietf-core-coral-05 — I-D.ietf-core-coral EXTERNAL
- IETF.draft-ietf-core-links-json-10 — I-D.ietf-core-links-json EXTERNAL
- IETF.draft-ietf-core-rd-dns-sd-05 — I-D.ietf-core-rd-dns-sd EXTERNAL
- IETF.draft-silverajan-core-coap-protocol-negotiation-09 — I-D.silverajan-core-coap-protocol-negotiation EXTERNAL
- Open Mobile Alliance, "Lightweight Machine to Machine Technical Specification: Transport Bindings (Candidate Version 1.1)", June 2018, <https://openmobilealliance.org/RELEASE/LightweightM2M/V1_1-20180612-C/OMA-TS-LightweightM2M_Transport-V1_1-20180612-C.pdf>. EXTERNAL
- IETF RFC 3306 [Active*]
- IETF RFC 3307 [Active*]
- IETF RFC 3849 [Active*]
- IETF RFC 4122 [Superseded*]
- IETF RFC 4944 [Active*]
- IETF RFC 5771 [Active*]
- IETF RFC 6724 [Active*]
- IETF RFC 6775 [Active*]
- IETF RFC 6874 [Superseded*]
- IETF RFC 7228 [Active*]
- IETF RFC 7641 [Active*]
- IETF RFC 8106 [Active*]
- IETF RFC 8132 [Active*]
- IETF RFC 8141 [Active*]
- IETF RFC 8613 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9176.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9176, Constrained RESTful Environments (CoRE) Resource Directory. Available at https://doi.org/10.17487/RFC9176
Snippet:
IETF RFC 9176, Constrained RESTful Environments (CoRE) Resource Directory. Available at https://doi.org/10.17487/RFC9176
HTML (ISO 690 compliant)
Preview:
IETF RFC 9176, Constrained RESTful Environments (CoRE) Resource Directory. Available at https://doi.org/10.17487/RFC9176
Snippet:
<span class="citation"><cite>IETF RFC 9176</cite>, Constrained RESTful Environments (CoRE) Resource Directory. Available at <a href="https://doi.org/10.17487/RFC9176" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9176</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9176, Constrained RESTful Environments (CoRE) Resource Directory
doi: 10.17487/RFC9176
url: https://doi.org/10.17487/RFC9176
doi: 10.17487/RFC9176
url: https://doi.org/10.17487/RFC9176
Snippet:
<li> <cite id="bib-rfc9176">IETF RFC 9176</cite>, Constrained RESTful Environments (CoRE) Resource Directory <span class="doi">10.17487/RFC9176</span> </li>
Referenced By
- IETF RFC 9528 [Active*]