Document: draft-ietf-core-dns-over-coap Title: DNS over CoAP (DoC) Reviewer: Vladimír Čunát Review result: Ready dnsdir assigned me reviewing this draft. I found no issues in there, except a nit below. Note that my knowledge around constrained systems (including CoAP) is close to zero, so I could easily miss issues in those aspects. I've read through this whole document and glanced at some related constrained stuff. Aside: I'd think that DNS people in IETF mostly won't be thrilled to have yet another transport for DNS, but I understand that the current DNS encryption options aren't great for such very constrained use cases, and I don't expect DoC to become common outside of those cases. Nit: some examples use `ARCOUNT` and some don't. I'd suggest to unify all to `ADDITIONAL`. -- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx
