sys/cord/doc.txt: Update additional references to RFC 9176 #21159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Area: network
mguetschow
added
the
CI: ready for build
|
Thanks! Looks like there are some unrelated commits in this PR, would you mind rebasing and dropping them? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description:
This PR updates the doc file of the
CORDmodule in RIOT. Updates:Testing procedure:
cord_epandcord_epsimsubmodules seemed not to be correct, not only for the RFC 9176, but also for the draft-ietf-core-resource-directory-27. Consequently, since the draft-ietf-core-resource-directory-15 was the original version used before the reference update to the draft-ietf-core-resource-directory-27, it was compared with it and was found out that the references are valid for draft-ietf-core-resource-directory-15 . During the reference update from draft-ietf-core-resource-directory-15 to draft-ietf-core-resource-directory-27 they were seemingly not included in the updating process.Issues/PRs references: