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

Reservation request message
by John MacAuley 06 Apr '11

06 Apr '11

Peoples, I have attached an XML file that contains an example reservation request message. Ignore the namespace information and the schemaLocation statement as these would not be included within the SOAP message. John.

4 11

comments to WSDL files
by Radek Krzywania 06 Apr '11

06 Apr '11

Hi, Michal has get through the WSDL file, the comments are below: - WSDL seems to be fine, and not very difficult to adopt in various software (i.e. AutoBAHN) - In ServiceTerminationPointType, it would be useful to have information whether port is tagged or not (VLANs information is not stored also). I know that we would like to keep the messages as technology agnostic as possible, but we need to have a balance between functionality and simplicity/universality here. In case of AutoBAHN we can probably do some workarounds to evade the issue, however this is not plug-and-play ;) Best regards Radek ________________________________________________________________________ Radoslaw Krzywania Network Research and Development Poznan Supercomputing and radek.krzywania(a)man.poznan.pl Networking Center +48 61 850 25 26 http://www.man.poznan.pl ________________________________________________________________________

5 8

Security attributes
by Jerry Sobieski 06 Apr '11

06 Apr '11

I propose the following high level approach for V1: We have defined two levels of AA: "Session layer" between NSAs, and "Request layer" at the primitive/connection context. I pose we define a "security attributes" element that consists of: a) Security Type := Identifies the security mechanism this element provides. b) Secutity Credentials := Contains a string of security information to be interpreted by the mechanism specified in the Type field. When initializing the NSA to NSA session, this element will authenticate each NSA to the other, and then each NSA will decide whether the other [remote] NSA is authorized to communicate with the local NSA. For any service request, the request must be authorized. The Service Definition will specify the set of recognized and allowable AA mechanisms for each network. The user request must specify one allowable mechanism in the service request. Initially, the NSI CS spec will require NSAs to recognize and support two levels of security: a) "simple security" consisting of a string passed to the authorizing agent for lookup in a flat text file, b) "better security" a more sophisticated AA scheme such as X509 or the like (details TBD by someone who understands these issues in greater detail.) I will code this into the XSD for the Service Defs. Any comments or additional necessary detail, please let me know. Jerry

3 3

clearer naming for service definitions
by Guy Roberts 06 Apr '11

06 Apr '11

Jerry, As discussed in today's NSI call a clearer naming scheme would be helpful for service definitions, the following is proposed (with thanks to Inder and Tomohiro): Service Capabilities Definition (SDC) - This is often referred to as the 'service definition', so from Jerry's document: 'The Service Definition (SD) is a machine readable textual document that identifies each attribute of the service and the range of values that attribute will allow'. ... and I think defines a default value? Service Request Description (SRC) - this is a request for a specific instance of a service. It is created by the Requester Agent when it assigns desired values to each of the attributes described in the SDC. The SRC is sent from the RA to the PA in a Connection Request. Service Instance Description (SID) - this is a description of an actual service instance, the attribute values reflect the values chosen and confirmed by the Provider Agent. Would these terms help clarify your service definition document? Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

4 4

Minutes from today's call
by Guy Roberts 30 Mar '11

30 Mar '11

... can be found here: http://forge.gridforum.org/sf/go/doc16245?nav=1 _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0

Service Definition
by Jerry Sobieski 30 Mar '11

30 Mar '11

My offered text for the V1 spec J

1 0

tomorrow's NSI conf call (note new times)
by Guy Roberts 30 Mar '11

30 Mar '11

Hi all, The following is dial-in information for tomorrow's NSI call, please note the change to summer time in Europe: 7:00 PDT 10:00 EDT, 15:00 GMT, 16:00 CET, 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: NSI connection service definition. NSI WSDL/XSD review Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

2 1

WSDL/XSD example documents
by John MacAuley 24 Mar '11

24 Mar '11

Here are two example specifications that I think would be a good template to start with. 29199-01-800.doc is the 3GPP ParlayX common type specification that came with supporting XSD (I did not include), while 29199-02-800.doc is the 3GPP ParlayX specification for ThirdPartyCall which also came with XSD and WSDL (I did not include). John.

1 0

tomorrow's NSI call
by Guy Roberts 23 Mar '11

23 Mar '11

Hi all, The following is dial-in information for tomorrow's NSI call, time: 7:00 PDT 10:00 EDT, 14:00 GMT, 15:00 CET, 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: NSI connection service document. Guy _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

2 1

minutes from last Wednesday's NSI call
by Guy Roberts 21 Mar '11

21 Mar '11

..... are available here: http://forge.gridforum.org/sf/go/doc16236?nav=1 _____________________________________________________________________ ** Guy Roberts, PhD Network Engineering & Planning * * Tel: +44 (0)1223 371300 * * City House Direct: +44 (0)1223 371316 * 126-130 Hills Road Fax: +44 (0)1223 371371 * Cambridge * CB2 1PQ E-mail: guy.roberts(a)dante.net<mailto:guy.roberts@dante.org.uk> D A N T E United Kingdom WWW: http://www.dante.net _____________________________________________________________________

1 0