...
Time | Agenda Item | Lead | Notes |
3 min |
| Chairs |
|
2 min | Review of previous action items | Chairs |
|
20 mins | HPKE Support | Wenjing Chu | See the Wikipedia article on hybrid encryption and IETF RFC 9180. Wenjing explained the purpose of section 8 of the Working Draft and why it references both LibSodium sealed box and HPKE. See screenshot #1 below. Sam Smith explained that TSP can support both. He clarified that each "base mode" in the HPKE spec can be assigned a different CESR code. He said that CESR can support hundreds of codes if we need them. Each code identifies any combination of parameters across all of the algorithms and inputs. That is an example of the cryptographic agility of CESR. If LibSodium adds another base mode that interoperates with RFC 9180, then that can be assigned another CESR code. Neil Thomson: "Sounds like a case for Lipsodium as initially supported with clear path/compatibility/commitment to HPKE family for future." Sam Smith: "We need to be smarter than past choices about too many cryptographic options". We need to be very exact about which combinations we choose. Wenjing then covered how HPKE will be used in our ESSR pattern. See screenshot #2 below. |
10 mins | Resolution of key rotation question | Wenjing Chu | See second action item above. |
20 mins | Other prep for moving to Implementers Draft | Chairs | Our plan has been to move to Implementers Draft by end of February. What remains to be done to reach that goal? |
5 mins |
| Chairs |
Screenshots/Diagrams (numbered for reference in notes above)
#1
...
#2
...
#3
...
#4
...
#5
...
#6
...
#7
...
#8
...
#9
...