IETF Logo Mail Archive

Re: [netconf] IANA templates for algorithms

"Salz, Rich" <rsalz@akamai.com> Wed, 19 February 2020 01:06 UTC

Return-Path: <rsalz@akamai.com>
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 6A3131208A3 for <netconf@ietfa.amsl.com>; Tue, 18 Feb 2020 17:06:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 1CU1pmlztlk2 for <netconf@ietfa.amsl.com>; Tue, 18 Feb 2020 17:06:21 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97C81120898 for <netconf@ietf.org>; Tue, 18 Feb 2020 17:06:21 -0800 (PST)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id 01J128j1014548; Wed, 19 Feb 2020 01:06:21 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=NLj487tdcL3ZD04GbWaQNleZuDrEQBA5nQmc8BjiZ7g=; b=Hp+UxsHjtzzMWsODvM2ravJd/NKe9RXIIZf981rSPzFchLuexrBoH1hT9sTKW7dfDzRL qvjoydvnBGvsh/TU9OFMWmy58D8MnZDlSDwfBOMjHwYp9r4tpWd2StFL51iZ86tsZ7EF bFrHx7r1gC2Vjt5yPy9fNTHhsOZGi20VSgpgy1vjXr4VRccvQcnUGcagecCZyZtpOKnE 19ZWZx2Epr2lgD5QfEq2JZSnyobG7KKqzxmsnot8X4DPLhHnHFZ+c1TCPVhfmUONoLxA /hJbloM42zxYDX8t4l0Cll9gGE4GXq+9o8s+pv6nhuwQbZ1vQgnEDo1O9s3kX6JqNjjB iQ==
Received: from prod-mail-ppoint8 (prod-mail-ppoint8.akamai.com [96.6.114.122] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2y68sf6sgk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 19 Feb 2020 01:06:21 +0000
Received: from pps.filterd (prod-mail-ppoint8.akamai.com [127.0.0.1]) by prod-mail-ppoint8.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 01J1367m015015; Tue, 18 Feb 2020 20:06:20 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint8.akamai.com with ESMTP id 2y6cv2tc51-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 18 Feb 2020 20:06:20 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 18 Feb 2020 20:06:18 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Tue, 18 Feb 2020 20:06:18 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Kent Watsen <kent+ietf@watsen.net>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: IANA templates for algorithms
Thread-Index: AQHV5rp+7/ibLSq920GDrcD49mcMyKghtB8A
Date: Wed, 19 Feb 2020 01:06:18 +0000
Message-ID: <8713517D-96E9-45CF-8ABF-8691581A8F89@akamai.com>
References: <010001705ad1e8a3-891d7081-80c2-4a0d-857e-f6242b1a8793-000000@email.amazonses.com>
In-Reply-To: <010001705ad1e8a3-891d7081-80c2-4a0d-857e-f6242b1a8793-000000@email.amazonses.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.22.0.200209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.114.104]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4C6C046D76918846963E04FD3ADA6EE2@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-02-18_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=834 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-2002050000 definitions=main-2002190003
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-02-18_08:2020-02-18, 2020-02-18 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 impostorscore=0 spamscore=0 clxscore=1011 phishscore=0 lowpriorityscore=0 adultscore=0 bulkscore=0 mlxlogscore=806 malwarescore=0 mlxscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2001150001 definitions=main-2002190002
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/shv2KZIOgufw7L53UKSjEk-i1Tk>
Subject: Re: [netconf] IANA templates for algorithms
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, 19 Feb 2020 01:06:28 -0000

>    Neither of these registries help us, at least not directly.  Yes, they provide enumerations for on-the-wire protocol values, but they fail to provide an enumeration for, e.g., a 2048-bit RSA key.
  
Yes, RSA size is not relevant to the protocols.

>        2) engage an "expert reviewer" to see if any of the new entries
            regard an undefined algorithm and, if so, a TBD process is
            used to add the new algorithms to the appropriate YANG
            module (e.g., iana-symmetric-algorithms), which would be
            automatically published by IANA.
    
By undefined, you mean "unknown to YANG" I assume, and not "a new crypto alg not previously used in TlS (for example)."

>      2a) update some new TBD registry (e.g., “base algorithms”).
            This would need to be done by a crypto expert (not the
            NETCONF WG or YANG Doctors.  Good candidates might
            the Security ADs or, perhaps better, the WG that published
            the source RFC.
I don't know if the sec folks would be interested in this but I could be wrong.  It might be good to have a brief chat F2F in Vancouver, which I can help set up.

v2.23.0 | Report a Bug | By Email