search

mojaloop / design-authority-project

This is the Issue and Decision Log for tracking mojaloop and related Designs
1 stars 2 forks source link

Discuss ILPv4 introduction to Mojaloop #114

Open bushjames opened 1 week ago

bushjames commented 1 week ago

Request Summary:

Note: Part of ISO-20022 workstream.

There are multiple issues to discuss when considering the adoption of ILPv4 in Mojaloop. This ticket serves as a place holder for those discussions and a way of recording DA views, opinions and decisions relating to this and related topics.

Note that ILPv4 is a precursor to native ISO-20022 interface due to the single crypto field available in the proposed spec.

Request Details:

A full impact assessment needs to be done. Note that this change will touch critical code areas and requires very thorough up-front design thinking.

Artifacts:

Dependencies:

Accountability:

Decision(s):

- **Approved By:** ### Details - [ ] Actual decision made as a result of discussion ## **Follow-up**: - [ ] Actions to implement the decisions
bushjames commented 1 week ago

Tentatively scheduled for discussion 11th September 2024 @ 0900 UTC.

bushjames commented 4 days ago

Discussed at DA meeting 2024-09-11 0900 UTC. @MichaelJBRichards presented the issues around using ILPv4 in Mojaloop ISO-20022 API instead of v1 as the move to ISO gives us an opportunity to update to the latest version. CCB likes the idea of using v4 in moja ISO API but is hesitant to update FSPIOP to v4 due to the volume of work required by MMO tech providers to upgrade also.

DA discussed the issues around supporting both v1 and v4 packets across FSPIOP and ISO-20022 APIs and made the following decisions:

(voting members present: @bushjames, @MichaelJBRichards, @PaulGregoryBaker, @vijayg10 , @elnyry-sam-k)

  1. The DA agrees that the Mojaloop ISO-20022 implementation should use ILPv4 packets exclusively.
  2. The DA agrees that FSPIOP v1.0 and v1.1 should continue to be supported and should use ILPv1 packets exclusively.
  3. Changes made to sdk-scheme-adapter aka Mojaloop Connector to support the Mojaloop ISO-20022 API must facilitate a configuration option to choose between the two main API types, FSPIOP or ISO. Each should use the appropriate ILP packet version as above.

Note that points 1 and 2 above imply that the switch will have to be able to cope with both types to ensure backward compatibility and must be able to determine which should be applied to validate ILP data given the incoming message formats.

Point 2 above shall be discussed in more detail at a later date.