Re: [secdir] [Last-Call] Secdir last call review of draft-ietf-netconf-crypto-types-20

Kent Watsen <kent+ietf@watsen.net> Tue, 14 September 2021 17:03 UTC

Return-Path: <0100017be5436c1b-801549ca-b4b1-41a1-bdb7-9f1429d5450e-000000@amazonses.watsen.net>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 463A73A2617; Tue, 14 Sep 2021 10:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRQbKS3SXzrZ; Tue, 14 Sep 2021 10:03:28 -0700 (PDT)
Received: from a8-33.smtp-out.amazonses.com (a8-33.smtp-out.amazonses.com [54.240.8.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A87F3A25F4; Tue, 14 Sep 2021 10:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1631639006; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=/qTu0gko4n78ZLG8HUkUWwrP6gRickBCG3+vXbGLNTw=; b=ZelKVeOs82YY6jbIx7W0IdbWCXO1CNUaKqJGn1zXfLMumqWieat07sKhlCsLJ/J6 TTxXutOjs3ZO3ZRqKQhqeWZHcOB2+KczwbpIhdFstC2jnYf8nwU/WdtiaHzqkpKGknc y7JUMRhxGyFlvv/27IrSOK1k+wqf+uqeEf0JnNJ8=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100017be5436c1b-801549ca-b4b1-41a1-bdb7-9f1429d5450e-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE1235DC-76E4-4762-8E0D-21D7398B92E5"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Tue, 14 Sep 2021 17:03:26 +0000
In-Reply-To: <0cc201d7a979$10ab7cd0$32027670$@smyslov.net>
Cc: secdir@ietf.org, draft-ietf-netconf-crypto-types.all@ietf.org, "netconf@ietf.org" <netconf@ietf.org>
To: Valery Smyslov <valery@smyslov.net>
References: <162982978380.3381.17549750696257276827@ietfa.amsl.com> <0100017b8819bf19-1f20d528-72e4-462c-884a-6c29eff0769b-000000@email.amazonses.com> <017c01d79b5e$a00a0000$e01e0000$@smyslov.net> <0100017b89613006-504db539-c16c-4c87-8772-2b6676e9c295-000000@email.amazonses.com> <034d01d79e3d$a5b5d5b0$f1218110$@smyslov.net> <0100017be4ba7624-b2b8c900-5ee4-431a-b902-422a4576bd62-000000@email.amazonses.com> <0cc201d7a979$10ab7cd0$32027670$@smyslov.net>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.09.14-54.240.8.33
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/GfFamx9SeSjFWApo2n6KdPkRl2s>
Subject: Re: [secdir] [Last-Call] Secdir last call review of draft-ietf-netconf-crypto-types-20
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2021 17:03:45 -0000

Hi Valery,


>             Implementations SHOULD only use transport algorithms to those 
> 
>           s/transport algorithms/secure transport/
> 
> That substitution by itself seems to result in an incomplete sentence.  How about this:  
>  
>           "Implementations SHOULD only use secure transport algorithms meeting local policy.”
>  
>           I was trying to avoid using combination of words “transport algorithm”
>           just to make text more accurate (usually we have transport protocols,
>           which are implemented using some crypto algorithms, if we talk
>           about secure transports). So how about:
>  
>           Implementations SHOULD only use secure transport protocols meeting local policy.
>  
>           ?


Done.



> I removed the last sentence but did NOT add “a few words”, because the existing text already covers the “need to stay current” angle.  The current “last” paragraph reads:
>  
>             Implementations SHOULD only use secure transport algorithms 
>             meeting local policy.  A reasonable policy may, e.g., state that
>             only ciphersuites listed as "recommended" by the IETF be used.
> 
> Good?
>  
>           Works for me if you replace “algorithms” with “protocols” :-)
> 

Done (per above)

>           (I still think that referencing RFC 7525 would be helpful, but it’s up to you, it’s definitely not a big deal).
> 

Added.   Resulting diffs here: https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-crypto-types-21.txt <https://www.ietf.org/rfcdiff?url2=draft-ietf-netconf-crypto-types-21.txt>


>           Thank you,
>           Valery.
> 

No, thank you!  :)

K.