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

Oxford feature list
by Guy Roberts 13 Jun '12

13 Jun '12

attached _____________________________________________________________________ ** Guy Roberts, PhD Senior Transport Network Architect * * 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

Topology (was Re: Identifiers)
by Jeroen van der Ham 13 Jun '12

13 Jun '12

Hi, > First a minor nit: the current NSI form is "urn:ogf:network:stp:<networkname>:<local part>" . I.e. there is no "opaque" multilevel subspace under the <networkname> component in STPs. The local part is up to <networkname> to define, so it is opaque in my view, and can have as many sub-levels as they want. > A basic question occurs to me: Why do names need to be consistent within NSI and NML? What breaks if NSI maintains its current naming scheme? This is IMO the wrong question from a bigger perspective. From an OGF standpoint, the goal of the NSI is to define a network service interface. The goal of the NML is to define a network markup language. Since both groups fall under the same standardisation organisation, the question ought to be "how can NSI use the NML model?". > I believe the NSI hierarchical two-tuple <networkid>:<localid> must be maintained as we reconcile the NML form to NSI. I think this will prove high useful in both path finding and topology distribution. Since the DNS name is still part of an STP, you still have a separate network-id. > It seems to me the <DNS> requirement for the NML name could be relaxed slightly to be a bit more flexible for NSI network name requirements without undue harm to NML. > > I suggest that there is no need to name STPs with a year component - this should be removed. (Why is it even required for NML?) Please read again what was in my reply earlier, or refer to the urn:ogf:network request document that is in the NML repository. Jeroen.

1 0

first draft of NSI v2.0
by Guy Roberts 12 Jun '12

12 Jun '12

Hello all, In preparation for OGF35 next week, please find a draft version of NSI v2.0 document here: https://forge.ogf.org/sf/go/doc16446?nav=1 Thanks everyone for your contributions! Regards, Guy From: Guy Roberts Sent: 12 June 2012 11:30 To: nsi-wg(a)ogf.org Subject: Tomorrow's NSI conf call The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 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: * Preparations for Delft * Contributions to NSI v2.0 CS protocol document Guy _____________________________________________________________________ ** Guy Roberts, PhD Senior Transport Network Architect * * 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 conf call
by Guy Roberts 12 Jun '12

12 Jun '12

The following is dial-in information for Wednesday's NSI call, time: 7:00 PDT 10:00 EDT, 15:00 BST, 16:00 CEST, 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: * Preparations for Delft * Contributions to NSI v2.0 CS protocol document Guy _____________________________________________________________________ ** Guy Roberts, PhD Senior Transport Network Architect * * 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

Call for papers: Collaborative research using eScience infrastructure and high speed networks
by Inder Monga 12 Jun '12

12 Jun '12

**** apologize if you receive multiple copies of this call for proposals ****** Dear Friends, The attached link to call for papers <http://www.surfnet.nl/en/Hybride_netwerk/SURFlichtpaden/Pages/Collaborative…> is a wonderful opportunity present at a workshop co-located with IEEE international conference on eScience to be held on 9th October in Chicago, Illinois. The talks are accepted based received 1 - 2 page abstracts. The accepted talks will have an opportunity to publish written papers in a special section of the scientific journal Future Generation of Computer Systems (FGCS). The link with the details on the workshop is at : http://www.surfnet.nl/en/Hybride_netwerk/SURFlichtpaden/Pages/Collaborative… The workshop and the special section will focus on scientific use-cases in which high-speed wide area networks , such as enabled by NRENs around the world and by the GLIF community, are used in a novel way. The workshop will cover and highlight applications that use such networks to connect instruments and facilities around the world in a novel manner. It will also explore upcoming trends in the design and architectures of these advanced networks. Topics of interest include, but are not limited to, the following: * Distributed applications running on high-speed networks * Network architectures for integrated e-Science research * Advances in networking devices and protocols that support management and control of distributed e-Science infrastructures * Models for networks and infrastructure descriptions suitable for inter-NRENs cooperation Researchers are invited to submit extended abstracts describing a scientific use case of the advanced use of distributed resources connected by high speed (national or international) networks. Extended abstracts of 600 to 1200 words (one to two A4 pages) must be submitted in English, the official language of the conference. These should be accompanied (attached to the extended abstract above the two pages) by a short professional biography of the author(s) and the full names and contact details of the author(s) as outlined below. Keywords will assist the program committee in planning the final program of the conference. Important Dates: Workshop abstract submission: 25 June 2012 Workshop acceptance notification: 11 July 2012 Final extended abstract: 10 September 2012 Workshop: 9 October 2012 For the special section in FGCS: Full paper submission: 15 October 2012 Please send your abstracts to creihsn-submission(a)list.surfnet.nl <mailto:%20creihsn-submission@list.surfnet.nl> Look forward to your participation and abstract! Inder -- Inder Monga 510-486-6531 http://www.es.net Follow us on Twitter: ESnetUpdates/Twitter <http://bit.ly/bisCAd> Visit our blog: ESnetUpdates Blog <http://bit.ly/9lSTO3><http://bit.ly/d2Olql>

1 1

Issue 62 in ogf-nsi-project: Rename guaranteed and preferred elements in TechnologySpecificAttributesType
by ogf-nsi-project＠googlecode.com 11 Jun '12

11 Jun '12

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-1.1 New issue 62 by jmacau...(a)gmail.com: Rename guaranteed and preferred elements in TechnologySpecificAttributesType http://code.google.com/p/ogf-nsi-project/issues/detail?id=62 Description of Issue: Rename guaranteed and preferred elements in TechnologySpecificAttributesType to mandatory and optional. Discussion of Issue: As discussed on weekly call the guaranteed and preferred elements should be changed to to mandatory and optional to better represent their behaviours. Resolution of Issue: Rename elements in types file.

1 2

Issue 61 in ogf-nsi-project: Allocate new namespace version to WSDL version 1.1.
by ogf-nsi-project＠googlecode.com 10 Jun '12

10 Jun '12

Status: Accepted Owner: jmacau...(a)gmail.com Labels: Type-Defect Priority-Medium FoundInVersion-1.1 FixedInVersion-1.1 New issue 61 by jmacau...(a)gmail.com: Allocate new namespace version to WSDL version 1.1. http://code.google.com/p/ogf-nsi-project/issues/detail?id=61 Description of Issue: The ogf-nsi-cs-v1.1 branch was created but the WSDL was not modified to contain a new namespace so it currently collides with the version 1.sc Discussion of Issue: No discussion needed. New namespace must be allocated to distinguish between versions. Resolution of Issue: Created a new namespace version based on 1.1 creation on 2011/12.

1 2

Summarization of ERO discussion
by Chin Guok 07 Jun '12

07 Jun '12

Hi all, Sorry for not getting this out sooner. There has been some discussion in a smaller group on how to resolve the ambiguity of EROs that use bi-directional STPs. I've tried to capture the proposed solutions from the discussion and present them in the attached slide deck. I apologize to the folks in the discussion if I misrepresented your proposals, please feel free to make corrections. Thanks. - Chin

3 3

Topology section
by Jeroen van der Ham 05 Jun '12

05 Jun '12

Hi all, Today I've done some more work on the Topology section, see: https://docs.google.com/document/d/1HIo7uQl7DbTe_y-cnPOrqDkspoRBaTKVVrrldUR… Basically, I've broken down the Topology section into sub-problems: 1) Representation, where we use mostly the DTOX representation, supplemented with NML and 2) Distribution. The Distribution is then further sub-divided into: - Bootstrapping, how do NSAs initially find each other - Further exchange, how do NSAs learn about the world - Updating, how do we distribute updates to the network - Policy, what do we do with it I think these are all pretty manageable problems, with the exception of the policy on topology exchange. I propose we punt it to a next version once we have some experience on how this works. AFAIK we all agree that basic information in the DTOX representation is required for NSI to function at all, and we have no experience with additional information yet. Jeroen.

1 1

1 month to submission CFP: Computer Networks Special Issue on Future Internet Testbeds
by Jeroen van der Ham 05 Jun '12

05 Jun '12

Hi all, This is somewhat short notice, but I think an excellent opportunity to write about our current experiences with the Automated GOLE testbed so far. I'm willing to take the lead on this article, and am looking for other contributors. Jeroen. Begin forwarded message: > Special Issue on Future Internet Testbeds > http://www.journals.elsevier.com/computer-networks/call-for-papers/special-… > > Important dates > Paper submission: 01-07-2012 (extended) > Acceptance notification: 15-09-2012 > Final papers: 15-11-2012 > > It is increasingly recognised that the current Internet architecture is being challenged by unprecedented scale, new applications, untethered mobile wireless access, and domain-specific network scenarios and technologies including MANETs (mobile ad hoc networks) and wireless sensor networks. At the same time we increasingly rely on the Internet for all aspects of our lives. > > The ability to evolve the Internet architecture to meet these challenges depends in part on the ability to test proposed protocols, services and configurations in a realistic setting at an appropriate scale. This requires testbeds that have significant scale, geographic scope, and that have a programmable Internet waist to permit experimentation with new addressing, forwarding, routing, and signalling paradigms. The GENI (Global Environments for Network Innovation) program in the US, and FIRE (Future Internet Research and Experimentation) programme in Europe have recognised and are funding this need. > > With this special issue of Computer Networks, we solicit papers that that describe the results of experimentation on the architecture, implementation, and deployment of Future Internet (FI) testbeds. While we are especially interested in experimental results, we also seek insightful papers that describe testbed architectures and their deployment issues, challenges, and experience. > > Topics of interest include, but are not limited to: > > • programmable FI testbed architectures > • scalability in node count, interconnection complexity, and geographic scope > • interoperation and extension across research networks (such as Internet2, NLR, GÉANT2, JANET, JGN-X, and KOREN/KREONET) > • heterogeneity and FI testbeds for domain-specific networks > • alternative communication paradigms (e.g. packets vs. circuits) > • deployment challenges and experiences > • federation of heterogeneous testbeds with one another and with > • instrumentation and measurement of FI testbeds > • management of FI testbeds that are distributed across administrative domains > • security, use policy, and broad research community access to FI testbeds > • experiment design, methodology, and verification > • experimental results that could not have been achieved on traditional end-system or localized testbeds (e.g. PlanetLab or Emulab) > > Submission format > The submitted papers must be clearly written in excellent English and describe original research which is not published nor currently under review by other journals or conferences. Author guidelines for preparation of manuscript can be found at www.elsevier.com/locate/comnet/ > > Submission Guideline > All manuscripts and any supplementary material should be submitted through the Elsevier Editorial System (EES). The authors must select as “Future Internet Testbeds” when they reach the “Article Type” step in the submission process. The EES website is located at: http://ees.elsevier.com/comnet/ > > Guide for Authors > This site will guide you stepwise through the creation and uploading of you article. The guide for Authors can be found on the journal homepage (www.elsevier.com/comnet/) > > > Guest Editors > > James P.G. Sterbenz > The University of Kansas, Lawrence, Kansas, USA. jpgs(a)ittc.ku.edu > Lancaster University, Lancaster, United Kingdom. jpgs(a)comp.lancs.ac.uk > > David Hutchison > Lancaster University, Lancaster, United Kingdom. d.hutchison(a)lancaster.ac.uk > > Paul Müller > Kaiserslautern University, Kaiserslautern, Germany. pmueller(a)informatik.uni-kl.de > > Chip Elliott > GENI Project Office, Raytheon BBN Technologies, Cambridge, Massachusetts, USA. celliott(a)bbn.com > > _______________________________________________ > geni-announce mailing list > geni-announce(a)geni.net > List info: http://lists.geni.net/mailman/listinfo/geni-announce > Unsubscribe: http://lists.geni.net/mailman/options/geni-announce/vdham%40uva.nl?login-un…

3 2