Re: [acvp] Hello and welcome

"Barry Fussell (bfussell)" <bfussell@cisco.com> Thu, 06 September 2018 20:45 UTC

Return-Path: <bfussell@cisco.com>
X-Original-To: acvp@ietfa.amsl.com
Delivered-To: acvp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8303A130F1F for <acvp@ietfa.amsl.com>; Thu, 6 Sep 2018 13:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 QX_RrkNSa18V for <acvp@ietfa.amsl.com>; Thu, 6 Sep 2018 13:45:01 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A326130EC0 for <acvp@ietf.org>; Thu, 6 Sep 2018 13:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8453; q=dns/txt; s=iport; t=1536266701; x=1537476301; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=vjrxSjWAXUKEdksTmAhepU4cuMnQt8MSAUt0oZLkPt0=; b=KEnWoQsFO51s9d8pg9gVvTa6VsWrtjL7NYksw/XWjCmlHjl2GDwNB7gf 6nL6C34HVCOGgOvkScYXbRwfLM1+OXwi1+blIo2N4KivBYVFUol7b/fP/ z6VbxGZkaZ+dj8TfdgD/oWFNoQJnDhKmoYcg/WmZUcOSog/MnlsNXnyzw g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DPAACYkZFb/5ldJa1bGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYJXTSplfygKi3qMIYINkH2FM4F6CyOEA0YCg1whNBgBAgEBAgE?= =?us-ascii?q?BAm0cDIU4AQEBBC07BhsCAQgRBAEBKAcyFAkIAQEEARIIDIJCTCgBdGQPpge?= =?us-ascii?q?KBQWKXheBQT+BEoF9gRWDGwKCF4UiAo0qjkcJAoY0gQSIPR+BQIQ9iGqLMog?= =?us-ascii?q?jAhEUgSQdOIFVcBU7gmyGAYpSb4sVK4EBgR0BAQ?=
X-IronPort-AV: E=Sophos;i="5.53,339,1531785600"; d="scan'208,217";a="451983184"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Sep 2018 20:44:44 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id w86Kihso028712 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 6 Sep 2018 20:44:44 GMT
Received: from xch-aln-004.cisco.com (173.36.7.14) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 6 Sep 2018 15:44:43 -0500
Received: from xch-aln-004.cisco.com ([173.36.7.14]) by XCH-ALN-004.cisco.com ([173.36.7.14]) with mapi id 15.00.1367.000; Thu, 6 Sep 2018 15:44:43 -0500
From: "Barry Fussell (bfussell)" <bfussell@cisco.com>
To: "Vassilev, Apostol (Fed)" <apostol.vassilev@nist.gov>, "acvp@ietf.org" <acvp@ietf.org>
Thread-Topic: Hello and welcome
Thread-Index: AdQo3nHB8aAV6IfgTqS4Xxp3vnEj5QdQ2Hzw
Date: Thu, 6 Sep 2018 20:44:43 +0000
Message-ID: <eff58a0092ed4a998a42a2579dbfd482@XCH-ALN-004.cisco.com>
References: <BL2PR09MB10921C87BA2EE20D1586C154FF2E0@BL2PR09MB1092.namprd09.prod.outlook.com>
In-Reply-To: <BL2PR09MB10921C87BA2EE20D1586C154FF2E0@BL2PR09MB1092.namprd09.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.150.34.72]
Content-Type: multipart/alternative; boundary="_000_eff58a0092ed4a998a42a2579dbfd482XCHALN004ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/acvp/FMxun7kswpI9DjdjVpKNw3M6m9Q>
Subject: Re: [acvp] Hello and welcome
X-BeenThere: acvp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Cryptographic Validation Protocol <acvp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acvp>, <mailto:acvp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acvp/>
List-Post: <mailto:acvp@ietf.org>
List-Help: <mailto:acvp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acvp>, <mailto:acvp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Sep 2018 20:45:03 -0000

Apostol,

Thanks for kicking off the discussion. I'd like to also welcome comments on the information
we presented at our side meeting. That slide deck is also available at the github link you
provided below.  We are targeting early October for submitting the 3 drafts and look forward
to working with everyone to make this a success.

Thanks,

Barry Fussell

From: acvp [mailto:acvp-bounces@ietf.org] On Behalf Of Vassilev, Apostol (Fed)
Sent: Tuesday, July 31, 2018 11:24 AM
To: acvp@ietf.org
Subject: [acvp] Hello and welcome

Hi everybody,

Welcome to the ACVP mailing list. I hope some of you were able to attend the presentation at the SAAG meeting and the side meeting on Thursday evening. For those who were not there,  please check the slides and the recording from the SAAG event. The slides for the side meeting can be found at https://github.com/usnistgov/ACVP/tree/master/slides/IETF102. Hopefully, this will give you some information about the problem we are trying to solve, the approach we have taken and the current status.

In terms of what's next for ACVP with IETF, we are working on improving the protocol specification to align it with the IETF requirements for an internet draft. FYI, our public working repository is at https://github.com/usnistgov/ACVP. In particular, we are planning to highlight how one can extend the capabilities of the protocol to add testing for other algorithms. This was one of the important asks from the community that we heard during the conference, both formally and informally in conversations. My plan is to position a minimal set of specifications for this purpose, including the specifications of the protocol and the testing of symmetric block ciphers.  Based on this minimal set, we can initiate the discussion. The specifications of the other supported types of algorithms and extensions would follow.

In the meantime, please let us know if you have questions or comments regarding the background for this project or the direction we are taking.

Looking forward to working with all of you,
--
Apostol Vassilev
Chairman - Automated Cryptographic Validation Testing Industry Working Group