May 11, 2007 OASIS ebXML CPPA Teleconference Notes

Attendance

Pete Wenzel

Dale Moberg

Monica Martin

Regrets, both travelling

Pim van der Eijk

Sacha Schlegel

Agenda is located at http://lists.oasis-open.org/archives/ebxml-cppa/200705/msg00001.html

Webinar discussion omitted. Pete and Monica are overbooked for webinar tasks that week, so Sacha, Dale and potentially a technology and business expert with direct experience in a CPPA based community ramp environment will cover webinar.

So we headed directly into a second pass over the May 10 version of the ebMS v 3 enhancement table (attached with notes and corrections made during meeting).

The focus in the second pass was to review the items marked “New” and the proposals and discussions added in the May 10 draft by the editor.

Id could be covered with no new items, just with some suggestions about how to form identifiers of varying granularity to identity PModes. Still some work to explain conventions. Consensus seemed to be to derive this value from existing values and not make the conventions recommended and not mandatory.

Some information items from the Business topic will be included in a new DocExchange module; name is to be proposed when schema content model created.

Consensus favored the proposal to explore extending the AccessAuthentication content model to handle usernames and passwords for wsse usage. Pete brought up the problem of whether signature would be over unencrypted values. Dale brought up the problem of how to allow validity check of instance without decrypting. Both Pete and Dale will pursue seeing how this kind of problem is solved elsewhere (if it has been). Dale proposed that signatures be over encrypted values. Not certain whether that was agreed to, so need to consider again.

Dale will create a detailed complexType for the modified AccessAuthentication and indicate where it can go. Also he will create the new ebMS 3 DocExchange complexType.

The last topic addressed the notify producer and consumer Boolean flags. Everyone agreed that these values modify local MSH to application interaction. Dale said that the kinds of interaction in place might be of interest to the remote party, even though the interaction is a local matter (and no configuration details are supplied). Monica pointed out how different these features are from the normal collaboration configuration values at the core of CPPA. Also, no matching is really needed between partners when forming a CPA (or so it appears at present). Monica wondered how we could make this an optional part of the CPPA. The topic was far from exhausted by the time everyone had to move on to the next calls. Monica also mentioned that we should consider how this complements or complicates BPSS signals (especially for exceptions). We will have to consider that at future teleconferences.

PMode Information Item	CPPA v 3.0 Information Source

Agreement (AgreementRef)	/CollaborationProtocolAgreement/@cpaId
Initiator.Party	PartyInfo/PartyId and @type
Responder.Party	PartyInfo/PartyId and @type
ID	[Proposal] New information item: This optional information item’s value can be formed by concatenating the value of @cpaId with the value of @action. Granularity range can vary by using service or just cpaId etc.
[Initiator\|Responder].Authorization. username	New information item. XML encrypted item, used in wsse header targeted at ebms actor role. [Proposal background] Must be potentially distinct for each action binding. There already is an element AccessAuthentication used in describing the mode of HTTP authentication in use. We can now make use of XMLEncryption for data confidentiality of values. [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
[Initiator\|Responder].Authorization. password	New information item. XML encrypted item, used in wsse header targeted at ebms actor role. [Proposal: see above]

MEP	DocExchange module element for ebMS 3.0. URI, e.g: http://www.oasis-open.org/committees/ebxml-msg/one-way. ./two-way
MEPbinding	Possibly qualifies how transport is used. Attribute URI, e.g: http://www.oasis-open.org/committees/ebxml-msg/push
ProtocolAddress	Transport/Endpoint
Protocol.SOAPversion	New information item 1.1 or 1.2 [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchagne/ebXMLReceiverBinding to contain this information.


BusinessInfo.Service	Service
BusinessInfo.Action	@action
BusinessInfo.Role Note both sides need role values in To and From information items	CollaborationRole/Role/@name or new override value in ActionContext2
BusinessInfo.PayloadProfile	New [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.
BusinessInfo.PayloadProfile.maxSize	New [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.
BusinessInfo.MPC	New[ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.
BusinessInfo.Properties	New – List of 4-tuples [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.

ErrorHandling.SenderErrorsTo	CHECK New [Discussion] Where the MSH sends errors to an alternative endpoint so this might be an Endpoint with a special purpose value or mshSignal default channel
ErrorHandling.ReceiverErrorsTo	defaultmshSignal channel
ErrorHandling.AsResponse	syncReply mode value of mshSignal or a more inclusive value
ErrorHandling.ProcessErrorNotifyConsumer	New, include? [Discussion] This Boolean flag modifies MSH to application interaction
ErrorHandling.ProcessErrorNotifyProducer	New , include? ? [Discussion] This Boolean flag modify MSH to application interaction

ErrorHandling. DeliveryFailuresNotifyProducer	New ? [Discussion] This Boolean flag modifies MSH to application interaction

atLeastOnce.Contract	MessagingCharacteristics.AckRequested
atLeastOnce.AckOnDelivery	New, include? [Discussion] This Boolean flags modify MSH to application interaction
atLeastOnce.AcksTo	defaultMsh syncReplymode
atLeastOnce.AckResponse	defaultMsh syncReplymode
atLeastOnce.ReplyPattern	syncReplyMode, defau ltMsh, and override for pull mode

atMostOnce.Contract	MessagingCharacteristics.DuplicateElimination
inOrder.Contract	DocExchange/ReliableMessaging/MessageOrderSemantics = Guaranteed
StartGroup	New [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.
Correlation	New [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.
TerminateGroup	New [ProposedLocation] Add a new module under DocExchange/ebXMLSenderBinding and DocExchange/ebXMLReceiverBinding to contain this information.

WSSVersion	New [Discussion] We might document WSS as a protocol value
Signature	New extensions needed for element selection
Signature.Attachment	Look at attachments, see whether excludefromsignature present
Signature.Certificate	Ref to signing certificate
Signature.HashFunction	NonRepudiation/HashFunction
Signature.Algorithm	NonRepudiation/SignatureAlgorithm
Encryption	New extensions needed for elements attachments
Encryption.Certificate	DigitalEnvelope/ EncryptionCertiifcateRef
Encryption.Algorithm	EncryptionAlgorithm
Encryption.MinimumStrength	@minimumStrength
WSS.username	New [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
WSS.password	New [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
WSS.Token.digest	New [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
WSS.Token.nonce	New [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
WSS.Token.created	New [Proposal] Extend content model for AccessAuthentication to handle username and password information. Allow AccessAuthentication as an optional module under DocExchange/[DocExchangeBindingType] ?
WSS.PModeAuthorize	New but see HTTP auth support BusinessCharacteristics/@isAuthorizationRequired
SendReceipt	MessagingCharacteristics/@signAck and BusinessTransactions/@isNonReudiationofReceiptRequired
SendReceipt.ReplyPattern	syncReply = Signals or Both

ebxml-cppa message