Meeting Date & Time

18 Oct 2023 This Task Force meets every Wednesday. There are two meetings to serve different time zones:

NA/EU meeting: 08:00-09:00 PT / 15:00-16:00 UTC
APAC meeting: 18:00-19:00 PT / 01:00-02:00 UTC

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

Zoom Meeting Links / Recordings

NOTE: These Zoom meeting links will be replaced by links to recordings of the meetings once they are available.

Attendees

NA/EU:

APAC:

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	Leads	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. New Members:
2 min	Review of previous action items	Leads	ACTION: ALL TSPTF MEMBERS review the Github discussion on appraisability framework criteria and contribute your proposed criteria. ACTION: Wenjing Chu to make sender VID required in the Working Draft. ACTION: Wenjing Chu to review section 3.4.1 to see about adding an optional signature on the plaintext within the ciphertext. ACTION: Wenjing Chu to review section 3.4.2 to decide if the ciphertext block can be removed. ACTION: Wenjing Chu to add an explanation of why the innermost layer can use a different envelope format than the outer layer. ACTION: Drummond Reed and Wenjing Chu to coordinate with Kevin Griffin to set up the repo for the Working Draft with the goal of being converted over to drafting in Markdown by our next meeting in two weeks.
10 mins	Recap of TSP at Internet Identity Workshop	Leads	We gave two sessions: ToIP Trust Spanning Protocol for Muggles — slides prepared by Drummond ToIP Trust Spanning Protocol Deep Dive — slides prepared by Wenjing Judith Fleenor shared that one person she talked to thought we were putting security into the IP stack. She said that came from showing the two hourglasses side-by-side. ACTION: Drummond Reed to post an issue to the ToIP Technology Architecture Specification to add the "waist-and-neck" diagram.
5 mins	VID Appraisability Framework	All	Review the GitHub discussion so far and agree on next steps.
5 mins	VID Specification?	Drummond Reed	After our sessions at IIW, Eric Scouten, Senior Engineering Manager on Adobe's Content Authenticity Initiative, sat down with Drummond to talk about VIDs. He is interested enough in how VIDs can tie into existing X.509 infrastructure that he's potentially willing to help form a new Task Force to produce a VID Specification. Drummond is having lunch with Eric this Friday to further discuss this. ACTION: Drummond Reed to check with Darrell O'Donnell about his explorations into X.509 interop. Sam Smith also talked with Eric about how to use X.509 certs securely with the right policy. The security can come from the VID and key state. That's what the VID Appraisability Framework will support. Tim Bouma cautioned to not make the same mistake of requiring X.509 PKIs for everything and it wasn't taken up. The VID can provide technical trust, but not institutional trust. Darrell O'Donnell put it this way: "Human trust must be embeddable". Wenjing pointed out that can be done in many ways. Sam Smith pointed out that Adobe's motivation is that their tooling is the most frequent source of producing deep fakes. Wenjing Chu shared a picture of the Content Credentials mark from the Linux Foundation C2PA project to build trust and claim ownership. You can click the "CR" button to see the provenance and then "inspect" it much more deeply. Try this: contentcredentials.org.
30 mins	Working Draft Progress Review	Wenjing Chu	Wenjing ran us through the table of contents of the Working Draft he is producing (screenshot #1 below is a sample). He has taken care of all the action items from the last meeting (see above). One of his key takeaways from the IIW review sessions was that the spec should include the routing protocol from the start. So he has added that section. He previewed the other revised or new sections (screenshots #2-#5). We discussed also adding "simple multicast" option. Sam Smith felt that it would be good to add that option as it will have a lot of value. ACTION: Wenjing Chu will add a section to the Working Draft for a simple multicast protocol. Wenjing has added a signature block, which Sam noted will satisfy the legal requirement for a signature to be over the plain text. Sam said that RFC 9180 defines hybrid public key encryption. It defines the recommended modalities of public key encryption.
5 mins	Review decisions/action items Planning for next meeting	Leads