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

Consider Network Topology and Location Information as Primary Identifying Attributes #9

Closed
adammontville opened this issue Apr 17, 2015 · 5 comments

Comments

@adammontville
Copy link
Contributor

This issue was raised during an endpoint ID design team meeting (see notes for 2015-04-17).

@djhaynes
Copy link
Contributor

djhaynes commented Jan 6, 2017

We currently have an IE for location (see 7.52 in -08). I don't believe we have anything explicitly defined for network topology, but, someone can design one if they want and it can be used as an identifying attribute. We also no longer have a concept of primary/secondary identifying attributes. Given that, can we close out this issue?

@sacm
Copy link

sacm commented Jan 6, 2017 via email

@henkbirkholz
Copy link
Member

@dave: Could you please add a little bit more context or the URI of a resource that illustrates your input a bit?

@danny: As SACM is focused on the enterprise domain. Maybe link-layer neighborhood (or shared-broadcast-domain, which would imply a broadcast-domain label) could be an optional attribute for layer2 interfaces? For network layer something similar like a next-hop-routing-neighbor attribute might be feasible for layer3 interfaces?

@djhaynes
Copy link
Contributor

djhaynes commented Jan 9, 2017

@henkbirkholz would you be interested in defining a couple of IEs for describing network topology location?

@djhaynes
Copy link
Contributor

djhaynes commented Mar 6, 2017

Here's a link to the three words location scheme that David mentioned.

http://what3words.com/

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

4 participants