That is a good question. I like the way you track vlans in the current port object. Very simple. However, it is not really modelling the concept of a vlan service topology. With the STP concept being a port abstraction, we need a way to point an STP to underlying network constructs. For example, in one version of STP I pointed it to an Ethernet port and had stored a vlan id in the STP to indicate the STP was modelling a specific vlan. Jerry pointed out that this would complicate the STP definition, and therefore, we should point it to a modelled vlan instead of directly to a port. Is NML planning on modelling Ethernet services as another topological layer with dedicated objects? On 2011-08-24, at 3:52 AM, Jeroen van der Ham wrote:
On 23 Aug 2011, at 00:04, John MacAuley wrote:
On 2011-08-22, at 5:10 AM, Jeroen van der Ham wrote:
How do you envision labels to be added to the above topology?
When you say labels do you mean the display names as I have used then here or VLAN tags?
I mean VLAN tags in the current topology, but wavelengths, timeslots, et cetera in future topologies.
Jeroen.