AMWA-TV / is-06

AMWA IS-06 NMOS Network Control Specification (Deprecated)
https://specs.amwa.tv/is-06
Apache License 2.0
14 stars 10 forks source link

Clarify constraints on a Network Device's LLDP configuration #32

Closed garethsb closed 4 years ago

garethsb commented 5 years ago

LLDP (IEEE 802.1AB) seems to allow both Chassis ID and Port ID to use a number of sub-types.

In IS-06, the JSON schemas and documentation require that a Network Device's chassis_id MUST be the MAC address and the port_id MUST be the "Ethernet Interface information" or "the ifAlias".

However I think the spec would benefit from a clear statement that requires the LLDP emitted by the Network Device (switch) to correspond, identifying the relevant sub-types.

garethsb commented 5 years ago

References:

Given the means of discovery likely to be available to the Broadcast Controller and IS-04 Nodes, I think this implies that the IS-06 specification requires LLDP transmitted by network devices (switches) MUST use Chassis ID sub-type 4 "MAC address" and Port ID sub-type 1 "interface alias". If that were not true, the IS-06 schemas could not be met by transferring data from the IS-04 Node "attached_network_device" to the IS-06 Endpoint.

Is that so?

I'm not sure that the spec(s) require that IS-06 Endpoints (IS-04 Nodes) must transmit LLDP? If they do, they presumably MUST use Port ID sub-type 3 "MAC address" in order that the switch can match it to the Endpoint "port_id"?

NEOAdvancedTechnology commented 4 years ago

Gareth to make pull request for consensus position

garethsb commented 4 years ago

What's missing is top-level documentation in IS-06 that says IS-06 Network Device interfaces MUST transmit LLDP, signalling Chassis ID = MAC address and Port ID = ifAlias, and that an IS-06 Endpoint interface must transmit LLDP, signalling Port ID = MAC address (so far as I can see, there is no constraint in either spec on which LLDP Chassis ID subtype a Node/Endpoint should use?).

Unless I'm mistaken and IS-06 is usable without LLDP?

NEOAdvancedTechnology commented 4 years ago

Issue is solved.