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

Topology Distribution document
by Jeroen van der Ham 31 May '13

31 May '13

Hi all, I've uploaded a new version of the Topology Distribution Informational GFD. This document discusses the requirements and possible solutions for the topology distribution for NSI as we have identified them so far. (Note that this is different from the Topology Syntax document which defines the syntax to be used. That is going to be an RP instead of an Informational). The document can be found at https://redmine.ogf.org/dmsf_files/12980?download= Jeroen.

2 4

Re: [Nsi-wg] Issue 5 in ogf-nsi-project: Query on requester interface - is this needed?
by ogf-nsi-project＠googlecode.com 22 May '13

22 May '13

Comment #7 on issue 5 by imo...(a)gmail.com: Query on requester interface - is this needed? http://code.google.com/p/ogf-nsi-project/issues/detail?id=5 This discussion was not concluded, but I will capture the thoughts as were shared on the call: 1. Query as a separate WSDL was discussed, issue 22 has also been opened for this 2. The main use-case was monitoring or management agents that might not be NSAs. Unanswered questions are: a. Can query work if the entities querying are not NSA agents? b. Should query be a separate WSDL in any case? c. Which credentials - user credentials or peer relationships when walking the service tree? 3. There was support on the call for the need for query in both directions whether it be commercial networks or research networks scenario. This discussion was not deemed important for 1.0SC and resolution postponed till another date Inder

1 2

Wednesday's NSI call
by Guy Roberts 29 Apr '13

29 Apr '13

Hi all, 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. - Reservation versioning and state machine - runtime schema validation - Removal of globalReservationId from the GenericConfirmedType. - Removal of the GenericConfirmedType and GenericRequestType. _____________________________________________________________________ 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

Reserved State Machine
by Henrik Thostrup Jensen 29 Apr '13

29 Apr '13

Hi I think some of the confusion around the Reservation State Machine (RSM) comes from that a connection can have multiple revisions and that each revision can actually go through the states. This makes it very tricky to have a state machine that works across multiple revisions. A better approach might be to have an RSM per revision. I have attached a PDF of how I think such a state machine could look. Reserve_Aborted is now a stable state, indicating that the revision has failed. A new revision can be started from all stable states. This makes it very clear where each revision is in its lifecycle. There could be a state after Reserve_Committed to indicate that the reservation has been superseeded by a new revision, but since we probably wouldn't expose that, I don't think it is strictly needed. The Provision State Machine (PSM) and Lifecycle State Machine (LSM) should be per connection. On a side note: I think having 2PC will create more problems than it solves, as getting that to work in a multi-domain environment is going to be very tricky. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

2 1

WSDL changes
by John MacAuley 25 Apr '13

25 Apr '13

Peoples, As I go through the documentation process, and we finalize some of the last open items, we will be sending e-mail requesting approval. It would be appreciated if you could please make it a priority to provide feedback as soon as possible so we can get resolution and move forward. Henrik has requested the removal of "globalReservationId" from the GenericConfirmedType since it is a convenience element only. I have no issue with the proposed change but want to make sure no design teams are using the capabilities. At the bottom of the e-mail is the component that will be modified. In addition, Henrik has proposed the collapse of the GenericConfirmedType and GenericRequestType to remove the separate type wrapper and make the impacted messages of type ConnectionIdType. For example, the provision message set would not be defined as the following: <xsd:element name="provision" type="tns:ConnectionIdType" /> <xsd:element name="provisionConfirmed" type="tns:ConnectionIdType /> So I am asking for approval on the following two items: 1. Removal of globalReservationId from the GenericConfirmedType. 2. Removal of the GenericConfirmedType and GenericRequestType. Thanks, John <xsd:complexType name="GenericConfirmedType"> <xsd:annotation> <xsd:documentation xml:lang="en"> This is a generic type definition for a "Confirmed" messages in response to a successful processing of a previous "Request" message such as provision, release, and terminate. Elements: globalReservationId - An optional global reservation id that was originally provided in the reserve request. connectionId - The Provider NSA assigned connectionId for this reservation request. This value will be unique within the context of the Provider NSA. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element name="globalReservationId" type="tns:GlobalReservationIdType" minOccurs="0" /> <xsd:element name="connectionId" type="tns:ConnectionIdType" /> </xsd:sequence> </xsd:complexType>

1 0

Today's NSI conf call minutes
by Guy Roberts 24 Apr '13

24 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

Wednesday's NSI call
by Guy Roberts 23 Apr '13

23 Apr '13

Hi all, 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. - Synchronous query usage - Reservation versioning and state machine - Subscribing to notifications _____________________________________________________________________ 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

Issue 80 in ogf-nsi-project: Move XML types definitions from WSDL files to main XML schema.
by ogf-nsi-project＠googlecode.com 23 Apr '13

23 Apr '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-2.0 New issue 80 by jmacau...(a)gmail.com: Move XML types definitions from WSDL files to main XML schema. http://code.google.com/p/ogf-nsi-project/issues/detail?id=80 Description of Issue: XML validation in some Java toolkits cannot do schema enforcement when XML schema is defined in WSDL files. Resolution of Issue: Move XML types definitions from WSDL files to main XML schema. -- 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

Proposal: Subscribing of events in NSI
by Henrik Thostrup Jensen 19 Apr '13

19 Apr '13

Hi At the meeeting yesterday John brought up the point of where notifications should be send to, as this is currently not properly defined. This is for messages such as dataPlaneStateChange and errorEvent (which includes forcedEnd and other). One solution is to use the replyTo that was specified during the initial reserve. This has a number of limitations though, as it is not possible to change the where notification events go, and it is not possible to notify multiple parties. Instead we came up with the suggestion of explicit subscriptions. This means including to new messaging primitives for subscribing and subscribe to notifications. Furthermore we would add a way to indicate subsription in the header for future events. This allows subscribing in a reserve without having to send a seperate subscribe message. This can either be a flag indicating to use the replyTo field or a seperate field (are there any uses for different replyTo and subscription events). Implications of adding this: * Two new message primitives: subscribe and unsubscribe. - A subscribe message will have a single endpoint, and can specify a number of connection ids. - The return message should specify which connection ids the subscription succeeded * A flag or a field in the header for subscribing. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

3 3

Wednesday's NSI conf call
by Tomohiro Kudoh 17 Apr '13

17 Apr '13

Hi all, 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. - Synchronous query usage ---- Tomohiro Kudoh t.kudoh(a)aist.go.jp Information Technology Research Institute National Institute of Advanced Industrial Science and Technology (AIST) Tsukuba-Central 2, 1-1-1 Umezono Tsukuba Ibaraki 305-8568 Japan Phone: +81-29-861-5761 Fax: +81-29-862-6601

4 3