DSB Maintenance Iteration 20: Agenda (10 July 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Meeting Details
- Date and time: 10/07/2024, 2:00pm – 4:00pm AEST
- Location: Microsoft Teams Click here to join the meeting
- Dial-in details:
- Meeting ID: 494 389 362 467
- Passcode: PZFPkd
- Dial In Number: +61 2 6188 4842
- Phone Conference ID: 779 012 902#
- MI Chair: Elizabeth Arnold
- MI Solution Architect: Nils Berge
- MI CX Designer: Eunice Ching
- Maintenance overview: Further information
- Maintenance issues: See here
- Maintenance project board: See here
- Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 353 - Maintenance Iteration 20
- 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, if the number of candidates selected 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
- Requirements Analysis
- Maintenance Iteration 20 Candidate Selection
- Any other business
Introductions
The purpose of this meeting is to identify issues, raised on the standards-maintenance repository, as suitable candidates for Maintenance Iteration 20.
Requirements analysis on a number of items carried over from Maintenance Iteration 19 will continue. One candidate has also been carried over.
Release Plan
- The changes arising from Maintenance Iteration 19 were published in v1.31.0 on 3 July 2024.
- The outcome of Maintenance Iteration 20 will likely be published in v1.32.0.
Requirements analysis
| Domain | # | Issue | Comments |
|---|---|---|---|
| Security | 628 | Addition of a DH-side endpoint for querying the status of a consent establishment flow | Findings available in this comment Carried over from MI 19 |
| Banking | 636 | Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction ACTION: DSB to follow up with Dima on the request for Australian Payments to investigate and provide an opinion. ACTION: DSB to schedule offline discussion with SISS (Josh) on broader analysis outcomes. | Carried over from MI 19 Actions outstanding deferred to next meeting |
Maintenance Iteration 20 Candidate Selection
Maintenance Iteration 20 Holistic Issue
- For minor edits and corrections, please post requests on Issue #647 Maintenance Iteration 20 Holistic Feedback
Candidates carried over from Maintenance Iteration 19
| Domain | # | Issue | Change Type |
|---|---|---|---|
| CX / Documentation | 573 | Clarification on handling of standard claims in request object ACTION: DHs to compare what is advertised on OpenID configuration endpoint with authorization requests to determine if any discrepancies exist and whether ADRs are checking endpoints before requesting unsupported claims. ACTION: DSB to continue analysis of how ADR and DH should handle unsupported scopes in different scenarios, including the considerations mentioned above. | Carried over from MI 19 |
Maintenance Iteration 20 Candidates
Participants are invited to suggest issues for consideration.
CX
- Issue #646 - Clarify selection of Trusted Adviser in the CX Guidelines has been added to this Iteration at the request of the Data Standards Chair.
InfoSec
- Issue #648 Adopt BCP 195 for TLS ciphers has been added for security hygiene purposes. This issue will address stage 2 described in Issue #643 Update TLS cipher suite requirements to address DHEat Attacks and Raccoon Attack vulnerabilities, Stage 1 was implemented as a result of Maintenance Iteration 19 in v1.31.0.
Any other business
Participants are invited to raise topics related to the Data Standards that would benefit from the groups' consideration.