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

Identify device as endpoint or switch with LLDP #3

Open
sdhesika opened this issue Jun 8, 2017 · 1 comment
Open

Identify device as endpoint or switch with LLDP #3

sdhesika opened this issue Jun 8, 2017 · 1 comment
Milestone

Comments

@sdhesika
Copy link
Contributor

sdhesika commented Jun 8, 2017

Should we be using LLDP capacity type to identify whether attached device is an endpoint or a Network. For example: Switch (bridge - type =3) or Endpoint (Station - type = 8). This will help in multi-vendor switch environments.
Email thread:
https://basecamp.com/1791706/projects/12900329/messages/69380784

Thomas has added a user story for it in the following thread (user story copied below):
https://basecamp.com/1791706/projects/12900329/messages/69380784#attachment_287904223

As a networked media operator, I need my SDN controller to be able to distinguish between endpoints and network devices in a predictable and consistent fashion in a multi-vendor environment, so that network topology can be coherently inferred by the SDN controller and communicated to NMOS services so that NMOS services can effectively authorize the streams that I desire.

One proposal is similar to the one above with a small change:
If the network device can reliably do LLDP with Bridge type -3 and the endpoint can reliably do ARP (including receiver only endpoint), we have a solution to this issue. Please review and comment.

@garethsb
Copy link
Contributor

This is related to #32, and discussion in 'Full Stack' group. Perhaps with IS-06 as a northbound API, for true multi-vendor interoperability, a common southbound API (e.g. OpenFlow) needs to be discussed.

@NEOAdvancedTechnology NEOAdvancedTechnology added this to the v2.0 milestone Mar 30, 2020
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

3 participants