Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intermediary System bullet in Section 6.3 #32

Open
wenjing opened this issue Sep 2, 2022 · 2 comments
Open

Intermediary System bullet in Section 6.3 #32

wenjing opened this issue Sep 2, 2022 · 2 comments
Assignees
Labels
priority: medium This issue is important to resolve before the next release. status: pr-in-progress The issue has been assigned and work is in progress. type: content The issue involves normative content; resolution requires group consensus.

Comments

@wenjing
Copy link
Collaborator

wenjing commented Sep 2, 2022

This text "Intermediary Systems may be required to assist in the interactions between the Endpoint Systems. Intermediary systems are involved in the ToIP Trust Spanning Protocol, and are themselves Endpoint Systems (for another ToIP Identifier Controller)(2)"
has several problems. Propose new text "Intermediary Systems may be used to assist in the interactions between the Endpoint Systems. In that context, Intermediary systems are involved in the ToIP Trust Spanning Protocol, and may themselves be Endpoint Systems. Intermediary systems are not a dependency to Endpoint systems' trust relationship."

Also footnote (2) should be removed. That information is not central to this text and brings in a set of unexplained dependencies on Aries and Aries RFC which can be misleading and problematic.

@wenjing wenjing self-assigned this Sep 2, 2022
wenjing added a commit that referenced this issue Sep 2, 2022
Update Section 6.3 to draft 3 with edits to the bullet point on Intermediary Systems, including removing footnote 2. See issue #32
@talltree
Copy link
Collaborator

talltree commented Oct 13, 2022

This text "Intermediary Systems may be required to assist in the interactions between the Endpoint Systems. Intermediary systems are involved in the ToIP Trust Spanning Protocol, and are themselves Endpoint Systems (for another ToIP Identifier Controller)(2)"
has several problems. Propose new text "Intermediary Systems may be used to assist in the interactions between the Endpoint Systems. In that context, Intermediary systems are involved in the ToIP Trust Spanning Protocol, and may themselves be Endpoint Systems. Intermediary systems are not a dependency to Endpoint systems' trust relationship."

+1 to this change.

@talltree
Copy link
Collaborator

talltree commented Oct 13, 2022

Also footnote (2) should be removed. That information is not central to this text and brings in a set of unexplained dependencies on Aries and Aries RFC which can be misleading and problematic.

While I don't entirely disagree, this footnote was suggested by @dhh1128 and I thought it added a lot of value in terms of explanatory power. For context to those new to this thread, here is the text of footnote (2):

The distinction between Intermediary Systems and simple routers on the Internet is well described by the Hyperledger Aries community in Aries RFC 0046. The terminology mapping is: "Intermediary System" = Aries "mediator", and router on the internet = Aries "relay".

Since in section 10 we have examples where we do cite explicit technologies in order to illustrate specific patterns, could we do the following:

  1. Change the footnote to reference section 10.1, where we have an example of Hyperledger Aries architecture.
  2. Work the substance of the current footnote either into the text of section 10.1, or into a footnote there.

@talltree talltree added priority: medium This issue is important to resolve before the next release. status: pr-in-progress The issue has been assigned and work is in progress. type: content The issue involves normative content; resolution requires group consensus. labels Oct 14, 2022
@talltree talltree self-assigned this Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium This issue is important to resolve before the next release. status: pr-in-progress The issue has been assigned and work is in progress. type: content The issue involves normative content; resolution requires group consensus.
Projects
None yet
Development

No branches or pull requests

2 participants