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

NSI working group meeting @ Maastricht
by Guy Roberts 04 Jun '13

04 Jun '13

Hi All, This is a reminder that we will have an NSI working group meeting on Friday afternoon between 13:30-17:30 in the MECC building following the GLIF meetings. This will be a closed working group meeting and for this reason it will not appear on the GLIF agenda. No registration is required to attend the event. The target for this meeting is to review the draft NSI CS protocol v2.0 document and agree to submit it for public comment. I will send the meeting room details to this list as soon as I have them. Regards, Guy _____________________________________________________________________ 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

More document reviewing
by Henrik Thostrup Jensen 03 Jun '13

03 Jun '13

Hi everyone I've reviewed section 4, 5, 6 in the document. Have attached the document (based on v14) with tracking changes (next time can we do LaTeX please :-)) Some comment with the most controversial stuff: Some write startTime and other start_time (and similar with other things). I've corrected most to "start time", however I think the most important think is consistency, so if someone feels it should be one over the other, go ahead, but please just keep it consistent. Remember this is the CS protocol, not the NSI protocol. Section 4.2: I've changed the title from provision to activation, but more importantly changed some text about what to set start time to if immediate activation is required, so please review that if you have a bone in that. Section 5: In general, very short sections, which makes it seem a bit different. Some of them can probably be joined. 5.4: I have remark about correlationId, I don't think it is needed at coordinator level, only at the MTL. 5.5: I am not sure what the purpose of the list of timeout causes is. I'd merge 5.7 and 5.8 Finally, do we call it "a reservation" or "a connection". We are not consistent with this at all. My take is that is "a connection", as a reservation is only a subset of what it is. There are also quite a few changes and some comments for section 5. Chin, please review. /Henrik

3 2

Issue 91 in ogf-nsi-project: Remove ConnectionState from ErrorEventType and ReserveTimeoutRequestType
by ogf-nsi-project＠googlecode.com 03 Jun '13

03 Jun '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 91 by jmacauley: Remove ConnectionState from ErrorEventType and ReserveTimeoutRequestType http://code.google.com/p/ogf-nsi-project/issues/detail?id=91 Connection states in ErrorEventType and ReserveTimeoutRequestType notifications are not needed. We can remove the ConnectionState from these notifications. -- 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 90 in ogf-nsi-project: Add originatingNSA and originatingConnectionId to ReserveTimeoutRequestType
by ogf-nsi-project＠googlecode.com 03 Jun '13

03 Jun '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 90 by jmacauley: Add originatingNSA and originatingConnectionId to ReserveTimeoutRequestType http://code.google.com/p/ogf-nsi-project/issues/detail?id=90 Reserve timeout notification does not currently model the originating NSA or connectionId which triggered the reservation timeout. We must add 2 new parameters originatingNSA and originatingConnectionId to track the needed information. -- 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 88 in ogf-nsi-project: Move versioned child objects into criteria for query results
by ogf-nsi-project＠googlecode.com 03 Jun '13

03 Jun '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 88 by jmacau...(a)gmail.com: Move versioned child objects into criteria for query results http://code.google.com/p/ogf-nsi-project/issues/detail?id=88 In current NSI CS version 2 the recursive child path object is not versioned with the reservation criteria information, permitting only specification of the current version reservation path. We will need to move the child information into the criteria structure to permit per version specification of path. -- 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 89 in ogf-nsi-project: Add optional connectionId parameter in the ServiceException type.
by ogf-nsi-project＠googlecode.com 03 Jun '13

03 Jun '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 89 by jmacauley: Add optional connectionId parameter in the ServiceException type. http://code.google.com/p/ogf-nsi-project/issues/detail?id=89 Add an optional connectionId parameter in the ServiceException type to avoid using optional variables field for this key attribute of a reservation. -- 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