We gave two sessions:

1. ToIP Trust Spanning Protocol for Muggles — slides prepared by Drummond
2. 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.

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.

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.

ACTION: Drummond Reed to check with Darrell O'Donnell about his explorations into X.509 interop.

ACTION: Drummond Reed to report back on his lunch with Eric Scouten with a recommendation about a VID Core Specification Task Force.

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. 

APAC:

We discussed that it is so much faster for Wenjing to proceed with the initial writing of the Working Draft as a Google doc that it is fine to wait until it is relatively complete before we move it into GitHub so we can begin to file issues against it.