[DNSOP] Dnsdir last call review of draft-ietf-dnsop-glue-is-not-optional-08

Nicolai Leymann via Datatracker <noreply@ietf.org> Thu, 11 May 2023 11:37 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: dnsop@ietf.org
Delivered-To: dnsop@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9388DC151B26; Thu, 11 May 2023 04:37:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Nicolai Leymann via Datatracker <noreply@ietf.org>
To: dnsdir@ietf.org
Cc: dnsop@ietf.org, draft-ietf-dnsop-glue-is-not-optional.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 10.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <168380503358.28686.13554617137283468068@ietfa.amsl.com>
Reply-To: Nicolai Leymann <n.leymann@telekom.de>
Date: Thu, 11 May 2023 04:37:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3sk4kAOou2ITQ6luTqRpJ4L3Gos>
Subject: [DNSOP] Dnsdir last call review of draft-ietf-dnsop-glue-is-not-optional-08
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 May 2023 11:37:13 -0000

Reviewer: Nicolai Leymann
Review result: Ready


I was assigned as the dnsdir reviewer for ietf-dnsop-glue-is-not-optional.

The document is on standards track and describes the DNS Glue requirements in
Referral Responses. It updates RFC1034 (one of the core RFCs for DNS). The
draft is well written and easy to understand.  The document is ready for

Major issues:

Minor issues:

  RFC1034 uses "in domain" (section 3.5) but the proposed change uses