Re: [netconf] netconf-tls wasRe: Summary of updates

Kent Watsen <kent+ietf@watsen.net> Wed, 26 May 2021 14:11 UTC

Return-Path: <01000179a904608d-c11a7d4b-c1de-4351-a52f-78a8783d5915-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0B63A2FD6 for <netconf@ietfa.amsl.com>; Wed, 26 May 2021 07:11:53 -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, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 7egwMXjIx_h4 for <netconf@ietfa.amsl.com>; Wed, 26 May 2021 07:11:48 -0700 (PDT)
Received: from a48-110.smtp-out.amazonses.com (a48-110.smtp-out.amazonses.com [54.240.48.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EF0B3A2FD5 for <netconf@ietf.org>; Wed, 26 May 2021 07:11:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1622038307; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:Feedback-ID; bh=+J1gq142N9qQ7JbPXPBbTGMtmWCdlB+fMW20CJsrvm4=; b=B+6fXlxevDhUPgIPDxYCJ7qc89NgRz5Iro4kmRoEhbXqhlmvr7czi1sHkE9why6t 3qnBV2l9B5qCGwwg2GmydLi9zwlE8tsFawaL4bXS10RGtVPzOhq3X8LTq6oLNK1KSIi bFd+Wt+bqG4uggvg9PLKIzD6xdNghnJ5dEq9P/2o=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Kent Watsen <kent+ietf@watsen.net>
In-Reply-To: <20210526063920.jvs7acjnhma4uimm@anna.jacobs.jacobs-university.de>
Date: Wed, 26 May 2021 14:11:47 +0000
Cc: tom petch <ietfc@btconnect.com>, "netconf@ietf.org" <netconf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <01000179a904608d-c11a7d4b-c1de-4351-a52f-78a8783d5915-000000@email.amazonses.com>
References: <0100017980c49236-7975b99d-b591-4da2-a118-f6598517c4e5-000000@email.amazonses.com> <AM7PR07MB624835D8BE54144D97221817A02B9@AM7PR07MB6248.eurprd07.prod.outlook.com> <010001798c0d947e-4d2d14f5-9f0e-450d-ac99-e18c260f0c2b-000000@email.amazonses.com> <AM7PR07MB6248FF0E1E5A053D4FA2BDC4A0299@AM7PR07MB6248.eurprd07.prod.outlook.com> <01000179a0aa5d37-4810234e-8db2-434d-b8fa-780c1648955a-000000@email.amazonses.com> <AM7PR07MB624888AD4CB3C09809B22702A0259@AM7PR07MB6248.eurprd07.prod.outlook.com> <01000179a5bdc371-b665451f-61d4-4364-9d55-e9369f3adc8e-000000@email.amazonses.com> <20210526063920.jvs7acjnhma4uimm@anna.jacobs.jacobs-university.de>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2021.05.26-54.240.48.110
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/eyYpMndFBfWwlLdY39R5SqR21E4>
Subject: Re: [netconf] netconf-tls wasRe: Summary of updates
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 14:11:54 -0000

>>   Any version of TLS may be configured.  TLS 1.0 [RFC2246] and TLS 1.1
>>   [RFC4346] are historic and hence the YANG "feature" statements
>>   enabling them are marked "status obsolete".  TLS 1.2 [RFC5246] is
>>   obsoleted by TLS 1.3 [RFC8446] but still is common use, and hence its
>>   "feature" statement is marked "status obsolete".  All the "feature"
> 
> I think it should say deprecated for TLS 1.2 since this is what the
> YANG definitions say

Yes. It was only an issue in the Introduction section, as the YANG had/has 1.2 as “deprecated".


> (I guess a typo, and change 'is common use' to
> 'in common use').

Quite right, fixed.


K.