- Nsi-wg - lists.ogf.org

updated
by John Vollbrecht 26 May '09

26 May '09

Attached is a revised strawman for the NSI architecture document. This is to review at the OGF in Chapel Hill May 27-28 2009. This is still a work in progress, though it has come a long way. Some sections are not done and some are still being worked on. The document as a whole needs editing for consistency. Comments and suggestions are encouraged. I am putting together an acknowledgement section, but have not completed it - I will include this in later drafts. The document has had all corrections accepted from earlier versions, but still has some comments. Suggestions and comments may be added by modifying the text with change tracking on, or by sending comments to the list. John

1 0

[Fwd: EVO Booking : NSI-WG from Fri, 22 May 09 15:30 +0200 (CEST)]
by Artur Barczyk 23 May '09

23 May '09

Hi, this booking is now extended from now until the end of OGF26, so it can be used during the sessions next week, with the same connection parameters given below. Cheers, Artur -------- Original Message -------- Subject: EVO Booking : NSI-WG from Fri, 22 May 09 15:30 +0200 (CEST) Date: Wed, 20 May 2009 17:13:45 +0200 From: <evosupport(a)vrvs.org> To: <Artur.Barczyk(a)cern.ch> Hello Artur Barczyk, You have BOOKED a meeting in EVO (http://evo.caltech.edu) Title: NSI-WG Description: NSI-WG test for OGF26 Community: Universe Meeting Access Information: - Meeting URL http://evo.caltech.edu/evoGate/koala.jnlp?meeting=M9MIMi2e2BD2Dl929BDD99 - Phone Bridge ID: 1011348 Central European Summer Time (+0200) Start 2009-05-22 15:30 End 2009-05-22 16:30 Japan Standard Time (+0900) Start 2009-05-22 22:30 End 2009-05-22 23:30 Eastern Daylight Time (-0400) Start 2009-05-22 09:30 End 2009-05-22 10:30 Pacific Daylight Time (-0700) Start 2009-05-22 06:30 End 2009-05-22 07:30 EVO Phone Bridge Telephone Numbers: --------------- - USA (Caltech, Pasadena, CA) +1 626 395 2112 - Switzerland (CERN, Geneva) +41 22 76 71400 - Slovakia (UPJS, Kosice) +421 55 234 2420 - Italy (INFN, several cities) http://server10.infn.it/video/index.php?page=telephone_numbers Enter '4000' to access the EVO bridge - Germany (DESY, Hamburg) +49 40 8998 1340 - USA (BNL, Upton, NY) +1 631 344 6100 - United Kingdom (University of Manchester) +44 161 306 6802 - Australia (ARCS) +61 0261128742 Canberra 0282124591 Sydney 0362370281 Hobart 0386858362 Melbourne 0731390705 Brisbane 0884631011 Adelaide 0864616718 Perth - Netherlands (Nikhef, Amsterdam) +31 20 7165293 Dial '2' at the prompt --------------- If you would like to add a telephone bridge at your institute, please contact EVO at evocontact(a)vrvs.org -- Dr Artur Barczyk California Institute of Technology c/o CERN, 1211 Geneve 23, Switzerland Tel: +41 22 7675801

1 0

Call Wed and revised strawman
by John Vollbrecht 22 May '09

22 May '09

We will have a call Wed at 9ET - call information Call: +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 I attach an updated version of the strawman. It includes a number of changes - I suggest that if you are looking at it fresh you turn off showing changes -- I actually tried to turn it off without accepting changes but when I tried to send it that way it always turned tracking back on. Maybe there's a way ----- I would like to discuss the strawman on Wed. The section under Job Control is basically what Sebastien sent - I would like to discuss that, and then perhaps the section on reservation that Guy is working on or the naming section. If you have suggestions please let me know. I believe that Guy will not be able to make the call Wed. Guy is setting up meetings at Chapel hill. We can talk about that. We hope to have at least one joint meeting with the NML group and to have a session where we invite other groups in to explain what we are trying to do and how we think other groups will fit. We could try to identify the appropriate groups. Anyone working on mods for the document are encouraged to submit them in a strawman form asap. We should review who will be contributors - notes from minutes a few weeks ago -- P1 Chin G to follow up on authors for monitoring section AP2 John V to follow up with Aaron to see if he can lead topology sharing section. --- (Martin has been designated as lead for this) AP3 John V to follow up with JS/GK confirm lead for path computation section The purpose of this call was to assign authors to the Architecture deliverable. The author assignment is summarized here: 1. Naming and modelling This section considers the naming of network objects and the data modelling of these objects. (changed as below) Lead author: JV Authors: GR, JH Due date: 13 May 2. Topology sharing This section considers how topologies can be exchanged over the NSI interface. Lead author: Martin Swany Author: GR, JH, RK, JA Due date: 13 May 3. Path computation This section considers how path computation relates to the NSI interface – describes where is this function can be performed and the inputs and outputs of the path computation function. Lead author: GK/JS (to be confirmed) Author: RK, JA Due date: 13 May 4. Authentication and trust This section considers how to authenticate a user, ie how to validate users are who they claim to be. Lead author: Mary ? Author: JV Due date: 13 May 5. Authorization and policy This section considers the rights/authorizations that a user has once they have been authenticated. This section will not be covered in Chapel Hill 6. Service Discovery This section considers a service that replies to queries on resource/service availability. Lead author: EE Author: JS, JMa Due date: 6 May 7. Environments (tree/chain) This section considers the management plane/control plane architecture of the NSI, i.e. the way that the data flows over the NSI interface Lead author: RK Author: GR Due date: 6 May 8. Scheduling and job control --- Sebastien Soudan has provided input here This section considers how scheduling is supported by the NSI and associated job control flows. Lead author: TK Author: PP, SS Due date: 13 May 9. Connection Restoration This section considers how connections are restored after failure Lead author: CG Author: Artur Due date: 13 May 10. Monitoring This section considers how connection monitoring can be implemented Lead author: CG Author: AL/JB/JMe (to be confirmed) Due date: 13 May 11. Reservation This section described how a connection can be reserved and the associate parameters. Lead author: GR Author: JA, JV Due date: 13 May -- _____ John Vollbrecht Senior Network Engineer, Internet2 office 734 352 4960 cell 734 395 7890

4 4

[Fwd: EVO Booking : NSI-WG from Fri, 22 May 09 15:30 +0200 (CEST)]
by Artur Barczyk 21 May '09

21 May '09

(For those not attending the call today: we'll have a test meeting using EVO, as a candidate to be used at the NSI sessions at OGF26. If you're interested, please join, otherwise sorry for the "spam".) Please find below the booking details for the test-call on Friday. If you join from a PC, as first time user you'll need to register at http://evo.caltech.edu - that's just so that the system will recognise you in the future, and display your participation in the meeting correctly. Then, you can simply join by clicking on the link given in the reservation below which should place you directly in the meeting, or you can launch EVO from http://evo.caltech.edu and look for the meeting "NSI-WG". It will be available 15 minutes before the start (I believe). I didn't set any password, but if calling in via the bridge, the system will ask you for the meeting id (1011348 as per below). Hope to meet you on Friday. Cheers, Artur -------- Original Message -------- Subject: EVO Booking : NSI-WG from Fri, 22 May 09 15:30 +0200 (CEST) Date: Wed, 20 May 2009 17:13:45 +0200 From: <evosupport(a)vrvs.org> To: <Artur.Barczyk(a)cern.ch> Hello Artur Barczyk, You have BOOKED a meeting in EVO (http://evo.caltech.edu) Title: NSI-WG Description: NSI-WG test for OGF26 Community: Universe Meeting Access Information: - Meeting URL http://evo.caltech.edu/evoGate/koala.jnlp?meeting=M9MIMi2e2BD2Dl929BDD99 - Phone Bridge ID: 1011348 Central European Summer Time (+0200) Start 2009-05-22 15:30 End 2009-05-22 16:30 Japan Standard Time (+0900) Start 2009-05-22 22:30 End 2009-05-22 23:30 Eastern Daylight Time (-0400) Start 2009-05-22 09:30 End 2009-05-22 10:30 Pacific Daylight Time (-0700) Start 2009-05-22 06:30 End 2009-05-22 07:30 EVO Phone Bridge Telephone Numbers: --------------- - USA (Caltech, Pasadena, CA) +1 626 395 2112 - Switzerland (CERN, Geneva) +41 22 76 71400 - Slovakia (UPJS, Kosice) +421 55 234 2420 - Italy (INFN, several cities) http://server10.infn.it/video/index.php?page=telephone_numbers Enter '4000' to access the EVO bridge - Germany (DESY, Hamburg) +49 40 8998 1340 - USA (BNL, Upton, NY) +1 631 344 6100 - United Kingdom (University of Manchester) +44 161 306 6802 - Australia (ARCS) +61 0261128742 Canberra 0282124591 Sydney 0362370281 Hobart 0386858362 Melbourne 0731390705 Brisbane 0884631011 Adelaide 0864616718 Perth - Netherlands (Nikhef, Amsterdam) +31 20 7165293 Dial '2' at the prompt --------------- If you would like to add a telephone bridge at your institute, please contact EVO at evocontact(a)vrvs.org

1 0

tree vs chain
by Tomohiro Kudoh 20 May '09

20 May '09

please see attached.

1 0

call reminder/ Wed 5/20
by John Vollbrecht 20 May '09

20 May '09

We will have a call tomorrow at 9ET for all who can make it. I will send out some slides by end of day, and Tomohiro is also planning on sending a revised doc he has worked on with Sebastien before the meeting. Others may also have input by then. We will also talk about plans for OGF sessions next week. Call: +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 John

1 1

dynamic GOLE pilot discussion list
by John Vollbrecht 15 May '09

15 May '09

At the march GLIF meeting in Catania the concept of a dynamic GOLE was discussed and Lars Fischer suggested that we start a dynamic GOLE project within GLIF. At the ad hoc GLIF meeting on April 27 in Washington there was a consensus to form a group to define what the pilot GOLE would be and present it at the GLIF meeting in the fall. GLIF has set up a mail group pilotdynamicgole(a)glif.is to discuss this and prepare a presentation for GLIF. Any interested in participating in this may join pilotdynamicgole(a)glif.is by sending email to info(a)glif.is and requesting to be subscribed (or unsubscribed). I will send out some initial ideas about what such a pilot could be and suggest some times to have a call to discuss these in a followup email. GOLE operators, including those at MANLAN, NetherLight and StarLight have indicated interest in helping to define this project, and once it is defined to evaluate whether to implement. In addition to defining the hardware and software required to support a pilot dynamic GOLE I expect there will be discussion about who will connect to the pilot(s) and what applications will run on them. These could have interesting technical and political characteristics. Please subscribe to pilotdynamicgole(a)glif.is if you want to get further emails about this. Also please let me know if you have questions. Anyone interested in participating is welcome to join the mail group. John John Vollbrecht Senior Network Engineer, Internet2 office 734 352 4960 cell 734 395 7890

1 0

Re: [Nsi-wg] NSI naming
by John Vollbrecht 14 May '09

14 May '09

On May 12, 2009, at 9:24 AM, Martin Swany wrote: > Hi Jeroen, > > I'm (re-?) adding Jason to the cc list as he's right in the middle of > this discussion as well. > > I would add that I think that we are all very close on the way in > which things are related, which gives rise to layers/levels of > the network. I think that the "Relation" element that we're using > in UNIS (perfSONAR/DCN) land really makes the expressions > there start to look like the RDF 3-tuples in a way. While that > problem > is hard, I think that we've been inching closer to having a common > solution framework. > I think the relation might work for this if it is defined -- but still it is complicated and important to agree on. See comment below. > best, > martin > > On May 12, 2009, at 4:13 AM, Jeroen van der Ham wrote: > >> Hi, >> >> I think Martin's analysis of your description is correct. >> I only want to add that you seem to be contradicting yourself >> regarding layering, and I think it is very important that we clear >> that up. >> >> Before I begin, I want to clear something up: >> Networks transport data by encapsulating it in different layers. I >> think we can all agree on that analysis, and we all know what >> layers are in general. Therefore I don't want to complicate this >> (already complex) discussion by introducing yet another term (i.e. >> "level"). >> >> Then on to your analysis: in the beginning you say that NSI wants >> to describe links at a certain layer going over links at a lower >> layer. Then later on you say that NSI operates at a single layer >> for a particular request. >> >> Current networks operate at multiple layers (Ethernet, SONET, >> Lambda, etc.). Therefore, if the NSI wants to be able to provision >> services across these networks, then it will have to handle >> multiple layers. >> >> Please realise that the NML is currently describing a layer-less >> model. Layers are not part of the model and we are only describing >> the general things that are part of every layer. So NML is >> currently not able to describe that links at one layer run over a >> link at a lower layer. >> >> As Martin said, describing layers, and the adaptations between them >> is a very very hard problem. One that the NML group will be taking >> on soon though. I agree this is hard. I think levels and layers are different. Layers apply to protocol layers. I may misuse the term. Levels for me apply to what can be switched for a given topology. I.e. A given topology allows VLANS to be created ete, by concatenating VLANS at each edge point. The VLANS to be switched are carried on something else - SONET trunks, GOLEs, Ethernet trunks, etc. Level in this case refers to VLANs on one level and what carries them on the other. >> >> >> >> Jeroen. > John Vollbrecht Senior Network Engineer, Internet2 office 734 352 4960 cell 734 395 7890

2 2

2-phase commit
by Tomohiro Kudoh 13 May '09

13 May '09

Hi all, Here is an explanation of 2-phase commit. Tomohiro

1 0

call tomorrow -May 8
by John Vollbrecht 13 May '09

13 May '09

We will have a call tomorrow morning Wed 5/8 at 9AM ET. Call information is Call: +1-734-615-7474 (PSTN CALL-OUT DOES NOT WORK) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 possible agenda - NSI meeting last week continue discussion of architecture strawman doc update on contributions John Vollbrecht Senior Network Engineer, Internet2 office 734 352 4960 cell 734 395 7890

5 6