DSB Maintenance Iteration 19: Agenda (12 June 2024) - ConsumerDataStandardsAustralia/standards GitHub Wiki
Meeting Details
- Date and time: 12/06/2024, 2:00pm – 4:00pm AEST
- Location: Microsoft Teams Click here to join the meeting
- Dial-in details:
- Meeting ID: 465 176 022 288
- Passcode: gWgzgd
- Dial In Number: +61 2 6188 4842
- Phone Conference ID: 193 570 554#
- Chair: Elizabeth Arnold, DSB
- MI Solution Architect: Hemang Rathod, DSB
- Maintenance overview: Further information
- Maintenance issues: See here
- Maintenance project board: See here
- Maintenance Iteration Decision Proposal: Consultation on Decision Proposal 347 - Maintenance Iteration 19
- Maintenance Iteration meeting Plan and Minutes: 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.
Agenda
- Introductions
- Maintenance Iteration 20
- Release Plan
- Requirements Analysis
- Maintenance Iteration 19 Candidates
- Any other business
Introductions
The purpose of this meeting is to finalise the documentation for solutions on Maintenance Iteration 19 candidates. Where this is not possible the candidate will be moved to Maintenance Iteration 20.
Maintenance Iteration 20
Commencement date is 10 July 2024.
The DSB is no longer issuing calendar invites from the Contact account, however everyone Registered for MI19 will have received an invite to Register for MI20. New participants can Sign up and please keep an eye out for the step where you select the calendar type to receive the invitation.
Release Plan
- The outcome of Maintenance Iteration 19 will likely be published in v1.31.0. A decision document is being prepared for the Data Standards Chair.
Requirements analysis
| Domain | # | Issue | Comments |
|---|---|---|---|
| Common | 610 | Addition of an (18 or over) Age Verification Flag | See this comment for an update. |
| Security | 628 | Addition of a DH-side endpoint for querying the status of a consent establishment flow | Findings available in this comment Continue discussion in MI20 |
| 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. | In progress |
Maintenance Iteration 19 Candidates
| Domain | # | Issue | Change Type |
|---|---|---|---|
| MI19 | 638 | Maintenance Iteration 19 Holistic Feedback | No Change |
| CX | 633 | Collection Consents - Authorisation Amendment ACTION: Participants required to indicate preference for Options 1 - 4. | Non-breaking change |
| Energy | 640 | Retirement date for Get Generic Plan Detail v2 and Get Energy Account Detail v3 ACTION: Energy retailers requested to comment on the thread to determine appropriate retirement date | Non-breaking Change |
| Documentation | 362 | Security Profile: Request Object - Inconsistency in example for sharing_duration and cdr_arrangement_id ACTION: Request for participants to comment on the ticket to clarify requirements. | No change |
| Documentation | 415 | Disambiguation of the claims for a response from the introspection endpoint | |
| 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. | Carry over to MI20 |
| Documentation | 615 | Plan Obligation Milestones for 2025 ACTION: Participants to indicate the proposed 2025 dates are suitable.. | Non-breaking change |
Any other business
Participants are invited to raise topics related to the Consumer Data Standards that would benefit from the groups' consideration.
The DSB would like to raise and discuss Issue #643 Update TLS cipher suite requirements to address DHEat Attacks and Raccoon Attack vulnerabilities