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

Should we define "Endpoint Profile" or "Profile"? #45

Closed
adammontville opened this issue Jul 17, 2017 · 1 comment
Closed

Should we define "Endpoint Profile" or "Profile"? #45

adammontville opened this issue Jul 17, 2017 · 1 comment
Assignees
Labels

Comments

@adammontville
Copy link
Contributor

Endpoint Characterization mentions a "profile" of endpoint attributes, and Endpoint Classification states that an "endpoint profile" is a form of declarative guidance used to define a class of endpoints. Do we need to explicitly define either "profile" or "endpoint profile"?

@henkbirkholz
Copy link
Member

That is worthwhile, I think.

"Endpoint Profile" is very useful - but we have to point out that it might refer to more than one target endpoints and more than one "Endpoint Profiles" might point to a single target endpoint... depending on the information that can be acquired to compose the "Endpoint Profile". Without a well-known "trusted" (RFC4949) label, there can be this ambiguity in expressiveness.

As a reference, "Identity" from RFC4949 allows for this ambiguity.

RFC4949 references the CC protection profile. To be more aligned with CC we could pull in some reference of "security target" and therefore know what the declarative guidance side is.

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

No branches or pull requests

2 participants