-
Notifications
You must be signed in to change notification settings - Fork 6
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
Comments
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? |
Maybe you should look at the way in which what three words is being used, or the hot desk deployments in the largest incident response center in the world in new york for desk taps!
Best Regards,
Dave
David S. Misell MBCS MIET CISSP
david.misell@bcs.org
07710380044
misell.dave on skype
… On 6 Jan 2017, at 19:41, Danny Haynes ***@***.***> wrote:
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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
_______________________________________________
sacm mailing list
***@***.***
https://www.ietf.org/mailman/listinfo/sacm
|
@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? |
@henkbirkholz would you be interested in defining a couple of IEs for describing network topology location? |
Here's a link to the three words location scheme that David mentioned. |
This issue was raised during an endpoint ID design team meeting (see notes for 2015-04-17).
The text was updated successfully, but these errors were encountered: