August 2013 - Nsi-wg - lists.ogf.org

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

Issue 102 in ogf-nsi-project: Existing capacity and burst size definitions in p2p service too small for expected values.
by ogf-nsi-project＠googlecode.com 01 Aug '13

01 Aug '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-2.0 New issue 102 by jmacauley: Existing capacity and burst size definitions in p2p service too small for expected values. http://code.google.com/p/ogf-nsi-project/issues/detail?id=102 Description of Issue: Capacity and burstsize are defined as xsd:int which cannot represent a 100 Gbps service. Discussion of Issue: xsd:int was originally chosen because rates were in Mbps, and this converted to a base int in java. We must change to a larger representation such as xsd:long that will also map to a basic java type. Resolution of Issue: Need to change xsd:int to xsd:long to hold these larger rates. -- 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 101 in ogf-nsi-project: Define Service Description XML Schema
by ogf-nsi-project＠googlecode.com 01 Aug '13

01 Aug '13

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-2.0 New issue 101 by jmacauley: Define Service Description XML Schema http://code.google.com/p/ogf-nsi-project/issues/detail?id=101 Need to create service description XML schema for describing a service, the associated service schema, parameter ranges and default, other attributes of a service, and the service specific errors. -- 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 2

3 issues changed in ogf-nsi-project
by ogf-nsi-project＠googlecode.com 01 Aug '13

01 Aug '13

Updates: Status: Fixed Comment by jmacauley: Closed issue with revision r78. Affected issues: issue 75: Clean up documentation in WSDL and XSD files. http://code.google.com/p/ogf-nsi-project/issues/detail?id=75 issue 98: Decouple service specific schema from NSI-CS core schema http://code.google.com/p/ogf-nsi-project/issues/detail?id=98 issue 99: Update namespace for final NSI-CS v2.0 schema http://code.google.com/p/ogf-nsi-project/issues/detail?id=99 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

DRAFT: A-GOLE service description and supporting XML schema
by John MacAuley 01 Aug '13

01 Aug '13

All, I have submitted the updated service schema, the draft A-GOLE service description, and the draft service description XML schema. I have attached the A-GOLE SD and SD schema to this e-mail. I need to refactor the SD schema to clean it up a bit, but this will give you the basic idea. John

1 0