IETF Logo Mail Archive

Re: [netconf] crypto-types: why symmetric keys?

"Salz, Rich" <rsalz@akamai.com> Fri, 04 October 2019 16:59 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 6E78A120910 for <netconf@ietfa.amsl.com>; Fri, 4 Oct 2019 09:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, 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 ASGfqr5j5vHe for <netconf@ietfa.amsl.com>; Fri, 4 Oct 2019 09:58:58 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 CECD81208D9 for <netconf@ietf.org>; Fri, 4 Oct 2019 09:58:58 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id x94GqSsv012509; Fri, 4 Oct 2019 17:58:55 +0100
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=w+EUwTAWzyd9NEK832Y0mYhZjY2MeUzpBnK2XJy0Bdk=; b=JwxjOPhjHKk4WawrgUE0EcX+zamtu5/P+mGHh1kPbcJoLlpdbXdfTPPz2AwXsO/ZN5se wRtspPKwh7gd8GZhzqcEhNOBheEMx6xMRxuqkisgfS+gfKi6sSWRDs1y6PowD7BYBSmF 2Kdr5Nct463agSCilO4SHeNNnKt82YQ1FaTXzUCaoVBxOuoD2C34TP8B+8xpmmlzl/3q 7GeV5UAjmO4BrSN5AOJFhjcZq89qeo5/kDgY7Rz1VxEzYjesklZyIlb9lbwAPXglEWGK xn+AH447VELQHOh3NpJppuRtNPYMhpMPUcsrgpS79USHHgwgq0AGIt/Noy6iXt2RKMpA WQ==
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2ve6gvru27-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 04 Oct 2019 17:58:54 +0100
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x94GW9Wf026124; Fri, 4 Oct 2019 12:58:54 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint6.akamai.com with ESMTP id 2va2uw98cc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 04 Oct 2019 12:58:54 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 12:58:53 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1473.005; Fri, 4 Oct 2019 12:58:53 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] crypto-types: why symmetric keys?
Thread-Index: AQHVerjc4I0mNpxxdEmkYSi/07A3oqdK8zsA///BUgA=
Date: Fri, 04 Oct 2019 16:58:52 +0000
Message-ID: <017A9541-641B-4826-983B-7C47AFA1A3AD@akamai.com>
References: <B840CB4A-3DF9-4C1B-825D-F24A72EFC90F@akamai.com> <84a2ff74-67fb-069b-a9bc-4bd4187ee1bc@alumni.stanford.edu>
In-Reply-To: <84a2ff74-67fb-069b-a9bc-4bd4187ee1bc@alumni.stanford.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1e.0.191003
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.233]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F096563ABE14924C8AE1C9FB519C3436@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-04_09:, , 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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910040145
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-04_09:2019-10-03,2019-10-04 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 impostorscore=0 mlxlogscore=999 priorityscore=1501 malwarescore=0 suspectscore=0 bulkscore=0 lowpriorityscore=0 clxscore=1011 phishscore=0 spamscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910040146
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/p6KqqcXFYD9x2FkKl-uTqfeFsUQ>
Subject: Re: [netconf] crypto-types: why symmetric keys?
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: Fri, 04 Oct 2019 16:59:03 -0000

    > What’s the use-case for needing to configure symmetric keys?
    >
    
>    Provisioning SNMPv3 USM comes to mind.
  
Thanks.

If we are going to partition crypto-types into smaller pieces, then it seems we have three things now:
	TLS (https servers, certs and keys for RSA and ECDSA)
	SSH ("raw" public and private keys)
	SNMP (symmetric keys)

v2.23.0 | Report a Bug | By Email