Library for interacting as endpoint and lookup client with CoRE Resource Directories. More...
Library for interacting as endpoint and lookup client with CoRE Resource Directories.
The cord
([Co]RE [R]esource [D]irectory) module provides endpoint and lookup client functionality for interacting with CoRE Resource Directories (RDs) as defined in RFC 9176
.
RFC 9176
defines two types different roles for nodes when interacting with a RD:
endpoint
: registers and manages entries at the RDclient
: performs different kind of lookups Figure copied form RFC 9176
.
endpoint (ep)
and lookup client (lc)
. This should hopefully prevent some confusion in conjunction with the client
and server
roles as defined by CoAP.This module is structured in a number of submodules with goal to reflect the different roles described in RFC 9176
:
cord_ep
: standard endpoint implementation following the rules as defined i.a. in sections 5.2, 5.3, A.1, and A.2cord_epsim
: endpoint implementation following the simple registration procedure as defined in section 5.3.1cord_lc
: lookup client implementation for querying information from an RD using the lookup interfacescord_config
: header file collection (default) configuration values used throughout this modulecord_common
: shared functionality used by the above submodules Modules | |
CoRE RD Common | |
Shared functionality for CoRE Resource Directory endpoints. | |
CoRE RD Configuration | |
Configuration options for CoRE RD endpoints and lookup clients. | |
CoRE RD Endpoint | |
Library for using RIOT as CoRE Resource Directory endpoint. | |
CoRE RD Lookup Client | |
Library for using RIOT as CoRE Resource Directory (RD) lookup client. | |
CoRE RD Simple Registration Endpoint | |
CoRE Resource Directory endpoint using the simple registration procedure. | |