[dnsdir] Dnsdir early review of draft-ietf-core-dns-over-coap-01

Tim Wicinski via Datatracker <noreply@ietf.org> Thu, 22 December 2022 17:12 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsdir@ietf.org
Delivered-To: dnsdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 537B3C1516E5; Thu, 22 Dec 2022 09:12:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tim Wicinski via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
Cc: core@ietf.org, draft-ietf-core-dns-over-coap.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.4.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <167172912731.30303.7478512800074751429@ietfa.amsl.com>
Reply-To: Tim Wicinski <tjw.ietf@gmail.com>
Date: Thu, 22 Dec 2022 09:12:07 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsdir/Z6muT0kb4IgRcbkALMLcfXkHAps>
Subject: [dnsdir] Dnsdir early review of draft-ietf-core-dns-over-coap-01
X-BeenThere: dnsdir@ietf.org
X-Mailman-Version: 2.1.39
List-Id: DNS Directorate <dnsdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsdir>, <mailto:dnsdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsdir/>
List-Post: <mailto:dnsdir@ietf.org>
List-Help: <mailto:dnsdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsdir>, <mailto:dnsdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2022 17:12:07 -0000

Reviewer: Tim Wicinski
Review result: On the Right Track



I'm doing an early review of draft-ietf-core-dns-over-coap
for the DNS Directorate.  This is only an early review.

Status:  On the right track, but should have another review or reviews
as it reaches WGLC status.

While this draft is focused on the communication between a DNS-over-CoAP client
and DNS-over-CoAP server, the communication between the DNS-over-CoAP Server 
and the "DNS Server" is done using DNS-over-DTLS, which the DNS community has
not seen implementations in use.  The whole communication between the 
the DoC Server and the "DNS Server" should be expanded upon.   

The document talks about "DNS Server" but it needs to be more precise - is this
a DNS Recursive Resolver, Stub Resolver or DNS Authorative Server?  The document
needs to be more precise about this.  Please see 
https://www.rfc-editor.org/rfc/rfc8499#page-16 for more details. 

Before WGLC, from the DNS perspective a working implementation for observation.
While the authors and WG may feel that this DNS interaction will be 
constrained to the CoAP environment, but those who operate DNS
infrastructure will feel this may be wishful thinking.