- From: John, Anil <anil.john@hq.dhs.gov>
- Date: Tue, 22 Sep 2020 21:27:52 +0000
- To: "Bouma, Tim" <Tim.Bouma@tbs-sct.gc.ca>, Credentials CG <public-credentials@w3.org>
- Message-ID: <BLAPR09MB728465DA67280558E11250F8C53B0@BLAPR09MB7284.namprd09.prod.outlook.com>
Hi Tim, The test artifacts and suites we used can be found linked off this message. https://lists.w3.org/Archives/Public/public-credentials/2020Jun/0100.html The test plan is attached to that e-mail as well. Also attached to this email FYI. I appreciated the invitation and the opportunity to participate in your kick-off call. Just sent you an invite to our Cohort level kick-off in late Oct just now. We will be discussing how to expand the surface area of the tests and the shared work to be done by all the companies in the cohort. – Hope you can join us! 😊 Best Regards, Anil This document contains pre-decisional and/or deliberative process information exempt from mandatory disclosure under the Freedom of Information Act, 5 U.S.C. 552(b)(5). Do not release without prior approval of the Department of Homeland Security. From: Bouma, Tim <Tim.Bouma@tbs-sct.gc.ca> Sent: Tuesday, September 22, 2020 4:41 PM To: John, Anil <anil.john@hq.dhs.gov>; Credentials CG <public-credentials@w3.org> Subject: RE: DHS S&T SVIP Call - Prevent Forgery & Counterfeiting of Certificates and Licenses || Phase 1 Interoperability Test Plan - Latest Version CAUTION: This email originated from outside of DHS. DO NOT click links or open attachments unless you recognize and/or trust the sender. Contact your component SOC with questions or concerns. Hi Anil, Is this the latest version of your test plan? I’d like to use this as a starting point for our own challenge, unless you have a later revision. Thanks again for attending the call. It was a big boost for us! Tim From: John, Anil <anil.john@hq.dhs.gov> Sent: April 20, 2020 11:02 AM To: Credentials CG <public-credentials@w3.org> Subject: DHS S&T SVIP Call - Prevent Forgery & Counterfeiting of Certificates and Licenses || Phase 1 Interoperability Test Plan Hello W3C CCG, I hope this message finds you safe and healthy. I wanted to provide an update on some work we are currently doing that may be of interest to this group in the area of standards-based multi-vendor interoperability. Background ---- * https://lists.w3.org/Archives/Public/public-credentials/2018Nov/0124.html<https://urldefense.us/v2/url?u=https-3A__can01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Flists.w3.org-252FArchives-252FPublic-252Fpublic-2Dcredentials-252F2018Nov-252F0124.html-26data-3D02-257C01-257CTim.Bouma-2540tbs-2Dsct.gc.ca-257C51572a347e474f3e637408d7e53c7fdc-257C6397df10459540479c4f03311282152b-257C0-257C0-257C637229920322742784-26sdata-3DVl5oSz9GVAC-252B0pFQ69GwKn1w4h0O951ssPdK4t8-252F6DM-253D-26reserved-3D0&d=DwMFAg&c=2plI3hXH8ww3j2g8pV19QHIf4SmK_I-Eol_p9P0CttE&r=FUgYmx6LTIaPqn7QR6TBfzml-fqCTpab-djgqlCFtgU&m=EU44Nybx_wm1YofUoCEAGy-JI2iA1-Uj5peFwCgxb8s&s=UztaM7HD9XFDG59N3DgcBRT4oP8o8Dy_PAxGzlAK6qQ&e=> * https://lists.w3.org/Archives/Public/public-credentials/2020Jan/0008.html<https://urldefense.us/v2/url?u=https-3A__can01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Flists.w3.org-252FArchives-252FPublic-252Fpublic-2Dcredentials-252F2020Jan-252F0008.html-26data-3D02-257C01-257CTim.Bouma-2540tbs-2Dsct.gc.ca-257C51572a347e474f3e637408d7e53c7fdc-257C6397df10459540479c4f03311282152b-257C0-257C0-257C637229920322742784-26sdata-3DpmraEAlMwY-252BYx1giNR2IYaZ5rvdz-252BBwIe0aOIy-252BdJuk-253D-26reserved-3D0&d=DwMFAg&c=2plI3hXH8ww3j2g8pV19QHIf4SmK_I-Eol_p9P0CttE&r=FUgYmx6LTIaPqn7QR6TBfzml-fqCTpab-djgqlCFtgU&m=EU44Nybx_wm1YofUoCEAGy-JI2iA1-Uj5peFwCgxb8s&s=t2KDOlh-ow3Dtah2iExpegcYxtJl_9AVG1reFd6WWmM&e=> Interoperability Plug-Fest ---- We believe that innovation should be built on a foundation of interoperability. To that end, the startup companies that we have awarded contracts to need to demonstrate to the Government, in Phase 1, a Minimum Viable Product that shows the adaptation of their Product to support, among other things and most critically, an interoperable implementation of DIDs/VCs. How that is demonstrated to the Government is flexible, so what DHS SVIP is resurrecting is the grand tradition (from WAAY back in the SAML and WS-* days) of the Interoperability Plug-Fest. “Interoperability Plug-fests are a safe environment to test your code's degree of conformance with a respective standard, and how well it interoperates with other implementations of the same standard. Ideally, standards would be interpreted identically by all implementers, and hence all implementations would interoperate, but often enough that is utopia (though standards authors work very hard to minimize this). Such situations, where tests fail, the analysis of the failures can discover shortcomings in the standard document itself, illustrate discrepancies in interpretation, or in formal testing settings, errors in the test suite used.” Please find attached the high level Phase 1 test plan that provides information on what we will be testing and how we will be conducting the testing early next month. Feedback on the test plan to this list, directly to me, or to any of the participants is encouraged and would be appreciated. Best Regards, Anil Anil John Technical Director, Silicon Valley Innovation Program Science and Technology Directorate US Department of Homeland Security Washington, DC, USA Email Response Time – 24 Hours [https://www.dhs.gov/science-and-technology/svip]
Attachments
- image/png attachment: image001.png
- application/pdf attachment: DHS.ST.SVIP-Call-Preventing-Forgery-Interop-Test-Plan-Phase-1.pdf
Received on Tuesday, 22 September 2020 21:28:27 UTC