- Nsi-wg - lists.ogf.org

NSI voting
by Guy Roberts 02 Feb '15

02 Feb '15

Hello All, The NSI co-chairs have now agreed the NSI working group voting process, this is described here: https://redmine.ogf.org/dmsf_files/13392 We have kept the voting process as simple as possible and it will only be used as a last resort if a rough consensus cannot be reached. Please let me know if you have any questions about the process. As discussed on the last NSI conf call, we need a decision on the NSI Topo/Doc Distribution method, so we will go to a vote on this. The schedule for the vote is as follows: - The authors of the Topo/Doc distribution proposals should review the 'NSI fundamental principles' document and check that their proposal conforms with these principles. - Any conflict or variation from the fundamental principles should be explained so that the implications can be understood by the working group. - The proposals and supporting documentation should be submitted to the NSI mailing list by the end of the day on the 28th February - The NSI working group will have 2 weeks to review the submissions before voting. Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0

Procedure to request demos at the GEC 22 / US INSPIRE / OGF 43 + GLIF event
by Sill, Alan 30 Jan '15

30 Jan '15

Dear OGF groups in the Infrastructure area, There will be demo opportunities available at the GEC 22 + OGF 43 event. Please see the information below regarding how to request a demo and how these will fit into the overall agenda. If you are interested in giving a demo outside of this opportunity at a Meetup or Cloud Plugfest, or as part of an OGF session, please also let me know and I will convey this to the organizers of those events. The main focus of the GEC22 demos is on direct networking topics, whereas those in the latter categories can be of broader interest. Thanks, Alan (for the OGF events team) -------------------- Begin forwarded message: Hi Alan, The demo is at GW, http://groups.geni.net/geni/wiki/GEC22Agenda. There wil be max of 55 demos (GENI and US-Ignite) and we are still waiting for demo proposal to come in so we can do the review and do the final selection. If there is any interest in doing a demo, here is the link. http://groups.geni.net/geni/wiki/GECDemoSubmission Cheers, Henry

1 0

Call for presentations at the NSI-WG meetings in Washington
by Guy Roberts 27 Jan '15

27 Jan '15

Hello NSI working group, This is a reminder that there will be an NSI meeting on 25th-27th March co-located with GEC22 and the GLIF winter techs. Please remember to register by the end of February to get the early bird rate. A high-level agenda is available here: http://groups.geni.net/geni/attachment/wiki/GEC22Agenda/GEC22Agenda-22Jan20… I am now preparing a detailed agenda for the NSI working group meetings. If you would like to present, could you please let me know and I will add you to the agenda. Please remember that any presentations must be submitted to the NSI mailing list one week in advance of the meeting to give everyone a chance to prepare. Regards, Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0

Minutes from today's NSI conf call...
by Guy Roberts 21 Jan '15

21 Jan '15

.... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6598 _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0

NSI working group processes
by Guy Roberts 21 Jan '15

21 Jan '15

Hello All, The NSI co-chairs are working on refining the working group procedures to help expedite the process of getting standards agreed. To help the process along we have put together a list of core NSI principles. The purpose of this document is to set out a baseline set of requirements that new NSI proposals need to adhere to. The document will help authors quickly check that their proposal aligns with the core concepts of NSI. This document is only for internal use by the working group and will not be published as a GFD. You can see this document here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6601 We will also be adding some additional documents which will clarify working group process for reviewing and agreeing proposals. I will be explaining this some more in today's NSI conf call. Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0

Wednesday's NSI conf call
by Guy Roberts 20 Jan '15

20 Jan '15

The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 ET, 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: - All to update their progress on NSI documentation - NSI core principles document - process for reviewing NSI submissions/proposals - Speeding up decision making in NSI - introducing a voting process - Agenda for NSI meeting in Washington - security sessions, demos, shared meetings with GLIF, evening discussion group... etc. _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0

No NSI meeting tomorrow Jan 7 2015
by Chin Guok 06 Jan '15

06 Jan '15

Hi all, Hope everyone enjoyed the break and are having a great start to the year. We will not have a meeting tomorrow, but be aware that we plan to cut over to the new topology schema this month. John will be sending out the details on this. Thanks! - Chin -- Chin Guok NOC: (510) 486-7600 Network Engineer (800) 333-7638 ESnet Network Engineering Group (AS293) Lawrence Berkeley National Laboratory

1 0

Security and Exchanges
by Henrik Thostrup Jensen 17 Dec '14

17 Dec '14

Hi (part two of the security and pathfinding) We are currently treating exchange points like switches (which is not really that weird, as that is what they are). Specifically, we are treating them as an independent domain, which does not reflect that the ports on exchange is leased by the connecting network, and hence be under control of the NSA of that network. Allowing a third party NSA to create circuits on an exchange to another networks port violoates the simple principle that an NSA should be in charge of the networks resources. This means that a network can no longer decicde how it wants to allocate its resources, which is pretty bad. There are some potential solutions to this like allocating a static vlan range to a certain network-network combination, but it is inefficient resource-wise. Requiring a token is another possiblity, but adds much complexity, as the token must be aquired apriori. As there is no standard mechanism in place for acquiring these, it would often end up being a long-lived token with wide permissions, which is less than ideal security-wise. The following presents a scheme that keeps the port under control by their respective NSA, doesn't require any static pre-allocation, and does not require any out-of-band token distribution. It can be seen as a standard mechanism for acquiring a token for setup. It does change the path setup flow somewhat, and requires special behavior for the exchange NSA, and the pathfinders using it. Finally it requires a control-level peering between the two NSAs responsible for the networks connecting to the exchange. We have the following scenario: Two networks: A & B One exchange: X The networks connect to the exchange on port X.A and X.B. NSA for network A, wants to setup a circuit from A to B over the exchange. The NSA for the exchange knows the identities of the NSAs for Network A & B, but will only allow them to allocate resource on their port. Having an exchange NSA operate in this manner is essential, as networks should only be able to allocate resources on their own ports (I don't consider the exchange backplane to be an issue here, usally congestion happens on the links). The circuit is setup on the following way: NSA for Network A, requests a circuit on the exchange from port X.A to a logical/virtual STP, named X.IC (for interconnect) in this example. The NSA for X recognizes that NSA A has the right to allocate resouces on port X.A, and grants the request. The STP returned for X.IC, is not X.IC, but instead X.A with a label (or token) on it. This label is randomly generated, and cannot be guessed (it could be a UUID, but it doesn't matter). Hereafter NSA A, makes a request to NSA B, with the newly created STP (with token), to create a circuit (could be tree or chain, doesn't matter), lets say it connect to B.P. NSA B will split this request up into two requests: One to NSA X for X.A to X.B (using the token, NSA X allow using X.A, and the NSA B is allowed to use X.B), and an internal link from X.B to B.P. When both requests have completed, a reply is send to NSA A. A perhaps more comprehensible version of the example: 1: Request from NSA A to NSA X: Reserve: X.A -> X.IC Response: X.A -> X.A?token=a5cbdf88-73e0-11e4-a1b3-f0def14b5d43 2. Reserve from NSA A to NSA B: Reserve: X.A?token=a5cbdf88-73e0-11e4-a1b3-f0def14b5d43 -> B.P 2A: Request from NSA B to NSA X: Reserve: X.A?token=a5cbdf88-73e0-11e4-a1b3-f0def14b5d43 -> X.B Response: X.A - X.B 2B: NSA B Interal Reserve: Reserve: X.B -> X.P Response: X.B -> X.P Response: X.A -> B.P Using this schema we avoid the situation where third party NSAs can allocate resource on networks without going through the NSA of the network. For the scheme to work, NSAs operating exchange points need to change the behavior of what they allow and how links are set up. Furthermore, they need to advertise this behaviour through their discovery service. Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet

3 4

Fwd: [cloudlab-announce] CloudLab is up and running
by Sill, Alan 16 Dec '14

16 Dec '14

FYI. This project is closely related to GENI and may be of interest to the NSI-WG for testing. Any feedback on new or existing projects that we should call to the attention of the OGF community at large for testing purposes or any other related topic for useful or related projects would be helpful. Alan Begin forwarded message: From: Robert Ricci <ricci(a)cs.utah.edu> Subject: [cloudlab-announce] CloudLab is up and running Date: December 16, 2014 at 12:09:10 PM CST To: <announce(a)cloudlab.us> Reply-To: <contact(a)cloudlab.us> We're happy to announce that CloudLab is up and running, and ready to accept users! Sign up for an account at: https://cloudlab.us/signup.php Many things are still in an early state, but we have enough in place for you to start getting some real work done. The cluster at the University of Utah is up, and clusters at Wisconsin and Clemson are coming soon. We have example profiles that provision bare-metal nodes and full, dedicated installs of OpenStack to get you started quickly. You can define experiments through CloudLab's GUI and provision both hosts and networks. You can also try out alpha-stage features like defining profiles through Python scripts. Coming in the near future are versioned images and profiles, persistent block storage, and quick profile creation. Come give it a try! Our user manual, including a "getting started" chapter: http://docs.cloudlab.us/ Descriptions of the clusters that we have up and on order: http://docs.cloudlab.us/hardware.html Join our community mailing list: https://groups.google.com/forum/#!forum/cloudlab-users [You're receiving this message because you signed up for the cloudlab-announce list. To be removed from the list, simply send a message with the subject 'remove' to <announce-remove(a)cloudlab.us>]

1 0

NSA Description Document
by Guy Roberts 10 Dec '14

10 Dec '14

Hello All, The GWD-R document: 'Network Service Interface, NSA Description Document' has now been submitted to Richard Hughes-Jones (OGF area director for infrastructure) to review before going out to public comment. You can download this document here: https://redmine.ogf.org/dmsf_files/13338 Guy _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect GEANT Limited Email: guy.roberts(a)dante.net<mailto:guy.roberts@dante.net> Tel: +44 (0)1223 371316 Mob: +44 (0)7881 336417 GEANT Limited is part of the GÉANT Association Networking. Services. People Learn more at: www.geant.org<http://www.geant.org/> and www.dante.net<http://www.dante.net/> GEANT Limited registered in England & Wales. Registration Number 2806796. Registered Office - City House, 126-130 Hills Road, Cambridge CB2 1PQ _____________________________________________________________________

1 0