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

minutes from today's NSI meeting
by Guy Roberts 12 Jan '12

12 Jan '12

... are available here: https://forge.ogf.org/sf/go/doc16372?nav=1 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 _____________________________________________________________________

1 0

NSI Topology discussion
by Guy Roberts 12 Jan '12

12 Jan '12

Please take a look at this document for today's NSI call: https://docs.google.com/document/d/1xXxRmH9LUuZoq-Ce-1clvLPDBUI9iiJEkmmw2be… 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 _____________________________________________________________________

1 0

tomorrow's NSI call
by Guy Roberts 11 Jan '12

11 Jan '12

Hi all, 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: * STPs and topology descriptions * Error codes * Other issues 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

Multi-layer pathfinding
by Jerry Sobieski 05 Jan '12

05 Jan '12

As I offered before the holidays, here is my take on how we might address multi-layer pathfinding in NSI. I suggest we take this topic next week... Jerry

2 1

STP
by Tomohiro Kudoh 05 Jan '12

05 Jan '12

Hi All, Here is my slide about STP representation and topology description. Tomohiro

4 4

minutes from today's NSI call
by Guy Roberts 05 Jan '12

05 Jan '12

... are available here: https://forge.ogf.org/sf/go/doc16370?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

Wednesday's NSI call
by Guy Roberts 04 Jan '12

04 Jan '12

Hi all, 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: * Usecase: pathfinding with explicit topologies: Jeroen v d Ham * Proposal for STPs and topology descriptions: Tomohiro Kudoh * Error codes * Other issues 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 _____________________________________________________________________

1 0

ServiceException needs further details
by John MacAuley 04 Jan '12

04 Jan '12

Resend.... I have added some new errors I implemented as part of CS11. Please comment and add to the list. Guy would like to add an appendix in the CS protocol document. John. Peoples, I took and action to start the error handling discussion so that we, as a group, can document the error messages and behaviors. I would like to start it off with when an NSIServiceException is returned as a SOAP fault to a request, and when it is returned in a specific failed response message. OpenDRAC used the strategy of validating a “key” set of attributes in the request before returning an ACK response or SOAP fault. This gives OpenDRAC the opportunity to validate parameters needed to accept the message for processing, and possibly return the asynchronous failed message at a later time. Here is the list of parameters I will validate in a reservation message and return a SOAP fault if they are incorrect or missing. HTTP authentication – if you don’t have valid credentials you are rejected with an HTTP 40x message. correlationId - needed for any acknowledgment, confirmation, or failed message. Must be unique within the context of the providerNSA otherwise the request cannot be accepted. replyTo - we will send the confirmation, or failed message back to this location. We do not validate the contents of the endpoint, just that it exists. Reservation – if the reservation parameters are not present then we reject. requesterNSA and providerNSA – must be present and resolve to an NsNetwork in topology. Also, the providerNSA must be the NsNetwork OpenDRAC is managing or we reject the message. connectionId – this is used as the primary reference attribute for reservation state machines and must be present. If any of these fields are missing or invalid OpenDRAC will return a SOAP fault containing the NSIServiceException set to an appropriate error message. I typically fill in MISSING_PARAMETER - "SVC0001", "Invalid or missing parameter" for this generic case and specify attributes identifying the parameter in question. Here is a list of error messages currently implemented in OpenDRAC. The list continues to expand. I have kept the text generic with the specific error values being returned in the associated attribute list. We will also need to agree on the format of the message/errorId. MISSING_PARAMETER, "SVC0001", "Invalid or missing parameter" UNSUPPORTED_OPTION, "SVC0002", "Parameter provided contains an unsupported value which MUST be processed" ALREADY_EXISTS, "SVC0003", "Schedule already exists for connectionId" DOES_NOT_EXIST, "SVC0004", "Schedule does not exists for connectionId" MISSING_SECURITY, "SVC0005", "Invalid or missing user credentials" TOPOLOGY_RESOLUTION_STP, "SVC0006", "Could not resolve STP in Topology database" TOPOLOGY_RESOLUTION_STP_NSA, "SVC0007", "Could not resolve STP to managing NSA" PATH_COMPUTATION_NO_PATH, "SVC0008", "Path computation failed to resolve route for reservation" INVALID_STATE, "SVC0009", "Connection state machine is in invalid state for received message" INTERNAL_ERROR, "SVC0010", "An internal error has caused a message processing failure" INTERNAL_NRM_ERROR, "SVC0011", "An internal NRM error has caused a message processing failure" STP_ALREADY_IN_USE, "SVC0012", "Specified STP already in use" BANDWIDTH_NOT_AVAILABLE, "SVC0013", "Insufficent bandwidth available for reservation" Would people like to add to the list? Comments? John.

3 3

Endpoint update for northernlight
by Henrik Thostrup Jensen 02 Jan '12

02 Jan '12

Hi everyone (especially to the topology maintainer) Northernlight is now running TLS, and only TLS. Meaning no regular http requests will be accepted. Right now it should not perform any certificate verification, but that will come later. The endpoint for the northernlight is now running on port 9443, meaning that this is the URL for the nsa endpoint: http://orval.grid.aau.dk:9443/NSI/services/ConnectionService I realize this will break things. Both the TLS only, and the endpoint change (though that is just an topology update), but I think this is an important thing to push for. Of course Northernlight is an edge-node with no transits in the current topology to impact is minimal, but I hope to upgrade Starlight (which has a rather central place in the topology) sometime in January, so if you haven't started on TLS support, now is the chance :-). Have a nice christmas/holiday/work during the latter half of December. Best regards, Henrik Henrik Thostrup Jensen <htj at ndgf.org> NORDUnet / Nordic Data Grid Facility.

1 1