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

Altenatives test case spec clarifications #79

Open
jordig100 opened this issue Jun 12, 2023 · 1 comment
Open

Altenatives test case spec clarifications #79

jordig100 opened this issue Jun 12, 2023 · 1 comment
Assignees

Comments

@jordig100
Copy link
Collaborator

Missing to clarify in the table page 63, the Secure E and E_A meaning.

I think E is just encripted but not access, and E_A encrypted but not access.

Is this correct?

What are the cases where you have an non-supported extension and another alternative with a supported extension? Not clear in the table.

@JimZuber
Copy link
Collaborator

A few comments....
1)The test case where we have non-supported and supported extensions is P_XPX_0722_02

2)I notices some typos in the pass/fail criteria for test case P_XPX_0722. "08" should be deleted. "07" should be "04"

3)Agreed, I forgot to put the definition in for E and E_A, which is as follows. The meaning of E_A is the inverse of what you guessed. An E by itself means that it is encrypted but the consumer does not have access.

E = Encrypted
A = Consumer has access to encrypted model

Assume we can make these updates whenever other updates are done. If urgent, I could do it now.

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

No branches or pull requests

2 participants