October 2010 - Nsi-wg - lists.ogf.org

NSI meetings at OGF30
by Guy Roberts 12 Oct '10

12 Oct '10

The schedule for OGF30 is now available. NSI-WG has 3 sessions on Wednesday between 11.00am and 5.00pm. http://www.ogf.org/gf/event_schedule/index.php?event_id=17 Guy

1 0

Dinner meeting at GLIF?
by Jerry Sobieski 12 Oct '10

12 Oct '10

Hi all- What was the final resolution for an NSI gathering at GLIF? When and where..? Thnaks! Jerry

2 1

Connection Service Architecture
by Takahiro Miyamoto 07 Oct '10

07 Oct '10

Hi all, My comments are in the attached file. Best regards, Takahiro -- Takahiro MIYAMOTO <tk-miyamoto(a)kddilabs.jp> Integrated Core Network Control And Management Laboratory KDDI R&D Laboratories, Inc. TEL: +81-49-278-7455 / FAX: +81-49-278-7811

1 0

path description in NSI messages
by John Vollbrecht 07 Oct '10

07 Oct '10

attached is a description of how paths might be described in NSI. I think it could be useful in discussing options. John

2 1

Fwd: WiFi @CERN
by Harold Teunissen 07 Oct '10

07 Oct '10

Folks, It seems that you need to preregister your WiFi device before getting access at the CERN network next week. Use this link https://network.cern.ch/sc/fcgi/sc.fcgi?Action=VisitorRegistration to perform the registration. You also need the name of your LHCOPN conact person. Cheers, Harold Sent from my iPad

1 0

connection timing issues
by John Vollbrecht 07 Oct '10

07 Oct '10

Attached is a revised description of connection timing issues. This is revised from the set of issues I sent out yesterday, which includes changes from our discussion today. I include changes suggested by Tomohiro, Radek, Jerry and Inder. I hope this can help move discussion forward. The issue of whether there needs to be a notify when a connection is established seems to me to be orthogonal to the other issues, but may not be. If there is reason for it to be included in the timing issues described in the first sections of this paper. If so, I am hoping someone can make that case explicitly. John

1 0

time issue
by John Vollbrecht 06 Oct '10

06 Oct '10

Hello all - Jerry and I had a discussion last week about the time issue. I think we developed a useful approach. The idea is to define two times, which I think we all agree exist. 1) available time - time a connection is available to the application to communicate between devices 2) resource time - time a resource is reserved to support available time To further define these - Available time - requested by the user for its application - provided by the network. resource time - time a resource is allocated to a connection - includes setup and teardown time, if any - is time in reservation calendar for resource Available time requested cannot be provided exactly by network because it cannot predict exactly length of setup and take down. I believe we all agree with this. Therefore provided available time can at best approximate requested available time. We agreed that when a user requests automatic start connection it would request available time and the provider would schedule resource time to get as close as possible. When a request is for user initiated connection the time would be for reserved time, and the user initiation can start anytime after the reserved time. Available time depends on setup and take down times of equipment. ----------------- I think we agreed on the above definitions. The definition of time seem useful in discussing what goes in connection service messages. We also talked about some possible implications of this. The difference between available and resource time is setup and takedown time. While it is impossible to be sure exactly how long they will be, it may be possible to define something statistical. For example setup takes an average of 17 sec with std deviation of N. If this is can be defined for the resource, then one can make a prediction about when a connection will be available with a degree of confidence. For example this would allow one to request an automatic connection, for example, at 5pm and have it available 99% of the time. If the average setup time is 17 seconds and I add 10 seconds to be 99% sure, then the service would initiate the connection at 5:00:00 - 0:00:25, or 4:59:35. We talked about including this "setup requirement" in the connection service definition of and NSA, and by implication including this in requests and replies. I think this is worth talking about in the group. John

11 48

minutes from today's NSI call
by Guy Roberts 06 Oct '10

06 Oct '10

... are available here: http://forge.gridforum.org/sf/go/doc16070?nav=1 Guy

1 0

timing diagram
by Guy Roberts 06 Oct '10

06 Oct '10

... attached diagram for connection service automatic timing

1 0

tomorrow's NSI conf call
by Guy Roberts 06 Oct '10

06 Oct '10

Hi all, The following is dial-in information for Wednesday's NSI call: Time: 7:30 PDT 10:30 EDT, 15:30 BST, 16:30 CEST, 23:30 JST Call: +1-734-615-7474 (Please use if you do not pay for Long Distance) or +1-866-411-0013 (toll free US/Canada Only) Enter access code: 0155180 Agenda: 1. NSI Framework document has completed 30 day public comment period, comments need to be incorporated and document released. https://forge.gridforum.org/sf/go/artf6449?nav=1 2. Review the ongoing discussion on the timing of the connection service: http://forge.gridforum.org/sf/go/doc16067?nav=1 Guy

3 3