Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resolve and comment out TODOs #16

Merged
merged 2 commits into from
Feb 25, 2024
Merged

Resolve and comment out TODOs #16

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
85b95f8
fix: resolve unnecessary TODOs
JKRhb Feb 25, 2024
97620a3
chore: comment out remaining TODOs in the document
JKRhb Feb 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 5 additions & 11 deletions draft-romann-mud-constrained.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,8 @@ entity:
--- abstract
This document specifies additional ways for discovering and emitting
Manufacturer Usage Descriptions (MUD), especially in constrained environments,
utilizing the Constrained Application Protocol (CoAP).

TODO: Should be updated.
utilizing the Constrained Application Protocol (CoAP), CoRE Resource Discovery,
and CBOR Web Tokens.

--- middle

Expand All @@ -66,15 +65,12 @@ Furthermore, this document specifies a method of encoding MUD URLs in (signed)
CBOR Web Tokens (CWTs) {{!RFC8392}}, which allows MUD managers to better validate the
authenticity of both the URL itself and the associated MUD file.

The rest of this document is structured as follows: ... TODO

## Terminology

{::boilerplate bcp14}

Building upon the terminology defined in {{!RFC8520}}, this specification introduces the following additional terms:

TODO. (Remove if there are no additional terms.)
This specification re-uses the terminology defined in {{!RFC8520}}.
<!-- Additionally, it introduces following terms: TODO -->

# Architecture

Expand Down Expand Up @@ -104,7 +100,7 @@ COAP GET request to a well-known URI via multicast.
Note that the protocol used for communication between the MUD Receiver and
MUD Manager is not specified in this document and implementation-specific.

TODO: Refine diagram
<!-- TODO: Refine diagram -->

<!--
TODO: Fix once plantuml is included in the GitHub Actions Docker image.
Expand Down Expand Up @@ -307,8 +303,6 @@ In addition to the registration endpoint defined in {{?RFC9176}}, MUD managers M

# Obtaining a MUD URL in Constrained Environments

<!-- TODO: This can probably be improved -->

With the additional mechanisms for finding MUD URLs introduced in this document, MUD managers can be configured to play a more active role in discovering MUD-enabled devices.
Furthermore, IoT devices could identify their peers based on a MUD URL associated with these devices or perform a configuration process based on the linked MUD file's contents.
However, the IoT devices themselves also have more options for exposing their MUD URLs more actively, using, for instance, a MUD manager's registration interface.
Expand Down
Loading