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

Issue 69 in ogf-nsi-project: Remove the STP orientation element.
by ogf-nsi-project＠googlecode.com 07 Mar '13

07 Mar '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 69 by jmacau...(a)gmail.com: Remove the STP orientation element. http://code.google.com/p/ogf-nsi-project/issues/detail?id=69 Description of Issue: Questions were raised with respect to the usefulness of the STP orientation element. Discussion of Issue: GR presented on Orientation attribute: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6532 Discussion on whether Orientation attribute is needed… HTJ and GR thought not, JS thought that it was needed and will present a discussion paper. Resolution of Issue: Remove orientation attribute. -- 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 2

Issue 72 in ogf-nsi-project: Remove NetworkIdType definition
by ogf-nsi-project＠googlecode.com 07 Mar '13

07 Mar '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 72 by jmacau...(a)gmail.com: Remove NetworkIdType definition http://code.google.com/p/ogf-nsi-project/issues/detail?id=72 Description of Issue: Original NSI CS 1.0 WSDL definition had all base identifiers such as NetworkId defined as base types (NetworkIdType) to centralize the XML type definition in a single location. This made it easer to change during all the churn in naming discussions. However, there is no only a single place NetworkId is used and a request has been made to remove the separate NetworkIdType definition. Resolution of Issue: Minutes NSI-WG conf call 23 Jan 2013 - Remove superfluous NetworkIdType since there is now only one use of the type definition and include xsd:string directly in element. -- 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 2

Issue 74 in ogf-nsi-project: Make ServiceExceptionType variables optional in ogf_nsi_framework_types_v2_0.xsd
by ogf-nsi-project＠googlecode.com 07 Mar '13

07 Mar '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 74 by jmacau...(a)gmail.com: Make ServiceExceptionType variables optional in ogf_nsi_framework_types_v2_0.xsd http://code.google.com/p/ogf-nsi-project/issues/detail?id=74 Description of Issue: ServiceExceptionType includes a non-optional variables element which itself can contain zero or more variable instances. When no variables require specification the variables element is still required in current ogf_nsi_framework_types_v2_0.xsd definition. Resolution of Issue: Minutes NSI-WG conf call 23 Jan 2013 - Add a minOccurs="0" constraint on variables element in ogf_nsi_framework_types_v2_0.xsd definition. -- 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 2

Notification messages
by Tomohiro Kudoh 06 Mar '13

06 Mar '13

All, Attached is a slide deck including description of data plane related notifications. Tomohiro

1 0

google doc NSI v2.0 features
by Guy Roberts 06 Mar '13

06 Mar '13

https://docs.google.com/document/d/1_X0pqbc-DqbzDI_C259rz9npk7EuEmZFoq3CU98… _____________________________________________________________________ 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 75 in ogf-nsi-project: Clean up documentation in WSDL and XSD files.
by ogf-nsi-project＠googlecode.com 06 Mar '13

06 Mar '13

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 75 by jmacau...(a)gmail.com: Clean up documentation in WSDL and XSD files. http://code.google.com/p/ogf-nsi-project/issues/detail?id=75 Description of Issue: Documentation in the current WSDL and XSD files for NSI CS 2.0 is inconsistent with the schema content. Resolution of Issue: Make documentation consistent with schema content. -- 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 0

Fwd: [wg-all] New documents in public comment: Usage Record 2.0 and NML Base Schema
by Jeroen van der Ham 05 Mar '13

05 Mar '13

Please take note to this message :) Begin forwarded message: > From: Greg Newby <gbnewby(a)alaska.edu> > Date: 5 maart 2013 21:35:56 CET > To: All WG <wg-all(a)ogf.org> > Subject: [wg-all] New documents in public comment: Usage Record 2.0 and NML Base Schema > > Dear OGF members and affiliates: > > Two new documents have begun public comment. Please consider reading > and providing feedback. Brief affirmations are very useful to > demonstrate community input and support. More detailed analysis is > also, of course, welcome. > > All documents in public comment are accessible here: > > http://redmine.ogf.org/projects/editor-pubcom/boards > > Note that this is an updated location, using the new Redmine > tracker system. Anyone may register for a Redmine username. > > These documents hav been newly added for public comment: > > * Usage Record 2.0, recommendations track document, via Usage > Record WG > > * NML Base Schema version 1, recommendations track document, via > Network Markup Language WG > > -- Greg Newby, OGF Standards Editor > > Dr. Gregory Newby, Director of the Arctic Region Supercomputing Center > Univ of Alaska Fairbanks-909 Koyukuk Dr-PO Box 756020-Fairbanks-AK 99775-6020 > e: gbnewby(a)alaska.edu v: 907-450-8663 f: 907-450-8603 w: people.arsc.edu/~newby > > -- > The wg-all mailing list is an umbrella list for all > OGF mailing lists. If you are subscribed to any OGF > mailing list, you will receive mails to wg-all. > > wg-all mailing list > wg-all(a)ogf.org > https://www.ogf.org/mailman/listinfo/wg-all

1 0

Re: [Nsi-wg] Issue 41 in ogf-nsi-project: Do we replace the replyTo field with a topology/NSA configuration lookup?
by ogf-nsi-project＠googlecode.com 05 Mar '13

05 Mar '13

Comment #3 on issue 41 by takahiro...(a)gmail.com: Do we replace the replyTo field with a topology/NSA configuration lookup? http://code.google.com/p/ogf-nsi-project/issues/detail?id=41 I want to use the replyTo field. Currently, all NSA act as requester and provider. In this case, we are able to look up the csProviderEndpoint of requesters easily. However, in near future, some NSA act as only a requester, e.g. PerfSONAR and AutoEarth. It is difficult to describe and manage all requester endpoints as same as provider ones. Moreover, it causes a high barrier to publish new requesters. Therefore, a requester endpoint should be obtained using the replyTo field in the SOAP message payload.

1 7

tomorrow's NSI conf call
by Guy Roberts 05 Mar '13

05 Mar '13

The following is dial-in information for Wednesday's NSI call, Time: 7:00 PDT 10:00 EDT, 15:00 GMT, 16:00 CET, 24: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: - Preparation for OGF37 o assignments of docs o first go at NSI v2.0 feature list _____________________________________________________________________ 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

Overly complex discovery WSDL
by Henrik Thostrup Jensen 04 Mar '13

04 Mar '13

Hi I've been looking at the discovery WSDL, and was a bit amazed with how complicated it turned up being. Now I have not been very active in NSI for the last couple of months, and have missed a couple of meeting, but I think we've ended up with something a lot more complex than what we discussed in Oxford and the mailing lists. For the request it looks like this: queryNsaRequest :: QueryNsaRequestType queryNsaRequest :: RequestType filter :: FilterType * nsaId :: NsaIdType * serviceType :: xsd:string * This is my own notation. Sorry if it is tricky to read. For the request it possibly to define summary of detailed request, but I haven't found any documentation on what should be returned for what. Secondly it is possible to have multiple filters, each specifying multiple nsaIds and serviceTypes. The parameters for each filter should be ORed, however there does not appear to be any documentation for how to deal with multiple filters. It also appears to be complete and utterly overkill as most NSAs will host 2 or 3 services. Now, for the response: queryNsaResponse :: QueryNsaResponseType discovery :: NsaDiscoveryType * # nsaId # softwareVersion # startTime # currentTime services :: ServicesType * service :: ServiceType #other :: any description :: xsd:string versions :: VersionsType * version :: VersionType # name # version # endpoint # wsdl # url # other :: any other :: any * capabilities :: CapabilitiesType * capability ft:TypeValuePairType # type :: xsd:string ! # targetNamespace :: xsd:anyURI value :: xsd:string * other :: any * Here we are dealing with a datastructure potentially 9 levels deep. Arguably, some of this is due to the ackward way XML/WSDL handles lists, but there are still 4 levels of nested lists. I won't go into any details here. I am not trying to do a witch-hunt on John here. In fact he may just have been listening to everyone, but what we ended up with here is pretty bad, and is in my opion very far from what we discussed in Oxford. I think we need to setup some review of WSDLs as well in order to ensure that these things do not spin out of control like this. Anyways, something to talk about tomorrow :-). Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

2 3