Update from Libraries Mailing List Kim Laine Microsoft

Update from Libraries Mailing List Kim Laine (Microsoft) Yuriy Polyakov (Duality & NJIT) 4 th Homomorphic Encryption Standardization Workshop, Santa Clara, CA August 17, 2019

What happened since the workshop in Toronto? Libraries mailing list discussions ❑ Development of one common API for all HE schemes may be premature ❑ A library-agnostic API for related schemes is more practical, e. g. , for BFV/BGV, CKKS, and TFHE ❑ There are essentially no tutorials on HE schemes for application developers ❑ The library group should prepare white papers on HE schemes ❑ It is hard to develop APIs without the white papers on HE schemes ❑ Programmer-friendly description of schemes, APIs, and encoding methods would help the adoption of HE ❑ A white paper for each scheme, API, or encoding method would be valuable

What happened since the workshop in Toronto? Other activities ❑ Revised the Homomorphic Encryption Wikipedia article to better reflect the current state of HE ❑ More libraries have added support for CKKS ❑ Usability is seen as a major challenge for CKKS adoption ❑ CKKS bootstrapping is actively explored by several library teams, however its efficiency for standard HE parameters and usability still need to be improved for practical use of CKKS bootstrapping ❑ IARPA HECTOR program has started ❑ One of the goals of the HECTOR program is to develop a framework that would allow programmers to build applications with native encrypted computing capabilities

What library-related documents are needed? The library group is responsible for documents related to schemes, APIs, and encoding methods. What documents should be prepared? Who are the main readers of the documents? ❑ We are proposing to write a white paper for each scheme, API, and plaintext encoding method. ❑ The target readers are application developers who want to understand how to choose the right scheme and its implementation, how to use the scheme, and select parameters that comply with the HE standard and provide correct results.

What white papers are being written? ❑ Section 3. 1 -w 1: Brakerski/Fan-Vercauteren Scheme ❑ Section 3. 2 -w 1: TFHE Scheme ❑ Section 3. 3 -w 1: API Recommendations for BFV and BGV schemes (so far mostly captures the API presented in Toronto)

Layout of scheme white papers ❑ Introduction: briefly describes the security assumptions, typical input data type, and key parameters ❑ Data Encoding ❑ Public-Key Encryption ❑ Homomorphic Encryption Operations ❑ Security ❑ Parameter Selection ❑ Further Reading