Internet-Draft DataRight+: Australian DataRight+ Profil September 2024
Low Expires 6 March 2025 [Page]
Workgroup:
datarightplus
Internet-Draft:
draft-authors-datarightplus-dio-profile-latest
Published:
Intended Status:
Experimental
Expires:
Author:
S. Low
Biza.io

DataRight+: Australian DataRight+ Profile

Abstract

This is the ecosystem profile for the Australian DataRight+ deployment, an extension upon the Australian Consumer Data Right. This specification seeks to extend, in a non-conflicting way, [PROFILE-AU-CDR] to enhance the functionality within the Australian ecosystem.

Notational Conventions

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 6 March 2025.

Table of Contents

1. Scope

The scope of this document is intended to combine the extensions created as part of the DataRight+ initiative into a profile that sits upon the baseline context of the Australian CDR, ostensibly described in [PROFILE-AU-CDR].

2. Terminology

This specification utilises the various terms outlined within [DATARIGHTPLUS-ROSETTA].

3. Providers

In addition to complying with the relevant provisions in [PROFILE-AU-CDR] Providers:

  1. MUST make available a discovery document as outlined in [DATARIGHTPLUS-DISCOVERY];
  2. MUST support, where appropriate, the provisions outlined in [DATARIGHTPLUS-VERSIONING];
  3. MAY support delivering the Banking Transaction Detail List as specified by [BULK-BANKING-TX-DETAIL]
  4. MAY support establishing Sharing Arrangements as specified by [DATARIGHTPLUS-SHARING-ARRANGEMENT-V2];

4. Initiators

In addition to complying with the relevant provisions in [PROFILE-AU-CDR] Initiators:

  1. MUST support Enhanced Versioning as outlined in [DATARIGHTPLUS-VERSIONING];
  2. MUST utilise the Provider discovery document as outlined in [DATARIGHTPLUS-DISCOVERY];
  3. MAY support accessing the Banking Transaction Detail List as specified by [BULK-BANKING-TX-DETAIL]
  4. MAY support establishing Sharing Arrangements as specified by [DATARIGHTPLUS-SHARING-ARRANGEMENT-V2];

5. Acknowledgement

The following people contributed to this document:

6. Normative References

[BULK-BANKING-TX-DETAIL]
Low, S., "DataRight+: Bulk Transaction Detail", <https://datarightplus.github.io/datarightplus-banking-bulk-transactions-v1/draft-authors-datarightplus-banking-bulk-transactions-v1.html>.
[DATARIGHTPLUS-DISCOVERY]
Low, S., "DataRight+: Discovery", <https://datarightplus.github.io/datarightplus-discovery/draft-authors-datarightplus-discovery.html>.
[DATARIGHTPLUS-ROSETTA]
Low, S., "DataRight+ Rosetta Stone", <https://datarightplus.github.io/datarightplus-rosetta/draft-authors-datarightplus-rosetta.html>.
[DATARIGHTPLUS-SHARING-ARRANGEMENT-V2]
Low, S. and B. Kolera, "DataRight+: Sharing Arrangement V2", <https://datarightplus.github.io/datarightplus-sharing-arrangement-v2/draft-authors-datarightplus-sharing-arrangement-v2.html>.
[DATARIGHTPLUS-VERSIONING]
Low, S., "DataRight+: Enhanced Endpoint Versioning", <https://datarightplus.github.io/datarightplus-enhanced-versioning/draft-authors-datarightplus-enhanced-versioning.html>.
[PROFILE-AU-CDR]
Low, S., "DataRight+: Australian CDR Profile", <https://datarightplus.github.io/datarightplus-cdr-profile/draft-authors-datarightplus-cdr-profile.html>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.

Author's Address

Stuart Low
Biza.io