- Nsi-wg - lists.ogf.org

Topology Service presentation/demo for NSI call for tomorrow (Wed 8/14)
by Chin Guok 14 Aug '13

14 Aug '13

Hi all, We had a summer intern (Ahmed El-Hassany) working at ESnet on some topology stuff in the last couple months, and he put together a prototype topology service that might be useful for the NSI-WG. Just some background, Ahmed was the primary architect of the GENI Topology service which uses the RSpec format, so he has a bunch of experience behind him. Unfortunately he has now taken up a research position at UC Berkeley, so the prototype topology service will remain in its current state till we find resources to further its development. Having said that, a testing instance of the service is running at http://lstest.es.net:8080/urns. The documentation of using it is located at https://github.com/ahassany/topology-service/wiki/Using-NML-NSI-Topology-Se…. All the tutorial topologies that Jeroen put up on GitHub (see forwarded email) has been loaded into the service. You can list all NSAs by: curl http://lstest.es.net:8080/urns/ Or get a specific one by: curl http://lstest.es.net:8080/urns/urn:ogf:aruba.example:2013:nsa <http://lstest.es.net:8080/urns/urn:ogf:network:es.net:2013:nsa> For tomorrow's meeting, Ahmed will do show-and-tell, so please log into www.readytalk.com and use the 7-digit access code 8937606 to access the "show" portion of the meeting. 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: - Prototype topology service presentation/demo Thanks all. - Chin -------- Original Message -------- Subject: [Nsi-wg] Tutorial Topologies Date: Thu, 8 Aug 2013 13:20:40 +0200 From: Jeroen van der Ham <vdham(a)uva.nl> To: NSI Working Group <nsi-wg(a)ogf.org> Hi all, I have created new topologies for the tutorials. These follow the same schema as the updated Automated GOLE topologies. The new tutorial topologies should follow the same topology as the old ones. The domain names for all of them are "aruba.example" (using the IETF reserved namespace for examples). They can be found at the tutorial repository: https://github.com/jeroenh/NSI-Tutorial-Topologies/tree/master/topos Jeroen. -- Chin Guok NOC: (510) 486-7600 ESnet Network Engineering Group (AS293) (800) 333-7638 Lawrence Berkeley National Laboratory

1 1

Network portion of an STP
by John MacAuley 13 Aug '13

13 Aug '13

Peoples, What am I suppose to put in the network portion of the STP? I was looking in the topology schema and there is nothing specifically called "network" so should I assume it is the topology URN? networkId = "urn:ogf:network:example.org:2013:topology" As a follow-up, do I also then populate the local portion with the full URN of the port? localId = "urn:ogf:network:example.com:2013:eth0-out" Thank you! John

4 4

DynamicKL NSI 2.0 is available
by 이경민 12 Aug '13

12 Aug '13

3 2

Tutorial Topologies
by Jeroen van der Ham 08 Aug '13

08 Aug '13

Hi all, I have created new topologies for the tutorials. These follow the same schema as the updated Automated GOLE topologies. The new tutorial topologies should follow the same topology as the old ones. The domain names for all of them are "aruba.example" (using the IETF reserved namespace for examples). They can be found at the tutorial repository: https://github.com/jeroenh/NSI-Tutorial-Topologies/tree/master/topos Jeroen.

1 0

minutes from today's NSI conf call
by Guy Roberts 07 Aug '13

07 Aug '13

.... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6529 _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

Wednesday's NSI conf call
by Guy Roberts 07 Aug '13

07 Aug '13

Hi all, 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: - Service Definition schema documentation - Error message handling - CS doc editing - Chairing next weeks call _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0

Service Description for ETS
by John MacAuley 06 Aug '13

06 Aug '13

Peoples, I am preparing to make a service description for the Ethernet Transport Service (ETS) we are running on the A-GOLE. I need opinions on minimum, maximum, and default values for this service. Can you please provide feedback on the following: 1. serviceType == ETS.A-GOLE 2. reservation duration - minimum X and maximum Y (no default) 3. capacity - minimum X and maximum Y (no default) 4. directionality - values (Bidirectional, Unidirectional) with default Bidirectional 5. symmetricPath - values (TRUE, FALSE) with default FALSE 6. sourceSTP mandatory 7. destSTP mandatory 6. ero optional 7. mtu - minimum X, maximum Y, default Z 8. burstsize - minimum X, maximum Y, default Z Have I missed anything? Thank you, John

3 5

Change of xsd:int for large numbers
by John MacAuley 05 Aug '13

05 Aug '13

People, As I have been going through the service description I realized we are going to have problems with our current use of xsd:int which is a signed integer value. If you remember we changed from the xsd:integer to an xsd:int in release 1.0 to simplify coding in Java since it uses a base int type instead of an Integer object. This was okay in release 1 since we were specifying bandwidth in Mbps, however, with the introduction of service descriptions it is possible to specify the units for capacity. This means with our current xsd:int definition we are unable to specify bps for capacity. Also, it looks like burst size as an xsd:int will also not work. Is anyone against me changing these to an integer or perhaps nonNegativeInteger? Thanks, John

3 4

Issue 100 in ogf-nsi-project: Need no GenericErrorType to communicate INVALID_TRANSITION errors
by ogf-nsi-project＠googlecode.com 03 Aug '13

03 Aug '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 100 by jmacauley: Need no GenericErrorType to communicate INVALID_TRANSITION errors http://code.google.com/p/ogf-nsi-project/issues/detail?id=100 Description of Issue: For those requests like reserveAbort, provision, release, etc. there is no GenericFailedType reply. How can errors such as INVALID_TRANSITION be passed to the RA? Discussion of Issue: The specific failed messages were removed for operations such as provision because there was a view that it would not fail, and therefore, would not require failed transitions in the state machine. However, there are some errors that do not cause state machine transitions. At the moment there is no mechanism that would permit their return to the requesting agent after a message has been accepted for processing (a service exception can be returned instead of an ACK, but this is only during the message acceptance phase). Resolution of Issue: Add a generic error message that can be returned to indicate a non-state machine affecting error. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Issue 103 in ogf-nsi-project: NSI errors allocation to messages
by ogf-nsi-project＠googlecode.com 02 Aug '13

02 Aug '13

Status: Accepted Owner: tkudoh...(a)gmail.com Labels: Type-Defect Priority-Medium New issue 103 by guy.robe...(a)gmail.com: NSI errors allocation to messages http://code.google.com/p/ogf-nsi-project/issues/detail?id=103 Description of Issue: The table in Appendix B of the NSI CS v2.0 document lists a set of error cases. To which message do each of these errors apply? Discussion of Issue: GR: propose that we add a column in the table to indicate which errors are valid for which messages. Resolution of Issue: -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1