RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
Code Releases Activity

sys/net/app/cord and examples: Update references to -27

Browse Source 
With all (the few necessary) changes done, this can claim -27
compatibility.
This commit is contained in:
chrysn 2021-03-01 11:59:57 +01:00
parent 6542f7008f
commit 049b5179a7
7 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
examples/cord_ep/README.md
View File

@ -4,7 +4,7 @@ CoRE Resource Directory: Endpoint Example
This example application demonstrates the usage of RIOT's Resource Directory
(RD) endpoint module, called `cord_ep`. This module supports the registration,
update, and removal procedures as defined in
[draft-ietf-core-resource-directory-15](https://tools.ietf.org/html/draft-ietf-core-resource-directory-15).
[draft-ietf-core-resource-directory-27](https://tools.ietf.org/html/draft-ietf-core-resource-directory-27).
Usage
=====

4
examples/cord_epsim/Makefile
View File

@ -32,8 +32,8 @@ CFLAGS += -DRD_ADDR=$(RD_ADDR)
include $(RIOTBASE)/Makefile.include
# For debugging and demonstration purposes, we limit the lifetime to the minimal
# allowed value of 60s (see draft-ietf-core-resource-directory-11, Table 2)
# For debugging and demonstration purposes, we limit the lifetime to just one
# minute
RD_LT ?= 60
# Set CONFIG_CORD_LT only if not being set via Kconfig

2
examples/cord_epsim/README.md
View File

@ -3,7 +3,7 @@ CoRE Resource Directory: Simple Endpoint Example
This example shows how a node can register with a CoRE resource directory using
the simple registration procedure as described in
draft-ietf-core-resource-directory-15, section 5.3.1.
draft-ietf-core-resource-directory-27, section 5.1.
When running this example, you **must** define the RD server's IPv6 address
statically, using the `RD_ADDR` environment variable:

4
examples/cord_lc/README.md
View File

@ -4,7 +4,7 @@ CoRE Resource Directory: Lookup Example
This example application demonstrates the usage of RIOT's Resource Directory
(RD) lookup module, called `cord_lc`. This module supports the lookup of
resources and endpoints as defined in
[draft-ietf-core-resource-directory-20](https://tools.ietf.org/html/draft-ietf-core-resource-directory-23).
[draft-ietf-core-resource-directory-27](https://tools.ietf.org/html/draft-ietf-core-resource-directory-27).
The lookup can be done in two modes: a) raw: result of the lookup is returned
as is. b) pre-parsed: result of the lookup is parsed and only one link is
returned for each call.
@ -13,4 +13,4 @@ Usage
=====
The examples includes a shell command that you can use to interact with a given
RD, called `cord_lc`. Simply use that shell command without parameters for
more information on its usage.
more information on its usage.

4
sys/include/net/cord/ep.h
View File

@ -14,8 +14,8 @@
* This module implements a CoRE Resource Directory endpoint library, that
* allows RIOT nodes to register themselves with resource directories.
* It implements the standard endpoint functionality as defined in
* draft-ietf-core-resource-directory-15.
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-15
* draft-ietf-core-resource-directory-27.
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-27
*
* # Design Decisions
* - all operations provided by this module are fully synchronous, meaning that

4
sys/include/net/cord/lc.h
View File

@ -15,8 +15,8 @@
* allows RIOT nodes to lookup resources, endpoints and groups with resource
* directories.
* It implements the standard lookup functionality as defined in
* draft-ietf-core-resource-directory-23.
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-23
* draft-ietf-core-resource-directory-27.
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-27
*
* ## Lookup modes
*

10
sys/net/application_layer/cord/doc.txt
View File

@ -15,11 +15,11 @@
* # About
* 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 `draft-ietf-core-resource-directory-15`.
* (RDs) as defined in `draft-ietf-core-resource-directory-27`.
*
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-15
* @see https://tools.ietf.org/html/draft-ietf-core-resource-directory-27
*
* `draft-ietf-core-resource-directory-15` defines two types different roles for
* `draft-ietf-core-resource-directory-27` defines two types different roles for
* nodes when interacting with a RD:
* - `endpoint`: registers and manages entries at the RD
* - `client`: performs different kind of lookups
@ -39,7 +39,7 @@
* | EP |---- | |
* +----+
* ```
* Figure copied form `draft-ietf-core-resource-directory-15`.
* Figure copied form `draft-ietf-core-resource-directory-27`.
*
* @note In the context of this module, we refer to these roles as `endpoint
* (ep)` and `lookup client (lc)`. This should hopefully prevent some
@ -49,7 +49,7 @@
* # Structure
*
* This module is structured in a number of submodules with goal to reflect the
* different roles described in `draft-ietf-core-resource-directory-15`:
* different roles described in `draft-ietf-core-resource-directory-27`:
*
* - `cord_ep`: standard endpoint implementation following the rules as
* defined i.a. in sections 5.2, 5.3, A.1, and A.2