All, Forgot to write these up last week, but here is a summary of the discussed topics: 1. Inclusion of source and destination STP in ERO. No one could remember the argument from Oxford for including them in the ERO, so functionality will remain as is. Source and destination STP are not included in the ERO. 2. Optionality of serviceType in modify and Query results. The serviceType element is defined as optional in the reserve schema definition since we have overloaded the operation to also handle modify. The serviceType element MUST be present in the reserve request for a new schedule, and MAY be present in the reserve request for a reservation modification, but if it is present, it must have the same value as the serviceType specified in the original reserve (we do not currently support modification of serviceType). Documentation will be modified to clearly state this. The serviceType element MUST be returned in the query response. It is currently defined as optional but this is an oversight. 3. Strict versus flexible processing of service descriptions. We had a brief discussion on the call, but a longer one once the call completed. The heavier and processing of service descriptions is a complicated issue that will need to be formally defined and discussed in the context of implementation. At the moment it is still too nebulous and we need to firm it up with a common understanding. John On 2013-08-28, at 8:49 AM, John MacAuley <john.macauley@surfnet.nl> wrote:
Hi all,
I forgot I was hosting the meeting today, so here is a slightly tardy reminder:
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:
- Inclusion of source and destination STP in ERO. - Optionality of serviceType in modify and Query results. - Strick versus flexible processing of service descriptions. - Any other issues that have come up from a week of implementation. - Status updates.
John