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

Re: [Nsi-wg] SOAP Version
by John MacAuley 29 Jan '13

29 Jan '13

Sorry, I can't seem to control my e-mail client these days and it randomly picks an address to send from :-) On 2013-01-29, at 6:12 PM, John MacAuley <idiot(a)i.cant.work.my.email.client.properly.com> wrote: > Peoples, > > I had an action item to define which version of SOAP we are using in the standard. At the moment I believe all implementations are utilizing SOAP 1.1 by default. I say this because I have captured a few SOAP messages in the past and they all contain the following SOAP URL: > > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > > By definition the following name spaces apply to the specific SOAP versions: > SOAP 1.1 : http://schemas.xmlsoap.org/soap/envelope/ > SOAP 1.2 : http://www.w3.org/2003/05/soap-envelope > > I have used WSDL 1.1 to specify the protocol which typically lines up with SOAP 1.1. I believe most people's implementation will default to SOAP 1.1 unless specifically told to use SOAP 1.2. I therefore recommend we specifically declare that NSI CSv2 used the SOAP 1.1 binding. > > John > > References > W3C - From SOAP/1.1 to SOAP Version 1.2 in 9 points. http://www.w3.org/2003/06/soap11-soap12.html > > >

1 0

SOAP Version
by MacAuley, John (John) 29 Jan '13

29 Jan '13

Peoples, I had an action item to define which version of SOAP we are using in the standard. At the moment I believe all implementations are utilizing SOAP 1.1 by default. I say this because I have captured a few SOAP messages in the past and they all contain the following SOAP URL: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> By definition the following name spaces apply to the specific SOAP versions: SOAP 1.1 : http://schemas.xmlsoap.org/soap/envelope/ SOAP 1.2 : http://www.w3.org/2003/05/soap-envelope I have used WSDL 1.1 to specify the protocol which typically lines up with SOAP 1.1. I believe most people's implementation will default to SOAP 1.1 unless specifically told to use SOAP 1.2. I therefore recommend we specifically declare that NSI CSv2 used the SOAP 1.1 binding. John References W3C - From SOAP/1.1 to SOAP Version 1.2 in 9 points. http://www.w3.org/2003/06/soap11-soap12.html

1 0

Query renaming
by John MacAuley 28 Jan '13

28 Jan '13

Peoples, THe agreement out of our last meeting was to introduce the querySynch() command to support a synchronous (blocking) summary query command. This operation would not support the detailed query behaviours. To maintain consistency in operation naming, I would like to break the current asynchronous query operation into two separate commands: query() that would provide the asynchronous summary query for the schedule, and queryDetails() that would provide the recursive tree view of the schedule. query() would have the same parameters and confirmation result type as querySynch(). If people support this change, then I will go ahead and make it at the same time I add the querySynch() operation. I am open for naming changes as well. If someone thinks querySummary() and querySummarySynch() are better operation names. Thank you, John

3 3

Topology Syntax document
by Jeroen van der Ham 25 Jan '13

25 Jan '13

Hi all, I've prepared a document defining the NSI topology syntax extensions on NML. This basically codifies the syntax that we have been using in the Automated GOLE demo since SC. Feedback (and approval) is more than welcome! Jeroen.

1 0

orientation
by Guy Roberts 25 Jan '13

25 Jan '13

Henrik, Looking up my documentation on orientation I see that I came up with this definition: Orientation · Orientation attribute is used to assign a direction to a bidirectional STP to remove ambiguity when performing path computation. Orientation type is ingress or egress. Ingress/Egress is relative to the Network. See the attached document for discussion, but I think that we can drop the orientation attribute as there are other ways of solving the problem. 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. _____________________________________________________________________

2 1

minutes from today's NSI conf call
by Guy Roberts 23 Jan '13

23 Jan '13

Hello All, Please find minutes from today's NSI conf call here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6529 Please take a look as a few decisions have been made and some action points assigned. Thanks, 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

Fwd: Synchronous query operation
by John MacAuley 23 Jan '13

23 Jan '13

All, I am sending this out just in case it makes the agenda. You will have seen some of the slides before, but I think they are needed to frame the decision point. John Begin forwarded message: > From: John MacAuley <john.macauley(a)surfnet.nl> > Subject: Synchronous query operation > Date: 23 January, 2013 12:42:44 AM EST > To: Guy Roberts <Guy.Roberts(a)dante.net> > > If we have time tomorrow I would like to discussed the attached slides. > > John >

1 0

Fwd: Synchronous query operation
by John MacAuley 23 Jan '13

23 Jan '13

All, I am sending this out just in case it makes the agenda. You will have seen some of the slides before, but I think they are needed to frame the decision point. John Begin forwarded message: > From: John MacAuley <john.macauley(a)surfnet.nl> > Subject: Synchronous query operation > Date: 23 January, 2013 12:42:44 AM EST > To: Guy Roberts <Guy.Roberts(a)dante.net> > > If we have time tomorrow I would like to discussed the attached slides. > > John >

1 0

Issues for next NSI call
by Henrik Thostrup Jensen 22 Jan '13

22 Jan '13

Hi. As promised, here a number of issues, which I think we need to decide on. Please read them and understand the subject, so we don't have to spend most of the call explaining the issue itself. Please write if you would like to explain something before the meeting. * NML format decision We need to decide on a format for topology exchange (note that the model for all these are NML, is is just about the specific format). Options are: XML, OWL, N3 (unless we want to invent something). OWL and N3 are RDF based, where as the XML is a direct NML representation in XML. See the NML spec for XML and OWL examples. OWL and N3 examples can be seen in the autogole-topology repository at: https://github.com/jeroenh/AutoGOLE-Topologies/tree/nsiv2/goles All of the formats need to be augmented slightly for describing NSAs, but that is more or less trivial in all of them (and roughly the same procedure). Personally I like the XML representation is it the one most close to the actual mode, and seems easy to generate and parse. * Do we allow one NSA (by URL) to act for multiple networks This isn't clear and does affect some things in the protocol design. Personally I think this is way more trouble than it is worth, and it is easy to create different URLs for each NSA even if they are hosted within the same daemon. * Do we allow multiple NSAs for a single network Could potentially be used for redundancy. In case we allow them, should the NSAs have different identity or the same? * WSDL clean up Remove superflourous NetworkIdType and saml import ogf_nsi_connection_types_v2_0.xsd I don't expect any objections here. * Decide on SOAP 1.1 or SOAP 1.2 for NSI2 This affects requests (slightly), processing and SOAP Faults. It appears that most are on SOAP 1.1 (at least from the faults I have seen). * ServiceExceptionType variables ServiceExceptionType has the following variables decleration: <xsd:element name="variables" type="tns:VariablesType" /> Could we get minOccurs="0" on this, as not all exceptions are necessarely related to a variable. * Orientation In the WSDL we allow STPs to be specified without an orientation. What is the semantics for an STP without orientation? * Connection Identifier We currently have no good way of making an identifier for a connection (it is scoped within the requester identity). This means that there is no way for one entity to pass a connection reference to another. The easiest way to get this it allow NSAs to scope connection ids independently of requester identity, which means that a connection id at an NSA is always the same. This should allow us to create a URN for it at least. The real solution is to have a URL, but since we don't use a protocol where URLs are first-grade citizens that would require a major re-design. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

2 1

NSI sessions at OGF37
by Guy Roberts 22 Jan '13

22 Jan '13

Hello All, I have requested 4 NSI sessions for OGF37 in Charlottesville VA (I may increase this if necessary). For details of the location and for registration, please see the website: https://www.ogf.org/OGF37/ The aim of the NSI meeting will be to finalise the v2.0 functionality in particular the state machine, message handling and WSDL and associated usage. Please let me know if you would like to present at this meeting. 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