Story: Dataplane Signaling Implementation

[paullatzelsperger]

Feature Request

This issue serves as tracking issue for the Dataplane Signaling enhancement that was proposed in
this decision-record.

Additionally, this pull-request provides the technical architecture basics for it.

Which Areas Would Be Affected?

most Dataplane modules

Why Is the Feature Desired?

Allowing for better extensibility and customizability of the dataplane

Tasks on the control plane

• DPS: DataFlowRequest refactor #3908
• DPS: DataFlowController and DataFlowManager refactor #3899
• DPS: Implement a DataPlaneClient compliant with Signaling messages #3900
• DPS: DataPlane selection refactoring #3943
• DPS: Implement a new DataFlowController compliant with the signaling protocol #3901
• DPS: implement client side EDR cache #3898
• DPS: implements an EDR receiver compliant with the signaling spec #3968
• DPS: E2E test with HTTP pull scenario #3989
• DPS: extensions points to enrich DataFlowStartMessage #4043

Tasks on the data plane

• DPS: implement AccessTokenDataStore #3893
• DPS: implement DataPlaneAccessControlService #3894
• DPS: implement DataPlaneAccessTokenService #3895
• DPS: implement DataPlaneAuthorizationService #3896
• DPS: implement the Data plane Signaling API #3911
• DPS: Add Authorization to the Public API #3958
• DPS: DataPlaneManagerImpl refactor  #3990
• DPS: add support for terminate message  #3997

Common tasks

• Dataplane signaling: Define Signaling Messages and APIs #3897
• Story: add JSON-LD transformers for DataPlane Signaling #3934

Related tasks

• DSP 1.0: align DataAddress type with the new structure #3841
• DPS: Amend Architecture Document with sequence diagram #3903
• dsp: handle TransferSuspensionMessage #3350