Meeting Details

• Date and time: 18/09/2024, 2:00pm – 4:00pm AEST
• Location: Microsoft Teams Click here to join the meeting
• Dial-in details:
  • Meeting ID: 464 316 549 421
  • Passcode: NiYjec
  • Dial In Number: +61 2 6188 4842
  • Phone Conference ID: 969 637 712#
• Chair: Mark Verstege, DSB
• MI Solution Architect: Hemang Rathod
• Maintenance overview: Further information
• Maintenance issues: See here
• Maintenance project board: See here
• Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 356 - Maintenance Iteration 21
• Maintenance Iteration Meeting Schedule, Agenda and Meeting Notes: See here

Housekeeping

Recording

The Maintenance Iteration Calls are recorded for note taking purposes only. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material will be provided without the participant's consent. Participants may email [email protected] should they have any further questions or wish to have any material redacted from the record.

Acknowledgement of Country

We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.

We pay our respects to Elders past and present and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

Time management of Maintenance Iteration Meetings (if required)

• After the first meeting to groom the backlog, if the number of candidates and the anticipated complexity of them indicates timeboxing discussions is required, these time management practices will be put in place:
  • 5 minute delay will be removed. Meetings will commence at 2:00PM AEST.
  • Each discussion will be timed, if the discussion is not concluded within the allotted time, the discussion will be taken offline.
    • Allotted time will be determined based on the number of candidates in the iteration.
    • If the discussion on all issues has concluded and time remains, any issues scheduled for offline discussion can be revisited.
  • Start times will be estimated for each Domain and advertised when the Agenda is published.

Agenda

• Introductions
• Release Plan
• Maintenance Iteration 21 Candidates
• Requirements Analysis
• Other business

Introductions

Release Plan

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

Maintenance Iteration 21 Candidates

Carried over from MI 20

Domain	#	Issue	Change Type
Security	650	Weaken JARM Encryption Requirements for ADRs Waiting on information about data holders who require encryption on JARM responses.	Carry over to MI21

Requirements Analysis

Domain	#	Issue	Comments
Common	610	Addition of an (18 or over) Age Verification Flag.	DSB recommends closing this issue
Banking	553	Running balance available under transaction detail ACTION: ADR to clarify requirements in options proposed in original post. 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.
Banking	636	Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction 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.	Refer to NFR CG for async pattern
Energy	651	Supporting HTTP Status 429 passthrough from Secondary Data Holder ACTION: DSB to update issue as the details of the become available.	Trial in progress
Security	628	Addition of a DH-side endpoint for querying the status of a consent establishment flow
Security	649	Inconsistent JARM error codes	Relates to 628

Proposed for consideration

Domain	#	Issue	Comments
MI21	663	Maintenance Iteration 21 Holistic Feedback	Non-breaking
CX Guidelines	659	Enhancing CDR Adoption: Streamlining Account Selection and Improving Data Transparency.
Security	573	Clarification on handling of standard claims in request object.
Security	654	Clarify Transaction Security requirements.
Security	540	Data Recipient Software Product unable to indicate optional idtoken encryption requirement.
Security	666	Retirement of OIDC Hybrid Flow.
Security	667	Clean up of Refresh Token requirements.
Security	8	Adoption of detached signatures.
Banking	229	Service field in the Get Transaction Details API.	Related to 664 and 636
Banking	664	New Enums for Voluntary disclosure of additional service overlays.	Related to 229 and 636
Banking	656	A status of POSTED should indicate the final update for a transaction.	Related to 553
NFRs	660	Revise the Availability Requirements NFRs.	Pertains to Outages reporting and availability requirements
Admin	655	Get Metrics V5 error metrics documentation.

Any other business

Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.