Meeting Date & Time

02 Apr 2025 This Task Force meets every other Wednesday. There is a single meeting for the NA/EU. (Updates for the APAC time zone will be at the monthly TSWG APAC meeting the first Tuesday of every month.)

NA/EU meeting: 08:00-09:00 PT / 15:00-16:00 UTC

See the Calendar of ToIP Meetings for exact meeting dates, times and Zoom links.

Zoom Meeting Links / Recordings

NA/EU Meeting: https://zoom-lfx.platform.linuxfoundation.org/meeting/96565410414?password=9db52340-ad99-4a33-aa07-c44481d32968

To see the recording of the meeting, click on the calendar entry for the meeting in the ToIP Calendar. The link to the Zoom recording should appear there approximately one hour after the meeting ends.

Attendees

Agenda Items and Notes (including all relevant links)

Time	Agenda Item	Lead	Notes
3 min	Start recording Welcome & antitrust notice New member introductions Agenda review	Chairs	Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role. NOTICE: In addition to the licensing terms of this Working Group’s JDF charter, this Working Group operates under the official policy that any Working Group Participant who makes a contribution to a Draft Deliverable shall have a maximum of 45 days from the date of that contribution to exclude any Essential Claims pertaining to that contribution. New Members:
2 min	Review of previous action items	Chairs	None
30 mins	Continue Working Through Spec Revision Items	Wenjing Chu	We went over the spreadsheet that Wenjing has prepared to quickly resolve issues (see screenshot #1). We started with HOP codes (see screenshot #2). Sam Smith explained why the CESR design supports pipelining using the XHOP payload structure. We discussed how this design optimizes the ability for a core processor to process as many messages as possible because it allows the pipe to shunt off messages extremely efficiently to different cores. We discussed the ThreadID field at the tunnel level. Wenjing explained that some messages have nonces. Do we need both? Sam suggested that it should be "up-layered". Wenjing asked if it can be efficiently performed by an up-layer. Wenjing was convinced to not include a ThreadID at the base TSP layer because: a) not every up-layer protocol needs threading, and b) if they do need threading, they may need different kinds of thread IDs. We next discussed the relationship formation protocol. The question there was whether we needed a nonce. Sam pointed out that the relationship formation protocol requires VIDs, and VIDs need to be globally unique, so a separate nonce should not be needed. We next discussed codes for cyphersuites. Wenjing asked about the HPKE algorithms. Sam said they could be added to the primitive code table. See screenshot #3. Sam explained that CESR code allocation follows the Pareto Principle: single-character codes are used for the most frequent primitives, then two-character codes that start with 0 are the next set, then all other two-character codes, then four-character codes, then larger codes. It is all designed for efficient parsing. Next we discussed screenshot #4. Wenjing pointed out that the issue is that HPKE has its own code table. Sam explained that the entire HPKE code table can be prefixed with a single CESR code. Wenjing asked for a pointer to the CESR Master Code table, and Sam gave that pointer to the main CESR spec. Next we discussed signatures—see screenshot #5. That was a short discussion. Wenjing
10 mins	Other Issues (as time allows)	Chairs	See the issues list.
5 mins	Discuss planned presentations for Internet Identity Workshop #40	All
5 mins	Review decisions/action items Planning for next meeting	Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1

#2

#3

#4

#5

Decisions

None

Action Items

None (just continued work on the issues list)

Browser not supported