Re: [netconf] Pointers to major "crypto" threads?

"Salz, Rich" <rsalz@akamai.com> Thu, 08 August 2019 19:21 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 B4161120167 for <netconf@ietfa.amsl.com>; Thu, 8 Aug 2019 12:21:48 -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, RCVD_IN_DNSWL_LOW=-0.7, 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 (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 x5D_ajXt4IzM for <netconf@ietfa.amsl.com>; Thu, 8 Aug 2019 12:21:47 -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 38C331200A3 for <netconf@ietf.org>; Thu, 8 Aug 2019 12:21:47 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id x78J7faw006019; Thu, 8 Aug 2019 20:21:46 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=BVfcv8mGkyo+V0qV2OJ3ngvVwENj6m0ficJJGCUNehY=; b=dYpB7iHX+TpGkl0W+7VlnTWU68OMzgZTsjO5ihm4lcj7t3wkN49OGg4FeRKf+7fOvnkj 5zGG+e7XVNoVG2hkl6vhBSQtSCXa79QDdmy7DwH1FOp1kFW+7gEB4IRNnGxGzPKNIRTT TbPjMv92ItcRE2QsHmZmNke1gho/MU008zRN0ZVRLIQGTbVyN7tsqKcHftHQogVhWz+R vKaYv3MWZULiA/GKVRiT2QsyGuYaWgili4WzX69JxgbBb0n4egBLIUBqgQ8F2NIYbgoS vuVMw0X0L81PKgSQBTAlAjAY+Ljny7IxCskeZdC1HzgXDXY4plvr+sHi+18Zkx3sdfuw iw==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2u52p8qn48-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 08 Aug 2019 20:21:46 +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 x78JHh9J000328; Thu, 8 Aug 2019 12:21:45 -0700
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint5.akamai.com with ESMTP id 2u5888hbmr-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 08 Aug 2019 12:21:45 -0700
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 8 Aug 2019 15:21:44 -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; Thu, 8 Aug 2019 15:21:44 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Kent Watsen <kent+ietf@watsen.net>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: [netconf] Pointers to major "crypto" threads?
Thread-Index: AQHVTd+GClyYowveV0SIeQ8kbqJVDKbxpGEA///RXoCAAGfjgP//w6YA
Date: Thu, 8 Aug 2019 19:21:44 +0000
Message-ID: <49FD8DE7-596A-46E1-8CDA-BC23D02DF5D0@akamai.com>
References: <EB4BBC2F-161C-4AED-9C01-BFBB75C0D923@akamai.com> <0100016c71dc7c15-fd7a35b0-1414-497e-8ecc-aa59e239c628-000000@email.amazonses.com> <3BE70E76-AB66-4BF6-8FFD-A65F7294AD01@akamai.com> <0100016c729816e0-2c474f96-ffee-4aac-9020-f2821fe4480b-000000@email.amazonses.com>
In-Reply-To: <0100016c729816e0-2c474f96-ffee-4aac-9020-f2821fe4480b-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.1c.0.190804
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.106]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F654500C071C9B4DB21D4406DD717209@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-08_07:, , 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=555 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908080172
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-08_07:2019-08-07,2019-08-08 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 priorityscore=1501 adultscore=0 lowpriorityscore=0 mlxscore=0 spamscore=0 mlxlogscore=549 malwarescore=0 impostorscore=0 clxscore=1015 phishscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908080172
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/tw-D6jG_4umWkrfsCYGDC5UMuyo>
Subject: Re: [netconf] Pointers to major "crypto" threads?
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: Thu, 08 Aug 2019 19:21:49 -0000

>    I'm guessing that you have the same concern with this draft as expressed by others, and thus imagine the thread you are looking for is here: https://mailarchive.ietf.org/arch/browse/netconf/?q=I-D%20Action.
    
>    The NETCONF WG's ultimate objective is to define YANG modules enabling the configuration of the NETCONF and RESTCONF protocol stacks, for both client and servers (please see [1] and [2]).

Thanks for those pieces of information.  "I'll be back" :)