Versions Compared

Old Version 1

changes.mady.by.user Eric Scouten

Saved on

compared with

New Version Current

changes.mady.by.user Eric Scouten

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This Task Force meets every two weeks. There are two meetings to serve different time zonesInitially there is one meeting for NA/EU time zones (an APAC meeting may be added if there is sufficient demand):

  • NA/EU meeting: 08:30-09:30 PT / 16:30-17:30 UTC
  • APAC meeting: XX:00-XX:00 PT / XX:00-XX:00 UTC (none as yet)

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

Zoom Meeting

...

Recordings

  • NA/EU MeetingRecording:  https://zoom.us/rec/j/92418315404?pwd=R2xZdjNiVGZsOW5lb3pzQUdNT1RIZz09
  • APAC Meeting:  <insert Zoom link from ToIP Calendar entry here>

...

Attendees

NA/EU:

APAC:

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust noticeNew 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:
5 minAPAC meeting?

Eric Scouten 

ACTION: Eric Scouten  to send out notice to all members calling for an APAC meeting chair.
20 minsIntroductions / why we're here

Eric Scouten 

Use cases mentioned:

  • Bridging decentralized identity with existing X.509 trust infrastructure
  • Content Authenticity Initiative: Binding organizational and individual identity to broadcast messages
  • Content authenticity related to images/streams, audio
  • Trust registries
  • Conformity assessment for X.509 in verifiable identifier
  • Electronic transferable records (similar concept to content authenticity referred to as integrity)
10 minsIs did:x509 viable?All

For reference, here are the requirements for DID method specifications and here is one frequently referenced IETF standard for X.509 Public Key Infrastructure Certificates (RFC 5280).

  • Competitive tooling between X.509 resolution tooling and DID resolution tooling
  • What does it take to make X.509 satisfy the requirements of a VID?

Three broad classes of trust infrastructure:

  • Verifiable credentials
  • Content authenticity
  • Electronic transferable records

Governments will be especially interested in bridging with existing trust infrastructure.

20 minsInitial guidance and suggested reading for specEric Scouten 

On this topic, one ToIP wiki page we can refer to is Stages of Development for Working Groups & Task Forces. This was recently updated to provide more detail for each stage.

DECISION: Augment this working group's charter with a second output: a position paper from ToIP advocating that decentralized trust infrastructure should incorporate existing PKI infrastructure and explore strategic alternatives.

ACTION: Drummond Reed and Tim Bouma to co-author.

Suggested readings for TF members:

5 mins
  • Review decisions/action items
  • Planning for next meeting 
Leads

What are the action items for TF members over the 4 week break before the next meeting on January 11?

  • ACTION: Drummond Reed to review Trust Spanning protocol specification and post an analysis to Slack channel of suitability of VID section as a mini-spec.
  • ACTION: Judith Fleenor to ensure that Slack channel is set up for this TF. (DONE)
  • ACTION: Eric Scouten to review Microsoft did:x509 spec and post an analysis to Slack channel of suitability as a VID.

Screenshots/Diagrams (numbered for reference in notes above)

...