[DNSOP]Paul Wouters' Yes on draft-ietf-dnsop-dnssec-bootstrapping-10: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Mon, 27 May 2024 17:39 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 2F11BC14F71C; Mon, 27 May 2024 10:39:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171683154418.44497.18321850753241713647@ietfa.amsl.com>
Date: Mon, 27 May 2024 10:39:04 -0700
Message-ID-Hash: BX2G2PKLTRWAE2V4MNSVKR3XM26NLW2W
X-Message-ID-Hash: BX2G2PKLTRWAE2V4MNSVKR3XM26NLW2W
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dnsop.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-dnsop-dnssec-bootstrapping@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Subject: [DNSOP]Paul Wouters' Yes on draft-ietf-dnsop-dnssec-bootstrapping-10: (with COMMENT)
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IX7gvxOan-TfkcX0A_hQXIuOCSQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Owner: <mailto:dnsop-owner@ietf.org>
List-Post: <mailto:dnsop@ietf.org>
List-Subscribe: <mailto:dnsop-join@ietf.org>
List-Unsubscribe: <mailto:dnsop-leave@ietf.org>

Paul Wouters has entered the following ballot position for
draft-ietf-dnsop-dnssec-bootstrapping-10: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-dnssec-bootstrapping/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing all my DICSUSS items and comments. I have updated my ballot to Yes,

One last comment left on the new text:

       If all else fails, the domain owner might have to request the removal of
        all DS records (e.g., by using the special-value CDS/CDNSKEY RRset
        specified in [RFC8078] Section 4) and have the transfer performed

I think the "e.g." sentence should be removed. This is "in case the dns operator
is not cooperating", so in that case one would assume they wouldn't update these
records either (and the domain owner would need to go through their registrar
website, which would cause the records to be removed at the parent via EPP.