[DNSOP] Robert Wilton's No Objection on draft-ietf-dnsop-rfc5933-bis-12: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Fri, 25 November 2022 10:03 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 C4ACEC14F726; Fri, 25 Nov 2022 02:03:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dnsop-rfc5933-bis@ietf.org, dnsop-chairs@ietf.org, dnsop@ietf.org, tjw.ietf@gmail.com, tjw.ietf@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 9.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <166937058379.567.14301207829347677888@ietfa.amsl.com>
Date: Fri, 25 Nov 2022 02:03:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JZKw9gqgekqIZrzGwcLDweWX1xo>
Subject: [DNSOP] Robert Wilton's No Objection on draft-ietf-dnsop-rfc5933-bis-12: (with COMMENT)
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: Fri, 25 Nov 2022 10:03:03 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-dnsop-rfc5933-bis-12: 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-rfc5933-bis/



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

I support Roman's discuss.

I would rather see this document be published by the ISE than go through the
IETF stream.  My specific concern is than an operator who reads this RFC and
doesn't know the context may not be aware that this may be an inappropriate
algorithm to use.  Even if this is published via the ISE channel then I think
that it should be stated very clearly early in the document that the
cryptographic properties haven't been independently verified.

Regards,
Rob