10/3/01

Call to order Dale Moberg

Agenda Items:

Wednesday, October 3, Preliminary Agenda.

Joint Meeting – CPPA, MS

Attendance:

Brian Gibb

Daniel Weinreb

Tony Weider

Brian Hayes

David Fischer

Martin Sachs

Pete Wenzel

Kevin Liu

Arvola Chan

Peter Ogden

Pallavi Malu

Brad Lund

Kazunori Iwasa

Yokinori Saito

David Burdett

Dale Moberg

Doug Bunting

Sinisa Zimek

Attendance on Phone:

Chris Ferris

David Smiley

Bob Miller

Ian Jones

Colleen Evans

SanJay Cherian

Neelakantan Kartha – CPPA

Bruce Pedretti

Jamie Clark

9 AM: Discuss how best to capture intermediaries within the ebXML framework.

Should intermediaries be regarded as:

  1. part of the network infrastructure below ebXML conversations,
  2. a specialized forwarding agency requiring special ebXML support in Messaging and CPPA, or
  3. a node within ordinary ebXML conversations, captured in BPSS, and treated in accordance with standard CPPA and Messaging constructs? These decisions have most direct impact on possible changes for v1.1 of the CPPA specification.

10: Break

10:15 Continue with specific issues touching on Messaging and CPPA support for ebXML messaging. These include:

1. CPAid values in the header when no CPA exists.

2. Service and action values: where these values are found when both BPSS and CPPA exist and any recommendations about values used in other cases. See CPPA issue id 47 on CPPA’s normative appendix on use of CPPA specified values within ebXML header.

11:00 Continue detailed issue review: RM parameters and CPPA specification.

Via element: is any CPPA version 1.1 support needed? What parameters need to be per message configurable? Should CPPA ignore these or supply defaults? Prioritize issues for afternoon sessions. If major architectural principles remain unclear, decide whether to delete broken functionality from 1.1 versions until 2.0.

Noon Lunch

1 Resume detailed issue review using AM prioritization. Identify and agree upon action items where possible using the 1.1 criteria (fix what is broken or unacceptably unclear)

3 Break

3 :15 Continue detailed issue review, assembling all work and action items

4:15 Assess status of work to be completed. Record the action item owners and their scheduled commitments to complete.

Dale Moberg

  • Objectives of MSG – David B, Ian
  • v1.1 output by Dec – clarifications and bug fixes.
  • RM and support for Intermediaries
  • Need to agree to concepts this week.
  • Three implementations
  • Objectives of CPPA – Dale, Tony
  • Walkthrough of issues (v1.1 or v2.0)
  • Multipart out of scope for v1.1
  • Align with MSG
  • Spec for review by end of Jan
  • Submit to OASIS end of Feb
  • How do we treat Intermediaries – Dale
  • Specialized Schemas are potential problem for spec
  • Keep it Simple
  • Principles
  • part of the network infrastructure below ebXML conversations,
  • a specialized forwarding agency requiring special ebXML support in Messaging and CPPA, or
  • a node within ordinary ebXML conversations, captured in BPSS, and treated in accordance with standard CPPA and Messaging constructs? These decisions have most direct impact on possible changes for v1.1 of the CPPA specification.
  • Mailroom vs. Store-and-Forward

<discussion>

  • What is an IM?
  • Should the ebXML spec describe what is inside the business? (No)
  • Should we have a VIA? Yes, we already have it so we need to try to make it work.
  • Multiparty CPAs are v2.0.
  • Does CPPA really need to change to support Via? (consensus, no)
  • There are two architectures here (w/ or w/o Via).
  • Can we have a transparent IM approach.
  • Motion: to remove CPAId from Via and specify that Via elements values can override end-to-end CPAId parameters if there are any – David F
  • David B second
  • Chris motion to remove override. Ian second.
  • Vote on amendment – David B object.
  • New Motion: Remove CPAId from Via. No 1 abstain 2 Yes 7
  • Vote: 1 abstain. 10 yes.
  • Motion: for v1.1 to limit the described features and functions of IMs to forwarding only. Declaration of Intent. David F. Second - David B
  • Table Motion to wait for Quorum.
  • Yes 9, abstain 2, No 1
  • More Discussions
  • Should SyncReply be in CPA? Probably Yes, but not if this is modifiable Message by Message.
  • Go over Arvola's list – what is CPPA doing for v1.1
  • Certificate Support
  • SSL certificate support (CertRef w/ roles, dual keys)
  • Questions about other methods, S/MIME, XMLDsig
  • Encryption Support
  • EbXML w/o CPA (delete)
  • Clarify Retries, RetryInterval, PersistDuration
  • Acks/ DR – TBD
  • SyncReplyMode doesn't align with SyncReply?
  • Basic Authentication Question MS B.2.6
  • CPA for IM – CPAId taken out of Via
  • Use of CPA with ebXML-MS – Guide.
  • Add guide to DeliveryChannel
  • Joint between MS & CPPA
  • RefToMessageId
  • RosettaNet Retry Parameter – move to Brian Hayes
  • Piggyback signals
  • DR – TBD – Messaging
  • Guide to use CPPA/BPSS/MS together
  • Business Process Collaboration presentation – David B.
  • Service and Action Values
  • Should the Action be:
  • What the Requester is doing (ReceivePurchaseOrder)
  • What the Receiver is doing (ConfirmPurchaseOrder)

<discussion>

  • Recommendation: Action should be RequestingBusinessActivityName (first above)
  • Should we add an optional Role element in MessageHeader?
  • Service is listed in CPP
  • Action is listed in the BPSS document pointed to by an xlink in Service
  • What about two applications which route through a single mailroom?

Adjourn

10/4/01

ebXML-MS meeting

Ian Jones – Chair

Brian Gibb – Vice Chair

David Fischer – Secretary/Editor

Call to order – Ian Jones (phone)

Attendance:

David Fischer

Dale Moberg

Dan Weinreb (new voting member)

Yukinori Saito

Aynur Unal

Arvola Chan

Pete Wenzel

Kazunori Iwasa

David Burdett

Martin Sachs

Brian Gibb

Prasad Yendlori

Brad Lund

Doug Bunting

Phone:

Bob Miller

Colleen Evans

David Smiley

Ian Jones (chair)

Bruce Pedretti

Chris Ferris

Sanjay Cherian

  1. Administration
    Roll Call - Necessary for OASIS membership rules
    Organization
    Agree or redefine Agenda
  2. Colleen Evans can no longer be Editor. David Fischer nominated and confirmed as new Editor. David Fischer will continue as Secretary until a new Secretary can be confirmed (no volunteers).
  1. Discuss and approve Changes made to version 1.0 - Draft 1.02 Especially section 5 which replaced 5 & 6 in version 1.0
  2. Wait on change 120 – Acknowledgment Message must contain Acknowledgment element
  3. Discuss location of section 7.2.3 – location of version discussion
  4. Motion: Create new baseline v1.03 by accepting all changes with above caveats. No objections, Chris abstain.

<break>

  1. Review of decisions and discussion from joint session
  2. Review
  3. Two Motions – Review
  4. David B. discussion on Service/Action
  5. Actions
  6. How BPSS interacts (what to put in Action)
  7. Service can be obtained from CPA (list)
  8. MS should work with CPPA/BPSS team on this issue
  9. Chris suggested new optional Role element under To/From
    Words should be independently defined within messaging spec with non-normative note about how it relates to BPSS spec. No objections, no abstain, motion passed.
  1. Review all outstanding issues in Issues Log
  2. HTTP/S bindings to CPA parameters – after CPPA specifies parameter and mention pass-through parameters in Appendix B (HTTP Binding).
  3. Second signature can invalidate first signature. Defer
  4. Defaults for parameters. Defer
  5. Discuss functionality within / without the MSH
  6. Issues
  7. Overall functionality (figure 1)
  8. Is Forwarding function part of MSH?
  9. Reliable Messaging part of MSH?
  10. Security (non-Repudiation)
  11. End-to-End Retry is broken
  12. Possible Fix by eliminating IM Idempotency
  13. Possible Fix by adding RetryCount
    <discussion>
  14. Motion: Remove IM Duplicate Elimination – David F,
    Second David B. 8 Yes, 2 Abstain, 2 No – Passed.
  15. Motion: Include Forwarding as an MSH function – David F, fail for lack of Second
  16. Motion: Allow deliverySemantics=OnceAndOnlyOnce with AckRequested=None. David F, second Dan. 10 Yes, 1 No, 1 abstain. Pass.
  17. Motion: Value of deliverySemantics, change OnceAndOnlyOnce to DuplicateElimination. Dan, Second Pete. Add table. 1 No, – Tabled. Modify Motion: Replace deliverySemantics attribute with DuplicateElimination with values of True|False.
  18. Motion: Remove ReliableMessagingMethod – Doug – Non-voting member
  19. Motion: Tie Retry to Ack instead of deliverySemantics – Doug – Non-voting member
  20. API Parameters - deferred

Ajourn.

10/5/01 – Ian Jones (phone)

Attendance:

Brian Gibb

David Burdett

David Fischer

Kazunori Iwasa

Arvola Chan

Martin Sach

Daniel Weinreb

Yukinori Saito

Doug Bunting

Aynur Unal

Dale Moberg

Brad Lund

Phone:

Colleen Evans

Ian Jones

Prasad Yendluri

Bob Miller

Chris Ferris

Motion: Split the specification into three parts: 1) baseline 2) end-to-end RM 3) IM RM – David F. Second Brad 9 Yes, 3 No, 3 Abstain – Passed
Motion: We consider RM as one or more separate module(s). Chris, Second Brian.
11 Yes, 2 No, 1 Abstain – Passed

Take up previous day's motions (see above for vote results).

We will be splitting the current spec into modules (what Chris calls SOAP Bubbles). David F will make first pass with Chris & David B by Friday, 12 October.

SOAP Bubbles:

  1. Baseline (MessageHeader, ErrorList, Signature, Manifest, StatusRequest, StatusResponse, Ping/Pong - Bindings)
  2. DeliveryReceipt (DeliveryReceiptRequested, DeliveryReceipt-SyncReply)
  3. SingleHop-EndToEnd (ReliableMessaging- DeliverySemantics)
  4. MessageSequencing
  5. MultiHop (Via, TraceHeaderList, Acknowledgment)
  • SyncReply needs to be in both Via and MessageHeader
  • Via should be renamed NextActorData
  • Arvola to take over Issues Log

<lunch break>

Meetings:

Mondays @ 10:00am PDT weekly, starting Oct 15 for 90 minutes – non-voting

We will have two voting meetings per month (to be announced) and possibly two non-voting meetings per month.

Ian will publish warning list of those who are about to lose voting rights.

F2F November 13-15.

David B will send out message concerning place and time.

Quorum lost

Adjourn