[Add] Intdir last call review of draft-ietf-add-ddr-08
Juan-Carlos Zúñiga via Datatracker <noreply@ietf.org> Tue, 12 July 2022 19:23 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: add@ietf.org
Delivered-To: add@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD0EC157B39; Tue, 12 Jul 2022 12:23:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Juan-Carlos Zúñiga via Datatracker <noreply@ietf.org>
To: int-dir@ietf.org
Cc: add@ietf.org, draft-ietf-add-ddr.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <165765381817.5748.9738074002267876777@ietfa.amsl.com>
Reply-To: Juan-Carlos Zúñiga <juzuniga@cisco.com>
Date: Tue, 12 Jul 2022 12:23:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/qy1MEiNgx0Ec5dsPkko3faxqrWU>
Subject: [Add] Intdir last call review of draft-ietf-add-ddr-08
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2022 19:23:38 -0000
Reviewer: Juan-Carlos Zúñiga Review result: Ready with Issues I am an assigned INT directorate reviewer for <draft-ietf-add-ddr-08>. These comments were written primarily for the benefit of the Internet Area Directors. Document editors and shepherd(s) should treat these comments just like they would treat comments from any other IETF contributors and resolve them along with any other Last Call comments that have been received. For more details on the INT Directorate, see https://datatracker.ietf.org/group/intdir/about/. >From Section 1 Introduction, it is not obvious if the two mechanisms mentioned in the section are alternative or complementary, and how they relate to the DoT, DoQ and DoH requirements introduced in the same section. Section 4 gets into details about DoT and DoQ using IP addresses - it would be good to explain a little more about it in the Intro section. In Section 5, the requirements seem to overlap with draft-ietf-add-svcb-dns. It would be good to further clarify the relationship between the two specifications. Finally, since multiple solutions are presented, some recommendations about when, how and why one mechanism should be used vs the other would be useful to the reader. Best, Juan-Carlos
- [Add] Intdir last call review of draft-ietf-add-d… Juan-Carlos Zúñiga via Datatracker