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

Verification strength could be introduced #48

Closed
JaapFrancke opened this issue Nov 11, 2016 · 1 comment
Closed

Verification strength could be introduced #48

JaapFrancke opened this issue Nov 11, 2016 · 1 comment

Comments

@JaapFrancke
Copy link

JaapFrancke commented Nov 11, 2016

Organization:
2

Type:

Reference (Include section and paragraph number):
3.2.2.1

Comment (Include rationale for comment):
The specification indicates various Verification Methods. The description implicitely suggests one method is perceived as stronger than others.
I think it could make sense to somehow classify or order the various methods, so the RP can more easily decide whether or not it will use the attribute.

See also related comments here: #19

Suggested Change:
Provide guidance for strength of methods, or introduce a new Accuracy-attribute named "Verification Strength".
The RP can then say: I'll accept anything with strength at least "3".

Order of strength is probably

  1. Not verified
  2. Proof of possession
  3. Record verification
  4. Document verification
  5. Document Verification with Record verification



Organization: 1 = Federal, 2 = Industry, 3 = Other

@RGalluzzo
Copy link
Collaborator

We like this idea, but within the scope of this document we do not intend to score the verification methods. In the future we may consider exploring how different aspects of attribute metadata can be used to provide scoring of the attributes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants