...

Schema Proposal

1. tbc

Code Proposal

...

1. For "network-resource", add string "network-type" attribute.
   1. Has enumerated values e.g. ETH topology or OTN topology.
2. For "pnf", add boolean "is-abstract" attribute.
   1. Has "false" value by default.
   2. Set to "true" value to represent abstract node, i.e. group of PNFs abstracted and presented as a single node by domain controller.
3. For "logical-link", new enumerated values for "link-type" attribute, e.g. intra optical domain, inter optical domain, or inter operator domain.
4. For "p-interface", add integer "inter-layer-lock-id" attribute.
   1. Has discovered values based on IETF specifications, for correlation between related objects in ETH topology and OTN topology.
   2. Add EdgeRule to represent p-interface to p-interface relationship described by "inter-layer-lock-id" attribute.
5. For "p-interface", new enumerated values for "interface-type" attribute, e.g. "Tunnel Termination Point".
6. For "p-interface", add integer "local-link-connectivity" attribute.
   1. Has discovered values for "Tunnel Termination Point" objects based on IETF specifications, for correlation between related "Tunnel Termination Points"
   2. Add EdgeRule to represent p-interface to p-interface relationship described by "local-link-connectivity" attribute.

Code Proposal

1. tbc

Discussion of Impacts

1. pnf is also involved in other use cases. What is the impact of introducing the "abstract node" concept?
2. link-type values for logical-link need to be modeled. What is the impact of introducing new values?
3. interface-type values for p-interface need to be modeled. What is the impact of introducing new values?