[Nsi-wg] Issue 76 in ogf-nsi-project: Change WSDL so connection identifier is allocated by provider NSA

[ogf-nsi-project at googlecode.com]

Status: Accepted
Owner: jmacau... at gmail.com
Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0

New issue 76 by jmacau... at gmail.com: Change WSDL so connection identifier  
is allocated by provider NSA
http://code.google.com/p/ogf-nsi-project/issues/detail?id=76

Description of Issue:
In NSI CS v1.1 the requesting NSA provides the connection identifier that  
is used to reference the connection within the provider NSA.  This implies  
a connection can only be identified by the tuple (Requester NSA, Provider  
NSA, connection ID).  Furthermore, the context of a connection identifier  
is only addressable from the point of view of the Requesting NSA since we  
do not provide the ability to specify the referencing tuple within the  
existing protocol specification.  As a result, no external entities are  
able to reference a reservation within a provider NSA.

Resolution of Issue:
E-mail list discussion in late August 2012 agreed to changing the NSI CS  
v2.0 protocol to allow for provider allocated connection identifiers.  The  
following changes were agreed to:

1. In the ACK to the reservation request the Provider NSA will return the  
reservation ID it has associated with the new reservation.

2. The reservation confirm will still return the result of the reservation.

3. Connection Identifier specification will be relaxed to remove the need  
for a UUID.



-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings