Messaging Services TC Meeting Wednesday & Thursday October 9th & 10th
G Neelakantan Karta Sterling (part time)
Eric Van Lydegraf
(various times and duration)
- Proposed agenda accepted with one concern from Doug about attendance as we did not have a quorum to be able to vote on any issues.
- Due to the low attendance no need for formal secretary etc. was identified (Ian took minutes)
- Ian described current requirements and discussion on the nature and scope of the requirements followed to validate if these were still requirements.
- New requirements were added to the list – see web sit for the additions.
- The requirements were then prioritised and initial level of impact identified to try and identify which requirements would be suitable for a version 2.X release (i.e. bug fix and minor semantic changes) and which would be major changes resulting in a version 3.0 specification.
- During the discussions Relationships with WS-security and/or W3C groups were discussed and added to the requirements list. This is not strictly a requirement but could impact on several relating to SOAP version, security and multi-hop messaging.
- The WS-Security team currently schedule to release version 1.0 in March 03. This release is currently planned to include Digital Signature, Encryption of Soap header and attachments and carrying authentication tokens.
- Action Submit requirement to WS-Security TC to use our definition of signature transform as an option to allow us to remain upwardly compatible. The current draft proposes a different signature definition which would require us to change and make messages potentially incompatible between the existing Version 2.0 and any new release including the WS-security work. (See note below)
- Dale is arranging a conference call with the of WS-Security TC and Ian will present our requirements to the TC.
- Action Dale to talk to Karl about formal liaison to WS-Security. A preferred solution would be for the MSG TC to Security Joint Committee.
- Action Jeff to ask vendors with multi-hop issues that were identified during the Drummond Group interoperability testing to contact the TC with details.
- After discussion is was felt a sensible position to wait for SOAP 1.2 to become a recommendation before deciding if, how and when we would migrate to it.
- Action: Doug will begin to look at the issues list and ensure it is still relevant and accurate.
- Proposal: Sync reply requirement 20.
Amending the definition of reliable messaging to explicitly state that messages received out of sequence will not be made available to the application until all preceding messages have been received in the sequence.
This clarifies the semantics of the "Acknowledgement" element.
Amend "MessageOrder" element presence rule to explicate state that the CPA must set either SyncReply to "none " or "MSH Signals only"
Section 9.2 need reworking to include an error message of inconsistent should be returned if the message setting and CPA do not match.
Also make the use of "MSH signals only" the only mandatory "core" feature provided the underlining transport is synchronous.
- Mike Dillon raised a question about SOAP Action in the HTTP headers. A clarification on its inclusion in the reply may be required. This is believed to be an ambiguity in the SOAP 1.1 specification and therefore may be out of the scope of this TC. Also this may be superseded in SOAP 1.2 to be investigated as mandatory nature of SOAP Action is one of the items likely to change in the current drafts..
- Mike Dillon identified a conflict of the Soap HTTP content type when a message with no payload being multipart/related a simple change to the HTTP binding could fix this. This must be checked prior to any change to ensure consistency throughout the specification.
- No explicit exclusion of syncreply in a synchronous reply – This must be addressed as it is an potential problem if this is used although all identified implementations spotted that this was not a sensible implementation.
- For MIME headers they should be case insensitive. This requires clarification from the IETF MIME RFC’s before this is included.
- Use of the "@" in content Id and message Id, this may be a MIME spec reference issue. The spec is not consistent with use of this. As a minimum the specification must be made self consistent and validated against the MIME RFC’s
- Doug lead discussion on modularization of the existing structure of the message.
Proposal: Split message data and duplicate elimination from the message element and make them top level elements in their own right. Group CPAId and conversation into a new a top level element.
Implication: For a SOAP message to be an ebXML conformant message it would have to contain all the top level elements and it would also increase the size of each message and the speciofication.
- Dale re-joined the call and a discussion on CPP/A and messaging use of intermediaries. No current requirements to support mult-party transaction with intermediate CPAs.
- CPP/A have deferred work on WSDL as BPSS have asked them to wait until they had finished some investigating of how they will or may use WSDL. Also WSDL 1.2 is still very fluid and CPP/A will wait for a more stable version. Must effort is to complete the negation spec.
- X.12 will be using ebXML infrastructure in the future and will require a method to transfer from X.12 ISA structures etc. to ebXML messaging. This work will be subject to further discussion between X.12 people and this team. Currently Bob Miller is likely to move this forward.
- The work plan (below) was started and the first month of items identified.
- The Messaging TC thanks ASC X.12 for their support by hosting the meeting and especially to Ralph Berwanger for arranging this for us.
- The Meeting closed with a thanks to those that attended, your participation was appreciated and progress was made toward our goal of constant improvement of our specification
- Mike Dillon to own and lead on the Errata document to the 2.0 specification. Initial version within 1 month.
- Ian to announce errata document and start of version 3.0 with rational for noting being a 2.x release.
- Set-up liaisons with other teams mainly Security & BPSS.
Initial action that within 1 month the liaison with the appropriate security team will be established.
Submit security requirements to the appropriate team
- People to review existing issue list.
- People to review the requirements list that was prioritised.
- Set up a conference calling schedule the initial suggestion is 1 hour every 2 weeks on Wednesdays.
Next conference call: Wednesday 23rd 1pm PDT (4pm EDT, 9pm BST) kindly hosted by Sun, thanks Doug.
Agenda will be posted to the list.
Next face to face Mid January to February date to be defined preferable West Coast.
(Note – after the meting closed X.12 offered facilities at their next meeting in February in Denver)
Action: All conference calls and meetings must be supported both with hosting and participation.
Action: All OASIS membership rules for voting rights will be enforced to ensure an active TC, so far I have received only one formal request for a leave of absence. Please ensure that you are familiar with the TC guidelines. Failure to "attend" meetings does not prevent any member of OASIS participating in the discussion or meetings it only affects their right to vote on issues and approval of specifications. The drive behind this is the need to have sufficient people to form a quorum to vote!
The digital signature transform used by version 2.0 of the message service is to exclude items that we do not wish to sign, whereas the proposed WS-security version explicitly identifies those items it wish to sign. An affect of the messaging version is to prevents the addition of SOAP modules targeted at the end point.
Requirements list & Issues list on web site: http://oasis-open.org/