Update arch diagram to match terminology #311
Conversation
Per 4.2, Issuers are producing signed statement (with their crecdentials). Credentials is not mentioned in the Terminology section, not Credentials
Identify the relying party on the architecture diagram These relying party can perform different actions
A specialised relying party is the auditor. Add it to the architecture diagram
thibmeu
requested review from
henkbirkholz,
ad-l,
fournet,
yogeshbdeshpande,
SteveLasker,
JAG-UK,
OR13 and
aj-stein-nist
as code owners
Forgot to push the previous change
thibmeu
changed the title
thibmeu
force-pushed
the
update-arch-digram-to-match-terminology
branch
from
ff6c724
to
1aef2c1
Compare
There was a problem hiding this comment.
Thanks, @thibmeu
LGTM
Minor tweaks to fix the aasvg corners:
|
@thibmeu I have a slight concern with the diagram. Normally Replay log is explicitly done by Auditor so Under Replay Log, if the role is Auditor that is a more correct representation than a Generic Relying Party what you have currently! Also, Log Replay is a resource consuming operation and should be careful in promoting that to a generic relying parties. I suggest renaming that aspect to Auditor |
|
Also I have a concern, Verify Transparent Statements is a job of any Relying Party, not specifically for the Auditor? Did you intend to attach, the Auditor role to Verify Transparent Statements? |
From the terminology I read this as the Auditor builds verified transparent statement, while the replay log is a specialised relying Party but not necessarily an auditor Removing Auditor is also a possibility to not put too many entities, since it's relying parties anyway. What do you think? |
|
@yogeshbdeshpande I've addressed your comments following a discusion we had in person
|
Update Figure 1 to include components from the Terminology.
The newly generated diagram looks as follow
