@@ -4,7 +4,7 @@ coding: utf-8
44
55title : Using MUD in Constrained Environments
66abbrev : MUD and CoAP
7- docname : draft-romann-mud-constrained-latest
7+ docname : draft-romann-iotops- mud-constrained-latest
88
99category : info # std is not allowed for independent submissions, as it seems
1010submissiontype : independent
@@ -28,7 +28,6 @@ author:
2828 -
2929 ins : H. Damer
3030 name : Hugo Hakim Damer
31- organization : Universität Bremen
32313332 role : editor
3433 country : Germany
@@ -41,6 +40,7 @@ author:
4140
4241entity :
4342 SELF : " [RFC-XXXX]"
43+ ...
4444
4545--- abstract
4646This document specifies additional ways for discovering and emitting
@@ -101,7 +101,7 @@ the MUD URLs) may initiate the MUD discovery process:
101101The Thing can contact and register with MUD URL recipients, e.g. by sending a
102102CoAP POST request via Multicast and/or addressing a well-known registration endpoint.
103103Conversely, a MUD Receiver can initiate the discovery process, e.g. by sending a
104- COAP GET request to a well-known URI via multicast.
104+ CoAP GET request to a well-known URI via multicast.
105105
106106Note that the protocol used for communication between the MUD Receiver and
107107MUD Manager is considered out of scope for this document and is considered
@@ -170,7 +170,7 @@ If the other self description format or its method of distribution provides mean
170170In this specification, we will describe how to embed a MUD URL into a CoRE Link
171171Format {{!RFC6690}} resource, which may itself be retrieved directly from the device or through
172172a CoRE Resource Directory {{!RFC9176}}.
173- Additionally, we will define dedicated COAP resources both for providing and receiving MUD URLs.
173+ Additionally, we will define dedicated CoAP resources both for providing and receiving MUD URLs.
174174
175175<!--
176176TODO embed the chapter numbers into the previous paragraph once these chapters are properly refactored
0 commit comments