Peoples, I think the existing detailed DTOX topology models we have been generating are excellent. I can definitely see how I will be able to incorporate this into future versions of OpenDRAC as a primary topology import mechanism, however, I do not think it is capturing the simplified concepts in NSI that are needed for the demo. I have been playing around with the example topologies trying to massage them into a form where I can learn not only the network and STP topologies, but the managing NSA topologies as well. I found that the existing DTOX topology is very good at the details of nodes, switch matrixes, and ports, but I had a hard time filtering down to the simple aspects. I also believe we will get into some trouble if we try to use the port class to model STP while also modeling physical ports. I am not sure if the DTOX schema can handle this aspect, as I could not find a describing schema. I spent time over the last couple of days discussing this with Jerry while we worked through the plug fest scenarios. He provided good feedback and pulled together the attached slide showing the concepts we are trying to capture. I also mocked up an example OWL file with an NSI topology specific name space, and introduced the NSI concepts of NSnetwork, STP, and NSA. These classes are used to model their simplified namesakes from the NSI CS protocol, and are not meant to replace the DTOX definitions, but augment them with our NSI specific concepts. We can consider the NSI topology elements an overlay on the existing DTOX elements, reusing data properties and including references to DTOX object instances. (I removed the DTOX object instances from the file to simplify the example). I think this will become much clearer when running NSI on out real networks and not this abstract topology for the demo. I have not yet validated the attached OWL so I apologize if it contains errors. The following classes and properties are introduced in the file… NSnetwork: We model a NSI network with the NSnetwork class. Example URN: urn:ogf:network:NSnetwork:Aruba Properties: · label - display name for the network. · canSwap - indicates VLAN Id interchange is supported in the network domain. · managedBy - the Network Services Agent managing this network. · hasSTP - a set of references to the inter-domain Service Termination Points that are within this network. · hasPart - a set of references to the DTOX Node NamedIndividual representing network elements within this network. NSA: We model a Network Services Agent with the NSA class. Example URN: urn:ogf:network:nsa:dracproxy01.surfnet.nl Properties: · label - display name for the NSA. · managing - indicates the network being managed by this NSA. · connectedTo - represents an NSA to which this NSA has a peering relationship. · dnsName - DNS name of the NSA. · csProviderEndpoint - the SOAP endpoint for this NSA's CS provider interface. · adminContact - administrative contact information for this NSA. STP: We model a logical Service Termination point with the STP class. Example URN: urn:ogf:network:stp:Aruba:Aiden Properties: · label - display name for this STP. · partOf - indicates the member network of this STP. · connectedTo - a topological link identifying the peer STP to which this STP is connected. · mapsTo - the logical STP represented by this object instance maps through to this physical entity (port, vlan, etx.) in DTOX. We will need to start up a discussion after the plug fest to address the issue of NSI topology needs. I believe these changes will do until then. Comments? Thank you, John.