Third Draft Full Agenda for OASIS WS- Reliable Exchange 8/25
TC Teleconference
DIAL-IN NUMBERS:
USA Toll Free Number: 888-730-9142
USA Toll Number: +1-210-234-0018
PASSCODE: 68457
LEADER: MR MARC GOODNER
Queue management Chat will be administered on:
http://soaphub.homeip.net:8080/conf/room/wsrx
Those without access should announce by voice that they want to join the speaker Queue.
Tom Rutt will chair meeting and take minutes for meeting.
2
Review and approval of the agenda
1)
Roll Call
2)
Review and approval of the agenda
3)
Approval of the August 18th meeting minutes
4)
AI Review
5)
Any new issues since last conf-call
6)
Discussion of Issues
8)
Any New Business
8.1)
audio recording of Teleconf for backup
3
Approval of the August 18th meeting minutes
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14148/Minutes%20Teleconf%2008-18-2005.html
xx moved,
yy seconde.
??
Objections, Minutes ??.
4
AI Review
http://www.oasis-open.org/apps/org/workgroup/ws-rx/members/action_items.php
#0002: OASIS Staff should fix typographical error in charter of
missing space between “produces” and “do” the next time the charter is updated.
Owner: James Bryce Clark
Status: Open
Assigned: 2005-07-06
Due: 2005-07-08
#0012: Chair took an action item to get a ruling from Jamie on CVS
repository usage.
Owner: Paul Fremantle
Status: Open
Assigned: 2005-07-17
Due: ---
#0013: Chairs will propose a mechanism to manage the Queue on the
conference calls.
Owner: Sanjay Patil
Status: Open
Assigned: 2005-07-17
Due: ---
#0016: Marc G will form a team to discuss how do deal with
conformance related issues on the specification.
Owner: Marc Goodner
Status: Open
Assigned: 2005-07-29
Due: 2005-09-08
#0018: Fix any problems with Issue URLs
Owner: Marc Goodner
Status: Open
Assigned: 2005-08-04
Due: 2005-08-18
#0024: Provide concrete proposal for issue "InOrder delivery
assurance spanning multiple sequences"
Owner: Andreas Bjarlestam
Status: Open
Assigned: 2005-08-12
Due: 2005-08-25
#0025: Propose a "namespace change policy" for the schemas
produced by the TC
Owner: Christopher Ferris
Status: Open
Assigned: 2005-08-23
Due: ---
5
Potential New issues since last conf-call
· Re: [ws-rx] draft full agenda for 8/25 Teleconf
From Duane Nickull <dnickull@adobe.com> on 25 Aug 2005 14:18:50
-0000
The issue originator, in the above email, states that, in light of
the discussion linked below,
he would like to withdraw
this new issue from consideration.
· RE: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF, DOC versions of working draft
From "Paul Cotton" <pcotton@microsoft.com> on 18 Aug
2005 18:41:19 -0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF,DOC versions of working draft
From Duane Nickull <dnickull@adobe.com> on 18 Aug 2005 16:10:07
-0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF,DOC versions of working draft
From Doug Bunting <Doug.Bunting@Sun.COM> on 18 Aug 2005 15:00:38
-0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF,DOC versions of working draft
From Doug Bunting <Doug.Bunting@Sun.COM> on 18 Aug 2005 14:50:42
-0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF, DOCversions of working draft
From Christopher B Ferris <chrisfer@us.ibm.com> on 18 Aug 2005
12:00:39 -0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF,DOC versions of working draft
From Duane Nickull <dnickull@adobe.com> on 18 Aug 2005 02:27:43
-0000
· Re: [ws-rx] New Issue: Harmonization of Line
Numbers accross PDF,DOC versions of working draft
From Doug Bunting <Doug.Bunting@Sun.COM> on 18 Aug 2005 00:49:53
-0000
· New Issue: Harmonization of Line Numbers accross
PDF,DOC versions of working draft
From Duane Nickull <dnickull@adobe.com> on 17 Aug 2005 22:05:47
-0000
6
Discussion of Issues
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml
6.1 i001
Bilateral sequence negotiation
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml#i001
Proposals:
· Re: [ws-rx] i001 and Proposal
From Christopher B Ferris <chrisfer@us.ibm.com> on 25 Aug 2005
17:55:25 -0000
· i001 and Proposal
From "Lei Jin" <ljin@bea.com> on 25 Aug 2005 17:30:00
-0000
· RE: [ws-rx] Proposal to close i001
From "Lei Jin" <ljin@bea.com> on 24 Aug 2005 03:38:36
-0000
· RE: [ws-rx] Proposal to close i001
From "Marc Goodner" <mgoodner@microsoft.com> on 24 Aug
2005 01:31:57 -0000
· Re: [ws-rx] Proposal to close i001
From Doug Davis <dug@us.ibm.com> on 24 Aug 2005 01:09:36 -0000
· Proposal to close i001
From "Marc Goodner" <mgoodner@microsoft.com> on 23 Aug
2005 23:12:16 -0000
6.2 i004
wsa:messageID uniqueness requirments for retransmission
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml#i004
Proposals:
· RE: [ws-rx] Proposal for i004
From Jacques Durand <JDurand@us.fujitsu.com> on 25 Aug 2005
18:25:41 -0000
· Re: [ws-rx] Proposal for i004
From Anish Karmarkar <Anish.Karmarkar@oracle.com> on 25 Aug 2005
17:45:53 -0000
· RE: [ws-rx] Proposal for i004
From Christopher B Ferris <chrisfer@us.ibm.com> on 25 Aug 2005
12:10:56 -0000
· RE: [ws-rx] Proposal for i004
From "Marc Goodner" <mgoodner@microsoft.com> on 25 Aug
2005 07:42:02 -0000
· Re: [ws-rx] Proposal for i004
From Anish Karmarkar <Anish.Karmarkar@oracle.com> on 25 Aug 2005
07:29:20 -0000
· Proposal for i004
From "Marc Goodner" <mgoodner@microsoft.com> on 23 Aug
2005 23:13:29 -0000
Late posting from Jacques Durand:
I think Anish has a point.
I believe that Resending MUST not alter
wsa:messageId, nor anything in the SOAP envelope.
- wsa:messageId may have some relevance w/r to
MEPs, and whoever on the Sender side will verify that a wsa:RelatedTo is
correlating with a previous wsa:messageId must be sure of the messageId that
has been received, regardless of which retry made it to the RMD. If messageId
may be altered by the RMS or further intermediary, that won't work.
- also, that may affect the validity of
signatures. In 6.3 of SOAP Binding for WS-Addressing, there is clear
requirement that "To avoid breaking signatures,intermediaries MUST NOT
change the XML representation of WS-Addressing headers when relaying those
headers." The RMS may act as intermediary, and resending is just a
relaying technique...
Jacques
6.3 i005
Source resend of nacks messages when ack already received
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml#i005
Proposal:
· RE: [ws-rx] Issue i005
From "Winkler, Steve" <steve.winkler@sap.com> on 25
Aug 2005 18:16:55 -0000
· RE: [ws-rx] Issue i005
From "Winkler, Steve" <steve.winkler@sap.com> on 25
Aug 2005 18:07:45 -0000
· RE: [ws-rx] Issue i005
From "Marc Goodner" <mgoodner@microsoft.com> on 25 Aug
2005 16:58:30 -0000
· Re: [ws-rx] Issue i005
From Anish Karmarkar <Anish.Karmarkar@oracle.com> on 25 Aug 2005
06:43:32 -0000
· Issue i005
From "Winkler, Steve" <steve.winkler@sap.com> on 18
Aug 2005 21:10:51 -0000
Late posting from Steve Winkler:
Hi Marc,
The more compact wording is fine with me with
the exception that you've
changed the SHOULD to a MAY. I personally like the stronger wording,
but understand that it is an optional
performance enhancement. I think
the semantic difference between SHOULD and MAY
should be decided by the
TC.
I also think that we may need to investigate the
ability to advertise
the ability for destinations to trigger
retransmissions with Nacks as a
policy.
I'll look into this a little more and possibly raise a separate
issue to address this.
Cheers,
Steve
6.4 i012
Anonymous acksTo
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml#i012
Proposal:
· Re: [ws-rx] Proposal for i012
From Anish Karmarkar <Anish.Karmarkar@oracle.com> on 25 Aug 2005
18:29:37 -0000
· RE: [ws-rx] Proposal for i012
From Christopher B Ferris <chrisfer@us.ibm.com> on 25 Aug 2005
15:04:50 -0000
· RE: [ws-rx] Proposal for i012
From "Lei Jin" <ljin@bea.com> on 24 Aug 2005 22:00:09 -0000
· Proposal for i012
From "Marc Goodner" <mgoodner@microsoft.com> on 23 Aug
2005 23:15:51 -0000
Late posting by Anish:
Hi Lei,
How does your proposal address the scenario
where:
HTTP is being used, there aren't any
intermediaries, it is a request-response WSDL MEP, and the acks are to be sent
using the HTTP response (backchannel).
In such a case, what should the value of the
[address] property of AcksTo EPR be?
-Anish
--
6.5 i019 Sequence termination on Fault
http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.php/14147/ReliableMessagingIssues.xml#i019
Proposal:
· RE: [ws-rx] i0019 - a formal proposal - take 2
From Jacques Durand <JDurand@us.fujitsu.com> on 25 Aug 2005
18:10:11 -0000
· RE: [ws-rx] i0019 - a formal proposal - take 2
From Doug Davis <dug@us.ibm.com> on 25 Aug 2005 17:54:05 -0000
· RE: [ws-rx] i0019 - a formal proposal - take 2
From Jacques Durand <JDurand@us.fujitsu.com> on 25 Aug 2005
17:16:40 -0000
· i0019 - a formal proposal - take 2
From Doug Davis <dug@us.ibm.com> on 25 Aug 2005 13:55:50 -0000
· Re: [ws-rx] i0019 - a formal proposal
From Doug Davis <dug@us.ibm.com> on 25 Aug 2005 13:55:05 -0000
· RE: [ws-rx] i0019 - a formal proposal
From Doug Davis <dug@us.ibm.com> on 25 Aug 2005 13:47:59 -0000
· Re: [ws-rx] i0019 - a formal proposal
From Christopher B Ferris <chrisfer@us.ibm.com> on 25 Aug 2005
13:42:59 -0000
· Re: [ws-rx] i0019 - a formal proposal
From Doug Davis <dug@us.ibm.com> on 25 Aug 2005 12:37:08 -0000
· RE: [ws-rx] i0019 - a proposal: (more complete)
From Jacques Durand <JDurand@us.fujitsu.com> on 25 Aug 2005
01:37:01 -0000
· Re: [ws-rx] i0019 - a proposal: (more complete)
From Shivajee Samdarshi <shivajee@tibco.com> on 25 Aug 2005
00:52:59 -0000
· RE: [ws-rx] i0019 - a formal proposal
From Jacques Durand <JDurand@us.fujitsu.com> on 25 Aug 2005
00:50:58 -0000
· RE: [ws-rx] i0019 - a proposal: (more complete)
From Doug Davis <dug@us.ibm.com> on 24 Aug 2005 16:30:11 -0000
· RE: [ws-rx] i0019 - a proposal: (more complete)
From Jacques Durand <JDurand@us.fujitsu.com> on 24 Aug 2005
00:19:39 -0000
· RE: [ws-rx] i0019 - a formal proposal
From Doug Davis <dug@us.ibm.com> on 19 Aug 2005 05:50:33 -0000
7
Any New Business
7.1
audio recording of Teleconf for backup purposes