You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: