-
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
None
None
- DSB to consider the timing of retros and advise on a planned approach.
Decision Proposals required ‼️ I want to delete this section plus discuss 409 and other items added to the future plan with James to make sure we don't have any overlap, I'm concerned about two things, 1) 409 92 has been created to cover 534 and 541 but I still think we need to create one more item for the future plan and 2) 90, 88 and 93 - looks like overlap ‼️
The following items have been created as backlog items on the future-plan board.
- Issue #409: Dynamic Client Registration Response Time NFR
- Issue #435: Nominated representative end user for non-individual consumers - introduction of an Agent API
- Issue #462: Make additional account attributes available in bulk
- Issue #534: Define concrete NFRs for unattended traffic during high traffic periods and Issue #541: Raising of Traffic Threshold NFRs specified in the CDS
- Implement a Party Relationships API to address 'relationship' and 'authority' data requirements arising from Issue #513: Specify if an Account is a joint account in the API response
- Issue #405: Alternative mechanisms for OTP
- Release 1.20.0 has been...
‼️
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 |
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
| Domain | Issue # | Issue | Proposal Status | Change Proposed | Standards Staging link |
|---|---|---|---|---|---|
| MI 13 | Issue #551 | Iteration 13 Holistic Feedback | N/A | ||
| InfoSec | Issue #479 | Clarification on Minimum Algorithm Required for JARM | |||
| InfoSec | Issue #522 | OpenID Provider Configuration End Point parameter requirements | |||
| InfoSec | Issue #547 | Update SSA and Client Registration standards for JARM and Authorization Code Flow | |||
| InfoSec | Issue #535 | Standard appears to redefine requirements for private_key_jwt authentication | |||
| Energy | Issue #475 | Representation of Spot price based contracts for C&I customers | |||
| Energy | Issue #520 | Stepped solar feed in tariffs in Energy | |||
| Banking | Issue #513 | Specify if an Account is a joint account in the API response | |||
| Register | Issue #546 | Update Register and DCR Swagger specs to use Common Field Types | |||
| Register | Issue #544 | Update x-v header to be mandatory for Register APIs |
-
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