-
Notifications
You must be signed in to change notification settings - Fork 56
DSB Maintenance Iteration 13: Agenda & Minutes (9 November 2022)
Date and time: 9/11/2022, 2:00pm – 4:00pm AEDT
Location: Microsoft Teams Meeting
Dial-in details:
- https://teams.microsoft.com/l/meetup-join/19%3ameeting_MzRhZmJhZTctYzRhNi00ZGY4LTkxZDgtYWU5YWVmMjczMTBj%40thread.v2/0?context=%7b%22Tid%22%3a%22214f1646-2021-47cc-8397-e3d3a7ba7d9d%22%2c%22Oid%22%3a%2257cd8c59-9b50-4670-bc85-25281a11ec8d%22%7d
- Meeting ID: 496 099 061 829
- Passcode: qten9K
- Dial In Number: +61 2 9161 1229
- Phone Conference ID: 118 337 962#
- Quick Dial: +61 2 9161 1229,,118337962# Australia, Sydney
Chair: James Bligh, DSB
Maintenance overview: Further information
Maintenance project board: See here
Decision Proposal: This maintenance iteration is being consulted on under Decision Proposal 272: Maintenance Iteration 13
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 contact@consumerdatastandards.gov.au should they have any further questions or wish to have any material redacted from the record.
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, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.
- Introductions
- Outstanding Actions
- Release plan
- Open / Active Decision Proposals
- Proposing changes to the Standards
- Maintenance Iteration 13 Issues
- Any other business
- Next Steps
Meeting notes
The purpose of this meeting is to discuss proposals for the candidates under consultation in Maintenance Iteration 13.
- Retailers to raise a ticket on energy usage data covering multiple FRMPs. DSB to table this in their discussions with AEMO.
- Analysis ongoing
- The DSB has asked participants to publicly request Issue #479 be treated as urgent on GitHub.
None
- DSB to confirm with Energy retailers that readQualities in comment does not cause a breaking change.
- DSB to consider the timing of retros and advise on a planned approach.
- The purpose of the Retro is to review the Maintenance Iteration process not the outcome of it.
- We'll keep this action open to revisit the discussion at the end of MI13.
- Decision Proposal 259 for release 1.20.0 has been sent to the Chair for approval.
The following decision proposals are open for community feedback
| DP # | Decision Proposal | Closing date |
|---|---|---|
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Noting Paper | Noting Paper 255 - Approach to Telco Sector Standards | Link to consultation |
| Noting Paper | Noting Paper 258 - Independent Information Security Review | Link to consultation |
| Consultation | Decision Proposal 267 - Telco Data Language | TBD Link to consultation |
| Consultation | Decision Proposal 275 - Holistic Feedback on Telco Standards | TBD Link to consultation |
| Consultation | Noting Paper 276 - Proposed V5 Rules: Standards Impacts | TBD Link to consultation |
Review of October-December Quarter and new changes: https://github.com/ConsumerDataStandardsAustralia/future-plan/projects/1
Continue the discussion on channels available when proposing changes to the standards. See minutes from last meeting for more detail.
All open change requests can be found here: Standards Maintenance Issues.
The standards maintenance backlog can be found here: Data Standards Maintenance
-
Issue #479: Clarification on Minimum Algorithm Required for JARM
-
Issue #522: OpenID Provider Configuration End Point parameter requirements
-
Issue #547: Update SSA and Client Registration standards for JARM and Authorization Code Flow
-
Issue #535: Standard appears to redefine requirements for private_key_jwt authentication
-
Issue #546: Update Register and DCR Swagger specs to use Common Field Types
-
Issue #544: Update x-v header to be mandatory for Register APIs
InfoSec
-
Issue #479: Clarification on Minimum Algorithm Required for JARM
- ...
-
Issue #522: OpenID Provider Configuration End Point parameter requirements
- ...
-
Issue #405: Alternative mechanisms for OTP
- ...
-
Issue #547: Update SSA and Client Registration standards for JARM and Authorization Code Flow
- ...
-
Issue #535: Standard appears to redefine requirements for private_key_jwt authentication
- ...
Energy
Banking
Register
-
Issue #546: Update Register and DCR Swagger specs to use Common Field Types
- ...
-
Issue #544: Update x-v header to be mandatory for Register APIs
- ...
Non Functional Requirements (NFR)
-
Issue #534: Define concrete NFRs for unattended traffic during high traffic periods
- ...
-
Issue #541: Raising of Traffic Threshold NFRs specified in the CDS
- ...
Iteration 13 Holistic Feedback