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

Relabel Target Endpoint Identifier to Endpoint Identifier #78

Open
adammontville opened this issue Dec 10, 2017 · 3 comments
Open

Relabel Target Endpoint Identifier to Endpoint Identifier #78

adammontville opened this issue Dec 10, 2017 · 3 comments

Comments

@adammontville
Copy link
Contributor

It doesn't seem that a target endpoint identifier should be any different from the identifier for an endpoint that is not targeted.

@adammontville adammontville added bug and removed bug labels Dec 10, 2017
@henkbirkholz
Copy link
Member

An endpoint that is neither a Target Endpoint nor a SACM Component is an Excluded Endpoint (or "explicitly excluded target endpoint" if you will).

Having said that, it is correct that in this case we could omit the "target" in the term and the definition would be still correct.

I am neutral in this matter, with maybe slightly in favor of removing target in the term name and elaborating in the definition that this identifier is commonly used to differentiate and identify target endpoints.

@adammontville
Copy link
Contributor Author

Proposed definition:

Endpoint Identifier is a subset of endpoint attributes included in an endpoint characterization record, that is used to identify a given endpoint.

With expositional text:

Depending on the available identifying attributes, this reference can be ambiguous and is a "best-effort" mechanism. Every distinct set of identifying endpoint attributes can be associated with a target endpoint label that is unique in a SACM domain.

@henkbirkholz
Copy link
Member

I am okay with this change. One minor detail: I think we have to call it "identifying information elements" now.

adammontville added a commit that referenced this issue Jul 18, 2018
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