RFC 9176: Constrained RESTful Environments (CoRE) Resource Directory
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9176
- Published
- April 2022
- Authors
- C. Amsüss; Z. Shelby; M. Koster; C. Bormann; P. van der Stok
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 60
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9423Constrained RESTful Environments (CoRE) Target Attributes RegistryCurrent
April 2024
- RFC 6690Constrained RESTful Environments (CoRE) Link FormatCurrent
August 2012
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9952Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLSCurrent
March 2026
- RFC 9953DNS over CoAP (DoC)Current
March 2026
- RFC 8824Static Context Header Compression (SCHC) for the Constrained Application Protocol (CoAP)Current
June 2021
- RFC 3585IPsec Configuration Policy Information ModelCurrent
August 2003
- RFC 3342The Application Exchange (APEX) Option Party Pack, Part Deux!Current
July 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?