[Nsi-wg] Do we allow one NSA (by URL) to act for multiple networks?

[John MacAuley]

I had a funny feeling someone was going to bring this up :-)

You are correct in that we do need to distinguish between services, however, the NSA is not distinguished by the service endpoint.  A requester NSA can determine the protocol endpoint for a specific service and for a specific NSA through the Discovery Service.  If there are multiple NSA off of a common protocol endpoint, then the provider NSA element is used to determine the target NSA for that endpoint.  If the endpoint supports multiple services, then the service operation contained in the message will identify the specific service being targeted.

Does that address your concerns?  I wanted to make sure we clearly state that the providerNSA value should be the only value used to identify the NSA.  Would you like me to add the specific statement about how a shared endpoint should behave?

Thanks,
John

On 2013-01-31, at 4:20 AM, Jeroen van der Ham <vdham at uva.nl> wrote:

> 
> On 30 Jan 2013, at 23:10, Jerry Sobieski <jerry at nordu.net> wrote:
> 
>> --- Slide 4 last bullet:   If each NSI Service (e.g. Discovery Svc, Connection Svc, Topo Svc, etc)  is allowed to have different underlying messaging layer endpoints, (e.g. different SOAP endpoints) then the NSI messages cannot be delivered with *only* the NSA IDs (Slide 3 bullet 4).    Delivery will be dependent upon both the destination NSA ID *AND* the NSI service.    I.e. The destination NSI Service must also be known in order to differentiate and select the appropriate protocol (SOAP) end point.
> 
> No. The messages for the different services are different, thus it is very easy to differentiate between them.
> 
> Jeroen.
>