You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This page has agendas, notes, and action items from each meeting of the UFWG in reverse chronological order.

Tuesday, June 23 — 11:00-12:00 PT / 18:00-19:00 UTC

Agenda and Notes

  1. Welcome and Linux Foundation antitrust policy (André)
  2. Introduction of new members
    1. Richard Esplin—Director of Product at Evernym, very active in Hyperledger Indy, Ursa, Aries
    2. Cameron Boozarjomehri, Mitre
  3. Further call for chairs & vice chairs
    1. Chair volunteers: Dan Gisolfi, André Kudra, others?
    2. Vice Chair volunteers:
      1. Cameron Boozarjomehri
      2. Mathieu Glaude
    3. Karl mentioned that we want to more broadly socialize this WG to new members
      1. Drummond confirmed that this is a priority for all the WGs as we have many new members (over 100 total now)
    4. There was consensus to keep nominations open for one more meeting cycle
      1. ACTION: André to send an email to the all-members list inviting new members and nominations
  4. WIP initial work items—leads, updates, working mode, next steps
    1. Workflow decision tree—Dan Gisolfi as lead (tbc)
      1. Dan explained that the Steering Committee is working on a description of the standard ToIP work products / deliverables (specs, templates, recommendations, white papers, etc.)
      2. Dan and team are working on capturing the stages in the lifecycle of a utility project
      3. He proposes a team that defines the stages in the flow —building on examples of existing or planned projects like Sovrin, Bedrock, etc.
      4. This will help us collectively define the major elements of a utility project
      5. Dan invites anyone who wants to pair with him on this work, just ping him on Slack in the #utility-foundry-wg channel (or DM)
      6. Karl agreed that identifying the stages of a lifecycle is something that also applies to the Ecosystem Foundry WG
    2. ToIP Utility projects liaison—André Kudra as lead (tbc)
      1. André reported that he is in contact with the three potential utility projects underway in Germany
      2. He is encouraging them to join the ToIP Foundation to collaborate to advance their efforts
      3. Karl asked about what definition we currently have of a ToIP Layer One utility?
        1. Drummond said that the most "official" definition is the current ToIP stack defintion in Hyperledger Aries RFC 0298.
        2. Dan pointed out that any ToIP Foundation member could contribute a definition of a term for the ToIP Glossary: https://github.com/trustoverip/concepts-and-terminology-wg/issues/new/choose
      4. Dan suggested that this work item could involve creating a markdown list of the utility candidates
        1. Dan is fearful of the ToIP Foundation becoming a "dumping ground" of projects that may not be qualified
        2. His view is that our list should be utility project who are directly contributing or seeking guidance from this WG about participating
      5. André explained one example: LISSI (Let's Initiate SSI), formally the German name for "SSI for Germany" —  https://lissi.id/
        1. Associated with the German Ministry for Public Affairs
        2. Currently in the competition phase
        3. The next phase will filter it down to 3 projects that will share EU 15M in funding
        4. He believes it has a very good chance to be a successful ToIP Layer One utility
        5. Company that is the consortium lead: https://main-incubator.com/
        6. Also sponsored by a government ministry: https://www.bmwi.de/Navigation/EN/Home/home.html
      6. André explained a second example is called the "ECO Association" (in German) — https://www.eco.de/ 
        1. They have assembled several members who are interested in forming a network
        2. Want to be fully aligned with ToIP right away
        3. André has encouraged them to become Contributor Members ASAP
      7. The third one is GOVDigital — https://www.govdigital.de/
        1. Driven from the public sector for the public sector
        2. They are also contributing a little to the ECO Association
        3. Only public sector orgs will be able to run a node
        4. Also planning to use Hyperledger Indy 
      8. André shared this link about all the German projects
        1. https://www.digitale-technologien.de/DT/Navigation/DE/ProgrammeProjekte/AktuelleTechnologieprogramme/Sichere_Digitale_Identitaeten/Projekte_Wettbewerbsphase/projekte_wettbewerbsphase.html
      9. Findy (Finnish Indy) — https://www.findy.fi/
        1. Still recruiting members. Expect to join ToIP as both a utility, and as a group of

      10. Project in Austria — https://meinesichereid.org

      11. Alastria in Spain
      12. ACTION: Dan will start creating a file for listing projects and drop it into Slack
  5. Selecting/prioritizing further initial work items—preferences, leads, contributors, task force mode — Dan suggests that we tackle these once we have the SC document on ToIP deliverables
    1. ToIP Utility RFP templates
    2. ToIP Utility Best Practices documents
    3. ToIP Utility website and utility directory
    4. White paper repository & opportunities
  6. Topics for Future Meetings
    1. DanG: Utility Project Workflow
    2. Richard: Presentation on Indy-based utilities and progress of Indy
    3. Richard: Discussion about the current state of Aries, it's future, and interoperability
  7. Adding an APAC call time
    1. André proposes to do this on alternative weeks to the US/EU call

Tuesday, June 09 — 11:00-12:00 PT / 18:00-19:00 UTC

Agenda and Notes

Meeting recording (https://zoom.us/rec/share/5MVZf7yv2XFIY7fk71zmB_88AIDJX6a81SFN_qALmE8DRIo5DLdOJyVdcbx-HPgj)

  1. Welcome and Introductions (André)
    1. André Kudra, esatus, Germany
    2. Dan Gisolfi, IBM, New York, USA
      1. Convener of the Bedrock Business Utility
      2. This is the WG that will enable interop between ToIP Layer One utilities
      3. We will "prime the pump" for other utilities
      4. Suggest we start off with a high-level workflow
    3. Drummond Reed, Evernym, Seattle, USA
      1. Chief Trust Officer at Evernym
    4. Darrell O'Donnell, CEO, Continuum Loop, Ottawa, Canada
      1. Want to see us build a very boring utility layer
    5. Matt Davies, CTO, Finicity, Utah
      1. Want to ensure a strong foundation for financial apps higher in the stack
    6. Wenjiing Chu, Futurewei, Santa Clara, CA, USA
      1. Wants to understand the structure and dimension of Layer One 
      2. Goal is to build a stronger and more lasting foundation
    7. Mark Scott, San DIego, CA, USA
      1. Exploring all four of the initial WGs
      2. Generally more interested in the technical stack
    8. Steven Milstein, Ottawa, Canada
      1. Consultant, follower of SSI
      2. Interested in getting more deeply involved
    9. Arjun Govind, R3, typically in Philadelphia, currently in Bangalore
      1. Very interested in participating
    10. Sebastien Weidenbach, esatus AG, Technical Architect
    11. Markus Sabadello, co-founder, DanubeTech
      1. SSI architect
      2. Involved in the DHS Silicon Valley Innovation Program
      3. Sovrin Founding Steward
      4. Also operator of a Sovrin BuilderNet node
      5. Co-Chair of the Decentralized Identity Foundation Identifiers & Discovery (ID) Working Group
      6. Co-Editor, W3C Decentralized Identifier (DID) Specification
  2. Review of mission and scope
    1. André: we help as a community of practice for ToIP Layer One utility networks
    2. Drummond noted the ToIP Layer One utilities that are either existing or planned that may align with this mission
      1. Sovrin Network
      2. Bedrock Business Utility
      3. Findy (in Finland)
      4. Three forming in Germany—all are well aware of ToIP and aligned with interoperability with it—they are all interested in joining
        1. LISSI (Let's Initiate SSI), formally called SSI4DE (SSI for Deuscheland)
        2. govdigital—consortia of public data center providers in Germany that are planning a utility
        3. ECO Association of Internet companies in Germany
      5. Potential utility in Canada, possibly being incubated by the BC Gov Digital Trust Services team
      6. Austrian consortia that may be interested
        1. Banks, telcos, startups (DanubeTech has been an early participant)
    3. We broadly agreed that ToIP Layer One utilities are the foundational layer for decentralized PKI (DPKI)
  3. Proposed deliverables
    1. ToIP Utility RFP templates
    2. ToIP Utility Best Practices documents
    3. White papers
    4. ToIP Utility website including a directory of ToIP-compatible Utilities and Foundry Service Provider
    5. Workflow decision tree guidance <== proposed by DanG
  4. Potential Initial Work Items
    1. Develop ToIP Utility website and directory of ToIP-compatible Utilities
    2. Develop RFP templates and guides
    3. Develop ToIP Utility Best Practices documents and publishing process
    4. Initiate and maintain repository of relevant white papers and identify ToIP thought leadership white paper opportunities
    5. Build ToIP liaison with Utility projects and provide guidance
      • eco German Association of the Internet Industry (in planning)
      • Interop endeavors of govdigital and Findy
    6. Dan raised the liaison between a particular utility and a particular TIP (ToIP Interoperability Profile)
      1. Dan is interested in using this information to gauge market interest in particular Layer One technologies
  5. LF collaboration tools
  6. Github
    • Structure
      • Github training sessions/tools
  7. WG Chairs
    1. Dan Gisolfi is willing to volunteer (seconded by Drummond due to Dan's leadership in convening the Bedrock consortia)
    2. André Kudra was nominated by Darrell and seconded by Drummond
    3. We agreed to open nominations to the mailing list and formally agree on chairs in the next meeting
  8. Meeting time and cadence
    1. We agreed to stick with this meeting time slot once every two weeks
  • No labels