[DNSOP] Francesca Palombini's No Objection on draft-ietf-dnsop-nsec3-guidance-08: (with COMMENT)

Francesca Palombini via Datatracker <noreply@ietf.org> Tue, 10 May 2022 17:41 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 0011CC14F742; Tue, 10 May 2022 10:41:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francesca Palombini via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnsop-nsec3-guidance@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com, tjw.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Francesca Palombini <francesca.palombini@ericsson.com>
Message-ID: <165220448399.21295.16946574580416938307@ietfa.amsl.com>
Date: Tue, 10 May 2022 10:41:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SBEfIbLLFbHLXaQk50yuNxOKm94>
Subject: [DNSOP] Francesca Palombini's No Objection on draft-ietf-dnsop-nsec3-guidance-08: (with COMMENT)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 10 May 2022 17:41:24 -0000

Francesca Palombini has entered the following ballot position for
draft-ietf-dnsop-nsec3-guidance-08: No Objection

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-nsec3-guidance/



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

Thank you for the work on this document.

Before reading Alvaro's comment, I was going to bring up that the following
paragraph in Section 3.2 could be confusing for a reader who is aware of the
"Updates" RFC header.

   Note that this specification updates [RFC5155] by significantly
   decreasing the requirements originally specified in Section 10.3 of
   [RFC5155].  See the Security Considerations for arguments on how to
   handle responses with non-zero iteration count.

I see that Alvaro is questioning if this doc should actually update 5155, I
personally don't have a strong opinion, and don't think it is absolutely
necessary, although I am curious to hear if there has been discussion in the
community about it. In any case I think it would be good to rephrase the above
paragraph to avoid saying that this doc updates 5155 when it doesn't.

Thanks,
Francesca