The application use case of DoC is inspired by DNS over HTTPS [RFC8484]
(DoH). DoC, however, aims for the deployment in the constrained Internet of
Things (IoT), which usually conflicts with the requirements introduced by
-HTTPS.¶
+HTTPS.
+Constrained IoT devices may be restricted in memory, power consumption,
+link layer frame sizes, throughput, and latency. They may
+only have a handful kilobytes of both RAM and ROM. They may sleep for long
+durations of time, after which they need to refresh the named resources they
+know about. Name resolution in such scenarios must take into account link
+layer frame sizes of only a few hundred bytes, bit rates in the magnitute
+of kilobits per second, and latencies of several seconds [RFC7228].¶
To prevent TCP and HTTPS resource requirements, constrained IoT devices
could use DNS over DTLS [RFC8094]. In contrast to DNS over DTLS, DoC
utilizes CoAP features to mitigate drawbacks of datagram-based
@@ -1448,12 +1439,14 @@
TBD DNR Service Parameters + SVCB Resource Records (also see #22):¶
+Lenders, M., Amsüss, C., Gündogan, C., Nawrocki, M., Schmidt, T., and M. Wählisch, "Securing Name Resolution in the IoT: DNS over CoAP", Association for Computing Machinery (ACM), Proceedings of the ACM on Networking vol. 1, no. CoNEXT2, pp. 1-25, DOI 10.1145/3609423, , <https://doi.org/10.1145/3609423>.
+
[I-D.ietf-add-dnr]
Boucadair, M., Reddy.K, T., Wing, D., Cook, N., and T. Jensen, "DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)", Work in Progress, Internet-Draft, draft-ietf-add-dnr-16, , <https://datatracker.ietf.org/doc/html/draft-ietf-add-dnr-16>.
The authors of this document presented the design, implementation, and analysis of DoC in their
+paper "Securing Name Resolution in the IoT: DNS over CoAP" [DoC-paper].¶
diff --git a/draft-ietf-core-dns-over-coap.txt b/draft-ietf-core-dns-over-coap.txt
index b9242b1..2cad256 100644
--- a/draft-ietf-core-dns-over-coap.txt
+++ b/draft-ietf-core-dns-over-coap.txt
@@ -3,16 +3,16 @@
CoRE M. S. Lenders
-Internet-Draft FU Berlin
+Internet-Draft TU Dresden
Intended status: Standards Track C. Amsüss
-Expires: 11 January 2024
+Expires: 25 April 2024
C. Gündoğan
Huawei Technologies
T. C. Schmidt
HAW Hamburg
M. Wählisch
- FU Berlin
- 10 July 2023
+ TU Dresden & Barkhausen Institut
+ 23 October 2023
DNS over CoAP (DoC)
@@ -53,7 +53,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
- This Internet-Draft will expire on 11 January 2024.
+ This Internet-Draft will expire on 25 April 2024.
Copyright Notice
@@ -99,11 +99,13 @@ Table of Contents
10. References
10.1. Normative References
10.2. Informative References
- Appendix A. Change Log
- A.1. Since draft-ietf-core-dns-over-coap-02
- A.2. Since draft-ietf-core-dns-over-coap-01
- A.3. Since draft-ietf-core-dns-over-coap-00
- A.4. Since draft-lenders-dns-over-coap-04
+ Appendix A. Evaluation
+ Appendix B. Change Log
+ B.1. Since draft-ietf-core-dns-over-coap-03
+ B.2. Since draft-ietf-core-dns-over-coap-02
+ B.3. Since draft-ietf-core-dns-over-coap-01
+ B.4. Since draft-ietf-core-dns-over-coap-00
+ B.5. Since draft-lenders-dns-over-coap-04
Acknowledgments
Authors' Addresses
@@ -120,7 +122,14 @@ Table of Contents
The application use case of DoC is inspired by DNS over HTTPS
[RFC8484] (DoH). DoC, however, aims for the deployment in the
constrained Internet of Things (IoT), which usually conflicts with
- the requirements introduced by HTTPS.
+ the requirements introduced by HTTPS. Constrained IoT devices may be
+ restricted in memory, power consumption, link layer frame sizes,
+ throughput, and latency. They may only have a handful kilobytes of
+ both RAM and ROM. They may sleep for long durations of time, after
+ which they need to refresh the named resources they know about. Name
+ resolution in such scenarios must take into account link layer frame
+ sizes of only a few hundred bytes, bit rates in the magnitute of
+ kilobits per second, and latencies of several seconds [RFC7228].
To prevent TCP and HTTPS resource requirements, constrained IoT
devices could use DNS over DTLS [RFC8094]. In contrast to DNS over
@@ -444,13 +453,13 @@ Table of Contents
Level of maturity: production
- Version compability: draft-ietf-core-dns-over-coap-02
+ Version compability: draft-ietf-core-dns-over-coap-04
License: LGPL-2.1
Contact information: Martine Lenders
- Last update of this information: March 2023
+ Last update of this information: October 2023
7.2. DoC Server
@@ -459,13 +468,13 @@ Table of Contents
Level of maturity: production
- Version compability: draft-ietf-core-dns-over-coap-02
+ Version compability: draft-ietf-core-dns-over-coap-04
License: MIT
Contact information: Martine Lenders
- Last update of this information: March 2023
+ Last update of this information: October 2023
8. Security Considerations
@@ -567,6 +576,14 @@ Table of Contents
10.2. Informative References
+ [DoC-paper]
+ Lenders, M., Amsüss, C., Gündogan, C., Nawrocki, M.,
+ Schmidt, T., and M. Wählisch, "Securing Name Resolution in
+ the IoT: DNS over CoAP", Association for Computing
+ Machinery (ACM), Proceedings of the ACM on Networking vol.
+ 1, no. CoNEXT2, pp. 1-25, DOI 10.1145/3609423, September
+ 2023, .
+
[I-D.ietf-add-dnr]
Boucadair, M., Reddy.K, T., Wing, D., Cook, N., and T.
Jensen, "DHCP and Router Advertisement Options for the
@@ -578,9 +595,9 @@ Table of Contents
[I-D.ietf-core-href]
Bormann, C. and H. Birkholz, "Constrained Resource
Identifiers", Work in Progress, Internet-Draft, draft-
- ietf-core-href-12, 6 March 2023,
+ ietf-core-href-13, 10 July 2023,
.
+ href-13>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66,
@@ -629,9 +646,24 @@ Table of Contents
DOI 10.17487/RFC9250, May 2022,
.
-Appendix A. Change Log
+Appendix A. Evaluation
+
+ The authors of this document presented the design, implementation,
+ and analysis of DoC in their paper "Securing Name Resolution in the
+ IoT: DNS over CoAP" [DoC-paper].
+
+Appendix B. Change Log
+
+B.1. Since draft-ietf-core-dns-over-coap-03
+ (https://datatracker.ietf.org/doc/html/draft-ietf-core-dns-over-
+ coap-03)
+
+ * Amended Introduction with short contextualization of constrained
+ environments
+
+ * Add Appendix A on evaluation
-A.1. Since draft-ietf-core-dns-over-coap-02
+B.2. Since draft-ietf-core-dns-over-coap-02
(https://datatracker.ietf.org/doc/html/draft-ietf-core-dns-over-
coap-02)
@@ -653,7 +685,7 @@ A.1. Since draft-ietf-core-dns-over-coap-02
* Don't call OSCORE end-to-end encrypted
-A.2. Since draft-ietf-core-dns-over-coap-01
+B.3. Since draft-ietf-core-dns-over-coap-01
(https://datatracker.ietf.org/doc/html/draft-ietf-core-dns-over-
coap-01)
@@ -666,7 +698,7 @@ A.2. Since draft-ietf-core-dns-over-coap-01
* Add appendix on reference implementation
-A.3. Since draft-ietf-core-dns-over-coap-00
+B.4. Since draft-ietf-core-dns-over-coap-00
(https://datatracker.ietf.org/doc/html/draft-ietf-core-dns-over-
coap-00)
@@ -680,7 +712,7 @@ A.3. Since draft-ietf-core-dns-over-coap-00
* Add security considerations on ID=0
-A.4. Since draft-lenders-dns-over-coap-04
+B.5. Since draft-lenders-dns-over-coap-04
(https://datatracker.ietf.org/doc/html/draft-lenders-dns-over-
coap-04)
@@ -694,11 +726,11 @@ Acknowledgments
Authors' Addresses
Martine Sophie Lenders
- Freie Universität Berlin
- Takustrasse 9
- D-14195 Berlin
+ TUD Dresden University of Technology
+ Helmholtzstr. 10
+ D-01069 Dresden
Germany
- Email: m.lenders@fu-berlin.de
+ Email: martine.lenders@tu-dresden.de
Christian Amsüss
@@ -722,8 +754,8 @@ Authors' Addresses
Matthias Wählisch
- Freie Universität Berlin
- Takustrasse 9
- D-14195 Berlin
+ TUD Dresden University of Technology & Barkhausen Institut
+ Helmholtzstr. 10
+ D-01069 Dresden
Germany
- Email: m.waehlisch@fu-berlin.de
+ Email: m.waehlisch@tu-dresden.de