Meeting Date

  • The ToIP Trust Registry Task Force (TRTF) meets weekly twice every Thursday at the following times (to cover global time zones - see the Calendar of ToIP Meetings for full meeting info including Zoom links):
    • NA/EU 07:00-8:00 PT / 15:00-16:00 UTC 
    • APAC 18:00-19:00 PT / 02:00-03:00 UTC

Zoom Meeting Link / Recording

Attendees

NA/EU Meeting


Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
5 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • 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.
  • New Members:
1 minReminder - TSWG2 Mailing ListChairs

Reminder that the Technology Stack Working Group has a new mailing list. You need to join this as it involves the new charter that TSWG is operating under. You can do that here:

5 minReview of previous action itemsChairs



15 minOIDF usage in the wild

Mathieu Glaude or

Darrell O'Donnell 

Discussion of FindyNet and it's OIDF-based trust registry.

FindyNet

  • Government-funded initiative to support the development of digital trust
  • OIDF initiative was funded
  • Northern Block & Sphereon are working on it - working on libraries, plus adding some APIs (o/s as well).
    • Northern Block is incorporating this into their trust registry offering as a module
  • banking world (GAIN, etc.) has a lot of OIDF investment
  • OIDF is broad and needs profiles (e.g. open banking has a profile)
    • ...
  • Works in a hierarchical ecosystem
    • Mathieu Glaude will see about finding someone that can brief TRTF about OIDF and its real-world use.
  • Andor - noted a lack of o/s libraries for OIDF
  • Claims through Entity Statements, etc.
    • Profiles (OIDF) will help 


15 minsTRP Marketing Problem

Darrell O'Donnell 

  • People are still not understanding that TRP has a simple role of standardizing and simplifying the requests made of a system of record. 
  • They think TRP is a trust registry architecture.
  • how do we fix this?

DNS:

  • READs - cRud - whois & RDAP (registry data access protocol) - RESTful
    • Billions DNS reads/sec
  • UPDATES/MANAGEMENT - CRUD - EPP (extensible provisioning protocol) - CIRA adding RESTful here
    • 10-100 activities/sec

10 whois (runs over RDAP anyway) , 10Mn DNS queries/sec (Bns/sec)

EPP: 10-100/second

RDAP could provide TRP capability too.

Assets of a trust registry:

RFC 7482 - Registration Data Access Protocol (RDAP) Query Format (ietf.org)

    • Registrations - 
    • Registrants -
    • Trust Relationship - 
    •  

NAMING PROBLEM:

  • Trust Registy QUERY Protocol
    • TRQP RESTful API  
    • RDAP 
      • /rdap/trust/...
    • DIDComm Protocol 
    • ...

ADDITIONAL NEEDS:

  • Marketing (What IS the TRQP? What does it NOT do?)
  • When does it apply?
  • When should a systems integrator use TRP? When should they NOT use it?



CIRA - Canadian Internet Registry Authority for Canada

RDAP - https://www.rfc-editor.org/rfc/rfc7482

Could create an RDAP implementation for TRQP.

  • TRQP RDAP implementation

“Registration Data Access Protocol (RDAP) Query Format”

TRP - Query Format... Andrew Escobar 

10 minsEIC Summary

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



Screenshots/Diagrams (numbered for reference in notes above)

#1

rdap/trust/

#2




Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels