Ivan Petrov

Though we need to understand how to pass measurements in a generic way (considering that we'll have custom measurements)

> I personally don't like the name "attester" for this. This is specific to DICE (not generic attestation), and it does a much narrower thing that attesting in that it...

Stage0 `Attester` can contain the code that generates the Attestation Report. The idea is that we have attesters in each layer, and the last layer's attester becomes the one that...

Measurements can also be implemented via a `trait MeasurementProvider`, and they could run as part of the attester. I'm just trying to abstract the attestation logic behind one interface.

We still need an object from which we could request the `Evidence` (not the DICE data), for example when the Hostlib or an application wants to get an evidence.

We can keep the concept of attester as an object from which you could request an `Evidence` and make it a trait: ```rust trait Attester { fn get_evidence(&self) -> Evidence;...

> They won't even have the same evidence format, since there are no concept of layers in RTMRs. Ok, will not add a trait, and will keep a name `DiceAttester`,...

> @ipetr0v is this still relevant or useful for discussion? or can it be closed? I'll close this PR since it's outdated. But I still think it may be benefitial...

Replaced by https://github.com/project-oak/oak/pull/4722

Replaced by: - https://github.com/project-oak/oak/pull/4543 - https://github.com/project-oak/oak/pull/4722 - https://github.com/project-oak/oak/pull/4814 - https://github.com/project-oak/oak/pull/4961