Create Agenda & meeting Minutes for 4-22-26 TAC meeting

meeting-minutes/2026/2026-04-22-TAC.md

@@ -0,0 +1,127 @@
+---
+layout: default
+title: 2-26-04-22 TAC Meeting Record
+parent: 2026
+grand_parent: Meeting Minutes
+---
+
+# Post-Quantum Cryptography Alliance - Technical Advisory Council (TAC) Meeting 22 April 2026
+[**View Recording**](https://zoom.us/rec/share/5WKedTUjUnUNGyjbB3ESiwKul1AUHGwHqH4z2ijTcjKCwmyTdqbIoM7D_0H2qfVo.Fc0n10v2zRMtT3I4)
+*Recordings are also available on your [Open Profile](https://openprofile.dev/my-meetings) page under Past Meetings*  
+[**Join the meeting**](https://zoom-lfx.platform.linuxfoundation.org/meeting/98559442147?password=5e9d28b7-97d4-4628-9087-5f359dbf3d80)  
+[**PQCA Meeting Calendar**](https://pqca.org/calendar/)  
+[**Discord Server**](https://discord.pqca.org ))
+
+---
+
+### **Antitrust Policy Notice**
+
+Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at [linuxfoundation.org/antitrust-policy](https://linuxfoundation.org/antitrust-policy). If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
+
+---
+
+## Voting Representative Attendance (_Alphabetical by 1st name_)
+### Premier Member Representatives
+
+* [x] Brian Jarvis, AWS
+* [ ] ~~Michael Maximilien, IBM~~
+* [x] Norman Ashley, Cisco (OQS Rep)
+* [ ] ~~Sophie Schmieg, Google~~
+
+ ### Project Representatives
+* [ ] ~~Matthias Kannwischer, TCR~~
+* [x] Hanno Becker, AWS (PQCP)
+* [ ] ~~Andreas Schade, IBM (CBOMkit)~~
+* [x] Aditya Koranga, NgKore \[TAC Chair\]
+
+## Non-Voting Representative Attendance
+
+### LF Staff 
+* [x] Christina Harter 
+* [ ] ~~Hart Montgomery~~
+* [x] Tomaz Sedej
+
+### Other Attendees
+* [x] Katarina Amrichova, Siemens Healthineers
+* [x] Panos Kampanakis, AWS
+* [x] Sandip Dholakia, SAP
+* [x] Andy Warner, Google
+
+---
+# Meeting Agenda
+- Google's proposal: Central Repository for PQC capability tracking.
+- Christina:
+  - [TAC Vice Chair nominations](https://github.com/PQCA/governance/issues/new?template=TAC-vice-chair-nomination.yaml) open until Friday, April 24th
+  - One [mentorship](https://github.com/PQCA/TAC/issues/137) proposal submission under CBOMkit project
+  - [CBOMkit Now Supports Go](https://pqca.org/blog/2026/cbomkit-now-supports-go/) blog published on April 15th
+  - CBOMkit Pipeline post still under review by submitter  
+- PQCA Webinar with Google, recording now available.
+- Follow up:
+  - Invitation to OpenSSF team members for security baseline discussion
+- Project updates
+
+
+# Discussion & Updates
+
+### **Introduction of 1st Time Attendees**
+Andy Warner, Product Manager from Google, joined to discuss a Central Repository for PQC capability tracking.
+
+---
+
+### **PQC Capability Tracking Proposal (Google)**
+
+The primary focus of the meeting was a proposal from Google to establish a centralized repository for tracking Post-Quantum Cryptography (PQC) capability across software libraries, applications, and infrastructure. Andy presented the concept of a [crowdsourced repository](https://github.com/aww-aww/pqc-readiness/tree/main) within the PQCA GitHub organization that would use structured markdown tables to document PQC support across both open-source and proprietary technologies. The proposed scope includes cryptographic libraries (e.g., OpenSSL, BoringSSL), as well as broader systems such as HSMs, operating systems, network devices, and programming language ecosystems.
+
+The goal of the repository is to provide a clear, versioned view of PQC readiness across the ecosystem, enabling organizations to better understand migration paths and identify gaps in support. The group discussed several implementation considerations, including how to track version-level support, represent hybrid versus fully PQC-enabled implementations, and handle edge cases through annotations or notes fields.
+
+Different approaches to validating PQC readiness were also explored. Andy suggested a documentation-first approach with structured data and annotations, while Brian proposed supplementing this with runtime verification methods (e.g., inspecting TLS client hellos for PQC algorithms). Aditya noted that runtime approaches may be limited in scope, particularly for capturing server-side capabilities.
+
+The discussion also highlighted the importance of community involvement. Andy emphasized that while Google is willing to seed the repository with initial data and contribute to early curation, the effort should remain vendor-neutral and community-driven. The group agreed that broad participation across multiple organizations will be critical to ensure comprehensive and accurate coverage.
+
+To support this initiative, the TAC discussed forming a dedicated PQC Compatibility Tracking Working Group. This group would be responsible for defining scope, governance, contribution guidelines, and ongoing maintenance of the repository. Aditya expressed strong support for starting with a focused scope (e.g., cryptographic libraries) and expanding over time. Christina noted that formal approval may require quorum and potentially governing board input, and outlined next steps for establishing the working group, including defining membership, meeting cadence, and charter requirements.
+
+---
+
+### **Foundation Updates**
+
+- **TAC Vice Chair Nominations:** Christina reminded the TAC that [nominations are open](https://github.com/PQCA/governance/issues/new?template=TAC-vice-chair-nomination.yaml) until this Friday, April 24th. 
+- **Mentorship Program:** Christina reviewed updates on mentorship proposals, with Aditya [submitting a proposal](https://github.com/PQCA/TAC/issues/137) to extend language and library support in CBOMkit.
+- **Google & AWS Webinars:** Tomaz shared success metrics from a [recent Google webinar](https://pqca.org/webinars/2026/pqc-where-to-start-what-to-prioritize-and-how-to-facilitate-a-smooth-transition/) and highlighted an upcoming AWS webinar scheduled for June 1st.
+- **Webinars Page:** Christina shared a [new Webinars page](https://pqca.org/webinars/) on the PQCA website.
+- **Blog Post Updates:** Christina also shared a recent published blog post, [CBOMkit Now Supports Go](https://pqca.org/blog/2026/cbomkit-now-supports-go/). Katarina provided an update on the CBOMkit Pipeline post and will confirm once revisions are complete and ready for posting.
+
+---
+
+### **Project Updates**
+- OQS
+  - Norman reported that OQS is continuing development work.
+
+- PQCP
+  - Hanno provided updates on memory reduction efforts for mldsa-native and ongoing work on Rust bindings and the PowerPC 64 backend.
+  - Hanno will continue reviewing and integrating the PR for Rust bindings for mldsa-native and mlkem-native, and provide feedback/progress updates in upcoming meetings.
+  - mlkem-native/mldsa-native: Now using free RISC-V Github runners via the RISE project
+  - mlkem-native: Working on Rust bindings to be published on crates.io.
+  - mlkem-native: Renewed interest in a ppc64le backend - pending review.
+  - mldsa-native: Progress on memory optimizations and correctness proofs for assembly.
+  - mldsa-native: Some CBMC performance problems with union fixed upstream enabling proofs of memory-optimized code - currently work in progress.
+
+- CBOMkit
+  - No new updates.
+
+---
+
+### **Next Steps / Action Items**
+
+| Action Item | Owner | Status / Due Date |
+|-------------|-------|-------------------|
+| Include additional TAC members in decision-making for PQC Compatibility Tracking Working Group and confirm quorum requirements | Aditya / Christina | Before next TAC meeting |
+| Provide templates, governance guidance, and coordinate legal review for establishing the new working group | Christina | Before next TAC meeting |
+| Seed initial PQC compatibility repository data and participate in early working group efforts | Andy / Google team | Ongoing |
+| Set up CBOMkit mentorship proposal on LFX platform, finalize timeline, and open for applications | Christina | Before next TAC meeting |
+| Finalize updates to CBOMkit pipeline blog post based on review feedback | Katarina | Before publication |
+| Coordinate scheduling for OpenSSF baseline presentation at upcoming TAC meeting | Aditya / Hart | Before next TAC meeting |
+| Continue reviewing and integrating Rust bindings for mldsa-native and mlkem-native and provide updates | Hanno | Ongoing |
+
+---
+
+**Adjourned:** 7:51am PT.