Hi, From a topology point of view I don't see any restrictions. Jeroen. On 6 Mar 2013, at 22:28, John MacAuley <john.macauley@surfnet.nl> wrote:
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.
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.
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.
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