April 2013 - Nsi-wg - lists.ogf.org

Wednesday's NSI conf call
by Guy Roberts 09 Apr '13

09 Apr '13

The following is dial-in information for Wednesday's NSI call. Time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 23:00 JST 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Agenda: - Updates on preparation of the NSI v2.0 document. _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

minutes from today's NSI call
by Guy Roberts 03 Apr '13

03 Apr '13

... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6529 _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

NSI v2.0 MTL / Coordinator doc
by Chin Guok 03 Apr '13

03 Apr '13

Hi all, Here's my cut at the MTL / Coordinator. Please enable tracking if you are editing the .doc file. Thanks! - Chin

1 0

Wednesday's NSI conf call (note time change due to start of European summer time)
by Guy Roberts 02 Apr '13

02 Apr '13

The following is dial-in information for Wednesday's NSI call. Time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 23:00 JST note new times 1. Dial Toll-Free Number: 866-740-1260 (U.S. & Canada) 2. International participants dial: Toll Number: 303-248-0285 Or International Toll-Free Number: http://www.readytalk.com/intl 3. Enter 7-digit access code 8937606, followed by "#" Agenda: - Discussion on state of NSI v2.0 document preparation. _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

2 1

Issue 77 in ogf-nsi-project: Update WSDL and XSD namespaces to final NSI release 2.0 values.
by ogf-nsi-project＠googlecode.com 01 Apr '13

01 Apr '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 77 by jmacau...(a)gmail.com: Update WSDL and XSD namespaces to final NSI release 2.0 values. http://code.google.com/p/ogf-nsi-project/issues/detail?id=77 Description of Issue: For protocol version ontrol we need to update the namespace URL in both the WSDL and XSD to represent the finalized version. -- 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

1 1

Issue 79 in ogf-nsi-project: Update WSDL and XSD with agreed changes in Charlottesville meeting.
by ogf-nsi-project＠googlecode.com 01 Apr '13

01 Apr '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 79 by jmacau...(a)gmail.com: Update WSDL and XSD with agreed changes in Charlottesville meeting. http://code.google.com/p/ogf-nsi-project/issues/detail?id=79 The following are the changes agreed in Charlottesville that need to be updated in the WSDL/XSD: 1. Reservation version number is optionally specified by the RA. 2. Common two phase reservation and modify. 3. Model Charlotteville state machine changes. 4. Add Coordinator/MTL messageDeliveryRetry request and messageDeliveryTimeout notification. 5. Add reserveTimeout notification to handle no reserveCommit received. 6. Add generic errorEvent notification to cover existing notification cases covered by notification message. 7. Add dataPlaneStateChange notification. 8. Include a view of the reservation criteria at each NSA in the recursive query. -- 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

1 1

Issue 78 in ogf-nsi-project: Change activation state machine to the new DataPlaneStatus concept
by ogf-nsi-project＠googlecode.com 01 Apr '13

01 Apr '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 78 by jmacau...(a)gmail.com: Change activation state machine to the new DataPlaneStatus concept http://code.google.com/p/ogf-nsi-project/issues/detail?id=78 Description of Issue: Data plane should be activated if the PSM is in “Provisioned” state AND start_time < current_time < end_time. Activation is done at the timing of following events (if the above condition is met), using the latest reservation information: - PSM transits to “Provisioned” - At the start_time - Reservation is updated (by commit of modify) - Data plane is recovered from an error Data plane activation/deactivation are notified by DataPlaneStateChange.nt notification messages. Errors are notified by a generic error message PA and aggregator has DataPlaneStatus information: - (Boolean) Active: True if data plane is active. For an aggregator, this flag is true when data plane is activated in all participating children - (Int) Version: For a uPA, current (latest) reservation version number. For an aggregator, the largest version number of the participating children. This field is valid when Active is true. - (Boolean) VersionConsistent: Always true for uPA. For an aggregator, If version numbers of all children are the same, This flag is true. This field is valid when Active is true. When a valid field of DataPlaneStatus is changed, DataPlaneStatusChange.nt is sent up. -- 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

1 1

Issue 55 in ogf-nsi-project: correlationId is unneeded and complicates implementation significantly
by ogf-nsi-project＠googlecode.com 01 Apr '13

01 Apr '13

Status: Accepted Owner: ---- Labels: Type-Review Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1 New issue 55 by thost...(a)gmail.com: correlationId is unneeded and complicates implementation significantly http://code.google.com/p/ogf-nsi-project/issues/detail?id=55 Description of Issue: The correlationId attribute in the WSDL messages is unneeded. Furthermore it requires correct implementations to persistently keep track of the correlationsIds of active requests. Discussion of Issue: The WSDL adds a correlationId to track the correspondence between a request and the subsequent update for the status. However this correspondence is unneeded as the request already contains information about the connection in question. However having the correlationId requires both the requester and provider to keep a persistent (as in on-disk) record of currently active requests, in order to be crash and restart safe, i.e., the service must be able to respond to requests that came before it crashed/restarted. The correlationId also means that state updates are not idempotent as the client can only receive a request (state update) once. However it cannot be guaranties that a message with a state update will only be send once due to the coordination of message dispatching and updating this information persistently, where there will always be a window which can lead to inconsistency, where the message must be retransmitted. Having to keep track of requests in this way, is called a state-full protocol (note that this does not mean a non state-full protocol doesn't have any state), and is usually considered a bad idea do implementation complexity and poor scalability in high-performance systems (arguably this is not what we have though), as it makes load balancing and redundancy significantly more tricky. Furthermore it must be remembered that not all requests will have a callback. E.g., a provision before start time (i.e., auto-provision) followed by subsequent terminate request, will result in a callback for terminate, but not for the provision request. Here the client must then clear all pending correlationIds, complicating the implementation (the client side issues are simple though). All this is further complicated by the fact that we haven't established if it is the provider or requester which is responsible for ensuring that correct connection state is updated. Resolution of Issue: Remove correlationId from the WSDL. This will make the state update messages (reserveConfirmed, etc.) idempotent, meaning they can be repeated. The requester will then update any state references about the remote connection to fit with the last received message (this also has problems, but none that doesn't exist in the current protocol).

1 3