Issues with implementing Cascaded time-outs (Signatures, etc)

[NicoDuvenage]

Request:

We have a story to assess Telescopic timings. As the expiry is clearly in the definition, this creates an issue when the Items are signed. We need to have a mechanism to remove this element from the encrypted data, or have a counter which increments for each hop in the process. So each party knows they have less time in the expiry before it is automatically withdrawn. Currently, a response can be received too late in the process – even though technically it is within the allowed time.

Artifacts:

• [ ] Artifact to consider [@Contributor]

Decision(s):

• [ ] Actual decision made as a result of discussion

Follow-up:

• [ ] Alternative actions

Dependencies:

• [ ] If Applicable

Accountability:

• Owner:

Notes:

[NicoDuvenage]

Issue transferred to CCB Discussion board