Malcolm ran briefly through the latest version of the document and emphasized that there had been no significant comments/changes for some while.
It was agreed that the latest version will be incorporated in 1.5 essentially as is. Nigel will carry out editing and only raise critical issues (of which we expect there to be none. Minor issues will be covered in review.
There was a discussion on "pre-planned" state (that was highlighted during discussions on TAPI ConnectivityService "candidate" Computation). This is a state for resources that are effectively temporary fabrications that are not real in the network or plan (and that last only for the duration of the computation). The state is essentially outside the main lifecycle state structure. The state allowing the representations to be in conflict with others. It was agreed to not add this at this stage.
During the meeting we:
There was concern that 2.0 was being pushed out by 1.5 and 1.5+. Whilst 1.5 appeared appropriate content we need to discuss which 1.5 + features we should deliver before 2.0 and which after. The basic concern was that the longer we delay the backward compatibility issue the more users we will have and the more impact it will cause.
|Future call topics|