Desktop Agent Bridging meeting today at 2pm BST / 9am EST

0 views
Skip to first unread message

Kris West

unread,
Aug 24, 2022, 6:28:11 AM8/24/22
to fd...@finos.org
Hi All,

The FDC3 Desktop Agent Bridging Discussion group meeting is today @ 2pm BST / 9am EST:

WebEx info

Agenda

  • Convene & roll call, review meeting notices (5mins)
  • Review action items from the previous meeting (5mins)
  • Review updates to the proposal (35 mins)
    • Current proposal [WIP] 544 desktop agent bridging proposal #634Preview: https://github.com/finos/FDC3/blob/544-Desktop-Agent-Bridging-Proposal/docs/api-bridging/spec.md
    • Changes:
      • Fixed typos found during last meeting.
      • Clarified use of DesktopAgent identity fields and update meta.source to be of AppIdentifier OR DesktopAgentIdentifier type.
      • Added new DesktopAgentIdentifier type (for use on response messages that don't originate from an app, e.g., findIntent responses).
      • Removed meta.destination from responses messages. Response collation and routing should be performed using requestGuid only.
      • Completed set of payload fields used on request and response messages.
        • with the exception of handling for PrivateChannel events
      • Procedure for forwarding of Messages and collation of responses
      • Broke down the previously specified bridge timeout range to be 1500ms on the bridge side and added Desktop Agent timeout (waiting for bridge responses) to be 3000msAdded recommendation on Desktop Agent timeout handling behaviour when bridge stops responding
        • Added behaviour for an agent that is repeatedly timing out - Bridge should disconnect agent
        • Added details of workflows broken by disconnection and agent and bridge behaviours
        • Proposed new errors to add to Error enumerations
      • Added recommendation of a minimum wait period of 5 seconds on reconnection attempts
      • Added a list of FDC3 API calls that do NOT generate bridge messages.
  • Discussion of open issues (10 mins)
    • Advise on whether other agents report to users on connect/disconnect events? (SHOULD)
    • Next steps
      • Expand on how the DAB should create the JWT token (and its claims, which must change to avoid replay attacks) which it sends out in the hello message for DAs to validate.
      • Handling for PrivateChannel events
      • Complete detail on individual message exchanges
  • AOB & Adjourn (5mins)

See you there!

K

--

Kris West

Principal Engineer

Finsemble  
+1 (800) 821-8147
kr...@cosaic.io
Reply all
Reply to author
Forward
0 new messages