[netconf] crypto-types: why symmetric keys?

"Salz, Rich" <rsalz@akamai.com> Fri, 04 October 2019 13:37 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 5FEBB12087B for <netconf@ietfa.amsl.com>; Fri, 4 Oct 2019 06:37:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, HTML_MESSAGE=0.001, 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 qCkbhb0oge98 for <netconf@ietfa.amsl.com>; Fri, 4 Oct 2019 06:37:36 -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 1A3EB120046 for <netconf@ietf.org>; Fri, 4 Oct 2019 06:37:36 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x94Db47I005848 for <netconf@ietf.org>; Fri, 4 Oct 2019 14:37:29 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=cNmhAxgYQGaXp3vdTceoGuFHMwV+FspbivHIYRJN+Bw=; b=bwZk/sINIQBzfOO9R5FqgQVq/HXg7r0tRWEPnuPrkonAaB/oM4q7JRO+wQn9FT5M8dyG cnLLpD+3+fW0aobf+MuG2NjDQ9TKAWC9l38nYRGLJPEAS/JziB+CSrqji/WuM7kz0tzC +bDZKsLzIoco2rrMqzyUmVwPpaQog7UGX6hQ6xv66om8P7w+y8t0u7uX6QqvCJ8g/XcW 4RjuiN5yq6/seIq6v2VSjXDQMNcBY/jYQ1Bcj0/8kUbrg0irsEvG3V1zJVqivKTvjvxZ f6q/g63BELvi12IyWDsx6HMZo2kwVDyGz/g/mGoktUEVm58TObdcGGEgDa8qxvkHP5zm iA==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2v9vcuutgn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <netconf@ietf.org>; Fri, 04 Oct 2019 14:37:29 +0100
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x94DVt0w005620 for <netconf@ietf.org>; Fri, 4 Oct 2019 06:37:27 -0700
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint5.akamai.com with ESMTP id 2va5g9abmr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <netconf@ietf.org>; Fri, 04 Oct 2019 06:37:27 -0700
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 4 Oct 2019 09:37:27 -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 09:37:27 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: crypto-types: why symmetric keys?
Thread-Index: AQHVerjc4I0mNpxxdEmkYSi/07A3og==
Date: Fri, 04 Oct 2019 13:37:26 +0000
Message-ID: <B840CB4A-3DF9-4C1B-825D-F24A72EFC90F@akamai.com>
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: multipart/alternative; boundary="_000_B840CB4A3DF94C1B825DF24A72EFC90Fakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-04_06:, , 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=754 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1910040126
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-04_06:2019-10-03,2019-10-04 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 suspectscore=0 bulkscore=0 mlxlogscore=730 mlxscore=0 clxscore=1015 spamscore=0 impostorscore=0 adultscore=0 malwarescore=0 phishscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1910040127
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/IXZ5yg8uGaowIwFgtdKwfsznTxA>
Subject: [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 13:37:37 -0000

What’s the use-case for needing to configure symmetric keys?