Meeting Notes

Release Plan

• Current version is v1.31.0.
• The outcome of Maintenance Iteration 20 will likely be published in v1.32.0.

Maintenance Iteration 20 Candidates

Holistic Changes

• #647 - Maintenance Iteration 20 Holistic Feedback
  • Not discussed, no additional items added and no comments from participants.
    • ACTION Participants are requested to review the comments posted on this issue for details of proposed changes and advise of any concerns.

CX

• #646 Clarify selection of Trusted Adviser in the CX Guidelines
  • Discussion on the issue focusses on Rule 1.10C(4)(b) in relation to proposed changes to selection of a Trusted Adviser as shown in CX Guidelines.
    • ACTION DSB CX to post comments from CDR Agencies in response to discussion once analysed.

InfoSec

• #648 - Adopt BCP 195 for TLS ciphers

  • Wording of change has been adjusted to align with FAPI 2.0.
  • No comments from participants have been received to indicate whether it will be a breaking change, however DSB will proceed with the change, comments still welcome.
    • ACTION DSB to stage the change.

• #650 - Weaken JARM Encryption Requirements for ADRs

  • No information on data holders who require encryption on JARM responses is available for discussion, defer to a later meeting.

Banking

• #641 - Update CDS documentation to clarify expected rate value 'sign' (+/-) for each RateType
  • Discussion on how rates are interpreted resulted in a consensus that the standards shouldn't change although further clarification on the descriptions be considered to maintain consistency throughout the standards. Consultation on DP306 included a similar change regarding negative values however there was feedback against that change.
    • ACTION: DSB to consider the changes needed and post on the issue.

Energy

• #644 - AmountString field type impractical for energy tariffs

  • Not discussed, 'No change' proposed as stated in this comment.

• #652 - Specify units of currency to be used for the AmountString field type

  • No change to the outcome from the last meeting, consensus to change the description and incorporate a statement "currency is AUD unless stated otherwise'.
    • ACTION: Participants to comment on the issue to indicate preferred wording change.
    • ACTION: DSB to incorporate the outcomes from the last meeting and feedback provided in related posts to provide an updated description.

• #653 EnergyPlanTariffPeriod - cater for plans with no dailySupplyCharge

  • CNI daily supply charge are incorporated within network pass through charges, therefore passing a zero value is not appropriate.
  • Proposing Option 2 with adjusted text to remove statement about 'absent' to accommodate feedback from AGL and retain the current FDO.
    • ACTION: DSB to update proposed solution on the Issue.
    • ACTION: DSB is interested in feedback on use of the field from ADRs.

Requirements Analysis

Common

• #610 - Addition of an (18 or over) Age Verification Flag
  • Not discussed as there have been no comments since last meeting.
    • OUTSTANDING ACTION: Participants to provide examples of use cases.

Banking

• #553 - Running balance available under transaction detail

  • Overview of a way in which ADRs can calculate running balances was described, based on this comment
  • ADR consensus is there are likely compliance issues that prevents ADRs interpreting the data and differences in the way DHs have interpreted and implemented the rules.
  • Suggestion to consider a working group to explore contributing issues.
  • Caution against working around the problem, regulator requires issues to be raised to explore the frequency and number of issues ADRs are experiencing.
  • Consideration of timestamp in balance endpoint to assist with reconciling against records already collected.
    • OUTSTANDING ACTION ADR to clarify requirements in options proposed in original post.
    • OUTSTANDING ACTION ADRs to investigate whether information exists on differences between data holders that illustrate the problems with calculated balances.
    • OUTSTANDING ACTION DHs to provide clarification on the difference between 'current' and 'available' balances.
    • OUTSTANDING ACTION DHs to provide details on how balances are calculated.
    • ACTION DSB to escalate issue 553 to the Regulator.

• #636 - Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction

  • Exploration into data quality concerns continues with SISS and NPP. Suggested additional fields have been added to the issue for comment.
  • Suggestion that amount of detail should be reduced due to the need to make separate calls for extra information within core banking systems before the information can be returned.
  • Number of calls to the transaction detail endpoint are increasing with that trend anticipated to continue.
  • Concern that current TransactionDetail API is not fit for purpose.
  • Suggestion that an asynchronous API be developed.
    • OUTSTANDING ACTION: DSB to following up with NPP. In progress
    • OUTSTANDING ACTION: DSB to schedule offline discussion with SISS (Josh) on data quality analysis. In progress
    • OUTSTANDING ACTION Participants to provide feedback on summary of earlier discussions in comment

Energy

• #651 Supporting HTTP Status 429 passthrough from Secondary Data Holder
  • Trial to commence in coordination with AEMO and ACCC.
    • ACTION DSB to review scope of trial, including timing of change with AEMO and other impacted participants and ACCC

Not discussed

Security

• #628 - Addition of a DH-side endpoint for querying the status of a consent establishment flow

Other business

None

Next Steps

DSB will progress analysis on solutions for Candidates for further discussion in the next meeting and stage solutions for community review wherever possible.