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

"Endpoint Attribute" should probably not use "Information Element" in its definition. #42

Closed
adammontville opened this issue Jul 17, 2017 · 2 comments
Assignees

Comments

@adammontville
Copy link
Contributor

At present the definition of Endpoint Attribute begins with: "In the context of SACM, endpoint attributes are information elements..." Information Element is defined as "a representation of information about...objects of interest", and it is pointed out that Information Elements are part of our Information Model (building blocks, in fact). Does this, to anyone else, seem as though we are stating the "Endpoint Attribute" is an "Information Element"?

Concretely, the endpoint attribute "password length" is not actually on the endpoint, but is an information element in our information model with value 14.

Is there a way to define Endpoint Attribute without relying on how we intend to model it?

@henkbirkholz
Copy link
Member

henkbirkholz commented Jul 17, 2017

The declarative guidance on password length is indeed not an endpoint attribute. The actual length of a password (which hopefully cannot be inferred for security reasons) would be an endpoint attribute.

Not every Information Element is an Endpoint Attribute.

@adammontville
Copy link
Contributor Author

Aha! Ok, now things are starting to shape differently in my mind. Thank you.

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