Peoples,
I was running through the bootstrap procedure with Chin when the question of multiple NSA identifiers per software instance came up. Can someone please explain to me again why we need a one-to-one mapping between NSA (NSA identifier) and Network (Network Identifier)? It seems to be a very arbitrary restriction.
The WSDL does not define the framework or the protocol(s) - it simply defines the primitive interfaces. It does not express their functional meaning or semantics. You need to study the framework and/or protocols to make sure the protocol and framework continue to work properly in the face of the change you propose.I have looked through the existing WSDL definitions and there are no restrictions within it for this imposed rule. In addition, the topology schema could easily have multiple "managing" elements within the NSA object to allow it to reference multiple Network Identifiers, thereby creating a one-to-many relationship.
Can you describe the "very real network requirements" that cannot use separate NSA IDs for each service instance?
We have a very real network requirement to support multiple network services off of a single NSA software instance. For example, off of one NSA (urn:ogf:network:surfnet.nl:2012:nsa) we can support the ETS service (urn:ogf:network:surfnet.nl:2012:ets) and an EPL service (urn:ogf:network:surfnet.nl:2012:epl). At the moment, given the current restriction, I would have to have two separate NSA.
I actually think it is viable...with some explicit caveats:Does anyone have a reason why we can't remove this restriction?
Thank you,John
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg